priority problems with activeX

[lumsden]

Hi,

I am running an activeX container with a text editor (called codemax) which I'm using to display data. It writes the data to this container using a strictly typed call by reference node. If I write to this container quickly (say in a loop with a small delay), the cursor changes to busy (hour glass) and it prevents me from clicking anything else on the front panel until the writing completes. This seems like some sort of windows priority problem. Is there any way I can give the activeX container less priority or is this some other problem??

Thanks,
Mark

[Aaron Marks]

This does make some amount of intuitive sense. ActiveX containers run in the user interface thread of LabVIEW. If a property or invoke node takes a very long time to return, it could prevent the user interface from being able to detect events. There ins't anything you can really do from the operating system that would matter. Its somewhat odd for this to be a problem however. An ActiveX property really should not take so long to execute. Either way, to avoid it I think you would have to get the control to run in some other thread. I don't think this is possible. The only thought I had was to put another instance of the control in a subVI, set the subVI to run in a different thread, and don't show the subVIs front panel. I don't really think it will ma
ke a difference though.