The problem in a nutshell is that I can only access the value
of a global variable, but not the properties. With a reference,
I can access the properties through a property node.
Martin
Gee, thanks folks. I know that it's a kind of messy way to do
something like that, but it works (even if it takes a bunch of clock
cycles). For myself, in the long run I'd probably use a functional
global.
I thought about it afterwards and wasn't sure that I'd put the example
together correctly. I
Thanks - that was the last bit of the puzzle for me :-)
Martin
Well what do you know - I could upgrade my rating :-)
Martin
There is no way to tell LV that it is a global, it's not - it's as you
say a VI with uninitialized shift registers.
Why would you want to skip the call? One of the good things about
func.globals is the fact that they are VIs; if you try to write to it
and it's busy the code will wait the microseco
There seems to be cases where you want to skip the call, see http://zone.ni.com/devzone/conceptd.nsf/webmain/82E60E34E609C22A862569F8007E3F4A?opendocument";>Improving
Determinism with Functional Globals, LabVIEW 2-Style Globals, in
LabVIEW Real-Time - one of the few documents I found about the
topi
I would use a functional global instead (generally better than
ordinary globals). That global could also hold the reference to the
listbox however instead I would just add a method to the func.global
that gives you read and write access to the listbox contents.
Since it is a global though I would
I have searched quite extensively in the LabView documentation and on
ni.com to find out more about functional globals, but the information
is very sparse. Maybe it's just me overlooking something, but at first
sight, it looks simply like a normal subVI with uninitialized shift
registers. I can of
Agreed - in my (twisted?) mind I was just leaving the for a more
simple, elegant way to do it - if such a method existed. But you are
right, it is certainly not Rob's fault that NI has made it so
cumbersome to do. I am therefore upgrading my rating to (I'm not
sure I can remove the previo
Hi Robert,
Pretty excellent answer
Nirmal
Hi Martin,
Why do you require reference to global variable when it can be
accessed directly. I mean is there any advantage by using reference
method. I think if u eloboarte your consequences, we can share better.
Regards,
Nirmal
Hint: an excellent answer provided with a working example certainly
worths a ! (it's four stars rating... not "censored" =A6=AC)
It may not be the solution you expected but it is not the poster's
fault after all...
An excellent answer. Exactly what I was looking for. I had wondered if
it could be done along those lines, but did not know enough about the
"To more specific class" function to nail it myself.
Pity that it is not possible to do this directly (i.e. right-click a
global variable and select "Create
Thank you for your answer.
I know how to use global variables in general, but the problem is that
a Multicolumn Listbox (MCL) referred as a global is just the number of
the selected line(s). I would like to access the contents of
the MCL, which I perceive as a table. If this is a MCL in a normal V
Hi,
For changing the contents of any gloabal variable, you have to access
that global variable in a normal vi. Open a new vi, go to Block
diagram -> Function Pallete->Structure-> Global variable. Then right
click on this global variable-> replace by your global variable vi or
create a new global v
I wish to change the contents of the columns in a global multicolumn
listbox. As far as I can see, the only way to access the columns in a
multicolumn listbox is to create a reference to it and access the
ItemNames property. But how can I create a reference to a to a global
variable?
16 matches
Mail list logo