Matthew,
thanks for your feedback.
Looking forward to the ActiveX equivalent of setting a Value
(Signaling) Property. Would be great if NI decides to provide this
"event-driven power" soon.
Regards.
Frans.
Hi there!
The Call Library Function Node has a undocumented upper left input
wire, left of the output wire, corresponding to the return value, if
any.
It looks like I can use this wire to influence the order in which
different Call Library Function nodes execute. Is this a documented
feature I ca
Matthew,
in fact the solution "could" be very simple: SetControlValue () is the
ActiveX equivalent of the Value property, i.e. it allows to change the
value of a control but does not generate an event ... What I need, is
the ActiveX equivalent of the Value (Signaling) property, i.e. it
allows to c
Matthew,
the link works. Thanks !
I adapted my ActiveX client to programmatically change the value of
"Slide 2" of the example Value_Changed_Events.vi ... and it doesn't
work ... 8-(
The reason is that changing the value of "Slide 2" programmatically
using setControlValue () in my Active X clien
Matthew,
I was a bit too enthousiastic ... 8-(
Your proposal works when the VI is started by the ActiveX client, i.e.
an event is generated immediately.
However, once the VI runs, the value of the control connected to the
Value (Signaling) property (set either manually or via the Active X
client
Matthew,
the link you provided does not seem to work (at this very moment), but
your explanation was sufficient to change my example code and have my
ActiveX client generate an event. Great !
Thanks a lot for your help.
Frans.
Hi there !
I have a simple ActiveX client program (written in C) which uses
LabVIEW as ActiveX server, loads the specified VI, is able to set a
control value and run the VI.
When I use SetControlValue ("controlLabel", value), the corresponding
control indeed is set to the specified value and, if
