jgcode

Sweet! Can't wait

Well why didn't you let us know about it then?

I knew you could change the inputs but didn't know you could change the outputs, so thats pretty cool - thanks for sharing.

Lol

This thread was manually moved from OpenG to LAVA.

By the way its Rhythm not Rythem

This thread was manually moved from OpenG to LAVA.

This thread was manually moved from OpenG to LAVA. LabVIEWVersion__ogb (hacked).vi

This thread was manually moved from OpenG to LAVA. SetControlValueBug-LV2009.vi Set Control Value Variant__ogtk--fix.vi

This thread was manually moved from OpenG to LAVA.

This thread was manually moved from OpenG to LAVA.

This thread was manually moved from OpenG to LAVA.

Kudos!

Funnily enough, pink is my favorite color!

Cool. I have done stuff where the Main App sends Status Messages to the Splash Screen. Can you go into detail about how the hierarchy works here? Does the Splash Screen load the modules, then open the Main App so th modules stay in memory, then the Splash Screen goes out of memory etc... ?? Cheers -JG

FWIW this is what I do. I do it for the reasons you stated - to have time to load the main application and do any initialising I need before showing the UI. This is the general approach for most applications. As I do a lot of smaller applications so I decided to write some reuse code and have a generic splash screen engine. When requirements dictate, I just start with an engine template and go from there. This is my project, it has two important VIs Launcher - which is not statically coupled to the application hierarchy VI Tree - contains all other Top Level VIs (not Launcher) This makes the Build Spec very simple and does not need to be changed. I then create a Splash Screen for each application that can look like whatever (note: toolbar only shown in dev environment) The BD code looks like this - this is the reuse code. I just configure it with the Main VI and UI VI. The Engine does its stuff. Launches the Main VI in the background Does some fading out or other screen effects based on a Timer Then due to the RTE exiting if a FP is not in memory, the application does a check and waits for the UI's FP to be loaded. This means I have time to initialize the UI etc... before showing it. Pretty basic I know, but it works. I have other apps where the Splash Screen can create a log of the session, checks for driver version (DAQmx, dotNET) etc... I would like to add more features into the reusable code that I have in these other applications when I have the time.

Nice! I leave town for a few days and this is what happens... 10 points for trying, but my wife beat you to this about 6 months ago

That has be Crelf... ...lol

Thanks for all your hard work in growing the LabVIEW community and good luck at Jive Software! Also please keep tweeting - I really enjoy your feed. Cheers -JG

I would say similar too, but a bit bigger.

ShynR??

You may be onto something there, on second look the popup does say Message From webpage - of course I have no idea, as its unclear at this stage I just assumed LabVIEW code.

I am not sure 100% what you are trying to do (why show the dialog if a button is to be programmatically pressed regardless?). Having said that you could try checking the Key Focus property of the Ok Button on your dialog and if True then fire an event \ do something that is the same as a User pressing the Ok button.

Well then you will have to precheck the input by performing your own logic, correct the response if invalid, then prompt the user with a dialog. This seems like a lot of extra work and possibly intrusive from a User Interface point of view (repeatedly having to click on a dialog). You may find taking advantage of the built in coercion couple with for example, a tip strip\help may be a more graceful response or something similar to this. Depends on your requirements I guess. Cheers -JG