Forums

by Glen Richards >> Thu, 25 Sep 2003 23:40:08 GMT

I've got a server application running that spawns "GUI, No Forms" applications.

What is the easiest way to stop the "splash screen" from showing & the "jade start-up sound" from playing when the spawned app. starts?

Any ideas appreciated.


Glen
Encos

by cnwrwm1 >> Fri, 26 Sep 2003 0:21:56 GMT

Glen

In [JadeSound] section of the ini file set EnableSoundSupport=false. In [Jade] section, set OpeningForm=false.

Cheers

Richard Mitchell

by Glen Richards >> Fri, 26 Sep 2003 1:25:07 GMT

Hi Richard,

It is only when the "GUI, No Forms" app spawns that I want to have no splash screen or sound (normal apps I do want the sound & splash screen). I can temporarily (via code) disable/enable them by modifying the ini file as your have suggested - I was kinda hoping there was a cleaner way to do it (as someone may load a normal app while the ini is modified) - like a parameter on the Jade command line like silent=true or something like that. Perhaps this is something I could suggest as an NFS? - unless there is already another way to do it.

I am spawning the app via a node.createExternalProcess() call.

Cheers,


Glen

by Patwos >> Fri, 26 Sep 2003 8:05:44 GMT

It may be stating the obvious, but why not have a different ini file with these settings to avoid the splash screen etc and use that ini file when launching your GUI No Forms app?

Hope that helps,
Pat.

by Glen Richards >> Sun, 28 Sep 2003 23:15:13 GMT

Hi Pat,

Good tip - I had thought about it but didn't know how "standard" it was for Jade systems to have multiple jade.ini files. Plus it could turn into a nightmare maintaining multiple ini files.

Cheers,


Glen

by cnwrwm1 >> Sun, 28 Sep 2003 23:55:22 GMT

Pat's suggestion to use a different ini file is the interim way to address the problem. In JADE 6.0, you can use the name= commandline parameter to have different definitions for the same parameter, in a single ini file.

Cheers

Richard

by Martyn Leadley >> Wed, 8 Oct 2003 1:05:03 GMT

In Jade 6, on the command line you can put individual overrides to the ini file key/value pairs. Add JadeSound.EnableSoundSupport=false and Jade.OpeningForm=false to the command line of the program that you are starting via node.createExternalProcess().

Doing it this way you do not have to create named sections in the ini file or create/maintain a separate ini file.

Named sections are better when you have several keys in a section that need to be different. Where as putting section.key=value on the command line works well if there is only one or two values you want to change.

Martyn

by allistar >> Mon, 29 Sep 2003 8:36:09 GMT

If you are doing this at runtime why don't you generate the ini file automatically (as a copy of the currently used one) and tweak the couple of settings in it that need tweaking. Delete this tmeporary ini file when you are finished with it. That way you still only need to maintain one "master" ini file.

Regards,
Allistar.

------------------------------------------------------------------
Allistar Melville
Software Developer, Analyst allistar@silvermoon.co.nz
Auckland, NEW ZEALAND

Silvermoon Software
Specialising in JADE development and consulting
Visit us at: http://www.silvermoon.co.nz
*NEW* Simple web access to Jade at: www.silvermoon.co.nz/jhp.html ------------------------------------------------------------------