Leaderboard

If you just need to select one of the palette options based on external triggers, you can use the Palette:Active Tool property. In addition to, or in lieu of this, if you also want to zoom in to a specific range, you can use the scale range properties.

For references and more information, see worrydream.com/dbx Presented at Dropbox's DBX conference on July 9, 2013. Bret Victor -- worrydream.com http://vimeo.com/71278954

There is something on NI.com/labs that claims to do the most visited palette, not tried it yet but might be worth a look.

I'm okay with this for the same reason. But I would rather be consistent. Look at the sample I posted with the TDMS functions. That gets me every time that I need to be one pixel off whenever that palette is used. I would rather they were consistent with 5-3-3-5 (or what ever they picked). But I would say that 4-2-2-4 is my standard and very rarely deviate from it. But just as the style guide is a guide, I would say that a 4-2-2-4 setup should not be strictly enforced and if I were king of LabVIEW I wouldn't ban anyone if they used another.

Give this guy a try. It uses autoindexing and the Search 1D Array in order to find the necessary values. Compare Arrays.vi

Those stubs could be the culprit. Your DLLs may in the initialization routine (the code that gets executed automatically when the DLL is loaded into memory) do call some of these stubs expecting certain values or behavior and getting stuck in an endless loop waiting for these to change. Without seeing the DLL source code this is almost impossible to debug though. During the initialization routine of the DLL, even on Windows the system is more or less monopolized for the current process which can result in a very sluggish or even completely locked up system. If you have a chance to look at the source code or talk to the developer of the DLL, make sure they are not doing anything complicated in the DLLMain() function. That is the function called on loading and unloading of the DLL. In fact there are a lot of things you are not allowed to do in there at all, according to MS, one of them is for instance trying to load other DLLs dynamically, as that will have a good chance to lockup your system in a nice deadlock.

Maybe I made a superBoolean class that is a subset of the boolean class that I want to be more specific to. Or maybe I just grabbed the first two functions I knew would demonstrate my frustration and took a screenshot.

If you search ni.com/downloads and narrow by 2013 and NI Developer Suite you should be able to see the downloads for the three Platform DVD if you have SSP on the account you are searching with. The search URL I used is here - http://search.ni.com/nisearch/app/main/p/bot/no/ap/tech/lang/en/pg/1/sn/n1:2013,n8:142,ssnav:pdl/ Hopefully that works for you! - credit to Altenbach for the quick search path

Good luck with it. Xmodem_VISA.zip

Query: Isn’t it the DVR (or SEQ or other similar reference) that is an alternative to the Action Engine’s uninitialized shift register, rather than LVOOP? LVOOP is by-value, and you need something by-reference to stand in place of an action engine. The DVR is by-ref and can be shared among VIs with different con panes, in contrast to the shift register that is constrained to one VI.