mappings change (xmodmap or kbd layout change).
fix other events to have proper eina_bool too and enums
also remove already disabled old unimplemented events commented out.
SVN revision: 53942
when trying to free the mode_info. Not much functional difference with
this commit except that we do not call strndup if the nameLength is
<= 0.
SVN revision: 53477
Bad cedric, no cookie for you! While merging r39505 introducing
Ecore_Input you had all the code to go through Xutf8LookupString(),
but its documentation says (man Xutf8LookupString):
{{{
Note
®To ensure proper input processing, it is essential that the
client pass only KeyPress events to XmbLookupString,
XwcLookupString and Xutf8LookupString. Their behavior when a
client passes a KeyRelease event is undefined.
}}}
Yeah, Xlib is quite stupid and this makes no sense.
As this just happens for UP events, it was unnoticed for a long time
(19 months) as most apps just handle DOWN events, as it gets X
keyboard repetition and all.
Thanks to Otavio Pontes that spotted this bug while doing some code
for EPhoto (that for some weird reason uses UP instead of DOWN
events).
SVN revision: 52786
Please review it. i don't have the courage to read
everything again
It should compile on linux (committed from windows, but
corrected at the same time on linux. Thank you, VirtualBox
devs !)
SVN revision: 52784
Essentially the problem is this: For drag and drop Ecore currently handles the
position update calls. But usually the application wants to display some user
feedback - a window to display the drag selection for instance.
Now the way e17 does it is grab the mouse cursor movements and track them
itself. However ecore is already doing this, it's already walking window
trees, calculating real positions, _and_ sending them in an X client message.
So it seems rather silly to duplicate the code in the user app to get the same
info.
We could possibly have added a new event, but then we need to deal the fact
the position update may arrive _After_ the item has been dropped. Hilarity
ensures[1].
This callback is meant for purely the selection owner of the drag to use, so
it is a callback set, not an add.
[1] Segfaults probably. Nothing funnier.
SVN revision: 52181
Apply badzero.cocci, badnull.coci and badnull2.cocci
This should convert all cases where there's a comparison to NULL to simpler
forms. This patch applies the following transformations:
code before patch ||code after patch
===============================================================
return a == NULL; return !a;
return a != NULL; return !!a;
func(a == NULL); func(!a);
func(a != NULL); func(!!a);
b = a == NULL; b = !a;
b = a != NULL; b = !!a;
b = a == NULL ? c : d; b = !a ? c : d;
b = a != NULL ? c : d; b = a ? c : d;
other cases:
a == NULL !a
a != NULL a
SVN revision: 51487
Carsten Haitzler
Cedric BAIL
Gustavo Sverzut Barbieri
Eduardo de Barros Lima
Kim Woelders
Christopher Michael
Mike Blumenkrantz
Iván Briano
Vincent Torri
Bruno Dilly
Brett Nash
Lucas De Marchi
Sebastian Dransfeld
Leif Middelschulte