LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Active X Programming Style

I"m writing a hardware driver using an Active X server. I'm looking for opinions on how, spefically, I should open and close the Active X sessions. Should it be open every time the driver is used, or should the higher level VI take care of opening and closing the session and just pass the reference into the driver?
0 Kudos
Message 1 of 3
(2,976 Views)
I use ActiveX for my Video Capture application and I let the high level VI open the session once at the program start, pass the reference as the program is running, and close it at program completion.  Opening and closing it with each use seems to me to be a waste of CPU and doesn't serve any purpose.  The only time you may want to close it is to reinitialize the driver.
 
Matt
Matthew Fitzsimons

Certified LabVIEW Architect
LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison
Message 2 of 3
(2,954 Views)
That makes sense. I guess I'll try that way.
0 Kudos
Message 3 of 3
(2,939 Views)