timewaster1700

Michael thanks so much for your response. Do you use the basic 1 time version of Parallels or the subscription version. Seems like VMWare Fushion Pro would be cheaper by the time you factor in the subscription to get Parallels pro. I'd like the ability to copy VM's but maybe that's not that big of a deal. Has hardware communication been a problem with Parallels?

Looking at installing either VMWare Fashion, Parallels, or Virtual Box to run Windows 10 on my MacBook Pro for LabVIEW development. Whichever I use I want to have the best compatibility with USB and Ethernet hardware for NI hardware as well as third party. Virtualbox is appealing since its free but I'm not sure how well it works and was hoping to find out from you all what you've had success with before I waste a lot of time going down one path. Fushion looks amazing but wow $200 for their Pro license and $160 for their normal license is a lot.

I'm using MGI's Panel Actor. I have an application in which a nested actor launches other nested actors one at a time and inserts them into a subpanel. This works great in dev mode. I have the "Launched Nested" set to Autoshow = T. When I run it in an EXE the panel actors won't display in the subpanel. I thought maybe the autoshow was the problem so I added a message to the nest panel to "Send Show Msg" and it still didn't work. Any ideas on what could be causing these to fail to show in the EXE? The root panel actor and its nested panel start up and display but then when that nested panel tries to launch its own nested panels and display them in its subpanel that's the part that isn't working in the EXE but is in Dev mode. Thanks

Just starting looking at MGI's Panel Actors. In the examples, the root actor is always a panel actor and therefore the "Launch Root Panel.vi" is used. What if you have an application where your root actor is not a panel and you want it to be able to launch a panel actor. Do you just used launch nested panel or do you always have to have a root panel actor? I thought in general you want a single root actor unless you are communicating across network boundaries. To give you a better idea of what I want to do: I want: -Root actor is not a panel actor and launches and sets up some communication and other actors -Root actor launches a nested panel which is a panel actor that contains a subpanel. -This nested panel actor launches other panel actors and switches them into the subpanel as needed Thanks