Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Darren

  1. I really dislike the palettes too...especially since everything was rearranged in 8.0. If only someone could do something about them! I mean, if somebody with my distaste for the palettes happened to work in LabVIEW R&D, then he could add a feature in the next LabVIEW release that allowed me to write VIs faster than ever before, without having to ever bring up the palettes again. Man, that would be so great! Oh well, maybe someday. Someday... -D
  2. QUOTE (Aristos Queue @ Apr 29 2008, 01:30 PM) How are they faster than Ctrl-X/C/V? The X, C, and V keys are all very close to the left Ctrl key and typable with the left hand only. -D
  3. Check out the attached VI. It overrides those not-so-pretty tree symbols with better looking ones (specifically, the icons used in the Project Window). After you run this VI on your tree, whenever you add new items programmatically, if you set their symbol index to be one of the old-skool symbols, you'll get the nicer looking one instead. This should work in LabVIEW 8.0 and later. -D P.S. - To turn off the hierarchy lines on the tree, right-click the tree and uncheck Visible Items > Hierarchy Lines.
  4. QUOTE (Aristos Queue @ Apr 4 2008, 02:34 PM) When I wrote a LV Class-based app a while back, I tried to make the wire colors match the default banner colors. I used a darker, mustardy yellow with the yellow-bannered classes to make the wires look nicer on the diagram. I think it would be good to try to match up the wire colors to the banner colors by default. I would also like it if we cycled through more than 6 colors. -D
  5. Now that 8.5.1 is out, you should add it to the LV Version Used rings on our profile page. -D
  6. QUOTE (Val Brown @ Apr 4 2008, 01:46 PM) I don't think any discussion of beta software (including the topic of having been a beta tester) is allowed outside the private NI channels. -D
  7. QUOTE (orko @ Apr 2 2008, 08:31 AM) I actually used the http://en.wikipedia.org/wiki/Etch_A_Sketch#Etch_A_Sketch_Animator' rel='nofollow' target="_blank">Etch-A-Sketch Animator when I was a kid, which allowed you to erase... -D
  8. QUOTE (Phillip Brooks @ Apr 1 2008, 07:06 AM) This functionality is already supported in the Wire Bends test of the VI Analyzer. http://lavag.org/old_files/monthly_04_2008/post-4441-1207072727.png' target="_blank"> Hope this helps, -D
  9. QUOTE (TiT @ Mar 20 2008, 02:02 AM) Good point...I can't believe I never wrote a nugget about this. That situation has been remedied...see http://forums.ni.com/ni/board/message?board.id=170&thread.id=310317' target="_blank">here. -D
  10. QUOTE (PJM_labview @ Mar 19 2008, 07:49 PM) Sorry, I should have been more clear. You know how if you right-click in the diagram to bring up a temporary palette, when you pick something on the palette, it puts the object on your cursor to drop? Well, if you ctrl-right click instead and do the same thing, instead of dropping the object, it opens the panel of the VI (if the object you picked off the palette is a subVI). All I was saying was that it's an alternative to right-clicking on something in the palettes and choosing "Open VI", as was suggested earlier. -D
  11. QUOTE (Aristos Queue @ Mar 19 2008, 04:35 PM) I agree with Stephen...the established method for creating new VIs from a template is the New... dialog. How many times in a LabVIEW editing session are you guys wanting to create a new VI based on a template that resides in the palettes? Also, instead of the right-click > Open VI method, you can also have the diagram of a VI on the palettes open if you shift-right click to bring up the temporary palette (instead of just regular right-click). -D
  12. QUOTE (Aristos Queue @ Mar 19 2008, 10:36 AM) Yeah, of the 19 games for which I legitimately acquired the high score, 17 of them were removed. I'm not feeling incredibly motivated to go reclaim my top spot in the arcade, for fear of another unexpected reset at some point in the future. On the bright side, I do like the fact that there are more word-based games now. -D
  13. I'm normally a pretty gracious loser, but I just noticed that all my high scores in the LAVA Arcade (and there were 19 of them) were miraculously beaten within the past day or two by a new user named "SweetVictory". I'm suspicious as to the validity of these victories, however, as some of these scores were attained in 45 seconds on games that have an average play time of about 20 minutes (see the high scores on Plumber 2 as an example). The only valid excuse I would accept for this incident is if we discover that SweetVictory hacked the LAVA arcade using LabVIEW. -D
  14. Uncheck the Tools > Options > Block Diagram > Place front panel terminals as icons option. -D
  15. QUOTE(rolfk @ Feb 21 2008, 02:28 PM) I probably shouldn't have used a double-negative in my response. I was trying to say that the format will almost certainly change significantly between two x.y versions (i.e. 8.2 to 8.5). It almost always changes between two x.y.z versions too (i.e. 8.2.0 to 8.2.1), but I'm pretty sure there has been at least one instance in the past where an x.y.z upgrade did not result in a version bump in the save format, which means the save format *could* be the same between those versions. But regardless, I still advocate using the Get VI Version method over
  16. I wouldn't bet on the binary source not changing significantly between two x.y versions of LabVIEW. Perhaps two x.y.z versions... But if I were in your shoes, I would write a utility that uses the Get VI Version method (of the Application class) and the Save.For Previous method (of the VI class) to programmatically accomplish the task. -D
  17. QUOTE(Thang Nguyen @ Jan 30 2008, 10:04 AM) As I mentioned in my previous post, this property requires access to VI Scripting. Search around on the LAVA forums for more information on VI Scripting. -D
  18. QUOTE(BrokenArrow @ Jan 8 2008, 08:05 AM) Here's the description of the Arrays and Strings in Loops test from the VI Analyzer: Checks loops to see if they contain Build Array or Concatenate Strings functions. Avoid using these functions in loops because each call to them requires a dynamic resizing of the array or string, which can affect memory and processor time. This test does not check Timed Loops. Although there are cases (as illustrated in this thread) where repeated calls to Build Array inside a loop will not cause a performance degradation compared to other methods, there certai
  19. QUOTE(PJM_labview @ Oct 24 2007, 03:41 PM) The XDataNode is the "ear" that sticks off the side of the Timed Loop. The Timed Loop itself is a native LabVIEW structure. I'm fairly certain that there currently exists no way to create a G-based structure. -D
  20. I've had long save/load times, along with temporary hangs in the editor, when using SCC with LabVIEW and the SCC server I'm connected to becomes unresponsive... -D
  21. After I did some investigating, it seems like a breakpoint in a callback VI *should* be fired whenever debugging is turned on and reentrancy is turned off on the callback VI. Unfortunately, this isn't happening. I've filed a CAR (4EH9RQF2) on this issue. For now, I see three possible workarounds: (1) use the BDWin.Open property to open the callback VI diagram and probe wires on non-initial runs, (2) stick file I/O in the diagram of the callback VI to write debugging info to disk when it executes, and (3) the callback execution recorder utility posted earlier. -D
  22. Hi Danny, I'm not sure what the problem could be...I just tried following my own procedure in the previous post and it worked fine. Double-check that the folder you created under LabVIEW Data is called "VI Analyzer Tests" (must be spelled correctly and use spaces as shown). Also, I noticed that when I tried to save the LLB from the LAVA site, it tried to stick underscores on the LLB name (Find_VI_Calls.llb). Those underscores cannot be there...the filename should be "Find VI Calls.llb" with spaces instead of underscores. Also, you may have a problem if you try to put multiple copies of th
  23. I'm trying to figure out why the breakpoint isn't being hit when the callback VI executes. In the meantime, I found a potential workaround (that requires access to scripting). You can put a BDWin.Open property in the callback VI to cause its diagram to open on the first call of the callback. On any subsequent calls, you can probe wires and the probes will return the wire values. This method won't work if you are only interested in debugging the first call of the callback VI. I'll post here when I find out more about why the breakpoint doesn't work. -D
  24. What kind of "callback" VI are you referring to, i.e. how specifically is the VI being called? -D
  25. Seems to work fine on other apps, too. Any reasons we should use this approach instead of just killing the desired process from Task Manager? -D
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.