Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 07/20/2016 in all areas

  1. Not that I'm aware of. This is a trick I use it in the SQLite API for LabVIEW installer. When you read the licence it won't let you continue until you have scrolled all the way down. I get the scroll position of the end of the text first without updating the display and then check to see if it is reached.
    2 points
  2. Greetings Friends of LAVA, colleagues, cohorts, and Wireworkers Extraordinaire -- it's LAVA BBQ time! Date: Tuesday, August 02, 2016 Time: 7:30-10:00pm (after the NIWeek Block Diagram Party) Location: Scholz Garten, 1607 San Jacinto Blvd, Austin, TX 78701 (1 mile from Convention Center) Cost: $30 Early Bird (until July 15th) $35 Regular Admission (until July 31st) $40 At the door (Aug 1st - 2nd) Meal Options: Standard meal is your choice of brisket, ribs, or chicken, with sides of beans, cole slaw, and potato salad. A vegetarian option is available when purchasing tickets. Cash bar, beer and wine. Who: Everyone is welcome, including spouses traveling with you. Even if it's your first time, expect to recognize many faces/names from the forums and NI R&D. What to wear: It's an outdoor venue in Austin during August. So dress for the weather and comfort. Door Prizes: Towards the end of the event, we will have a raffle to give away prizes. All attendees are eligible and will receive a raffle ticket upon entry. or get tickets on The LAVA BBQ 2016 Event Page Do you want to sponsor a door prize? - Continue Reading: If you or your company want to sponsor a LAVA 2015 BBQ door prize, please post a reply below. You can also include a small blurb about your company and a link to your website in the post below. By donating a prize you and your company will receive a small announcement of your choosing, during the event. We will ask you to write the announcement on a post-it note and will attach it to the prize to be read before awarding it. We love the door prizes, but we love time for socializing too. Here are some guidelines to keep our event balanced and streamlined. We would prefer a single item donation. If donating more than one item, then multiple identical items is strongly preferred. So we don't spend our time on a flood of refrigerator magnets, please donate something valued at $25 or more. If donating non-tangible items or something that is not physically with you, then please bring a card with your contact info and instructions on how to collect the prize. This will be given to the winner. All prizes are acceptable except those listed below (examples from last year): Not recommended: Apparel (hats, t-shirts, underwear etc) Branded trade show booth type giveaways (mouse pads, pens, keychains etc) Software licenses (Toolkits, add-ons, LabVIEW) Jokes or something meant as a gag and not a real prize. Hope to see you there! Chime in once you buy tickets to let everyone know you're coming.
    1 point
  3. Hello all. So NI is trying something new this year for NI Week. Year after year NI gets feedback from those that attend NI Week and one of the most common things people ask for is more technical sessions. We don't care too much for a marketing presentation telling us how your company is awesome, and we don't really need NI to tell us about some new hardware we'll never use. But coming back from NI Week with new technologies that excite me and make my job get done better, makes my boss want to send me next year. So as a way for NI Week to get more technical, NI has dedicated a room at NI Week to advanced users to give presentations on advanced topics, allowing them to make up their own Advanced Users. This track will be in addition to the other tracks NI usually has for various industries, like aerospace, and automotive. These presentations will be given by advanced developers who are LabVIEW Champions and will focus less on marketing and more on being technical, sorta similar to what you'll see at a CLD/CLA Summit. So checkout Room 15 Tuesday and Wednesday for the advanced awesomeness, you should expect lots of hearty frank group discussions. It seems not all of the topics are posted by NI yet, but here are just some of them. And yes for a bit of self promotion I am giving an updated presentation on XNodes that I gave earlier this year.
    1 point
  4. "Resolved to customers satisfaction" it is then. FWIW. Escalation can be very quick or many days. It's only the time-zone differences that make the delay if (and this is a big if) the application engineer knows who to contact and can articulate your concern. This is why examples are so important. Once you have found a well connected application engineer that you can ask for by name to get past the front door bouncers - 24 hours max for a useful response.. As en ex European. - a telephone call with a follow up email (with example and bulleted list of questions) at 4pm and you will usually have the result sitting in your inbox in the morning . That named engineer is now your dive buddy (as much as they might resist ) in the murky waters of NI support procedure. Hold on to them as if your life depended on them because your sanity does
    1 point
  5. You have a lot of issues I've never seen, but I've experienced these at least. (1) I read somewhere that the VIs don't necessarily have code but do have metadata (for example names of VIs, connpanes, types)...not exactly a concrete explanation but it may be the reason behind the saves. (2) Is this outside of any libraries? Lvlibs and classes seem to have different rules, but I just tried loading a project in 2014 (not really using 2015 for much right now) and can verify that at least there, not all standalone VIs are loaded when the project loads. Could it be related to having SCC on? I never use the built in one because I found it to be terrible. (3) And preferably one that is accurate, too (re: #2) (4) Honestly I think you could just put "All of appbuilder" as a bullet point (5) I've seen this on occasion, but I wouldn't say its frequent. (6) To build fortitude. And of course, don't forget to also save the class and make sure labview doesn't crash in between, or else you get the friendly dialog about VIs not being part of the library they claim to be part of. (7) Thats a neat trick, although I would add, why does building the file view (the first time) take forever?
    1 point
  6. I'd expect at least a "clumping optimisations" hand-wave from paid support rather than a "dunno, ask someone else". The gesture controlled quad copter making it too dangerous to walk upstairs to ask R&D?
    1 point
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.