| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | ecore_x: init XEvents before passing to x | Marcel Hollerbach | 2017-08-01 | 1 | -2/+2 |
| | | | | | | | | | | | | | | | | | 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 | ||||
| * | remove xcb support in ecore_x and evas engines as per mailing list | Carsten Haitzler (Rasterman) | 2016-11-03 | 1 | -0/+1929 |
| 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 | |||||
 |
index : delta/enlightenment/efl.git | |
| git.enlightenment.org: core/efl.git |
| summaryrefslogtreecommitdiff |