diff --git a/3rd-parties/qtsingleapplication/doc/html/qtsingleapplication-example-loader.html b/3rd-parties/qtsingleapplication/doc/html/qtsingleapplication-example-loader.html index 6a36632..6b92350 100644 --- a/3rd-parties/qtsingleapplication/doc/html/qtsingleapplication-example-loader.html +++ b/3rd-parties/qtsingleapplication/doc/html/qtsingleapplication-example-loader.html @@ -165,7 +165,9 @@ return instance.exec(); } -

If the message could not be sent the application starts up. Note that false is passed to the call to setActivationWindow() to prevent automatic activation for every message received, e.g. when the application should just print a file. Instead, the message handling function determines whether activation is requested, and signals that by emitting the needToShow() signal. This is then simply connected directly to QtSingleApplication's activateWindow() slot.

+

If the message could not be sent the application starts up. Note that false is passed to the call to setActivationWindow() to prevent automatic activation for every message received, e.g. when +the application should just print a file. Instead, the message handling function determines whether activation is requested, and signals that by emitting the needToShow() signal. This is then simply connected +directly to QtSingleApplication's activateWindow() slot.

diff --git a/3rd-parties/qtsingleapplication/doc/html/qtsingleapplication.html b/3rd-parties/qtsingleapplication/doc/html/qtsingleapplication.html index 2754a3b..6a30744 100644 --- a/3rd-parties/qtsingleapplication/doc/html/qtsingleapplication.html +++ b/3rd-parties/qtsingleapplication/doc/html/qtsingleapplication.html @@ -80,11 +80,18 @@

Detailed Description

The QtSingleApplication class provides an API to detect and communicate with running instances of an application.

-

This class allows you to create applications where only one instance should be running at a time. I.e., if the user tries to launch another instance, the already running instance will be activated instead. Another usecase is a client-server system, where the first started instance will assume the role of server, and the later instances will act as clients of that server.

+

This class allows you to create applications where only one instance should be running at a time. I.e., if the user tries to launch another instance, the already running instance will be activated +instead. Another usecase is a client-server system, where the first started instance will assume the role of server, and the later instances will act as clients of that server.

By default, the full path of the executable file is used to determine whether two processes are instances of the same application. You can also provide an explicit identifier string that will be compared instead.

-

The application should create the QtSingleApplication object early in the startup phase, and call isRunning() to find out if another instance of this application is already running. If isRunning() returns false, it means that no other instance is running, and this instance has assumed the role as the running instance. In this case, the application should continue with the initialization of the application user interface before entering the event loop with exec(), as normal.

-

The messageReceived() signal will be emitted when the running application receives messages from another instance of the same application. When a message is received it might be helpful to the user to raise the application so that it becomes visible. To facilitate this, QtSingleApplication provides the setActivationWindow() function and the activateWindow() slot.

-

If isRunning() returns true, another instance is already running. It may be alerted to the fact that another instance has started by using the sendMessage() function. Also data such as startup parameters (e.g. the name of the file the user wanted this new instance to open) can be passed to the running instance with this function. Then, the application should terminate (or enter client mode).

+

The application should create the QtSingleApplication object early in the startup phase, and call isRunning() to find out if another instance of this +application is already running. If isRunning() returns false, it means that no other instance is running, and this instance has assumed the role as the +running instance. In this case, the application should continue with the initialization of the application user interface before entering the event loop with exec(), as normal.

+

The messageReceived() signal will be emitted when the running application receives messages from another instance of the same application. When +a message is received it might be helpful to the user to raise the application so that it becomes visible. To facilitate this, QtSingleApplication provides +the setActivationWindow() function and the activateWindow() slot.

+

If isRunning() returns true, another instance is already running. It may be alerted to the fact that another instance has started by using +the sendMessage() function. Also data such as startup parameters (e.g. the name of the file the user wanted this new instance to open) can +be passed to the running instance with this function. Then, the application should terminate (or enter client mode).

