isa/mutter
1
0
Fork 0
mirror of https://github.com/brl/mutter.git synced 2024-11-24 00:50:42 -05:00
Code Issues Packages Projects Releases Wiki Activity
b45d5ef3f5
mutter/src/wayland/meta-wayland-seat.h

88 lines
3.0 KiB
C
Raw Normal View History

wayland: Add basic input support This copies the basic input support from the Clayland demo compositor. It adds a basic wl_seat implementation which can convert Clutter mouse events to Wayland events. For this to work all of the wayland surface actors need to be made reactive. The wayland keyboard input focus surface is updated whenever Mutter sees a FocusIn event so that it will stay in synch with whatever surface Mutter wants as the focus. Wayland surfaces don't get this event so for now it will just give them focus whenever they are clicked as a hack to test the code. Authored-by: Neil Roberts <neil@linux.intel.com> Authored-by: Giovanni Campagna <gcampagna@src.gnome.org>
2013-05-03 13:51:22 -04:00
/*
* Wayland Support
*
* Copyright (C) 2012 Intel Corporation
*
* This program is free software; you can redistribute it and/or
* modify it under the terms of the GNU General Public License as
* published by the Free Software Foundation; either version 2 of the
* License, or (at your option) any later version.
*
* This program is distributed in the hope that it will be useful, but
* WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with this program; if not, write to the Free Software
* Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA
* 02111-1307, USA.
*/
wayland: Fix header file style
2014-04-22 18:09:38 -04:00
#ifndef META_WAYLAND_SEAT_H
#define META_WAYLAND_SEAT_H
wayland: Add basic input support This copies the basic input support from the Clayland demo compositor. It adds a basic wl_seat implementation which can convert Clutter mouse events to Wayland events. For this to work all of the wayland surface actors need to be made reactive. The wayland keyboard input focus surface is updated whenever Mutter sees a FocusIn event so that it will stay in synch with whatever surface Mutter wants as the focus. Wayland surfaces don't get this event so for now it will just give them focus whenever they are clicked as a hack to test the code. Authored-by: Neil Roberts <neil@linux.intel.com> Authored-by: Giovanni Campagna <gcampagna@src.gnome.org>
2013-05-03 13:51:22 -04:00
#include <wayland-server.h>
Clean up include macros mess The order and way include macros were structured was chaotic, with no real common thread between files. Try to tidy up the mess with some common scheme, to make things look less messy.
2018-07-10 04:36:24 -04:00
#include "clutter/clutter.h"
#include "wayland/meta-wayland-data-device.h"
wayland: Move the primary data device manager to its own file Instead of having everything clumped at MetaWaylandDataManager, split the primary selection to its own struct. This manager is handled separately from wl_data_device_manager and other selection managers, so they would be able to interoperate between them, even. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1193
2020-04-09 11:51:59 -04:00
#include "wayland/meta-wayland-data-device-primary.h"
Clean up include macros mess The order and way include macros were structured was chaotic, with no real common thread between files. Try to tidy up the mess with some common scheme, to make things look less messy.
2018-07-10 04:36:24 -04:00
#include "wayland/meta-wayland-input-device.h"
#include "wayland/meta-wayland-keyboard.h"
#include "wayland/meta-wayland-pointer.h"
#include "wayland/meta-wayland-tablet-tool.h"
#include "wayland/meta-wayland-text-input.h"
#include "wayland/meta-wayland-text-input-legacy.h"
#include "wayland/meta-wayland-touch.h"
#include "wayland/meta-wayland-types.h"
wayland: split headers and distribute structure definitions Instead of having all structures in one huge headers, move them in the appropriate place, and create one header for surface state. https://bugzilla.gnome.org/show_bug.cgi?id=707128
2013-08-30 12:03:30 -04:00
struct _MetaWaylandSeat
{
struct wl_list base_resource_list;
seat: Listen for ClutterDeviceManager signals in order to update capabilities The capability flags are determined from the device types of the slave devices that are currently attached. This also happens whenever a device is added or removed, so the capabilities are kept up to date, and clients know about these. On VT switch, all slave devices are temporarily removed, so the cascade of signals will make the seat end up with capabililities=0 while input is suspended. https://bugzilla.gnome.org/show_bug.cgi?id=733563
2014-07-23 09:33:03 -04:00
struct wl_display *wl_display;
wayland: split headers and distribute structure definitions Instead of having all structures in one huge headers, move them in the appropriate place, and create one header for surface state. https://bugzilla.gnome.org/show_bug.cgi?id=707128
2013-08-30 12:03:30 -04:00
wayland: Make seat devices GObjects This will make it possible to add signals and other GObject features. https://bugzilla.gnome.org/show_bug.cgi?id=771050
2016-04-01 04:39:30 -04:00
MetaWaylandPointer *pointer;
MetaWaylandKeyboard *keyboard;
MetaWaylandTouch *touch;
data-device: Put the DataDevice implementation in its own struct
2014-07-10 10:31:08 -04:00
MetaWaylandDataDevice data_device;
wayland: Move the primary data device manager to its own file Instead of having everything clumped at MetaWaylandDataManager, split the primary selection to its own struct. This manager is handled separately from wl_data_device_manager and other selection managers, so they would be able to interoperate between them, even. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1193
2020-04-09 11:51:59 -04:00
MetaWaylandDataDevicePrimary primary_data_device;
seat: Listen for ClutterDeviceManager signals in order to update capabilities The capability flags are determined from the device types of the slave devices that are currently attached. This also happens whenever a device is added or removed, so the capabilities are kept up to date, and clients know about these. On VT switch, all slave devices are temporarily removed, so the cascade of signals will make the seat end up with capabililities=0 while input is suspended. https://bugzilla.gnome.org/show_bug.cgi?id=733563
2014-07-23 09:33:03 -04:00
wayland: Make gtk-text-input "legacy" It is superseded by zwp_text_input_v3.
2018-08-13 12:03:49 -04:00
MetaWaylandGtkTextInput *gtk_text_input;
wayland: Implement text-input from wayland-protocols This protocol supersedes the internal gtk_text_input protocol that was in place. Functionally it is very similar, with just some more verbosity in both ways (text_change_cause, .done event), and some improvements wrt the pre-edit text styling.
2018-08-13 12:59:02 -04:00
MetaWaylandTextInput *text_input;
wayland: Implement text input protocol This is the implementation of the internal text-input protocol that will be used to communicate IMs (to be implemented by gnome-shell) with clients. The text_input protocol has its own focus expressed through enter/leave events, that will typically follow the keyboard's. The client will be able to communicate its current status (eg. focus state, cursor rectangle in surface coordinates, text surrounding the cursor position, ...) and will receive commands from the compositor (eg. preedit text, committing a string, ...). Whenever there is an active input method, the compositor will route key events directly through it. The client will not receive wl_keyboard events if the event is consumed by the IM.
2017-10-17 13:22:02 -04:00
seat: Listen for ClutterDeviceManager signals in order to update capabilities The capability flags are determined from the device types of the slave devices that are currently attached. This also happens whenever a device is added or removed, so the capabilities are kept up to date, and clients know about these. On VT switch, all slave devices are temporarily removed, so the cascade of signals will make the seat end up with capabililities=0 while input is suspended. https://bugzilla.gnome.org/show_bug.cgi?id=733563
2014-07-23 09:33:03 -04:00
guint capabilities;
wayland: split headers and distribute structure definitions Instead of having all structures in one huge headers, move them in the appropriate place, and create one header for surface state. https://bugzilla.gnome.org/show_bug.cgi?id=707128
2013-08-30 12:03:30 -04:00
};
wayland: Add basic input support This copies the basic input support from the Clayland demo compositor. It adds a basic wl_seat implementation which can convert Clutter mouse events to Wayland events. For this to work all of the wayland surface actors need to be made reactive. The wayland keyboard input focus surface is updated whenever Mutter sees a FocusIn event so that it will stay in synch with whatever surface Mutter wants as the focus. Wayland surfaces don't get this event so for now it will just give them focus whenever they are clicked as a hack to test the code. Authored-by: Neil Roberts <neil@linux.intel.com> Authored-by: Giovanni Campagna <gcampagna@src.gnome.org>
2013-05-03 13:51:22 -04:00
wayland: Fix header file style
2014-04-22 18:09:38 -04:00
void meta_wayland_seat_init (MetaWaylandCompositor *compositor);
wayland: Add basic input support This copies the basic input support from the Clayland demo compositor. It adds a basic wl_seat implementation which can convert Clutter mouse events to Wayland events. For this to work all of the wayland surface actors need to be made reactive. The wayland keyboard input focus surface is updated whenever Mutter sees a FocusIn event so that it will stay in synch with whatever surface Mutter wants as the focus. Wayland surfaces don't get this event so for now it will just give them focus whenever they are clicked as a hack to test the code. Authored-by: Neil Roberts <neil@linux.intel.com> Authored-by: Giovanni Campagna <gcampagna@src.gnome.org>
2013-05-03 13:51:22 -04:00
wayland: Fix header file style
2014-04-22 18:09:38 -04:00
void meta_wayland_seat_free (MetaWaylandSeat *seat);
seat: Reorder
2014-04-17 18:57:25 -04:00
wayland: Fix header file style
2014-04-22 18:09:38 -04:00
void meta_wayland_seat_update (MetaWaylandSeat *seat,
const ClutterEvent *event);
wayland: Update internal wayland state unconditionally Things like idle times and the cursor position need to be updated even if there's a mutter grab in effect. https://bugzilla.gnome.org/show_bug.cgi?id=712247
2013-11-13 15:41:29 -05:00
wayland: Fix header file style
2014-04-22 18:09:38 -04:00
gboolean meta_wayland_seat_handle_event (MetaWaylandSeat *seat,
const ClutterEvent *event);
wayland: Add basic input support This copies the basic input support from the Clayland demo compositor. It adds a basic wl_seat implementation which can convert Clutter mouse events to Wayland events. For this to work all of the wayland surface actors need to be made reactive. The wayland keyboard input focus surface is updated whenever Mutter sees a FocusIn event so that it will stay in synch with whatever surface Mutter wants as the focus. Wayland surfaces don't get this event so for now it will just give them focus whenever they are clicked as a hack to test the code. Authored-by: Neil Roberts <neil@linux.intel.com> Authored-by: Giovanni Campagna <gcampagna@src.gnome.org>
2013-05-03 13:51:22 -04:00
wayland: Add a wrapper for set_input_focus So we're not poking into seat internals.
2014-07-10 10:13:54 -04:00
void meta_wayland_seat_set_input_focus (MetaWaylandSeat *seat,
MetaWaylandSurface *surface);
wayland: Fix header file style
2014-04-22 18:09:38 -04:00
void meta_wayland_seat_repick (MetaWaylandSeat *seat);
wayland: Add basic input support This copies the basic input support from the Clayland demo compositor. It adds a basic wl_seat implementation which can convert Clutter mouse events to Wayland events. For this to work all of the wayland surface actors need to be made reactive. The wayland keyboard input focus surface is updated whenever Mutter sees a FocusIn event so that it will stay in synch with whatever surface Mutter wants as the focus. Wayland surfaces don't get this event so for now it will just give them focus whenever they are clicked as a hack to test the code. Authored-by: Neil Roberts <neil@linux.intel.com> Authored-by: Giovanni Campagna <gcampagna@src.gnome.org>
2013-05-03 13:51:22 -04:00
wayland: Handle window drags for touch events The grabbing state is now checked for both pointer/touch devices within the seat, and the grab start coordinates returned by meta_wayland_seat_get_grab_info(). https://bugzilla.gnome.org/show_bug.cgi?id=733631
2014-07-21 19:28:39 -04:00
gboolean meta_wayland_seat_get_grab_info (MetaWaylandSeat *seat,
wayland: remove pressed button checks from meta_wayland_pointer_can_grab_surface() Leave these checks up to the callers, the only uses of this function (indirect, through meta_wayland_seat_get_grab_info) are [wl_shell|xdg]_surface.move/resize/show_window_menu. In move/resize it makes sense to check for a button being pressed, because we must expect a button release event. However for xdg_surface.show_window_menu we 1) don't strictly need further events and 2) we must account for press+release event pairs being processed at once in the compositor before the client sees the former. That is eg. the case of touchpad 2nd/3rd button tap emulation, multifinger taps will emit the event pair at once, so when the client manages to request xdg_surface.show_window_menu, it'll be too late in the compositor side, so the request is ignored. https://bugzilla.gnome.org/show_bug.cgi?id=764519
2016-04-04 12:07:42 -04:00
MetaWaylandSurface *surface,
uint32_t serial,
gboolean require_pressed,
gfloat *x,
gfloat *y);
wayland: Make it possible to trigger popups through pointer/keyboard/touch Right now we just check the pointer serial, so the popup will be immediately dismissed if the client passes a serial corresponding to another input device. Abstract this a bit further and add a meta_wayland_seat_can_popup() call that will check the serial all input devices. This makes it possible to trigger menus through touch or keyboard devices. https://bugzilla.gnome.org/show_bug.cgi?id=756296
2015-10-09 10:42:06 -04:00
gboolean meta_wayland_seat_can_popup (MetaWaylandSeat *seat,
uint32_t serial);
wayland: Move checks for grabbing into a central location This means that we won't have as much work to do to introduce similar checks for touch.
2014-05-22 10:57:02 -04:00
wayland/seat: Add API to check whether a seat has a device class Meant to replace explicitly checking whether a MetaWaylandPointer/MetaWaylandKeyboard/MetaWaylandTouch has a seat or not to determine whether they are supposed to be active or not. https://bugzilla.gnome.org/show_bug.cgi?id=771305
2016-09-12 11:12:40 -04:00
gboolean meta_wayland_seat_has_keyboard (MetaWaylandSeat *seat);
gboolean meta_wayland_seat_has_pointer (MetaWaylandSeat *seat);
gboolean meta_wayland_seat_has_touch (MetaWaylandSeat *seat);
wayland: Fix header file style
2014-04-22 18:09:38 -04:00
#endif /* META_WAYLAND_SEAT_H */
Reference in New Issue Copy Permalink