kimcinoo
/
efl
forked from enlightenment/efl
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
efl/src/modules/ecore_evas/engines/wayland/ecore_evas_wayland_private.h

115 lines
3.6 KiB
C
Raw Normal View History

ecore_evas: Make the engines loadable modules Implementing support for loadables modules. It makes the engines been loaded when they are needed. It not breakes the api, so each engine still has its own api. The implementation basically is: * Functions that creates Ecore_Evas, for example ecore_evas_software_x11_new, request to load its module and then get the module's function to create the Ecore_Evas. * The other functions such as \(.*\)_window_get from the Ecore_Evas its interface and then call the appropriate method. * As there is no unified interface to communicate with the engines (not break api problem), all interfaces were declared in ecore_evas_private.h * Now the data necessary for each module is not declared in the Ecore_Evas_Engine structure, instead of this, the struct has a void pointer that is used by the modules. * In this first moment engines as software_x11 and gl_x11 were put together in the same module, but obviously exporting all the things necessary. SVN revision: 80280
2012-12-05 13:15:42 -08:00
#ifndef _ECORE_EVAS_WAYLAND_PRIVATE_H_
ecore-evas-wayland: Minor formatting fix NB: No functional changes, just formatting Signed-off-by: Chris Michael <cp.michael@samsung.com>
2016-12-02 11:00:04 -08:00
# define _ECORE_EVAS_WAYLAND_PRIVATE_H_
ecore_evas: Make the engines loadable modules Implementing support for loadables modules. It makes the engines been loaded when they are needed. It not breakes the api, so each engine still has its own api. The implementation basically is: * Functions that creates Ecore_Evas, for example ecore_evas_software_x11_new, request to load its module and then get the module's function to create the Ecore_Evas. * The other functions such as \(.*\)_window_get from the Ecore_Evas its interface and then call the appropriate method. * As there is no unified interface to communicate with the engines (not break api problem), all interfaces were declared in ecore_evas_private.h * Now the data necessary for each module is not declared in the Ecore_Evas_Engine structure, instead of this, the struct has a void pointer that is used by the modules. * In this first moment engines as software_x11 and gl_x11 were put together in the same module, but obviously exporting all the things necessary. SVN revision: 80280
2012-12-05 13:15:42 -08:00
ecore-evas-wayland: Minor formatting fix NB: No functional changes, just formatting Signed-off-by: Chris Michael <cp.michael@samsung.com>
2016-12-02 11:00:04 -08:00
# ifdef HAVE_CONFIG_H
# include "config.h"
# endif
ecore_evas: Make the engines loadable modules Implementing support for loadables modules. It makes the engines been loaded when they are needed. It not breakes the api, so each engine still has its own api. The implementation basically is: * Functions that creates Ecore_Evas, for example ecore_evas_software_x11_new, request to load its module and then get the module's function to create the Ecore_Evas. * The other functions such as \(.*\)_window_get from the Ecore_Evas its interface and then call the appropriate method. * As there is no unified interface to communicate with the engines (not break api problem), all interfaces were declared in ecore_evas_private.h * Now the data necessary for each module is not declared in the Ecore_Evas_Engine structure, instead of this, the struct has a void pointer that is used by the modules. * In this first moment engines as software_x11 and gl_x11 were put together in the same module, but obviously exporting all the things necessary. SVN revision: 80280
2012-12-05 13:15:42 -08:00
ecore-evas-wayland: Minor formatting fix NB: No functional changes, just formatting Signed-off-by: Chris Michael <cp.michael@samsung.com>
2016-12-02 11:00:04 -08:00
# define ECORE_EVAS_INTERNAL
ecore_evas: Register direct input cb from modules If the ecore_evas modules were using ecore_event_window_register() then they can also redirect everything though the direct callback instead.
2016-05-10 21:29:23 -07:00
ecore-evas-wayland: Minor formatting fix NB: No functional changes, just formatting Signed-off-by: Chris Michael <cp.michael@samsung.com>
2016-12-02 11:00:04 -08:00
# ifndef ELEMENTARY_H
ecore_evas: Make the engines loadable modules Implementing support for loadables modules. It makes the engines been loaded when they are needed. It not breakes the api, so each engine still has its own api. The implementation basically is: * Functions that creates Ecore_Evas, for example ecore_evas_software_x11_new, request to load its module and then get the module's function to create the Ecore_Evas. * The other functions such as \(.*\)_window_get from the Ecore_Evas its interface and then call the appropriate method. * As there is no unified interface to communicate with the engines (not break api problem), all interfaces were declared in ecore_evas_private.h * Now the data necessary for each module is not declared in the Ecore_Evas_Engine structure, instead of this, the struct has a void pointer that is used by the modules. * In this first moment engines as software_x11 and gl_x11 were put together in the same module, but obviously exporting all the things necessary. SVN revision: 80280
2012-12-05 13:15:42 -08:00
//#define LOGFNS 1
ecore-evas-wayland: Minor formatting fix NB: No functional changes, just formatting Signed-off-by: Chris Michael <cp.michael@samsung.com>
2016-12-02 11:00:04 -08:00
# ifdef LOGFNS
# include <stdio.h>
remove arguments of LOGFN in ecore_wayland modules as the are always the same Reviewers: raster, devilhorns Reviewed By: devilhorns Subscribers: devilhorns, cedric, #reviewers, #committers Tags: #efl Differential Revision: https://phab.enlightenment.org/D11777
2020-05-06 06:18:31 -07:00
# define LOGFN \
printf("-ECORE_EVAS-WL: %25s: %5i - %s\n", __FILE__, __LINE__, __func__)
ecore-evas-wayland: Minor formatting fix NB: No functional changes, just formatting Signed-off-by: Chris Michael <cp.michael@samsung.com>
2016-12-02 11:00:04 -08:00
# else
remove arguments of LOGFN in ecore_wayland modules as the are always the same Reviewers: raster, devilhorns Reviewed By: devilhorns Subscribers: devilhorns, cedric, #reviewers, #committers Tags: #efl Differential Revision: https://phab.enlightenment.org/D11777
2020-05-06 06:18:31 -07:00
# define LOGFN
ecore-evas-wayland: Minor formatting fix NB: No functional changes, just formatting Signed-off-by: Chris Michael <cp.michael@samsung.com>
2016-12-02 11:00:04 -08:00
# endif
# include <Eina.h>
# include <Ecore.h>
# include <Ecore_Input.h>
# include <Ecore_Input_Evas.h>
# include <Ecore_Wl2.h>
# include <Ecore_Evas.h>
# endif
ecore_wl2: Move ecore_wl2_window_rotation_change functions to be internal These functions are not used in efl wayland clients nor are they used in Enlightenment. As such, there is no reason that they need to be public API so this commit moves them to be Internal and updates Ecore_Evas engine code to include the internal header. ref T8013
2019-08-06 05:36:50 -07:00
# include "ecore_wl2_internal.h"
ecore-evas-wayland: Minor formatting fix NB: No functional changes, just formatting Signed-off-by: Chris Michael <cp.michael@samsung.com>
2016-12-02 11:00:04 -08:00
# include "ecore_wl2_private.h"
# include "ecore_private.h"
# include "ecore_evas_private.h"
# include "ecore_evas_wayland.h"
ecore_evas: Make the engines loadable modules Implementing support for loadables modules. It makes the engines been loaded when they are needed. It not breakes the api, so each engine still has its own api. The implementation basically is: * Functions that creates Ecore_Evas, for example ecore_evas_software_x11_new, request to load its module and then get the module's function to create the Ecore_Evas. * The other functions such as \(.*\)_window_get from the Ecore_Evas its interface and then call the appropriate method. * As there is no unified interface to communicate with the engines (not break api problem), all interfaces were declared in ecore_evas_private.h * Now the data necessary for each module is not declared in the Ecore_Evas_Engine structure, instead of this, the struct has a void pointer that is used by the modules. * In this first moment engines as software_x11 and gl_x11 were put together in the same module, but obviously exporting all the things necessary. SVN revision: 80280
2012-12-05 13:15:42 -08:00
typedef struct _Ecore_Evas_Engine_Wl_Data Ecore_Evas_Engine_Wl_Data;
ecore_evas: introduce wayland support for cnp & dnd This adds cnp support, actions are right now only mapped to "ask", further support can be added there, and synchronization can be added to register more available actions. However, i did not find *any* wayland implementation in gtk qt nor chromiumos that even use the action to indicate anything. This here also has a slightly different behaviour to X11 in terms of coordinates for motion,leave,enter. They can contain negative coordinates (which is due to the fact that wl is CSD and X11 is SSD. However, I did not want to fix this in any regard, as you might want to use that, and it would be a none trivial amount of code to fix that. Reviewed-by: Chris Michael <cp.michael@samsung.com> Reviewed-by: Mike Blumenkrantz <michael.blumenkrantz@gmail.com> Differential Revision: https://phab.enlightenment.org/D11329
2020-02-10 00:20:18 -08:00
typedef struct _Ecore_Evas_Wl_Selection_Data Ecore_Evas_Wl_Selection_Data;
struct _Ecore_Evas_Wl_Selection_Data
{
Ecore_Evas_Selection_Callbacks callbacks;
Eina_Promise *delivery;
Ecore_Wl2_Offer *offer;
const char *later_convert;
uint32_t sent_serial; //The serial of the last sent selection op
};
evas: document the wayland ecore_evas constructors Reviewers: cedric Subscribers: jpeg Differential Revision: https://phab.enlightenment.org/D4896 Signed-off-by: Cedric BAIL <cedric@osg.samsung.com>
2017-06-05 11:06:36 -07:00
struct _Ecore_Evas_Engine_Wl_Data
Fix formatting. Signed-off-by: Christopher Michael <cp.michael@samsung.com>
2013-02-05 04:48:25 -08:00
{
ecore-wl2: Port Ecore_Evas engines to use Ecore_Wl2 code Signed-off-by: Chris Michael <cp.michael@samsung.com>
2015-09-28 10:42:38 -07:00
Ecore_Wl2_Display *display;
wayland: implement session recovery add support for reconnecting wayland applications if the compositor dies disconnect -> destroy gl ctx + image textures -> block rendering -> reconnect -> create gl ctx -> create image textures -> unblock rendering -> sprinkle special seasoning on top -> just like ma used to make #SamsungFeatures @feature
2016-05-05 07:45:59 -07:00
Eina_List *regen_objs;
ecore-wl2: Port Ecore_Evas engines to use Ecore_Wl2 code Signed-off-by: Chris Michael <cp.michael@samsung.com>
2015-09-28 10:42:38 -07:00
Ecore_Wl2_Window *parent, *win;
ecore_evas: introduce wayland support for cnp & dnd This adds cnp support, actions are right now only mapped to "ask", further support can be added there, and synchronization can be added to register more available actions. However, i did not find *any* wayland implementation in gtk qt nor chromiumos that even use the action to indicate anything. This here also has a slightly different behaviour to X11 in terms of coordinates for motion,leave,enter. They can contain negative coordinates (which is due to the fact that wl is CSD and X11 is SSD. However, I did not want to fix this in any regard, as you might want to use that, and it would be a none trivial amount of code to fix that. Reviewed-by: Chris Michael <cp.michael@samsung.com> Reviewed-by: Mike Blumenkrantz <michael.blumenkrantz@gmail.com> Differential Revision: https://phab.enlightenment.org/D11329
2020-02-10 00:20:18 -08:00
Ecore_Event_Handler *sync_handler, *changed_handler, *end_handler, *send_handler, *offer_handler, *dnd_leave_handler, *dnd_motion_handler, *dnd_enter_handler, *dnd_drop_handler, *dnd_end_handler;
ecore_evas/wayland: Implement borderless_set engine method. It is needed to set the engine internal borderless property. Also update the border (frame) object, showing/hiding it as needed, and updating the framespace size when the frame object is handled by the engine.
2013-05-08 15:18:55 -07:00
int fx, fy, fw, fh;
wayland: Tick like a boss Instead of the clever but awful manual_render_set hack, actually do ticks based on frame callbacks. Fix T5850
2017-08-18 12:13:11 -07:00
Ecore_Wl2_Frame_Cb_Handle *frame;
ecore-evas wayland: use www protocol when available handle www protocol events and store the provided data into engine data Signed-off-by: Derek Foreman <derekf@osg.samsung.com>
2016-03-24 10:44:21 -07:00
int x_rel;
int y_rel;
uint32_t timestamp;
ecore_evas/wayland: handle added / removed seats Create or delete evas_devices with class EVAS_DEVICE_CLASS_SEAT for seats on each ecore_evas created so far. Initially it's named considering its Wayland id.
2016-10-03 08:34:10 -07:00
Eina_List *devices_list;
ecore-evas-wayland: rework window hint calcs to be more accurate this is still pretty broken for some directions, client-side aspect fml
2017-08-04 13:17:53 -07:00
int cw, ch;
ecore_evas: introduce wayland support for cnp & dnd This adds cnp support, actions are right now only mapped to "ask", further support can be added there, and synchronization can be added to register more available actions. However, i did not find *any* wayland implementation in gtk qt nor chromiumos that even use the action to indicate anything. This here also has a slightly different behaviour to X11 in terms of coordinates for motion,leave,enter. They can contain negative coordinates (which is due to the fact that wl is CSD and X11 is SSD. However, I did not want to fix this in any regard, as you might want to use that, and it would be a none trivial amount of code to fix that. Reviewed-by: Chris Michael <cp.michael@samsung.com> Reviewed-by: Mike Blumenkrantz <michael.blumenkrantz@gmail.com> Differential Revision: https://phab.enlightenment.org/D11329
2020-02-10 00:20:18 -08:00
Ecore_Evas_Wl_Selection_Data selection_data[ECORE_EVAS_SELECTION_BUFFER_LAST];
Ecore_Wl2_Offer *external_offer;
ecore-evas-wl: Add support for Window Manager rotations This patch adds support to Ecore_Evas_Wayland for Window Manager Rotations so that window managers which do support rotations are able to rotate an EFL wayland application. @feature Signed-off-by: Chris Michael <cp.michael@samsung.com>
2017-06-09 08:06:05 -07:00
struct
{
Eina_Bool supported : 1;
Eina_Bool prepare : 1;
Eina_Bool request : 1;
Eina_Bool done : 1;
Eina_Bool configure_coming : 1;
Ecore_Job *manual_mode_job;
} wm_rot;
ecore-evas-wayland: rework window hint calcs to be more accurate this is still pretty broken for some directions, client-side aspect fml
2017-08-04 13:17:53 -07:00
Eina_Bool resizing : 1;
ecore-evas wayland: use www protocol when available handle www protocol events and store the provided data into engine data Signed-off-by: Derek Foreman <derekf@osg.samsung.com>
2016-03-24 10:44:21 -07:00
Eina_Bool dragging : 1;
ecore-evas-wl: Defer creating surfaces for wayland canvas This code adds support for deferring of surface creation and showing inside Ecore_Evas Wayland. This is needed for Enlightenment so that it does not try to create or show surfaces until the compositor has had a chance to sync globals. This fixes an issue where early surface creation would cause a crash in the compositor due to globals not being syncd. @fix Signed-off-by: Chris Michael <cp.michael@samsung.com>
2015-12-11 08:26:24 -08:00
Eina_Bool sync_done : 1;
Eina_Bool defer_show : 1;
wayland: implement session recovery add support for reconnecting wayland applications if the compositor dies disconnect -> destroy gl ctx + image textures -> block rendering -> reconnect -> create gl ctx -> create image textures -> unblock rendering -> sprinkle special seasoning on top -> just like ma used to make #SamsungFeatures @feature
2016-05-05 07:45:59 -07:00
Eina_Bool reset_pending : 1;
wayland: use shell activated state to indicate focus in csd the current (v6) xdg-shell spec reads as follows: Client window decorations should be painted as if the window is active. Do not assume this means that the window actually has keyboard or pointer focus. so this is not equivalent to receiving/losing input focus and should not be propagated as such @fix
2017-05-17 13:02:53 -07:00
Eina_Bool activated : 1;
wayland: Tick like a boss Instead of the clever but awful manual_render_set hack, actually do ticks based on frame callbacks. Fix T5850
2017-08-18 12:13:11 -07:00
Eina_Bool ticking : 1;
ecore_evas: Make the engines loadable modules Implementing support for loadables modules. It makes the engines been loaded when they are needed. It not breakes the api, so each engine still has its own api. The implementation basically is: * Functions that creates Ecore_Evas, for example ecore_evas_software_x11_new, request to load its module and then get the module's function to create the Ecore_Evas. * The other functions such as \(.*\)_window_get from the Ecore_Evas its interface and then call the appropriate method. * As there is no unified interface to communicate with the engines (not break api problem), all interfaces were declared in ecore_evas_private.h * Now the data necessary for each module is not declared in the Ecore_Evas_Engine structure, instead of this, the struct has a void pointer that is used by the modules. * In this first moment engines as software_x11 and gl_x11 were put together in the same module, but obviously exporting all the things necessary. SVN revision: 80280
2012-12-05 13:15:42 -08:00
};
evas: document the wayland ecore_evas constructors Reviewers: cedric Subscribers: jpeg Differential Revision: https://phab.enlightenment.org/D4896 Signed-off-by: Cedric BAIL <cedric@osg.samsung.com>
2017-06-05 11:06:36 -07:00
/**
* @brief Create an Ecore_Evas window using a Wayland-based engine.
*
* @param disp_name Name of the Wayland display to connect to.
* @param parent ID of the parent window this Ecore_Evas window belongs
* to, or 0 if this is a top-level window.
* @param x Horizontal position of the Ecore_Evas window.
* @param y Vertical position of the Ecore_Evas window.
* @param w Width of the Ecore_Evas window to be created.
* @param h Height of the Ecore_Evas window to be created.
* @param frame Deprecated. (Just pass EINA_FALSE.)
ecore wayland: expand internal interface to pass engine option list. This is a prepartion patch to support msaa in wayland. ui window needs to deliver engine options (stencil, depth, msaa bits) to evas engine side, ecore_evas_wayland_egl should have the argument to pass.
2019-04-25 00:56:40 -07:00
* @param opt engine option list
evas: document the wayland ecore_evas constructors Reviewers: cedric Subscribers: jpeg Differential Revision: https://phab.enlightenment.org/D4896 Signed-off-by: Cedric BAIL <cedric@osg.samsung.com>
2017-06-05 11:06:36 -07:00
* @param engine_name Wayland engine to use for rendering.
* @return Ecore_Evas instance or @c NULL if creation failed.
*
* Like Evas' other window creation routines, this constructs an
* Ecore_Evas window object using an engine name and various common
* parameters. However, this connects to the display using a Wayland
* protocol for client-server communication rather than the X11
* protocol.
*
* Also, Wayland uses a direct rendering model that permits clients to
* do their own rendering and share it using one of a range of buffer
* sharing alternatives. The caller of this routine must specify which
* @p engine_name to use (e.g. @c "wayland_egl" or @c "wayland_shm").
*
* @see ecore_evas_new()
* @see ecore_evas_wayland_shm_new()
* @see ecore_evas_wayland_egl_new()
*/
ecore wayland: expand internal interface to pass engine option list. This is a prepartion patch to support msaa in wayland. ui window needs to deliver engine options (stencil, depth, msaa bits) to evas engine side, ecore_evas_wayland_egl should have the argument to pass.
2019-04-25 00:56:40 -07:00
Ecore_Evas *_ecore_evas_wl_common_new_internal(const char *disp_name, Ecore_Window parent, int x, int y, int w, int h, Eina_Bool frame, const int *opt, const char *engine_name);
ecore_evas_wayland: Minimize differences between shm and egl Finally bring these together as much as possible to avoid future diversions when bugs are only fixed in one or the other. There are functional changes - state tracking for client side effects is now added to the shm engine, some bug fixes for the egl engine have been brought to the shm engine.
2016-11-02 11:13:07 -07:00
ecore_evas: Make the engines loadable modules Implementing support for loadables modules. It makes the engines been loaded when they are needed. It not breakes the api, so each engine still has its own api. The implementation basically is: * Functions that creates Ecore_Evas, for example ecore_evas_software_x11_new, request to load its module and then get the module's function to create the Ecore_Evas. * The other functions such as \(.*\)_window_get from the Ecore_Evas its interface and then call the appropriate method. * As there is no unified interface to communicate with the engines (not break api problem), all interfaces were declared in ecore_evas_private.h * Now the data necessary for each module is not declared in the Ecore_Evas_Engine structure, instead of this, the struct has a void pointer that is used by the modules. * In this first moment engines as software_x11 and gl_x11 were put together in the same module, but obviously exporting all the things necessary. SVN revision: 80280
2012-12-05 13:15:42 -08:00
#endif /* _ECORE_EVAS_WAYLAND_PRIVATE_H_ */