Darren
-
Posts
622 -
Joined
-
Last visited
-
Days Won
66
Content Type
Profiles
Forums
Downloads
Gallery
Posts posted by Darren
-
-
QUOTE (lavezza @ Jun 5 2009, 03:56 PM)
Is the Property App.MenuLaunchVI available in the new scripting toolkit? I didn't see it. Is the functionality available with another call?The MenuLaunch.App and MenuLaunch.VI properties are private, which means they are not exposed in scripting. It would not be unreasonable, however, to expect a VI that wraps these properties in a future LabVIEW version.
-D
-
-
Try using a Case Structure...if the reset button is pressed, wire an empty string to the display (and into your feedback node). Otherwise wire in the string you're keeping in the feedback node.
-D
-
QUOTE (asbo @ Jun 3 2009, 07:43 PM)
Weekly Scripting Nuggets ... ?
Heh, maybe. We'll see what my time availability looks like in the coming weeks. Don't forget I have to come up with Weekly Normal Nuggets, too.
And I should probably figure out here pretty soon what I'm going to present at NI Week.-D
-
-
QUOTE (jdunham @ May 21 2009, 12:00 AM)
I'm not resting assured. My code overwhelmingly uses I32s and DBLs. Often I use Create Constant, but when the type has not yet been determined, then I go from the palette. It would be much better for me to have DBL and I32 available separately on the palette for both FP controls and BD constants. I suspect nothing will change, but you can't convince me the status quo is 'better'.I have a Quick Drop shortcut of 'nc' for Numeric Constant...I use it all the time to drop an I32 constant. I could see it being useful for a DBL constant to be on the palettes, simply so I could have a 'dc' shortcut to drop the DBL constants when I need them. I'll look into what it might take to get a DBL constant added to the palettes sometime in the future (the work would be trivial, it's just a matter of convincing the right people). For now, though, you could add your own DBL constant merge VI to the user.lib palettes, and use Quick Drop to have quick access to it.
-D
-
QUOTE (Black Pearl @ May 13 2009, 02:21 PM)
Actually, it is the default selector value (I just recently made this account). Furthermore, it is fun to assign oneself a Version that does not officially exist.Hah, I just realized that at some point in the past, I changed my profile to include LV 2009 too.
To add credibility to my previous statement, I've changed it back to only list the released LabVIEW versions I use. -D
-
QUOTE (crelf @ May 13 2009, 11:42 AM)
Perhaps LabVIEW 2009 is the default selector when ppl sign up? Maybe we should remove it from the list and only include officially released versions? I'm not sure what benefit having 2009 in there is if we can't share code on the forum (and we can't).I agree. I don't think it makes sense to list an unreleased LabVIEW version as an option when setting up a LAVA profile.
-D
-
QUOTE (Aristos Queue @ May 8 2009, 02:01 PM)
I don't consider it a blind spot. My http://forums.ni.com/ni/board/message?board.id=170&thread.id=380412' target="_blank">favorite feature of LabVIEW 8.5 was the For Loop with Break. I've probably used it hundreds, if not thousands, of times in code I've written in the past 2 years. And the few times I've needed the index of the For Loop when it stopped, I just used the iteration count within the loop. If I ever needed to know how many times the loop ran, I would just drop an increment in the loop and wire it to the iteration count. I never would have considered it a shortcoming of the For Loop that I had to do this.
-D
-
Also, the CLD is a 4-hour application coding exam, there aren't any "questions" on it to speak of. And this is too specific a question for the CLA. And probably too difficult for the CLAD.
-D
-
-
QUOTE (TobyD @ Apr 21 2009, 10:05 AM)
It was a big hit...to our reputations.That's hilarious. Man, this is so cool that there's HP calculator zealots here. I guess it goes with the territory, though...you guys all have impeccable taste in programming language, so it only makes sense that you'd all like the best calculators too.
-D
-
QUOTE (Mark Yedinak @ Apr 20 2009, 05:26 PM)
I don't have a picture but my kids like to give me crap about having an engraved name plate on the back of my HP 48G calculator.Awesome! I had an engraved name plate on my 48GX! I still contend the 48G series was the best graphing scientific calculator ever made (always bugged me that TI-85 was the standard in my high school). A few months back I reluctantly sold my 48GX, since I haven't used it since undergrad college. I sold it in 2008 for as much as I bought it for back in 1993!
-D
Oh, and in case anybody wants to start a calculator debate (snicker), I contend that the HP 32SII (which I still own) is the best non-graphing scientific calculator ever made. 384 bytes of user memory ftw!
-
Definitely a bug, I was able to reproduce in 8.6. I couldn't find a workaround, but I filed CAR# 160408 on the issue.
-D
-
Many of the VIs that ship with LabVIEW were written long ago, before too many people thought much about coding standards. We had the AEs go through and scrub all the examples a few years back, so a lot of those should have gotten better. As for vi.lib VIs, those don't typically get edited too much after being written. I do make it a habit to clean up any shipping VI I happen to be editing though (just did one this morning), so given enough years, I may single-handedly clean up vi.lib.
-D
-
Ben, your use of the term octothorpe just made my day! I thought my dad and I were the only ones who used the true name of the # symbol!
-D
-
QUOTE (Norm Kirchner @ Apr 2 2009, 05:20 PM)
http://lavag.org/old_files/monthly_04_2009/post-4441-1238728342.png' target="_blank">
Pass it the name of an object on the palette you want to bring up, and that palette will appear in the position you specify, with the object whose name you specified highlighted. So it works based off palette object names, not palette names, but it's the closest I can do.
-D
-
When you guys do start using Quick Drop, make sure to read my Advanced Quick Drop Tips post on the NI Forums. Keeping one hand on the keyboard for typing object name shortcuts, and one hand on the mouse for placement and wiring, is *exactly* what I do all day long.
-D
-
QUOTE (Michael Aivaliotis @ Mar 25 2009, 09:01 PM)
If I rename a parent dynamic dispatch VI, the children override VIs don't get renamed. I assume this is a known issue. I'm not sure if others think this is an issue that should be fixed but it's bugging me lately.I agree. It seems like something we should be able to do. But then again, there may be a good reason for why it can't be done...AQ?
-D
-
QUOTE (rpursley @ Mar 16 2009, 03:41 PM)
I had some delay problems when there were a couple toolkits on a machine with an expired license for that toolkit (primarily VI Analyzer). Once I uninstalled them, the problem disappeared.That was actually a bug in LabVIEW that I introduced in 8.6 where an expired VI Analyzer license would cause the long LabVIEW launch time (sorry about that). It's fixed in 8.6.1. The easiest workaround, as you discovered, was to uninstall the VI Analyzer after its license expired.
-D
-
QUOTE (Gary Rubin @ Mar 5 2009, 06:48 AM)
You don't? How do you differentiate between z's and 2's? I started putting lines through my z's in college, when I started to have trouble interpreting my physics equations.My Zs have a distinct angular upper corner...my 2s have a curved upper corner. They look pretty much exactly like 'Z' and '2'.
Thread hijack ftw!
-D
-
-
-
Looking at the diagram of the Conditional Error Probe (vi.lib\_probes\default\ConditionalErrorProbe.vi), it looks like either the General Error Handler CORE.vi or that mysterious Conditional Disable Structure is to blame.
-D
Enable/Disable & Show/Hide Controls
in User Interface
Posted
QUOTE (Norm Kirchner @ Jun 8 2009, 04:10 PM)
More details about the traverse VI http://labviewartisan.blogspot.com/2009/06/labview-scripting-tip-1-power-of.html' rel='nofollow' target="_blank">here.
-D