Leaderboard

What do you mean by your source tree is well defined? What I suggested doesn't require you to change your source layout. All you'd need to do is change the destination directory in the build spec to a shorter location (ex. C:\temp). That should reduce the destination path lengths. If the output needed to be at a certain location for other build tools, you could write a VI to copy the files from the new location back to the old location.

With this technic, i find that you can add few dynamic event sources and see them like only one source in the event editor. Contrariwise, you need unregistered each sources at the end. Note that : Typecast is used to rename dynamic event sourse (with the event refnum name). Eric

The multicolumn listbox has two different modes - it can either be a scalar and tell you which row the user has selected, or, if you allow the user to select multiple rows - an array of the row indexes that are selected. You switch between these modes by right-clicking on the control and selecting "Selection Mode". If you write to the value property you can select rows programmatically, if you read it you read the indexes of the rows currently selected. The active cell is used to choose which cell you will be editing programmatically. If e.g. you want to change the background color of the cell in row 2, column 4 - you create a property node where you first set the active cell to 2,4 - and then (just expand the property node to have another property underneath the active cell property) - write your new color to the background color property... I suggest you show contect help (Ctrl+H) and hover the mouse over the control and its different properties, the help window will teach you how to use it, much better than we can do here. Check out the examples that come with LV as well, Help->Find Example->Search tab->enter listbox as keyword...or try searching on ni.com.

Ok all you willing furry animals. Attached to this you will find the new architecture. I do not have a quick drop package just yet, but give me a day. But for now I need to validate that this install goes smoothly and still is functional on all of you're PCs The interface is still the nasty 2 floating windows and I'm up for recommendations on how you all think this would best be shown (1 detected speech window, for LVS core or QE, no window, how big, where to put, what options on the window and on and on. It should install to 2 primary locations LVS core goes in <project> (and there is a .lvproj in there as well to see how things are setup) Quick Edit and it's plug-ins go into <resource> (videos and documentation for creating new QE plugins are on the way) and just to make things difficult on you guys for the moment, you need to install RFSE Tools to your user.lib directory (still working on the best method of combining these into 1 install process) So as it stands, uninstall all LVS packages, install this new one, and also extrace RFSE Tools to your user.lib directory. Not all of the old QE commands are fully implemented yet, but there is a VI in the QE directory that shows the list of currently installed commands. More refinement on the way soon!! and please let me know asap of any install or getting started issues lavag_cr_LVSpeak-0.9.1-1.ogp RFSE Tools.zip