Mark Balla

QUOTE(Jonas @ Feb 21 2008, 02:21 PM) If you look down a few topics from this one you will see an invitation to beta test 8.6 It is very likely this will be the next release.

Of course we can! The question is "SHOULD WE"

The Open G vis "Get cluster elements by name" and "Set cluster elements by name" come in very handy when you are trying to programatically bundle and unbundle. You can also extract data types and get the cluster items as an array of variants by using the vis in the LabVIEW 8.5\vi.lib\Utility\VariantDataType folder

QUOTE(Jake of All Trades @ Jan 23 2008, 10:32 AM) You can replace the red triangle with a black arrow form the decorations pallet and it works as expected. Its not exactly what you are looking for but I think is looks better. http://lavag.org/old_files/monthly_01_2008/post-584-1201201622.png' target="_blank"> I did a xcontrol presentation for a usergroup back in December. the slides and examples can be found at www.nilvug.com

QUOTE(dgholstein @ Jan 21 2008, 08:57 PM) Hi Dan Welcome can you post the code or a link to the sql_LV.

QUOTE(Louis Manfredi @ Jan 16 2008, 03:32 PM) If you post it I will try and open it in 8.2 and convert it to 8.5

QUOTE(TobyD @ Jan 16 2008, 10:44 AM) Can you post the link?

The concept is something to think about but it is much too limited in a 2D space. If this idea was moved to a 3D world then it would be much more usable. I think the wii demo is what we are going to see more of in the future. Better interface through hardware enhanced by software.

QUOTE(TobyD @ Jan 14 2008, 06:26 PM) I went through my archives and dug out the DataAct editor and got the same result you did. brian175 was the creator of this software you might want to drop him a PM asking for help.

QUOTE(PJM_labview @ Oct 17 2007, 05:46 PM) OK PJM this one is for you. I've implemented a pairs matching and wiring program. Using Aristos' program I was able to create a program to categorize controls and indicators so they could be compared to each other. If two items match and one is a control and the other an indicator they are paired up and placed in a pairs array. All items that do not match up are placed in a controls or indicator array. Starting with the pairs array the program gets the highest item in a priority and tries to find it the array. When the array item is found it is wired to the connector pain according to a wiring list. When all the pairs are wired, the program moves on to the single controls array and then to the single indicators. So for most FP arrangements it's down to three button presses. "Select All", "By Pairs" , "Arrange and Cleanup" You will only have to move the controls or indicators that are in the wrong place. After starting the Fixer and creating a subvi do the following. 1: Select a control or indicator on the FP of the vi to fix 2: Bring up the SubVI fixer. Ctrl-Shift-Space (default) 3: Press the "Select All Controls" button to select all controls on the FP 4: Press the "By Pairs" button to automatically wire the FP items. 5: If the connection to the connector pain are not to your liking move the out or place ones to the correct location and press the "By Arangement" button 6: When all connection are good press the "Arrange & Cleanup" button to finish. Here are a couple of videos to demonstrate. Download File:post-584-1199684719.swf I would like to have people test this and see if it is stable and works for most programmers. The priority list may not be what every one likes. So if you open the _Subvis for FIXER\Pairs\Pairs_Catagory Priority Array.vi you will see instructions on how to change the wiring priority. Other added features Have FP center in monitor 1 on startup Added Max FP size setting in the Settings panel. Last folder selected to save in is remembered and is used next time. (Needs Testing) Here is the newest version. Just as a reminder to place the 3 items in your National Instruments\LabVIEW 8.5\project\ folder. Open LabVIEW and call the "FIX SUBVI" item from the tools menu. Press Ctrl-Shift-SpaceBar to have the fixer popup. Download File:post-584-1199685943.zip Download File:post-584-1199686110.zip QUOTE(Aristos Queue @ Oct 23 2007, 10:36 PM) LabVIEW classes should generally get the same treatment. When there are multiple classes on the same conpane, each with an "in" and an "out" terminal, the preference should be if the VI is owned by a given class then that class gets preferential treatment for being in the upper left and upper right. Otherwise, mimic the panel layout. QUOTE(Michael_Aivaliotis @ Oct 30 2007, 10:35 PM) So perhaps this cleanup tool in progress can run automatically after a "create sub-VI" action or something? Like a "disconnect all and reconnect correctly" function. I'll work on these next. Thanks again everyone for your Ideas, Code and Inspiration. Please keep your Comments, Suggestions, and Critiques coming. Mark.

