Mark Balla

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.

QUOTE(Gavin Burnell @ Oct 18 2007, 05:01 PM) Any chance you could post these or submit them to the CR. I am especially interested in the clean up all wire tool Thanks Mark

Ton, I took you vi and wraped it in a while loop. I ran it and opened and closed vis and could not get the event to fire.What am I missing. QUOTE(Michael_Aivaliotis @ Oct 18 2007, 05:57 PM) I'm up for it also. I would like to see a few more people commit to it before we move foward.QUOTE(tcplomp @ Oct 18 2007, 11:21 PM) So maybe Forum with Subversion/CVS support Ton Now that would be very cool :thumbup:QUOTE(JDave @ Oct 18 2007, 04:19 PM) This tool seems more like an entire toolbar. :thumbup: I was already thinking about toolbars, and Ton's link to his toolbar ideas reminded me that where it would be best to combine efforts is to work on a Development Time toolbar. Plugin tools and all. I mean this would be a perfect starting point of a Coding Challenge. Provide a toolbar framework and challenge people to come up with really neat tools to put in there. There was some brief mention of an OpenG toolbar, but nothing came of that. Anyway, I will make another thread to continue this discussion. I like the tool bar Idea.QUOTE(JDave @ Oct 18 2007, 04:19 PM) To coalesce efforts on the arranging and wiring of controls to the connector pane, I have a thought. It is cumbersome to require controls to be placed in exact bins like my tool requires. It is also cumbersome to put in placeholder decorations like your tool requires. Just to clarify it is not required that you place a decoration on the FP. You only need to use one as a place holder if the fixer doesn't wire the connector pane like you expected. Then all you have to do is double click on the FP and hit a key and you have your place holder I don't see what is cumbersome about that.

My Fixer would handle your points in the following Ways QUOTE(PJM_labview @ Oct 17 2007, 06:46 PM) On the Fixer there is a "Select All Controls" button that will select all controls on the front panel. QUOTE(PJM_labview @ Oct 17 2007, 06:46 PM) 2) Best attempt at connection will do the following (in order of priority): Connect error clusters (if present) to lower left and lower right respectively (regardless of the connector pane pattern). If references are present (like ref in, ref out), connect them on the upper left and upper right respectively. Connect any control/indicator pair having the same name pattern (ex: data in; data out or data in; data dup) at the same level on the connector pane respectively on the left and right side. Connect the remaining controls like they are mimicking the connector pane (see example below). The fixer doesn't differentiate types of controls from each other but this could be added. You would have to add the following modules to get this to work. Identify controls and pairs of controls by type (Error clusters, Refs) and by Label names. Define pair wiring and rules (Top corners, bottom corners, across edges) This get tricky if the pattern is not a constant. Apply these rules instead of doing a wire by position. It get really complicated if you try to do both. Create a way for the user to select rules and pairs. Not trivial but doable QUOTE(PJM_labview @ Oct 17 2007, 06:46 PM) 3) If there are controls/indicators I don't want to connect, I am not sure what the best approach is. Maybe if the controls/indicators are not in the visible window frame, it should not be connected (yes I think I like this). Since the Fixer depends on the user selecting the controls that are to be wired if it is not selected it is not wired. QUOTE(robijn @ Oct 18 2007, 02:46 AM) Wow this looks fantastic ! Thanks, this tool has saved me a lot of time what usually takes 3 minutes I can do in 20 seconds. I think the biggest benefit is that I create more subvis in my code. The fear of making a SubVI and then spending non value added time cleaning it up is greatly reduced. QUOTE(martin@aerodynamics @ Oct 18 2007, 07:07 AM) What I miss is someting like an Abort button to keep the old connetor pane... Can you explain in more detail what you mean? What is it you want to Abort? The "Use Current Wiring" button doesn't change the wiring or the pattern. Then if you use the "Arange & Cleanup" button only the FP will change. An example would be when you make a cluster bigger and it overlaps with other controls on the FP. This method also works when it is eaiser to manually wire instead of moveing controls around. Mark

