LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

picture fade out

Try this.

Load the Main VI by it's name or path (path in development mode, string in
executable). This makes sure the splash screen is loaded first. In the main
VI, make an occurence reference as input (wire it to the connector pane).
Then, in the splash screen, create an occurence, and run the main vi. When
the main vi triggers the occurence, fade out and disappear. You can also use
a VI reference with event structure, or a user event, queue, global, or
whatever to do the synchronisation.

Regards,

Wiebe.


0 Kudos
Message 21 of 28
(1,140 Views)

I didn't get much of that at all, but i've tried adding them to the same project earlier which had the effect that the splash took 20 sec to start (it waited until both were loaded). That's why i'm using System exec, to have a small independent program. that starts fast

 

/Y

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 22 of 28
(1,135 Views)

"Yamaeda" <x@no.email> wrote in message
news:1234973414127-855639@exchange.ni.com...
> I didn't get much of that at all, but i've tried adding them to the same
project earlier which had the effect that the splash took 20 sec to start
(it waited until both were loaded). That's why i'm using&nbsp;System exec,
to have a small independent program. that starts fast&nbsp;/Y

Ok, VI server is (mildly) advanced, but very good to know. There should be
example splash screens on the forum, not with fading screens, but it should
demonstrate the idea.

I'll see if I can make an axample, but it'll have to wait.

Regards,

Wiebe.


0 Kudos
Message 23 of 28
(1,119 Views)
As you can see in my previous post, i have a solution that works on non-LabVIEW applications, what i dont understand is why LabVIEW applications dont give the correct coordinates to the system.
G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 24 of 28
(1,102 Views)

"Yamaeda" <x@no.email> wrote in message
news:1235034613326-856182@exchange.ni.com...
> As you can see in my previous post, i have a solution that works on
non-LabVIEW applications, what i dont understand is why LabVIEW applications
dont give the correct coordinates to the system.

Well, it is hard to tell without the two most important sub vi's.


0 Kudos
Message 25 of 28
(1,087 Views)

This one is slightly modified and basically does the same thing (and shouldn't lack anything)

It still seems to close as soon as the program is visible in Application window though, and not when the programs window appear.

 

/Y

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 26 of 28
(1,081 Views)
You are checking if a proces exists. But when you start LabVIEW, the proces
exists maybe 10 seconds before the first window appears!

Checking for a window, or it's coordinates is also not very useful, since
the window can exsist, and have coordinates, long before it is shown. So, if
you really want to go that way, you also need to check if the window is
visible.

Hope it helps,

Wiebe.


Message 27 of 28
(1,069 Views)

I've solved it through a VB-forum. I've now managed to find out how to check for window visibility.

 

/Y

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 28 of 28
(1,047 Views)