EDN Admin
Well-known member
I know one can select Spash Screen as the application startup http://public.bay.livefilestore.com/y1pURLnpd-lRvoHrZQsAQNfijKMJs-uvsQECbA_X8kDH4Qy1nZMgx1_bLrBR9Y-lqqlbMsXJL599D9ipT9ffgkewQ/Startup%20form.jpg?psid=1
as per this illustration . I cant do that however because the application is called by another program which passes in parameters via Process.Start(). Depending on the passed in arguments, I need to either
<ol>
Go Directly to the MainForm or Go First to a Splash Screen which will then to the the Mainform after 5 seconds.
</ol>
I definitely need Step 2 above because of the slow startup time of creating an SocketConnection and the population of some Custom Controls only after the Socket connection has been established.
Would I use a startup class or module and then use that as the application startup form which could be establishing the SocketConnection while also launching a Splash Screen?
Thank you,
View the full article
as per this illustration . I cant do that however because the application is called by another program which passes in parameters via Process.Start(). Depending on the passed in arguments, I need to either
<ol>
Go Directly to the MainForm or Go First to a Splash Screen which will then to the the Mainform after 5 seconds.
</ol>
I definitely need Step 2 above because of the slow startup time of creating an SocketConnection and the population of some Custom Controls only after the Socket connection has been established.
Would I use a startup class or module and then use that as the application startup form which could be establishing the SocketConnection while also launching a Splash Screen?
Thank you,
View the full article