I posted and cross posted a problem I'm seeing with the Get Control Data Type.vi http://forums.ni.com/ni/board/message?boar...7&jump=true

My version of the while loop stop is posted here as well as others

I just ran into this problem today. Not sure if this is the same issue you are seeing. I had two vis with the same name "Build FLD Record". One owned by a class and one that wasn't If I were to remove the owned one from the class lvlib I would have two vis with identical names. This would cause a conflict so it looks like LabVIEW won't let you remove a vi from a class if it will cause a conflict in the project. When I closed the project and opened the class by itself the file could be removed from the class. When I reopened the project as expected a conflict showed up. Hope this helps

QUOTE(Aristos Queue @ Nov 5 2007, 02:58 PM) Thanks for finding this for me. I've been playing with the "GetLVClassInfo.vi" and there is an indicator I need clarified. What is the "Fully Qualified LV Class Name" represent and why is it an array. eveything I've tried so far will only output one item in the array which is the class name. In what circumstances will I see more than on item?

I've made enough improvements to make it worth posting the latest version 5. Here is the list of improvements from version 4 Change FP Layout Fixed the close if lonely problem. The fixer should now close if it is the only vi running. Improved the Active VI detection. In ver 4 you had to click on a vi while the fixer FP was opened for it to find it. Now its keeps track in the background. Added a recommended button. Since you can now set LabVIEW to make all input required by default this function is needed. The hot keys to popup the Main FP can now be set in the settings window. Default is still Ctrl-Shift-Spacebar. LV 8.5 LV8.2 Thanks again for all the feedback and ideas.

QUOTE(Michael_Aivaliotis @ Oct 30 2007, 10:35 PM) I totally agree and this is one the top reasons why I started this tool. QUOTE(Michael_Aivaliotis @ Oct 30 2007, 10:35 PM) If you have an error in and an error out I would like it to position the error in and error out in the right place I'm currently working on a function that searches selected FP items for matching pairs and applies wiring rules to them. QUOTE(Michael_Aivaliotis @ Oct 30 2007, 10:35 PM) AND name the error in to "Error IN" NOT something stupid like error out. In the settings of the fixer you can apply prefixes and suffixes to controls or indicators. It's an all or nothing setting though so if you set indicators to use a prefix of "Out" then all indicators will be set that way. QUOTE(Michael_Aivaliotis @ Oct 30 2007, 10:35 PM) So perhaps this cleanup tool in progress can run automatically after a "create sub-VI" action or something? Like a "disconnect all and reconnect correctly" function. I like it. Any Idea how to detect when the "create sub-VI" function has been called?

QUOTE(Aristos Queue @ Oct 29 2007, 04:24 AM) Here is ultimatly What I would like to see. Download File:post-584-1193669937.vi the "Qualified Name Out" indicator is the one that I Need the most. Thanks for your help.

QUOTE(Aristos Queue @ Oct 28 2007, 09:48 AM) The "Is This Control Of This LabVIEW Class" would be useful If I had a way to take a reference to a LabVIEW Object control and extract the LVClass Refnum out of it Any recommendations on how best to do this? F.Y.I. In 8.5 I have tried several ways to create a LabVIEWClassControl Ref Control and every method seems to crash LabVIEW. I also tried them in 8.2 and they work fine. Create control, Create SubVI, Select Class I briefly checked the LAVA bug list and 8.5 known issues list and didn't see this problem. I will file a bug report this week when I get time. QUOTE(Aristos Queue @ Oct 28 2007, 09:48 AM) "Close If Lonely" checks for VIs that are not "Close If Lonely". If the only VIs that are open are all marked as Close If Lonely, then all those VIs will close. It requires a sociable VI to keep the lonely VIs company.I can't check the code right at the moment, but I recall that an open project window will serve to keep a lonely VI company, too. Thanks for the clarification, I added the "Close if lonely" node in the Caller and they both shut down when no other "sociable" vis are present.

