Aristos Queue Posted June 5, 2009 Author Report Share Posted June 5, 2009 QUOTE (martin@aerodynamics @ Jun 3 2009, 10:08 AM) Thanks a lot- But why you didn't included your help files? :question: You got all the help files that exist. Yep, all of 'em. Quote Link to comment
Phillip Brooks Posted June 5, 2009 Report Share Posted June 5, 2009 QUOTE (Darren @ Jun 3 2009, 10:17 PM) 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 Haven't had time to play with the toolkit, but thanks for the first Scripting tip! http://labviewartisan.blogspot.com/2009/06...1-power-of.html Quote Link to comment
crelf Posted June 6, 2009 Report Share Posted June 6, 2009 QUOTE (ShaunR @ May 31 2009, 05:57 AM) Scripting only has value within the tool chain. You can't use it for in your distributions so there is no commercial value added other than tools for programmers (and I've been using Labview so long now, I don't really need anything that Labview doesn't provide). Not true - I've used scripting in several distributions that I've provided to customers. Not built executables, but distributions all the same. Quote Link to comment
Darren Posted June 6, 2009 Report Share Posted June 6, 2009 My 2nd blog post on scripting: LabVIEW Scripting Tip #2: Supporting Undo -D Quote Link to comment
ShaunR Posted June 6, 2009 Report Share Posted June 6, 2009 QUOTE (crelf @ Jun 5 2009, 06:07 PM) Not true - I've used scripting in several distributions that I've provided to customers. Not built executables, but distributions all the same. Semantics. If we want to be technically correct, I think I could have said "Binary Distributions". But the sense was correct. I would (tentatively) suggest that your "distributions" come under the heading "Tools for programmers" anyway. That is a small market in comparison to "compiled and configured" executable/binary distributions, especially in an environment which has historically been very open with source contributions. Quote Link to comment
crelf Posted June 6, 2009 Report Share Posted June 6, 2009 QUOTE (ShaunR @ Jun 5 2009, 02:33 PM) I would (tentatively) suggest that your "distributions" come under the heading "Tools for programmers" anyway. Sure, we create tools for programmers, but the case I was thinking of above was for end-users of a data logging application where they could easily drop down new things that they could then bind to other things. I'd show you a screenshot, but it's not a product that's for public consumption... yet Quote Link to comment
hooovahh Posted June 6, 2009 Report Share Posted June 6, 2009 Public consumption? Is that like eating the public? Are you sure that cannibalism is the right kind of image we want for VIE? Quote Link to comment
crelf Posted June 6, 2009 Report Share Posted June 6, 2009 QUOTE (hooovahh @ Jun 5 2009, 03:51 PM) Public consumption? Is that like eating the public? Are you sure that cannibalism is the right kind of image we want for VIE? It's always nice to eat new clients. Ummmm, I mean "meet"! Quote Link to comment
lavezza Posted June 6, 2009 Report Share Posted June 6, 2009 Is the Property App.MenuLaunchVI available in the new scripting toolkit? I didn't see it. Is the functionality available with another call? Thanks, Pat Quote Link to comment
Darren Posted June 6, 2009 Report Share Posted June 6, 2009 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 Quote Link to comment
i2dx Posted June 7, 2009 Report Share Posted June 7, 2009 QUOTE (lavezza @ Jun 5 2009, 10: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?Thanks, Pat no, but the ini-key that relveals the private property and invoke nodes is still working ... Quote Link to comment
Francois Normandin Posted June 8, 2009 Report Share Posted June 8, 2009 QUOTE (lavezza @ Jun 5 2009, 04: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? Am I the only one who read it as App.MenuLunchVIE? I must have been confused by Darren's avatar and all that cannibalism talk. QUOTE (crelf @ Jun 5 2009, 04:50 PM) It's always nice to eat new clients. Ummmm, I mean "meet"! And you prefer "meating" them in packs of three? Quote Link to comment
crelf Posted June 9, 2009 Report Share Posted June 9, 2009 QUOTE (normandinf @ Jun 7 2009, 08:48 AM) Am I the only one who read it as App.MenuLunchVIE? Working for VIE is certainly delicious QUOTE (normandinf @ Jun 7 2009, 08:48 AM) And you prefer "meating" them in packs of three? Damn it - you're on to me! I'd love to have you for lunch... Quote Link to comment
Antoine Chalons Posted July 15, 2009 Report Share Posted July 15, 2009 Hi I've just started a discussion on NI community / LabVIEW API to put requests for new properties/methods. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.