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

List:       kde-devel
Subject:    Quick KOM/Corba Question
From:       Kurt Granroth <granroth () kde ! org>
Date:       1999-01-06 3:58:33
[Download RAW message or body]

[try saying the subject 10 times fast!]

Anyway, I have a quick question about KOM and/or CORBA.  The 'signals'
example in the corba package does a fairly good job of describing how
to use signals in KOM... but only within one application.  This is
helpful, then, but not practical for "real world" use.  If I was not
going to have interaction *between* apps, then it makes more sense to
just use "native" Qt signal/slots.

Sooo, there *must* be a way of using KOM signals/slots between apps (else
why have them at all?).  My quick question is: how?  Can somebody with
a decent understanding of this explain in a few steps how one could modify
the signals example to have the Sender in one app and the Receiver in a
totally separate app and have them STILL send each other signals?

<totally_non-related_question>
Would it be at all possible to have slots that immediately return with
the KOM interface?  That is, say there is

App1:
void Receiver::slotClicked()
{
	for(;;);
}

and

App2:
	sender->clicked();
	printf("Got here!\n");

With native signals/slots, you will never get to the printf.  Is there a
way that the slotClicked() function would be called in app2 but execution
would continue in app1?
</totally_non-related_question>
-- 
Kurt Granroth
granroth@kde.org
http://www.pobox.com/~kurt_granroth

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