On Windows, if you launch the executable from a console window, a GUI application can neither write to or read from that console window. Sometimes it might be useful to use the console, for example for seeing debug output or for simulating a console mode with the same executable. In this case you can select the Allow -console parameter check box. If the user supplies the -console parameter when starting the launcher from a console window, the launcher will try to acquire the console window and redirect stdout and stderr to it. If you redirect stderr and stdout in the redirection settings, that output will not be written to the console.
If your GUI application uses SWT or QT Jambi instead of Swing, please select the uses SWT or QT check box below this radio button. This is mainly important for correct behavior on Mac OS X where the application must be started differently in this case. The executables on Microsoft Windows always include the XP manifest, so that on Windows XP, SWT applications are displayed in XP style and not in Windows 2000 style.
When you develop a service please note the following requirement: The main method will be called when the service is started.
To handle the shutdown of your service, you can use the Runtime.addShutdownHook() method to register a thread that will be executed before the JVM is terminated.
For information on how services are installed or uninstalled, please see the help on help topic on services.
StartupNotification
class of the
install4j launcher client API
you can register a startup handler to receive the command line parameters.
In this way, you can handle file associations with a single application instance.
This feature is only available on Microsoft Windows, on Mac OS X, single bundle media files
always behave this way.