QUOTE(tcplomp @ Oct 17 2007, 02:18 PM) Can you post a simple example vi with this in it. The detection of the active vi or the one the user last operated on is the big sticking point with stability. Stability got worse when I moved it to 8.5 When you say scripting keys do you mean the 7.1 INI keys or the 8.0 and beyond version?

QUOTE(PJM_labview @ Oct 17 2007, 02:47 PM) Fixed It. It is now version 2

QUOTE(tcplomp @ Oct 17 2007, 01:06 PM) Where is the "VI activation event" located?

QUOTE(PJM_labview @ Oct 15 2007, 04:23 PM) QUOTE(JDave @ Oct 16 2007, 10:22 AM) P.S. I appreciated the inspiration I received from your SubVI Fixer that I mentioned to PJM. Thanks for posting your code for that. QUOTE(robijn @ Oct 17 2007, 04:20 AM) Yes this would be a very handy LV feature or tool. It could also warn if you connect an error in at top-left or a functional global action (enum) at left or an output at left. If it could not match your controls to the 4x2x2x4 connector it could present you with a choice for an other one... or resize the window to have only the controls visible that are to be attached... or ask you politely to clean things up and position controls better... I like polite software. Joris I was going to hold off and wait until I had this perfected and I didn't want to hijack the thread. But with all the discussion on this topic that I have been working on for the last 2 years and JDave mentioning my old fixer, I can't resist showing what I have currently. This is the 8.2 version but I have 7.1 to 8.5 if you want them. The three items go in your LV project folder and FIX SUBVI is selected from the tools menu. The Basics go like this Start the program It will open and then minimize. create a subvi arrange controls on the FP so they correspond to how you want them wired on the connector pane Select all the controls that you wish to wire to the connector pane Press CTRL-Shift-Spacebar the Fixer will popup Select a Pattern Press "Wire By Arrangement" the connector pane will be wired Press "Arrange & Cleanup" The FP will be squared up, Labels will be arranged and changed based on settings, Prompt for save, Icon editor called, and documentation editor will be called. The subvi will also be relinked. (so it is not greyed out in its callers) Fixer will minimize until next time. Here is a brief video of how it works. http://lavag.org/old_files/post-584-1192643456.swf'>Download File:post-584-1192643456.swf One minor issue is it tends to bog down with large projects 600 or more vis in memory. This has to do with finding the active vi. Any feedback would be appreciated. There is a lot more to it but I will save that for later. this will eventually go in the CR once its a little more polished. Mark

Sorry to be the bringer of bad news but there is a problem with your code. As the team member responsible for this CR submission I would normally do this by pm but since you started the discussion here I need to warn every one there is a potential crash and I don't want anyone to lose any code because of it. If you call up the auto connector pane vi and purposely or accidentally try to move one of the box decorations LabVIEW will crash. See video. Download File:post-584-1192513096.swf I do have a few additional suggestions aside from fixing the crash. How about redrawing the decoration boxes when the scale or pattern is changed. Also it would be nice if we could move the boxes to the controls and have them auto wire.

QUOTE(Michael_Aivaliotis @ Oct 5 2007, 04:37 PM) How did you get LabVIEW to do this and does it work as expected?

QUOTE(jaegen @ Aug 21 2007, 01:05 PM) Thanks jaegen, I've been waiting for these so I can load 8.5 on my current test machine. It was great meeting you at NI week.

QUOTE(h1voltage @ Jun 22 2007, 12:43 PM) Justin goeres. Just recently added his LVOOP ImageMagick Interface to the CR. DESCRIPTION: This library provides an LVOOP-based interface to the powerful cross-platform ImageMagick image handling utility suite. It supports all of the ImageMagick utilities and almost every command-line operator (over 200 of them) with support for custom user-specfied operators for the edge cases. Several examples are included that demonstrate basic text & image creation, composition, and conversion in and out of LabVIEW (including VI icon creation).

Now thats the best Omis looking, goat calling, fife playing, hill billy whisteling rock and roll I ever heard.

QUOTE(denisetucker @ May 14 2007, 10:06 AM) If you don't need a permanent solution them I would recommend using a custom probe that tracks time. We talk about them here here is a in BD inline timmer that can be use instead of the sequence option. http://forums.lavag.org/index.php?act=attach&type=post&id=5863 http://forums.lavag.org/index.php?act=attach&type=post&id=5864

