|
From: Joakim P. \(LD/EAB\) <joa...@er...> - 2005-12-20 10:19:21
|
Hi Rolf,
>Chances are that there is no good solution which works both for pre
2.3.5 and later.
Sounds like you are approaching the source already! Hope it affects only
pyimport.c?
>>sys.stdin =3D StringIO ("".join (stdin)) # StringIO wants ASCII, =
LabVIEW
has UNICODE
>This sounds wrong. I'm positive that any string parameters LabVIEW
passes to a script are in
>ASCII. ...
Thanks for the correction, "sys.stdin =3D StringIO (stdin)" works!
(Something spooked me yesterday.)
>No! The variant datatype as used in LabVIEW is not documented, nor are
any of the LabVIEW manager >functions needed to deal with this datatype.
It is positively not directly compatible with a=20
>Windows OLE variant and my drive for reverse engineering such an
obscure datatype is close to 0.
I see.=20
Would you like to point me to where I can find docs about the LabVIEW
API for script nodes? I would like to have types for waveform plots and
xy plots. I have problems generating those types when calling LabVIEW
VIs from Python through win32com because that module doesn't distinguish
between tuples (clusters) and lists (arrays). I guess that module uses
OLE variants.
/Joakim
|