From: Christopher Michael <cpmichael1@co...> - 2011-11-05 20:47:02
On 11/05/11 16:22, Boris Faure wrote:
> On Sat, Nov 5, 2011 at 20:34, Christopher Michael
> <cpmichael1@...> wrote:
>> What is the reasoning for this ?? Makes little sense to me to send a
>> hide event for a border that is not visible (ie: not visible on screen
>> or already hidden). If the border is not visible on the screen (or
>> already hidden), then why send a hide event ??
> I'm using that event in e-tiling to know when a window disappears.
> Maybe this is not the correct event to do that.
Well, that would be the correct event (E_EVENT_BORDER_HIDE)...but what I
don't get is why you are resending the E_EVENT_BORDER_HIDE there.
1) e_border_hide function gets called and 'hides' the border (also sets
border->visible to false). This sends out the E_EVENT_BORDER_HIDE when done.
2) e_border_hide function gets called again and if it's not visible (ie:
e_border_hide was already called previously), you send the event
Get latest updates about Open Source Projects, Conferences and News.