If isRunning() returns true, but sendMessage() fails, that is an indication that the running instance is frozen.

Here's an example that shows how to convert an existing application to use QtSingleApplication. It is very simple and does not make use of all QtSingleApplication's functionality (see the examples for that).

 // Original
@@ -110,7 +117,8 @@
      mmw.show();
      return app.exec();
  }
-

Once this QtSingleApplication instance is destroyed (normally when the process exits or crashes), when the user next attempts to run the application this instance will not, of course, be encountered. The next instance to call isRunning() or sendMessage() will assume the role as the new running instance.

+

Once this QtSingleApplication instance is destroyed (normally when the process exits or crashes), when the user next attempts to run the application this instance will not, of course, be encountered. +The next instance to call isRunning() or sendMessage() will assume the role as the new running instance.

For console (non-GUI) applications, QtSingleCoreApplication may be used instead of this class, to avoid the dependency on the QtGui library.

See also QtSingleCoreApplication.

@@ -123,9 +131,13 @@

QtSingleApplication::QtSingleApplication ( int & argc, char ** argv, Type type )

Creates a QtSingleApplication object. The application identifier will be QCoreApplication::applicationFilePath(). argc, argv, and type are passed on to the QAppliation constructor.

QtSingleApplication::QtSingleApplication ( Display * dpy, Qt::HANDLE visual = 0, Qt::HANDLE cmap = 0 )

-

Special constructor for X11, ref. the documentation of QApplication's corresponding constructor. The application identifier will be QCoreApplication::applicationFilePath(). dpy, visual, and cmap are passed on to the QApplication constructor.

+

Special constructor for X11, ref. the documentation of QApplication's corresponding constructor. The application identifier will +be QCoreApplication::applicationFilePath(). dpy, visual, and cmap are passed on to +the QApplication constructor.

QtSingleApplication::QtSingleApplication ( Display * dpy, int & argc, char ** argv, Qt::HANDLE visual = 0, Qt::HANDLE cmap = 0 )

-

Special constructor for X11, ref. the documentation of QApplication's corresponding constructor. The application identifier will be QCoreApplication::applicationFilePath(). dpy, argc, argv, visual, and cmap are passed on to the QApplication constructor.

+

Special constructor for X11, ref. the documentation of QApplication's corresponding constructor. The application identifier will +be QCoreApplication::applicationFilePath(). dpy, argc, argv, visual, and cmap are +passed on to the QApplication constructor.

QtSingleApplication::QtSingleApplication ( Display * dpy, const QString & appId, int argc, char ** argv, Qt::HANDLE visual = 0, Qt::HANDLE cmap = 0 )

Special constructor for X11, ref. the documentation of QApplication's corresponding constructor. The application identifier will be appId. dpy, argc, argv, visual, and cmap are passed on to the QApplication constructor.

void QtSingleApplication::activateWindow ()   [slot]

diff --git a/ukuisearch-systemdbus/CMakeLists.txt b/ukuisearch-systemdbus/CMakeLists.txt index 4d67b37..5535ac8 100644 --- a/ukuisearch-systemdbus/CMakeLists.txt +++ b/ukuisearch-systemdbus/CMakeLists.txt @@ -11,6 +11,6 @@ target_link_libraries(ukui-search-systemdbus PRIVATE Qt${QT_VERSION_MAJOR}::DBus ) install(FILES conf/com.ukui.search.qt.systemdbus.service DESTINATION /usr/share/dbus-1/system-services/) -install(FILES conf/com.ukui.search.qt.systemdbus.conf DESTINATION /etc/dbus-1/system.d/) +install(FILES conf/com.ukui.search.qt.systemdbus.conf DESTINATION /usr/share/dbus-1/system.d/) -install(TARGETS ukui-search-systemdbus RUNTIME DESTINATION /usr/bin) \ No newline at end of file +install(TARGETS ukui-search-systemdbus RUNTIME DESTINATION /usr/bin)
Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies)