Hi Devi.
I think it´s not possible what you
want.
The LV 7.1 help says about events:
Use Events for Direct User Interaction Only
User interface events occur only when a user directly interacts
with the active front panel. In general, LabVIEW does not generate events if
you use
Title: Activex call delivers only unicode string, but ASCII is needed
Hi list,
I have the following code to call a LabVIEW VI via the Activex interface.
The string "strDataOut" holds the expected data result of the call .
Now I realized that the string coming back from the ActiveX call co
belongs these
problem ?
Martin
-Original Message-
From: Mark Hammond [mailto:[EMAIL PROTECTED]
Sent: Saturday, 25. June 2005 4:44 AM
To: Kuner Martin; python-win32@python.org
Subject: RE: [python-win32] win32com problem with LabVIEW
> It doesn´t work with the following code:
...
&
LabVIEW has an ActiveX interface. With that you can do nearly everything. The
IMHO greatest thing is, that you don´t have to write (or draw) nothing
additional to access your self written Vis via the ActiveX interface. The only
thing you need is the name of the VI. (see LV doc -> ActiveX)
With
utput parameters to the call).
paramVals: array of variants by ref (Input values for the input parameters and
return values from the output parameters in the order in which the names were
specified in paramNames)
---
Is a list object at that point not the right thing on python
I try to talk with Python to a LabVIEW-Application called "cbt" via ActiveX.
Now I´m running into problem calling the "Call" method.
Here´s the code:
import win32com.client
oLv = win32com.client.Dispatch("cbt.Application")
strVi = oLv.ApplicationDirectory + "\\cbt.exe\\" + "cdcAxLog
