LabVIEW windows blocked when TS Engine used as a process

[Zyl]

Hello all !

 

Here is a post that I created 2 days ago on NI forums : http://forums.ni.com/t5/LabVIEW/LabVIEW-windows-blocked-when-TS-Engine-used-as-a-process/m-p/2324742/highlight/false#M729301

 

My problem is that I'm currently building a software program requiring TS to be THE execution engine. I mean that almost all actions of playing VIs, sequences, and so on are based on a TS execution.

I then decided to use my traditionnal application framework (see pic attached).

 

And I'm facing a weired issue : if TS is run as a process (running in background), my main window acts like if it was modal. And then, when this main window is closed (end of execution), all other LV windows (lvproj, VI opened, ...) are not responding to mouse actions (I can't move the windows, click on buttons, ...) but react to keyboard actions... 

 

A guy from NI respond that it's caused TS API ActiveX components, and I shouldn't use it the I want to use it... 

 

Do you agree with him or is there something going wrong somewhere ?!

[Zyl]

With pic attached, it's always better !

 

Update : NI suggested to me to modify my architecture to fit with the architecture shown is 'Architecture_Suggested.png'.

What do you think of it ?

[Zyl]

Just to let you know, I modified my code to fit with the 'suggested architecture'.

It results in :

• No more window blocking
• My main window (mother window which contains a subpanel, in which my screens are loaded) terribly hangs !! (1 or 2 seconds before mouse click or window move becomes effective). Which implies that my whole software seems to lag... not very nice for my end users...
  

Do you have any suggestions to improve this ?