[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: porting kstars to QtDBus
From:       David Faure <faure () kde ! org>
Date:       2006-06-19 16:37:10
Message-ID: 200606191837.11135.faure () kde ! org
[Download RAW message or body]

On Monday 19 June 2006 18:24, Jason Harris wrote:
> On Monday 19 June 2006 08:51, David Faure wrote:
> > But the suspending kapp->dcopClient() used to suspend -any- incoming calls
> > in the application, didn't it? The "application IPC channel" is used by
> > "system-wide" (kde-wide) calls as well.
> >
> Ok, so the concern is that other apps will have problems if they try to send 
> an IPC signal to KStars while it's suspended.  This probably wouldn't occur 
> often, would it?  

Right, it wouldn't happen often in kde3 since kde-wide changes are not signalled 
via dcop (except for "ksycoca recreated").
But for kde4 the plan is to use dbus for both kinds of things.

> I have two DCOP functions that suspend the dcopClient: "waitFor(int)", which 
> pauses for a specific number of seconds, and "waitForKey(QString)", which 
> pauses until the specified key is pressed.
Sub-event loop? surely the script waits for the current call to return, so as long
as the method waits, the script can't continue. Or is pause/resume used to block
-other- scripts?

-- 
David Faure, faure@kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]