LAVA 1.0 Content

Spying on the serial connection can be done with 'portmon' however using a device when you don't know exactly the protocol is asking for issues. What kind of device is this? Ton

Spying on the serial connection can be done with 'portmon' however using a device when you don't know exactly the protocol is asking for issues. What kind of device is this? Ton

To expose the private items use the following settings: labview.SuperSecretPrivateSpecialStuff: Truelabview.SuperPrivateScriptingFeatureVisible: True I think the first will turn on private items etc. Ton

To expose the private items use the following settings: labview.SuperSecretPrivateSpecialStuff: Truelabview.SuperPrivateScriptingFeatureVisible: True I think the first will turn on private items etc. Ton

I could not get this to work with 8.6 Ton

I could not get this to work with 8.6 Ton

The Scrolling Led example on NI.com has a way to do this. I don't remember off hand how it worked but I think the init ability handles this. Ton

The Scrolling Led example on NI.com has a way to do this. I don't remember off hand how it worked but I think the init ability handles this. Ton

I like private events (and methods, properties) however it is not clear to see that they are private (like blue invoke nodes). Most of the time it is documented in the context help of that specific event, but at a glance it is hard to see. Does anyone know a solution? Ton

I like private events (and methods, properties) however it is not clear to see that they are private (like blue invoke nodes). Most of the time it is documented in the context help of that specific event, but at a glance it is hard to see. Does anyone know a solution? Ton

What about a 'Mouse down?' event and on a left click make it a right click? (left is button 1, right is button 2) Ton

What about a 'Mouse down?' event and on a left click make it a right click? (left is button 1, right is button 2) Ton

QUOTE (jed @ Jan 16 2009, 08:35 PM) QUOTE (Jim Kring @ Jan 16 2009, 09:35 PM) You can use the ActiveProject property of the MenuLaunchApp. If this is a null ref, then you know it wasn't launched from a project. These both methods are used in a chain in the OpenG builder. First th check is done on the name, then the active project is opened. Good luck, Ton

QUOTE (jed @ Jan 16 2009, 08:35 PM) QUOTE (Jim Kring @ Jan 16 2009, 09:35 PM) You can use the ActiveProject property of the MenuLaunchApp. If this is a null ref, then you know it wasn't launched from a project. These both methods are used in a chain in the OpenG builder. First th check is done on the name, then the active project is opened. Good luck, Ton

QUOTE (Dave Graybeal @ Jan 16 2009, 08:04 AM) I believe the only time you have to initialize a variable is if it isn't defined by an input or output of the formula node.

QUOTE (crelf @ Jan 16 2009, 03:43 PM) But durring the exam.... Keep in mind that this is the exam that will prove you know how to code in LV and they actually expect you to demonstrate you know how to develop in LV, so... make sure you document what you are planning to write so that in the event you do not finish and the code does not run, the grader wil still be able to access your LV skills based on what you said you wanted to do. I hve never been dinged for spelling or grammer on any of those exams so just type as fast as you can! Ben

QUOTE (crelf @ Jan 16 2009, 03:43 PM) But durring the exam.... Keep in mind that this is the exam that will prove you know how to code in LV and they actually expect you to demonstrate you know how to develop in LV, so... make sure you document what you are planning to write so that in the event you do not finish and the code does not run, the grader wil still be able to access your LV skills based on what you said you wanted to do. I hve never been dinged for spelling or grammer on any of those exams so just type as fast as you can! Ben

QUOTE (Marcus Törndahl @ Jan 16 2009, 09:21 AM) I suspect not. if it does not work with the non-in-memory VIs, just make sure you have the "Tree.vi" for app open when you make the change. Ben

QUOTE (Marcus Törndahl @ Jan 16 2009, 09:21 AM) I suspect not. if it does not work with the non-in-memory VIs, just make sure you have the "Tree.vi" for app open when you make the change. Ben

Good point, and while we are at it: Easily name a pane Easily name a splitter Easily get the owning pane of a control Ton

Good point, and while we are at it: Easily name a pane Easily name a splitter Easily get the owning pane of a control Ton

QUOTE (jpdrolet @ Jan 15 2009, 12:24 PM) The Recursive File List handles that situation by check the "shortcut" output. http://lavag.org/old_files/monthly_01_2009/post-29-1232041034.png' target="_blank"> Ben

QUOTE (jpdrolet @ Jan 15 2009, 12:24 PM) The Recursive File List handles that situation by check the "shortcut" output. http://lavag.org/old_files/monthly_01_2009/post-29-1232041034.png' target="_blank"> Ben

I agree with Neville that these are interesting questions. My experience with using VI served VI on RT systems was limited to invoking methods of an Action Engine running on the RT machine. Aside from an issue with a queues created by the AE being killed when the comm failed to the VI server (RT killed queue when remote connection was closed) they gave quick responses ( no benchmarks to share). Another issue I had to implement was due to too much data coming in too fast (after comm restored the history was transfered as a read from the AE) and the central PC was experiencing an update flood. This was fixed by changing the AE to only transfer a limited number of updates rather than everything at once. Back in the day of LV6 RT... Using VI server to touch an AE "was the way to go". Ben

I agree with Neville that these are interesting questions. My experience with using VI served VI on RT systems was limited to invoking methods of an Action Engine running on the RT machine. Aside from an issue with a queues created by the AE being killed when the comm failed to the VI server (RT killed queue when remote connection was closed) they gave quick responses ( no benchmarks to share). Another issue I had to implement was due to too much data coming in too fast (after comm restored the history was transfered as a read from the AE) and the central PC was experiencing an update flood. This was fixed by changing the AE to only transfer a limited number of updates rather than everything at once. Back in the day of LV6 RT... Using VI server to touch an AE "was the way to go". Ben