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

List:       kde-devel
Subject:    Re: Howto respond to a event before existing handlers
From:       Lindsay Mathieson <lindsay.mathieson () gmail ! com>
Date:       2010-04-25 1:41:13
Message-ID: 201004251141.13573.lindsay.mathieson () gmail ! com
[Download RAW message or body]

On Sun, 25 Apr 2010 09:35:22 am Thomas Lübking wrote:
> Event != Signal, i don't think there's a "newtab" event.
> 
> The eventfilter is a stack (LIFO) while the connections are a queue (FIFO)
> - so if you install an eventfilter latter than the critical ones, you'll
> be called before.
> You would want to listen to QEvent::ChildAdded, but iirc the child is
> already created then.
> 
> Otherwise you'll have watch the tab creating objects or connect to a signal
> that is emitted before the tab creation (such as KTabBar::newTabReques())
> and than it should not matter whether someone else has connected to that
> signal as well.


Actually not to worry, I've solved the problem now, was just looking at it the 
wrong way round.

Thanks,

-- 
Lindsay
http://blackpaw.jalbum.net/home
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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