QUOTE(jbrohan @ May 13 2007, 10:51 AM) I would recommend that you get it working in MAX first before you start using LabVIEW. I did a project about 6 months ago where I used the Latest FP drivers with LV7.0 using a FP 1601 over Ethernet.

QUOTE(Aitor Solar @ May 13 2007, 10:27 AM) Adam Rofer mentions it here Here is the vi I use. The neat thing about using this method is that it works the same as if you double clicked on icon of the vi. So my editor or any other custom editor work using this vi. http://forums.lavag.org/index.php?act=attach&type=post&id=5855 http://forums.lavag.org/index.php?act=attach&type=post&id=5854

For those that are using my icon editor or other home made editor using the lv_icon.vi option There is a LabVIEW LOCKUP problem when trying to edit a sub pallet in the pallet editor. If you open the pallet editor. http://forums.lavag.org/index.php?act=attach&type=post&id=5754 and then try to edit a sub pallet menu icon http://forums.lavag.org/index.php?act=attach&type=post&id=5755 Nothing happens. The icon editor is running in the background but it is somehow being suppressed by the pallet editor. If you are using my editor or you have set the lv_icon.vi to a non modal state then there is a work around. for Windows press (CTRL-Space-x) and the editor should maximize and work normally. If the icon editor is set to a modal or floating state then you are out of luck. I was unable to get LabVIEW back without the 3 finger salute (CTRL-ALT-DELETE) By default the lv_icon.vit and Sample_lv_icon.vi are set to Dialog which is modal. http://forums.lavag.org/index.php?act=attach&type=post&id=5757 So if you are going to create your own icon editor I would recommend setting the Windows appearance to default. http://forums.lavag.org/index.php?act=attach&type=post&id=5758 I have reported this issue to NI. My thanks to tcplomp for finding this bug and the work around.

QUOTE(Stevio @ May 4 2007, 11:54 AM) I have a vi that does this I posted it here I'm not sure what version it is in so here is the 7.1 version http://forums.lavag.org/index.php?act=attach&type=post&id=5737

QUOTE(Omar Mussa @ Apr 24 2007, 10:38 AM) Hey Omar, Great thread, Can you elaborate on methods or patters you found useful? I’m curious if you were able to keep your OOP as a by value paradigm or were you forced to wrap them in a queue in order to protect and pass the data between loops. One of the biggest drawbacks that I find with OOP is the difficulty of testing public Vis. Because the object data is not visible or settable it becomes difficult to inject data and see the results. Were you able to come up with an alternative way to test Publics. Thanks Mark

QUOTE(i2dx @ Apr 23 2007, 03:03 PM) Ok so what is the answer?

QUOTE(AdamRofer @ Apr 12 2007, 12:51 PM) I was hopping it was one of those vis buried deep in the vi llb somewhere. So far I haven't had any luck locating it.

Does anyone have a good method to call the Vi properties dialog page programmatically. I’m working on an automated documentation vi and would like use the built in LV documentation editor and not have to create my own. http://forums.lavag.org/index.php?act=attach&type=post&id=5478

QUOTE(martin@aerodynamics @ Jan 26 2007, 05:08 AM) Martin Can you post the vi or control you used to generate this picture. I am also working on updating the color picker on my icon editor.

QUOTE(vaimaro @ Mar 23 2007, 02:49 AM) Here is a method I use to solve this type of problem. On an Value change event it sets a flage and starts a delay timmer. It waits until the slider control has not change for a specified amount of time. I have tried to use the mouse up event but found it would not be detected if the mouse was moved off of the front Panel. hope this helps. http://forums.lavag.org/index.php?act=attach&type=post&id=5277''>http://forums.lavag.org/index.php?act=attach&type=post&id=5277'>http://forums.lavag.org/index.php?act=attach&type=post&id=5277

QUOTE(polyplay @ Mar 15 2007, 05:13 PM) Writing data to the terminal does not fire the Value change event. The easiest way to fire this event is to write data to the Value(Signaling) property of the string indicator. http://forums.lavag.org/index.php?act=attach&type=post&id=5206 http://forums.lavag.org/index.php?act=attach&type=post&id=5208