path: root/src/lib/ecore_x/ecore_x.c (follow)
Commit message (Collapse)AuthorAgeFilesLines
* ecore_x: init XEvents before passing to xMarcel Hollerbach2017-08-011-8/+8
| | | | | | | | | | | | | | | | it turns out that xlib is going to copy the complete struct into something internal. This might lead to the condition that a uninitalized value might be part of the struct, and when later the struct is read again the code might do wrong stuff since that value could be set now to a randomly other meaningfull value. This turned out on me in e as i could not write any letters like ßöäü, since that lead to a not returning call to _XReply internal of xlib. Dugging that showed that xlib was waiting on a reply of a call that never got executed, and the XEvent it is waiting on just contians a randomly correct value. @fix
* ecore_x: avoid crash during shutdown due to Ecore_Event queue.Cedric BAIL2017-03-091-0/+62
* remove xcb support in ecore_x and evas engines as per mailing listCarsten Haitzler (Rasterman)2016-11-031-0/+2499
as per mailing list discussion about dropping xcb support now. it hasn't been complete for a long time, thus not recommented for being turned on. as we are moving to a wayland world xcbmakes even less sense. as agreed, time to clean up a bit and remove a distraction as well as not well tested code. this also updates po's too. @feature