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

List:       kopete-devel
Subject:    Re: [kopete-devel] Interview in trunk
From:       Michel Hermier <michel.hermier () gmail ! com>
Date:       2006-01-12 17:44:31
Message-ID: 2e631f490601120944s35eb330ch () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


>
>
> Would using the Qt Event model be at all helpful?  Maybe avoid signal
> storms
> on connect.  However Events are 1:1, unlike signals/slots.  Maybe useful
> for
> handling a lot of changes at once if receiving them over IPC and want to
> return from the IPC handler quickly.  Could use ->queued connections for
> these cases though.


Hi
Speaking of Event model, I think using it is dangerous.
I mean, what is the event Type value will you use, and how will you ensure
that it will not (read never) be used by any other kdelibs (lib) or KDE
apps/kpart (unless there is a file like used for kdDebug registering all th=
e
types).
Michel

[Attachment #5 (text/html)]

<div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; \
BORDER-LEFT: #ccc 1px solid"><br>Would using the Qt Event model be at all \
helpful?&nbsp;&nbsp;Maybe avoid signal storms<br>on connect.&nbsp;&nbsp;However \
Events are 1:1, unlike signals/slots.&nbsp;&nbsp;Maybe useful for <br>handling a lot \
of changes at once if receiving them over IPC and want to<br>return from the IPC \
handler quickly.&nbsp;&nbsp;Could use -&gt;queued connections for<br>these cases \
though.</blockquote> <div>&nbsp;</div>
<div>Hi</div>
<div>Speaking of Event model, I think using it is dangerous.</div>
<div>I mean, what is the event Type value will you use, and how will you ensure that \
it will not (read never) be used by any other kdelibs (lib)&nbsp;or KDE apps/kpart \
(unless there is a file like used for kdDebug registering all the types). \
</div>Michel<br>&nbsp;</div>



_______________________________________________
kopete-devel mailing list
kopete-devel@kde.org
https://mail.kde.org/mailman/listinfo/kopete-devel


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