[Xcb] client message event strangeness

[Barton C Massey]

Sounds like memory has gotten trashed somewhere.  Post your
whole source for the failing example, and we'll try to track
down the problem.  I assume you've tried running under
valgrind, fixed all gcc -Wall warnings, etc?

	Bart

In message <Pine.LNX.4.64.0704101903051.14588 at grozny.maths.univ-evry.fr> you wrote:
> 
> Hey,
> 
> I have a strange behavior with ecore_xcb, and another simple xcb prog, 
> btw.
> 
> I want to get the event that is sent when I click on little cross of the 
> title bar (to delete a prog).
> 
> It should be the event #33 (client message). It seems reasonnable, and 
> Xlib sends it.
> 
> Now, with the cursor example (see the tutorial), if I add a printf when an 
> event is found:
> 
> 
>      if (e) {
>        printf ("event : %d\n", e->response_type);
> 
> nothing is displayed (xcb_poll_for_event is used) and the window 
> disappear.
> 
> With ecore_xcb (which is my main concern, actually), I get the event #161, 
> which is strange as X has only a maximum of event number of 35 (LASTEvent 
> in Xlib, which is, btw, not defined in XCB. Has it been forgotten ?)
> 
> Is there a logical explanation of that mess ?
> 
> thank you
> 
> Vincent
> _______________________________________________
> Xcb mailing list
> Xcb at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/xcb