RE: Window mapping/hang problem with SWT-GTK-DirectFB

[Rauch Sam-ra8883 <Sam Rauch motorola com>]

Thanks for the info - This brings up an alternative solution that only affects the linux-fb and directfb binding layers (not core gtk code).  Would it be correct to fix this issue in those binding layers by changing the GDK_MAP entry in the type_masks declaration from GDK_VISIBILITY_NOTIFY_MASK to GDK_STRUCTURE_MASK?

Entry 14 in type_masks[] for gdk/linux-fb/gdkmain-fb.c and gdk/directfb/gdkmain-directfb.c would change from:
    GDK_VISIBILITY_NOTIFY_MASK, /* GDK_MAP = 14, */
to:
    GDK_STRUCTURE_MASK,         /* GDK_MAP = 14, */

(and probably the same for GDK_UNMAP?)

Regards,

-Sam

-----Original Message-----
From: Federico Mena Quintero [mailto:federico ximian com] 
Sent: Monday, May 24, 2004 5:35 PM
To: Rauch Sam-ra8883
Cc: gtk-devel-list gnome org
Subject: Re: Window mapping/hang problem with SWT-GTK-DirectFB


On Thu, 2004-05-20 at 23:03 -0700, Rauch Sam-ra8883 wrote:

[snip]   
> 3) The DirectFB-GDK binding code sending GDK_MAP events to any window  
> that gets mapped, regardless of the event_mask field. (in  
> gdkwindow-directfb.c:send_map_events(), event_win would have to be set  
> by some other means than the current gdk_directfb_other_event_window()  
> call).  This seems the most like the X11 behavior, but it doesn't feel  
> right given the event_mask field.

X11 sends MapNotify events to windows which have the StructureMask or SubstructureMask set in their event mask; they don't have anything to do with VisibilityNotifyMask.  Perhaps the directfb backend should do the same.

Note that GtkWindow *does* include GDK_STRUCTURE_MASK in its realize method.

  Federico