09-09-2014 06:12 AM
For something like that, I prefer to use subpanels. It keeps things a lot more organized and scalable.
The idea with subpanels is you have a bunch of VIs off running on their own. You can then choose which VI gets put into the subpanel.
09-09-2014 06:42 AM
Thanks.
I hav never used subpanels in projects before. So by using subpanels I create more running loops? It will make more communication problems between them? Like pressing button on panel 1 shows panel 2 etc?
09-09-2014 06:54 AM
User Events are wonderful, wonderful things. So you just send a User Event to the main VI to open the other screen.
09-09-2014 03:23 PM - edited 09-09-2014 03:24 PM
mistake
09-09-2014 03:25 PM - edited 09-09-2014 03:26 PM
Thanks,
I have made another simple conceptual demo. Code isn't perfect but it is more about idea how it will work than style. Could You take a look and tell me if I think correctly??
So I have one GUI loops that controlls other demons displayed in GUI subpanel.
Demons can communicate with GUI by user event. Using Queue or other mechanism should work good too.
Sending some data to demons... Lets say I need to sent some data from IO loop to one demon. Queues should be good? But having separate queue for all demons will require a lot of effort and can be hard to manage...
Is it safe to kill demons only when GUI loop stops?
If You are doing projects by using these subpanels Could You please tell me about some benefits of using them?? This seems to be hard to maintain and debug. Previous solution with resized GUI and tab controlls was doing the same thing and was done in few minutes....
Thanks in advice 🙂
Edit. It Seems that I can't log out of my university account...
09-10-2014 07:56 AM
I experimented with that design tooday and It seems to be working. But I got error insane object that crashed labview 2 times. I have no ide why.