Is it possible to obtain a list (string) of all elements within a Global Variable?

[Ben]

My bad!!!!!

I fell for the "Anything is possible with LV" trap.

Yes this forum is not a good place for that discusion since it is intended to answer customers support Q and scripting is not supported.

I beg forgiveness for my sin.

Ben

[tst]

---

@Ben wrote:

tst wrote "I don't think that the scripting elements I refered to are unstable, ..."

I have personally experienced instability with scripting!

---

Obviously, some scripting stuff is unstable - after all, a lot of it is just temporary stuff.

A lot of other stuff, though, is only private because NI doesn't want to release it yet. NI itself is using it in LV, so it has to be stable enough to do some stuff. It's the same with Xnodes.

In this case, I was refering specifically to the New VI Object primitive and the Move method, although, as I said, they could also have problems.

[Ray.R]

Thanks guys!

I did come up with a simple, yet practical solution.  That's what happens when you do not have time to explore "possibilities". 

I created a Global Variable Template.  All I need to do is fill in the blanks when needed..

Yes, I agree... this is a bit weird, but not my call.  I'm building on existing code and interface(s).    Sorry to sound cryptic, but I have to make sure I do not cross any boundaries of NDA.. 

Joe!!???!!!  What??  You?? almost got kicked out of this forum??  Wow..  for talking about scripting??  But...  but.... but... Scripting is part of programming.  It's the balance between "it's gatta be done yesterday" and "doesn't it do everything"...    wow..  😮 Sorry to read that ...  😮

Oh well... another day, another week, another miracle..  or trick up the sleeve..  (enough rambling... back to wiring)..

RayR

[Joe_H]

This is a copy of an e-mail I got back from NI when I asked them why they removed my post from the forum. Just thought I would share this little bit of information with you all. There is also a discussion about it over on LAVA


Hi Joe,

This is a good question you posed. As you mentioned, there are other unsupported features and technologies that are discussed on our Discussion Forums. However, VI scripting is different in one significant way. Though it is currently unlicensed (because it's not a complete product), it will soon become a licensed technology, meaning that it must be purchased just like other software. It is in beta right now so it's not being sold yet but, in its final form, it will be a fully licensed product just like the LabVIEW Development System, Application Builder, Report Generation Toolkit, etc. Therefore, to share this technology is to break the licensing and/or Nondisclosure agreements. That is why we remove these posts from our website. Thanks for your understanding in this. If you have any other questions about this, feel free to respond anytime. Best regards,

J.R. Allen


----- Forwarded by Molly Koester on 06/22/2005 12:44 PM ----- Joseph Hoskins
06/22/2005 12:40 PM

To
Molly Koester
cc

Subject
Re: Post in the NI Discussion Forums

That is OK Molly, I pretty much knew that it would get removed. No hard
feelings to you or NI, I still love the forums. Just one question why can
we not post that type of thing, there are a lot of things that posted that
NI does not support, never will support, and will probably change in the
future that will cause programs to break when upgraded. I just wanted to
let people know that these things are out there.


Thanks anyway

Joe Hoskins

[Ray.R]

I didn't mean to open a can of worms with this one...

Interesting nevertheless...  However, I had something else in mind when referring to scripting. 

Everybody keeps pushing the envelope.  😄

back to wiring..

[DFGray]

Perhaps I just came in late and didn't catch something.  Does anyone know what the actual problem being solved here is?  While scripting and "hidden" methods are fun, could this problem be solved in a more pedestrian and solid manner using LV2 or shift register globals?  I don't know, because I don't have enough information.

However, if you want to do this, here are a couple of tips.

1. Even though it is less user friendly, you should use Class ID instead of Class Name when querying for a reference type.  Class Name has been know to change, so future upgrades could break your code.
2. There are a set of VIs in vi.lib to help you figure out the data type of variants.  They are in the process of being developed, so different versions of LV will have different capabilities.  Check them out in vi.lib\Utility\...  The actual location in Utility changes with LV version.  Earlier versions are in an LLB, later ones in a subdirectory.
   

[Ray.R]

Thanks DFGray,

I have not yet explored the use of  Class ID.  

My original quest was to populate a Global Variable with new parameters and values from an "editor" vi.  The parameters would be created on a new page of a Tab Control.  The "editor" would select an available page (or add a new page) on the TAB Control and create a string control with a unique name.  The string control would contain a script that would be sent to the target via Serial Port. 

Oh yeah... the topic has somewhat evolved along the way..  😉

RayR

Message Edited by JoeLabView on 11-07-2006 08:02 PM