summaryrefslogtreecommitdiffstats
path: root/tdecore/README.tdestartupinfo
diff options
context:
space:
mode:
authorMichele Calgaro <[email protected]>2024-11-05 12:24:20 +0900
committerMichele Calgaro <[email protected]>2024-11-19 22:26:14 +0900
commit1711870a073597c2282f32ad39a9b8ad5e1cf6bb (patch)
tree1fb9f1d9ad4ec650960add05c3dd287cd42c7d61 /tdecore/README.tdestartupinfo
parent87ad1e6c4d56fb52faa0d1af4afe5c33f05e6dca (diff)
downloadtdelibs-1711870a073597c2282f32ad39a9b8ad5e1cf6bb.tar.gz
tdelibs-1711870a073597c2282f32ad39a9b8ad5e1cf6bb.zip
Rename KUniqueApplication to TDEUniqueApplication and remove obsolete kapp.h and kuniqueapp.h headers
Signed-off-by: Michele Calgaro <[email protected]>
Diffstat (limited to 'tdecore/README.tdestartupinfo')
-rw-r--r--tdecore/README.tdestartupinfo6
1 files changed, 3 insertions, 3 deletions
diff --git a/tdecore/README.tdestartupinfo b/tdecore/README.tdestartupinfo
index 71e786b0d..e28bc99ed 100644
--- a/tdecore/README.tdestartupinfo
+++ b/tdecore/README.tdestartupinfo
@@ -119,7 +119,7 @@ Sending the application startup notification information :
it's done by classes like KRun ). See e.g. KRun sources for details.
During the starting of the application, the info may need some updating
( e.g. right after starting the app, the PID with hostname may be sent,
-or a PID change when KUniqueApplication forks into background ).
+or a PID change when TDEUniqueApplication forks into background ).
When it's detected that the started process exited, it an ASN info
about the finished process should be sent. Since the application may
have forked into background, the finish info should include the PID
@@ -143,7 +143,7 @@ Ideally, the application should read it, and set a window property
called _TDE_STARTUP_ID ( type XA_STRING ) at least on its first mapped
toplevel window to this value. It should also unset it, so it doesn't get
propagated to other applications started from it. It should also
-update the ASN info when necessary, e.g. when KUniqueApplication
+update the ASN info when necessary, e.g. when TDEUniqueApplication
forks into background, it sends the PID change. That's how compliant
applications should work, and this support for ASN should be provided
by toolkits. All TDE application should be compliant by now, since
@@ -192,7 +192,7 @@ There are 3 types of messages :
- change: message
- this message is like new: message, but it's only for updating existing
ASN info, if there's no ASN info for the given identification, it won't
- be created. This is used e.g. in KUniqueApplication when it forks
+ be created. This is used e.g. in TDEUniqueApplication when it forks
into background and sends info about the PID change - it should update
any existing ASN info, but mustn't create a new one, otherwise there
could appear ASN even for applications which shouldn't have ASN