Leaderboard

You need to use Dynamic Event registration to get the event. Use the following code register the event: And inside the event More info on dynamic events. Ton

What holds me back on the NI site is the NI.com site agreement Another thing that is holding me back (and is holding the community back) not just on NI.com, but on LAVA as well, is the fact that we lack a accepted distribution system. I am jealous of python where I can install a debian package and then use 'easy_install' to get a pacakge just by name. The LabVIEW tools network is a step forward, but I still cannot run a command 'install AQ-JSON-API' and the API will be installed. And we need to open up the source if we want to have a strong community. For instance ShaunR added support for escape quotes in the product. Now I have to go to his code, detect the changes (which is hard since LabVIEW is binary and he backsaved to 2009), merge these into my Mercurial repo(Done). My opinion: We (LAVA, OpenG, NI et al) need to agree on a license (do we mind 'Public-Domain'?) What is exactly the issue for NI that disallows it on BSD. The only limitation I see is the 'Attribution'. But attribution could be limited to a line in the on-line help of that feature. We need to start with source-code repositories. (heck there is allready a Lavacr project at google code in Subversion), and then create products/downloads We need a distribution system that is lightweighted and reliable Ton

If you are going to ignore my point, it's hard to have a discussion. The two APIs should line up. This way they won't.

Compiled VIs? "Compiled" does not apply to VIs in the conventional sense; everytime you make a change, the IDE is compiling. I think you mean in a built executable - the reason these don't show up is because they're in the Run-Time Engine, and a separate application instance to boot, which is separate from the development IDE.