Norm Kirchner

I work for NI now!

You need to disable the 'Lock Panel (Defer Processing of UI) until event completes' option for the event case. What's happening is that the event structure is locking the UI thread until all code inside of the case completes. In your case you've got another UI coming up which you need to interact with for the case structure to complete. A bit of a catch 22. It might feel wrong that it's happening to you, but there are a variety of good cases that that feature exists and behaves as it does. More commonly, for what you're trying to accomplish, people will make action loops which might receive a message to start open another panel instead of calling immediately from within the structure. However that's a more complicated solution and if you're just trying to keep things simple, then just unclick that option and you'll be off to the races.

Q, I'm excited to see the rebirth of this I just got my login, validated my account, but I am unable to create new pages. I'm using the recommended methods to no avail I've logged out and back in, but no dice. Any thoughts?

Can you clarify a little or throw up an example. Do you mean you want the .vim to be a member of the class or used inside a public VI in the class? I presume you mean the former. What happens if you use private accessors in that VI instead of calling the unbundle directly?

All, Thanks for chiming in. I actually hadn't heard of the promise of TS Lite and will be sure to bug the powers that be about it. All in all, most things here resonate with the themes I've heard before and am glad to have ammo in hand to go to the conversation with, as it's gotten delayed; so feel free to keep chiming in. If I had to sum up the big points Cost: LV exe is free cheapest TS deployment gets 500+ Simplicity: Simple enough needs that can get away without the extra features in TS Parallelization: not easy to implement or visualize parallel tasks Training: Don't want to learn another tool myself to dev or for other people to use; just not intuitive enough API woes: Buggy in important areas; hangs between LV Data Access: Getting data around, into and out and between the modules can be challenging Deployment: Just doesn't go smooth History: Been burned before for one situation, why go back TestStand Lite: when please? UI Editor: complicated and overloaded to the point of distraction UI Tester GUI: Understanding components and creating in LV is an untenable beast I hope that is a good representation. ~,~ The Captain was here

This is a terrific little piece of code! Thanks for working it up. Have you thought of possibly making it filterable based upon what color it's going against? The reason being is that I see this as a great addition to the current coloring for plots and default color sets, especially when you change the background from light to dark, or vice versa. See plot 12 for example

I know many people never go the route of using TestStand, choosing to roll their own sequencer and make it work (as I did once upon a time) However I'm starting to hear from a few folks who adopted TestStand and are going back to try to make their own sequencers (as I hope to never do) So, I shook the corporate tree some and have a meeting tomorrow for which I'm representing y'all, based on what I was hearing at NIWeek That being said, if any have gone the route of TS only to turn back, and you'd like your voice shared inside the guts of the mothership, please do share here. FWIW, If you've got specifics as to why you've never tried, that would be best for another thread. Thanks for understanding ~,~ The Captain was here Tag anyone you may know have done the same @Mark Yedinak@Mark Balla

BBQ Photos Courtesy of RightBalancePhotoG available at RBPG, FB and LAVAg.org https://rightbalancephotog.smugmug.com/LAVA-BBQ-2018/ Facebook Album

BBQ Photos Courtesy of RightBalancePhotoG available at RBPG, FB and LAVAg.org https://rightbalancephotog.smugmug.com/LAVA-BBQ-2018/