Page MenuHomePhabricator

ecore_wayland: check ecore_evas_activate feature to work well in wayland 2
Closed, ResolvedPublic

Description

ecore_evas_activate API .

like _ecore_evas_x_activate API, we need to _ecore_evas_wl_common_activate work well in wayland 2.

@devilhorns
in tizen, ECORE_WL_WINDOW_ACTIVATE/DEACTIVATE event exist, but I think we don't need this event anymore (but I'm not sure).
would you discuss this event can be removed with philippe.coval?

Usecase: backward compatability.

If the task was alredy implemented, we will close this task.(To check that the task is alredy implement can be task)
jypark created this task.Jul 23 2017, 7:55 PM
jypark updated the task description. (Show Details)Jul 23 2017, 7:58 PM
jypark added a subscriber: boram1288.
zmike added a comment.Jul 25 2017, 5:53 AM

Yes, this was added to upstream wl2 recently and I think it should be removed; there is already a window configure event (Ecore_Wl2_Event_Window_Configure) which is emitted at any point when the activate state can be changed. There is now the ecore_wl2_window_activated_get() function which can be used at any point to check if the window is active.

zmike closed this task as Resolved.Jul 25 2017, 5:53 AM
zmike added a comment.Jul 25 2017, 5:56 AM

Also in Wayland there is no method (other than a popup grab) to perform the same functionality as ecore_evas_activate. The window's 'active' state just means to draw the decorations as though the window is active, but I think you are talking about 'focus', which is determined by keyboard/pointer enter. As this is a hardware state, it is not able to be manipulated by clients.