SingleApplication
3.6.0
Replacement for QtSingleApplication
|
This is a replacement of the QtSingleApplication for Qt5
and Qt6
.
Keeps the Primary Instance of your Application and kills each subsequent instances. It can (if enabled) spawn secondary (non-related to the primary) instances and can send data to the primary instance from secondary instances.
You can find the full usage reference and examples here.
The SingleApplication
class inherits from whatever Q[Core|Gui]Application
class you specify via the QAPPLICATION_CLASS
macro (QCoreApplication
is the default). Further usage is similar to the use of the Q[Core|Gui]Application
classes.
You can use the library as if you use any other QCoreApplication
derived class:
To include the library files I would recommend that you add it as a git submodule to your project. Here is how:
Qmake:
Then include the singleapplication.pri
file in your .pro
project file.
CMake:
Then include the subdirectory in your CMakeLists.txt
project file.
Directly including this repository as a Git submodule, or even just a shallow copy of the source code into new projects might not be ideal when using CMake. Another option is using CMake's FetchContent
module, available since version 3.11
.
The library sets up a QLocalServer
and a QSharedMemory
block. The first instance of your Application is your Primary Instance. It would check if the shared memory block exists and if not it will start a QLocalServer
and listen for connections. Each subsequent instance of your application would check if the shared memory block exists and if it does, it will connect to the QLocalServer to notify the primary instance that a new instance had been started, after which it would terminate with status code 0
. In the Primary Instance SingleApplication
would emit the instanceStarted()
signal upon detecting that a new instance had been started.
The library uses stdlib
to terminate the program with the exit()
function.
Also don't forget to specify which QCoreApplication
class your app is using if it is not QCoreApplication
as in examples above.
Traditionally, the functionality of this library is implemented as part of the Qt application class. The base class is defined by the macro QAPPLICATION_CLASS
.
In freestanding mode, SingleApplication
is not derived from a Qt application class. Instead, an instance of a Qt application class is created as normal, followed by a separate instance of the SingleApplication
class.
Note: With the discarded arguments and the class name that sounds like a Qt application class without being one, this looks like a workaround – it is a workaround. For 4.x, the single instance functionality could be moved to something like a SingleManager
class, which would then be used to implement SingleApplication
. This can't be done in 3.x, because moving SingleApplication::Mode
to SingleManager::Mode
would be a breaking change.
To enable the freestanding mode set QAPPLICATION_CLASS
to FreeStandingSingleApplication
. This is a fake base class with no additional functionality.
The standalone mode allows us to use a precompiled version of this library, because we don't need the QAPPLICATION_CLASS
macro to define our Qt application class at build time. Furthermore, we can use std::optional<SingleApplication>
to decide at runtime whether we want single application functionality or not.
Use the standard CMake workflow to create a precompiled static library version, including CMake config files.
This can be used via:
Note: The QAPPLICATION_CLASS
macro is eliminated during CMake install.
The SingleApplication
class implements a instanceStarted()
signal. You can bind to that signal to raise your application's window when a new instance had been started, for example.
Using SingleApplication::instance()
is a neat way to get the SingleApplication
instance for binding to it's signals anywhere in your program.
Note: On Windows the ability to bring the application windows to the foreground is restricted. See Windows specific implementations for a workaround and an example implementation.
If you want to be able to launch additional Secondary Instances (not related to your Primary Instance) you have to enable that with the third parameter of the SingleApplication
constructor. The default is false
meaning no Secondary Instances. Here is an example of how you would start a Secondary Instance send a message with the command line arguments to the primary instance and then shut down.
Note: A secondary instance won't cause the emission of the instanceStarted()
signal by default. See SingleApplication::Mode
for more details.*
You can check whether your instance is a primary or secondary with the following methods:
Note: If your Primary Instance is terminated a newly launched instance will replace the Primary one even if the Secondary flag has been set.*
There are five examples provided in this repository:
examples/basic
examples/calculator
examples/sending_arguments
sending_arguments
where SingleApplication
is used in freestanding mode examples/separate_object
examples/windows_raise_widget
Each major version introduces either very significant changes or is not backwards compatible with the previous version. Minor versions only add additional features, bug fixes or performance improvements and are backwards compatible with the previous release. See CHANGELOG.md for more details.
The library is implemented with a QSharedMemory
block which is thread safe and guarantees a race condition will not occur. It also uses a QLocalSocket
to notify the main process that a new instance had been spawned and thus invoke the instanceStarted()
signal and for messaging the primary instance.
Additionally the library can recover from being forcefully killed on *nix systems and will reset the memory block given that there are no other instances running.
This library and it's supporting documentation, with the exception of the Qt calculator examples which is distributed under the BSD license, are released under the terms of The MIT License (MIT)
with an extra condition, that: