mirror of https://github.com/cutefishos/appmotor
You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
35 lines
1.2 KiB
Plaintext
35 lines
1.2 KiB
Plaintext
/*! \page singleinstance How to enable single instance support for the application
|
|
|
|
Usually user wants his application to be run as a single instance. This means,
|
|
that if the launched application is already running, the existing application
|
|
window is activated and no new application processes are started.
|
|
|
|
This can be achieved by adding --single-instance to the invoker command:
|
|
|
|
\verbatim
|
|
[D-BUS Service]
|
|
Name=com.nokia.<application_name>
|
|
Exec=/usr/bin/invoker --single-instance --type=m /usr/bin/<application_name>
|
|
\endverbatim
|
|
|
|
As a result, a lock file
|
|
\c /var/run/single-instance-locks/\<application_name\>/instance.lock is created.
|
|
If applauncherd cannot acquire the lock, it tries to find the corresponding
|
|
window and activates it.
|
|
|
|
This functionality is implemented in a position-independent executable called
|
|
single-instance. Applauncherd uses this executable as a library, but it can be
|
|
used as an ordinary program to start anything as a single instance:
|
|
|
|
\verbatim
|
|
/usr/bin/single-instance <application_name>
|
|
\endverbatim
|
|
|
|
Note, that in this case the launcher is not used.
|
|
|
|
Consider using --single-instance instead of the single instance functionality
|
|
provided by D-Bus, because it very likely is much faster.
|
|
|
|
*/
|
|
|