QUOTE(Aristos Queue @ Oct 23 2007, 11:36 PM) If I have a reference to a class control what is the best method to determine what it's class name is? The property and invoke nodes don't seem to have any way to extract class information.

QUOTE(silmaril @ Oct 25 2007, 02:25 AM) Ok I fixed this problem by sequencing the FP State Property before the OpenG vi. QUOTE(silmaril @ Oct 25 2007, 02:25 AM) Also there is still a breakpoint in the engine, that gets hit everytime I use the "Set as Required" button. fixed for the next rev QUOTE(silmaril @ Oct 25 2007, 02:25 AM) Looking at your code, one question comes to my mind: What exactly does the method "FP.Set Close If Lonely" do? This is a scripting node that will setup the vi to close if it is the only vi opened. I now relalize that it is not doing what was indended. Because the FIX SUBVI.vi and the _FIXER Subvis Main.vi are setup to both be opened and running I always have at least two vis opened. I will add this to the fixit list. Thanks a lot for the feedback and keep it comming. LAVA ROCKS Mark

QUOTE(silmaril @ Oct 24 2007, 05:01 AM) Thankyou for the feedback and trying out the tool. I hope it saves you some time. QUOTE(silmaril @ Oct 24 2007, 05:01 AM) The tool works very nice, as long as the name of the main VI starts with an underscore. I copied it into my projects directory and removed that underscore to get a Tools menu item for this. Now I get a funny problem: every time the tool changes the window focus to itself, it seems to detect the VI Activation event and sets "Target VI" to itself, which makes it impossible to use the tool anymore. Well it looks like I continue to be one of the most file upload challenged members in LAVA. I see I have yet again forgot to include a file. The file that is missing is called “FIX SUBVI.vi” and is the one that is you are suppose to see in the tools menu. It's main function is to remove the toolbars and scroll bars from the Main vi as well as call it. I have seen the problem where the main keeps bringing focus to itself. I put a quick and dirty fix in the “Active VI_Get Active VI From Global.vi”. By renaming the Main you disabled my fix and the problem returned. Here is my new and improved fix. Here is Version 4 it has the fixes above plus some icon cleanup.

The original topic on creating a tool to automatically wire a FP to the Connector pane was started here. My thanks to JDave for starting it. I started a new topic to track the progress of the SubVI Fixer. Here is Version 3 using the VI Activation Event that PJM showed me. Version 3 works the same as Version 2 but is much more stable. the Video is located Here QUOTE(PJM_labview @ Oct 17 2007, 06:46 PM) The next thing I want to do with this tools is implement PJM's suggentions. In the Settings_Change.vi I added a array of Clusters. The Clusters have two items a match pair type and an array of wirring priorities. My current plan this The next thing I need to figure out is how do I determine what controls match from their references. I could do it by label name only and I probably will to start with but I would like to do it by type. Does anyone have an Idea how to uniquely identify a FP item via reference. The goal is to differentiate (cluster of different components from each other, References of different types and objects of different classes).

QUOTE(PJM_labview @ Oct 19 2007, 11:27 AM) Thanks that works

QUOTE(PJM_labview @ Oct 19 2007, 11:27 AM) Thanks that works

QUOTE(tcplomp @ Oct 19 2007, 12:43 AM) Thats interesting it still doesn't work for me. I don't have the scripting keys enabled and I see my property node it a different color than yours. So is it true that I have to have the keys enabled to run the vi. That wasn't true for the 7.1 stuff. If this is the case I will not be able to use this function. I bring this tool with me when I work on clients machines and I'm not going to put the scripting on it.