path: root/src/lib/ecore_wayland (follow)
AgeCommit message (Collapse)Author
2015-07-14ecore-wl: Reset input keyboard repeat values when we cancel the timerChris Michael
Summary: If we end up cancelling the keyboard repeat timer due to no focused surface, we should also reset the input repeat values. @fix Signed-off-by: Chris Michael <>
2015-07-14ecore-wl: Don't renew keyboard-repeat timer if we have no focused surfaceChris Michael
Summary: During the keyboard repeat function, if we have no keyboard focused window to send the key to, then we should cancel the repeat timer. @fix Signed-off-by: Chris Michael <>
2015-07-14ecore-wl: Reset ecore_wl_input repeat values on keyboard leaveChris Michael
Summary: As we delete any keyboard repeat timers when we get a keyboard leave event, we should also reset any stored values there (key, sym, time, etc). @fix Signed-off-by: Chris Michael <>
2015-07-14ecore-wl: Reset input's pointer & keyboard focus on eventsChris Michael
Summary: If we get pointer or keyboard leave events, then reset the Ecore_Wl_Input's idea of focus (eg: set input->pointer_focus and input->keyboard_focus fields to NULL) just in case we cannot find a window for this surface. @fix Signed-off-by: Chris Michael <>
2015-07-08ecore-wayland: Remove improper use of EINA_UNUSEDChris Michael
Summary: 'version' is actually used inside this function so no need for EINA_UNUSED here. @fix Signed-off-by: Chris Michael <>
2015-07-01ecore-wl: disable session recoveryMike Blumenkrantz
this is guaranteed to crash in 100% of use cases.
2015-06-29Revert "ecore-input: add keysym to Ecore_Event_Key struct"Mike Blumenkrantz
This reverts commit c3f3c4eba80f0a7f388de608f2b1566213e73603. this was audited and found to be impractical due to portability concerns
2015-06-29ecore_wl: Hookup wl listener for uuid event from session recovery protocolStefan Schmidt
This should listen for events containing the assigned UUID from the compositor.
2015-06-29ecore_wl: Add generated session-recovery-protocol files to buildStefan Schmidt
For now these are generated externally by wayland-scanner and added here. Also keep the original xml protocol file here for now. This covers the client side for applications while the server side code sits with E as compositor.
2015-06-25Revert "ecore-wayland: Update xdg shell protocol file"Chris Michael
This reverts commit 5793a62fc839af489263c918b78adb7765f8566d. Reverted due to wrong version being pushed
2015-06-25ecore-wayland: Update xdg shell protocol fileChris Michael
Summary: This was a file that should have been updated with the bump to xdg_shell version 5 however it was not pushed with that update. @fix Signed-off-by: Chris Michael <>
2015-06-23ecore-wayland: Fix issue of events not getting dispatched properlyChris Michael
Summary: In order for wayland events to be processed properly, we should be dispatching any pending events off of the queue First before we make the call to flush. @fix Signed-off-by: Chris Michael <>
2015-06-08ecore-wayland: Fix T2466: Update xdg shell protocol codeChris Michael
Summary: This updates the xdg_shell protocol and code to support XDG_SHELL version 5. This allows EFL/Elm apps to function again in Weston. @fix Signed-off-by: Chris Michael <>
2015-05-21ecore-wl: Remove +x from ecore_wl_input.cChris Michael
Summary: Unsure how this file mode got changed, but it should not be +x. @fix Signed-off-by: Chris Michael <>
2015-05-20ecore-input: add keysym to Ecore_Event_Key structMike Blumenkrantz
currently only functional for x11, wl, drm @feature
2015-05-20ecore-wl: Set keycode in event structure for key down/upChris Michael
Summary: When we generate an Ecore key down/up event, we should also be setting the keycode in the event structure @fix Signed-off-by: Chris Michael <>
2015-05-12ecore-wayland: Input grab_count is unsigned int, no need for comparison < 0Chris Michael
Summary: As input->grab_count is an unsigned int there is no need for the < 0 comparison as that will always return false @fix Signed-off-by: Chris Michael <>
2015-05-12ecore-wayland: Add a grab_count variable for synchronization ↵jhyuni.kang
wl_input_grab/ungrab with pointer and touch event Summary: The touch screen device generates touch events. But in some special enviroments, a first finger will be matched to a pointer event(not touch event). And other fingers (second, third, ...) will be matched touch events. In that case ecore_wl_input_ungrab() is called abnormally. A first finger pressed, _ecore_wl_input_cb_pointer_button() call ecore_wl_input_grab(). A second finger pressed, _ecore_wl_input_cb_touch_down() is called but not grab. But when a second finger is released, _ecore_wl_input_cb_touch_up() call ecore_wl_input_ungrab() So ungrab function generate two mouse up events and a first finger is released. In other case, first finger pressed -> second finger pressed -> first finger release. That case when a first finger released a second finger release event is generated. So after that application doesn't get a release event about a second finger when a second finger is really released. I think in a multitouch case, ungrab function will be called when a all finger are released. So I add a grab_count variable for count currently touched fingers. And only called a ungrab funtion all fingers are released. Test Plan: In a touch screen supported multitouch, press two or more fingers and release. And watch events generation. Reviewers: raster, devilhorns Subscribers: cedric Differential Revision:
2015-05-11ecore_wl: get dpi after all pending events are handledBoram Park
Summary: ecore_wl_dpi_get will return the correct value after wl_output's events are handled Reviewers: zmike, devilhorns, bryceharrington Subscribers: cedric Differential Revision:
2015-05-07Check a key repeat using xkb ruled keycodejhyuni.kang
Summary: ecore_wayland get a key information using libxkbcommon's functions. Also generate key repeat check xkb keymap's information using xkb_keymap_key_repeats(). But xkb rules reflect X broken keycodes, so offset by 8. In ecore_wayland backend, other xkb funtions using offset keycode but only use default keycode to check key repeat. So I fix it to use xkb ruled keycode. Test Plan: Long press a key and watch repeated key events generate well Reviewers: devilhorns, raster Subscribers: cedric Differential Revision:
2015-05-07ecore: remove the need to order the header correctly for Windows.Cedric BAIL
2015-04-27ecore-wayland: Fix issue of efl/elm apps not setting opaque & input regionsChris Michael
Summary: Since evas handles surface damage & surface commit roles now, we no longer are calling ecore_wl_commit inside ecore_evas. This was causing the surface opaque & input regions to no longer be set. We fix that here by creating and setting opaque/input regions whenever the appropriate ecore_wl region functions are called. @fix Signed-off-by: Chris Michael <>
2015-04-27ecore-wl: reject key events which do not correlate to a valid keysymMike Blumenkrantz
2015-03-25Ecore: Use calloc() to initialize Ecore_Event_Key fullyJean-Philippe ANDRE
Some fields (eg. data) may not be properly initialized. Use calloc() instead of malloc() will ensure proper initialization even if we add more fields. These fields (data) would even be passed down to Evas as Evas_Event_Key_Down for instance.
2015-03-21Wayland: Fix compilationJean-Philippe ANDRE
Bad merge?
2015-03-20ecore_wayland: Check for nulls before wayland callsBryce Harrington
Summary: Wayland API routines by policy do not check input parameters for invalid values. In particular, many calls are wrappers through wl_proxy_marshal, which derefs its first argument without a check. So, for all wayland calls, always null check the first argument. Reviewers: zmike, cedric Subscribers: cedric Differential Revision:
2015-03-20ecore_wayland: Check for null inputsBryce Harrington
Summary: The other functions in this module check inputs; this one should as well. Reviewers: zmike Subscribers: cedric Differential Revision:
2015-03-20ecore_wayland: Add some commentsBryce Harrington
Summary: Signed-off-by: Bryce Harrington <> Reviewers: zmike Subscribers: cedric Differential Revision:
2015-03-17ecore-wayland: Use calloc rather than malloc+memsetBryce Harrington
Summary: In addition to being fewer lines of code, malloc + memset to 0 is slower than calloc. See Signed-off-by: Bryce Harrington <> Reviewers: zmike, cedric, devilhorns Reviewed By: devilhorns Subscribers: cedric Differential Revision:
2015-03-17ecore-wayland: Doublecheck input validityBryce Harrington
Summary: Most of the other ecore-wayland API will return NULL in the (hopefully theoretical) case of bad inputs; this API routine should so similarly for consistency. Reviewers: zmike, cedric Subscribers: cedric Differential Revision:
2015-03-17ecore_wayland: Improve API docsBryce Harrington
Summary: For calls that return pointers, specify that NULL is a potential return value. Add API documentation for some misc. routines missing it. Reviewers: zmike, cedric, devilhorns Subscribers: cedric Differential Revision:
2015-03-13ecore-wayland: Whitespace cleanupBryce Harrington
Summary: Remove trailing whitespace, convert tabs to spaces as per style guide. Reviewers: zmike Subscribers: cedric Differential Revision:
2015-03-13ecore-wl dnd target interface should accept a NULL mime_typeMike Blumenkrantz
according to protocol, this indicates that the target does not support the drop type
2015-03-13ecore-wl xdg surface configure no longer requires special case for fs/maxMike Blumenkrantz
the surface size comes directly from the compositor shell when applicable
2015-03-12ecore-wl now allocates cursor_theme_name struct member of Ecore_Wl_InputMike Blumenkrantz
previous behavior would result in invalid memory access if the externally-passed string were ever deallocated @fix
2015-03-12ecore-wl use calloc for Ecore_Wl_Input allocation instead of malloc+memsetMike Blumenkrantz
2015-03-12ecore-wl cursor setup no longer triggers errors on startupMike Blumenkrantz
@fix T2202
2015-03-12ecore-wl now prints an error when the socket diesMike Blumenkrantz
2015-03-10ecore-wayland: don't resize the window on focusDerek Foreman
Reviewers: devilhorns, zmike Subscribers: cedric Differential Revision:
2015-03-04ecore-wl windows now emit 0x0 configure sizes more reliably when fs/maximizedMike Blumenkrantz
2015-03-04ecore-wl update window saved.size on any resize instead of just fs/maximizeMike Blumenkrantz
2015-03-02ecore-wl: Send xdg_surface_set_window_geometry when we update windowChris Michael
size/position Summary: We should be implementing xdg_surface_set_window_geometry for efl apps, so this commit adds the function call to that. @fix Signed-off-by: Chris Michael <>
2015-02-26ecore-wl fullscreen state is based on either window type or attributeMike Blumenkrantz
fixes fullscreen state detection when being set to fullscreen by the compositor @fix
2015-02-03ecore-wayland: Don't send key repeat events for keys which should notChris Michael
get them Summary: Some keys in certain keyboard layouts should not be repeated so add a test which uses xkb to inform us if this key supports repeating. @fix Signed-off-by: Chris Michael <>
2015-02-01ecore-wl should maybe clear its repeat timer for keyboard on window freeMike Blumenkrantz
2015-01-23ecore-wayland: Don't send a mouse_up on grab release unless weChris Michael
actually have a grabbed button Summary: If we don't have an actual grabbed mouse button, then don't send a mouse up event. Caught this while adding e_grabinput support to Enlightenment. @fix Signed-off-by: Chris Michael <>
2015-01-20ecore-wl needs to also set xdg props again on showMike Blumenkrantz
fix T1819
2015-01-16ecore-wayland: Don't crash if we have no input->cursor_nameChris Michael
Summary: If we are using a touchscreen, there will be no pointer and thus no cursor_name to use. Trap for that case by checking if input->cursor_name is valid. @fix Signed-off-by: Chris Michael <>
2015-01-13ecore-wayland: Fix issue with Elementary DnD test not releasing mouseChris Michael
Summary: When we do an input_ungrab, we should be sending a mouse up event so that apps/elm/etc know that the mouse has been released. This fixes an issue in the Elm Features DnD test report by Daniel Zaoui @fix Signed-off-by: Chris Michael <>
2015-01-13ecore-wayland: Don't set move cursor unless we actually start a dragChris Michael
Summary: We should not be setting a 'move' cursor unless we actually make the call to start a drag @fix Signed-off-by: Chris Michael <>