ensegre

There is no such a thing like a property node of an event structure which tells what event has been fired (at least in a simple way that I could know), but it is completely possible for the code inside an event case to fire other event(s), which cause other cases of the same or of another structure to be called. You can use anything which generate events: value (signaling) of any control, dynamic events, etc. Personally I do such things all the time in simple GUIs. However, an event calling another event already smells of "you need rather a state machine" or "you need to think at architecture"

If the only way of commanding your camera is through the vendor sdk, bleh. As Rolf wrote, though YMMV. If by chance the camera is supported by v4l2, there you go; shameless self ad.

I see. Thanks Rolf. In fact I am so used to see Qt used by vanilla OSS, that I overlooked the issue of licensing. All technical potential showstoppers aside, in any case.

Just spitballing without knowledge, but via anything modern like Qt perhaps?

To start with, you probably want to write your results into an array of strings, not of numbers. And anyway, what should be the purpose of the while loop and of the event structure with infinite timeout?

alien --target=i386 is not it? (I forgot since last time)

Probably you shouldn't have. Forgot what I did then, but for me $ file /usr/local/JKI/VIPM/vipm /usr/local/JKI/VIPM/vipm: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.6.33, BuildID[sha1]=ff35d7adc7d9ef4e1ee0b41f6d67085e2c22dbe7, stripped $ file /usr/local/JKI/VIPM/support/*.so /usr/local/JKI/VIPM/support/lvanlys.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, stripped /usr/local/JKI/VIPM/support/lvzlib.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynam

I can build executables on my installations of 2018 and 2019 on Ubuntu, FWIW. Used alien as well (alien --install --scripts or something the like. Seem to remember also --target=i386 to force the installation of some component). Have not yet installed a 2020 so can't say, but is there chance that you skipped one rpm?

This one is simply great as a GUI for that. If you're looking for a programmatic way of monitoring running clones, I guess you simply have to look under the hood.

can't you put the 32 and the 64 set in two different directories and use the path-from-diagram?

as dadreamer says. One place where I remember I have used it is https://gitlab.com/enricosegre/LVVideo4Linux . Look in LV-libv4l2/Ancillary/libv4l2_path.vi and all its callers for an example.

I found this one dated 2016: http://download.ni.com/cert/doc/NI PCIe-5140.pdf

If you'd like to give me a review on this... I actually never used it for anything serious, but it was working for me.

Right, if I put it there I get all the brown and light blue bonanza. I was mislead by http://zone.ni.com/reference/en-XX/help/371361B-01/lvconcepts/customizing_your_work_environment/#How_LabVIEW_Stores_Options which is pointed at https://labviewwiki.org/wiki/LabVIEW_configuration_file. But uh, that is the help page for 8.2. Still, it is at odd with https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000PA7rSAG&l=en-IL

I see, thx. Still don't think my LV19 can toggle it with Ctrl-shift-DH, nor I seem to be able to create the brown nodes (it's ~/.labviewrc), but whatever. i was just curious.... thx for the conversion.