2009-11-24 16:22:44 +00:00
|
|
|
/*
|
|
|
|
|
* Clutter.
|
|
|
|
|
*
|
|
|
|
|
* An OpenGL based 'interactive canvas' library.
|
|
|
|
|
*
|
2011-01-18 12:57:12 +00:00
|
|
|
* Copyright © 2009, 2010, 2011 Intel Corp.
|
2009-11-24 16:22:44 +00:00
|
|
|
*
|
|
|
|
|
* This library is free software; you can redistribute it and/or
|
|
|
|
|
* modify it under the terms of the GNU Lesser General Public
|
|
|
|
|
* License as published by the Free Software Foundation; either
|
|
|
|
|
* version 2 of the License, or (at your option) any later version.
|
|
|
|
|
*
|
|
|
|
|
* This library 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
|
|
|
|
|
* Lesser General Public License for more details.
|
|
|
|
|
*
|
|
|
|
|
* You should have received a copy of the GNU Lesser General Public
|
|
|
|
|
* License along with this library. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
|
*
|
|
|
|
|
* Author: Emmanuele Bassi <ebassi@linux.intel.com>
|
|
|
|
|
*/
|
|
|
|
|
|
2009-11-23 16:07:16 +00:00
|
|
|
#if !defined(__CLUTTER_H_INSIDE__) && !defined(CLUTTER_COMPILATION)
|
|
|
|
|
#error "Only <clutter/clutter.h> can be included directly."
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
#ifndef __CLUTTER_INPUT_DEVICE_H__
|
|
|
|
|
#define __CLUTTER_INPUT_DEVICE_H__
|
|
|
|
|
|
2010-01-12 11:53:12 +00:00
|
|
|
#include <clutter/clutter-types.h>
|
2009-11-23 16:07:16 +00:00
|
|
|
|
|
|
|
|
G_BEGIN_DECLS
|
|
|
|
|
|
|
|
|
|
#define CLUTTER_TYPE_INPUT_DEVICE (clutter_input_device_get_type ())
|
|
|
|
|
#define CLUTTER_INPUT_DEVICE(obj) (G_TYPE_CHECK_INSTANCE_CAST ((obj), CLUTTER_TYPE_INPUT_DEVICE, ClutterInputDevice))
|
|
|
|
|
#define CLUTTER_IS_INPUT_DEVICE(obj) (G_TYPE_CHECK_INSTANCE_TYPE ((obj), CLUTTER_TYPE_INPUT_DEVICE))
|
|
|
|
|
#define CLUTTER_INPUT_DEVICE_CLASS(klass) (G_TYPE_CHECK_CLASS_CAST ((klass), CLUTTER_TYPE_INPUT_DEVICE, ClutterInputDeviceClass))
|
|
|
|
|
#define CLUTTER_IS_INPUT_DEVICE_CLASS(klass) (G_TYPE_CHECK_CLASS_TYPE ((klass), CLUTTER_TYPE_INPUT_DEVICE))
|
|
|
|
|
#define CLUTTER_INPUT_DEVICE_GET_CLASS(obj) (G_TYPE_INSTANCE_GET_CLASS ((obj), CLUTTER_TYPE_INPUT_DEVICE, ClutterInputDeviceClass))
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* ClutterInputDevice:
|
|
|
|
|
*
|
2010-01-15 11:37:43 +00:00
|
|
|
* Generic representation of an input device. The actual contents of this
|
|
|
|
|
* structure depend on the backend used.
|
2009-11-23 16:07:16 +00:00
|
|
|
*/
|
|
|
|
|
typedef struct _ClutterInputDeviceClass ClutterInputDeviceClass;
|
|
|
|
|
|
2014-03-17 18:19:52 +00:00
|
|
|
CLUTTER_AVAILABLE_IN_1_0
|
2009-11-23 16:07:16 +00:00
|
|
|
GType clutter_input_device_get_type (void) G_GNUC_CONST;
|
|
|
|
|
|
2014-03-17 18:19:52 +00:00
|
|
|
CLUTTER_AVAILABLE_IN_1_0
|
event/x11: Rework the way we translate X11 events
This is a lump commit that is fairly difficult to break down without
either breaking bisecting or breaking the test cases.
The new design for handling X11 event translation works this way:
- ClutterBackend::translate_event() has been added as the central
point used by a ClutterBackend implementation to translate a
native event into a ClutterEvent;
- ClutterEventTranslator is a private interface that should be
implemented by backend-specific objects, like stage
implementations and ClutterDeviceManager sub-classes, and
allows dealing with class-specific event translation;
- ClutterStageX11 implements EventTranslator, and deals with the
stage-relative X11 events coming from the X11 event source;
- ClutterStageGLX overrides EventTranslator, in order to
deal with the INTEL_GLX_swap_event extension, and it chains up
to the X11 default implementation;
- ClutterDeviceManagerX11 has been split into two separate classes,
one that deals with core and (optionally) XI1 events, and the
other that deals with XI2 events; the selection is done at run-time,
since the core+XI1 and XI2 mechanisms are mutually exclusive.
All the other backends we officially support still use their own
custom event source and translation function, but the end goal is to
migrate them to the translate_event() virtual function, and have the
event source be a shared part of Clutter core.
2011-01-04 12:32:04 +00:00
|
|
|
ClutterInputDeviceType clutter_input_device_get_device_type (ClutterInputDevice *device);
|
2014-03-17 18:19:52 +00:00
|
|
|
CLUTTER_AVAILABLE_IN_1_0
|
event/x11: Rework the way we translate X11 events
This is a lump commit that is fairly difficult to break down without
either breaking bisecting or breaking the test cases.
The new design for handling X11 event translation works this way:
- ClutterBackend::translate_event() has been added as the central
point used by a ClutterBackend implementation to translate a
native event into a ClutterEvent;
- ClutterEventTranslator is a private interface that should be
implemented by backend-specific objects, like stage
implementations and ClutterDeviceManager sub-classes, and
allows dealing with class-specific event translation;
- ClutterStageX11 implements EventTranslator, and deals with the
stage-relative X11 events coming from the X11 event source;
- ClutterStageGLX overrides EventTranslator, in order to
deal with the INTEL_GLX_swap_event extension, and it chains up
to the X11 default implementation;
- ClutterDeviceManagerX11 has been split into two separate classes,
one that deals with core and (optionally) XI1 events, and the
other that deals with XI2 events; the selection is done at run-time,
since the core+XI1 and XI2 mechanisms are mutually exclusive.
All the other backends we officially support still use their own
custom event source and translation function, but the end goal is to
migrate them to the translate_event() virtual function, and have the
event source be a shared part of Clutter core.
2011-01-04 12:32:04 +00:00
|
|
|
gint clutter_input_device_get_device_id (ClutterInputDevice *device);
|
2012-07-11 15:21:28 +00:00
|
|
|
|
|
|
|
|
CLUTTER_AVAILABLE_IN_1_12
|
|
|
|
|
gboolean clutter_input_device_get_coords (ClutterInputDevice *device,
|
|
|
|
|
ClutterEventSequence *sequence,
|
|
|
|
|
ClutterPoint *point);
|
2013-08-14 14:49:00 +00:00
|
|
|
CLUTTER_AVAILABLE_IN_1_16
|
|
|
|
|
ClutterModifierType clutter_input_device_get_modifier_state (ClutterInputDevice *device);
|
2014-03-17 18:19:52 +00:00
|
|
|
CLUTTER_AVAILABLE_IN_1_2
|
event/x11: Rework the way we translate X11 events
This is a lump commit that is fairly difficult to break down without
either breaking bisecting or breaking the test cases.
The new design for handling X11 event translation works this way:
- ClutterBackend::translate_event() has been added as the central
point used by a ClutterBackend implementation to translate a
native event into a ClutterEvent;
- ClutterEventTranslator is a private interface that should be
implemented by backend-specific objects, like stage
implementations and ClutterDeviceManager sub-classes, and
allows dealing with class-specific event translation;
- ClutterStageX11 implements EventTranslator, and deals with the
stage-relative X11 events coming from the X11 event source;
- ClutterStageGLX overrides EventTranslator, in order to
deal with the INTEL_GLX_swap_event extension, and it chains up
to the X11 default implementation;
- ClutterDeviceManagerX11 has been split into two separate classes,
one that deals with core and (optionally) XI1 events, and the
other that deals with XI2 events; the selection is done at run-time,
since the core+XI1 and XI2 mechanisms are mutually exclusive.
All the other backends we officially support still use their own
custom event source and translation function, but the end goal is to
migrate them to the translate_event() virtual function, and have the
event source be a shared part of Clutter core.
2011-01-04 12:32:04 +00:00
|
|
|
ClutterActor * clutter_input_device_get_pointer_actor (ClutterInputDevice *device);
|
2014-03-17 18:19:52 +00:00
|
|
|
CLUTTER_AVAILABLE_IN_1_2
|
event/x11: Rework the way we translate X11 events
This is a lump commit that is fairly difficult to break down without
either breaking bisecting or breaking the test cases.
The new design for handling X11 event translation works this way:
- ClutterBackend::translate_event() has been added as the central
point used by a ClutterBackend implementation to translate a
native event into a ClutterEvent;
- ClutterEventTranslator is a private interface that should be
implemented by backend-specific objects, like stage
implementations and ClutterDeviceManager sub-classes, and
allows dealing with class-specific event translation;
- ClutterStageX11 implements EventTranslator, and deals with the
stage-relative X11 events coming from the X11 event source;
- ClutterStageGLX overrides EventTranslator, in order to
deal with the INTEL_GLX_swap_event extension, and it chains up
to the X11 default implementation;
- ClutterDeviceManagerX11 has been split into two separate classes,
one that deals with core and (optionally) XI1 events, and the
other that deals with XI2 events; the selection is done at run-time,
since the core+XI1 and XI2 mechanisms are mutually exclusive.
All the other backends we officially support still use their own
custom event source and translation function, but the end goal is to
migrate them to the translate_event() virtual function, and have the
event source be a shared part of Clutter core.
2011-01-04 12:32:04 +00:00
|
|
|
ClutterStage * clutter_input_device_get_pointer_stage (ClutterInputDevice *device);
|
2014-03-17 18:19:52 +00:00
|
|
|
CLUTTER_AVAILABLE_IN_1_2
|
Eliminate G_CONST_RETURN
The G_CONST_RETURN define in GLib is, and has always been, a bit fuzzy.
We always used it to conform to the platform, at least for public-facing
API.
At first I assumed it has something to do with brain-damaged compilers
or with weird platforms where const was not really supported; sadly,
it's something much, much worse: it's a define that can be toggled at
compile-time to remove const from the signature of public API. This is a
truly terrifying feature that I assume was added in the past century,
and whose inception clearly had something to do with massive doses of
absynthe and opium — because any other explanation would make the
existence of such a feature even worse than assuming drugs had anything
to do with it.
Anyway, and pleasing the gods, this dubious feature is being
removed/deprecated in GLib; see bug:
https://bugzilla.gnome.org/show_bug.cgi?id=644611
Before deprecation, though, we should just remove its usage from the
whole API. We should especially remove its usage from Cally's internals,
since there it never made sense in the first place.
2011-06-07 14:49:20 +00:00
|
|
|
const gchar * clutter_input_device_get_device_name (ClutterInputDevice *device);
|
2014-03-17 18:19:52 +00:00
|
|
|
CLUTTER_AVAILABLE_IN_1_2
|
2011-01-18 17:33:22 +00:00
|
|
|
ClutterInputMode clutter_input_device_get_device_mode (ClutterInputDevice *device);
|
2014-03-17 18:19:52 +00:00
|
|
|
CLUTTER_AVAILABLE_IN_1_2
|
2011-01-18 17:33:22 +00:00
|
|
|
gboolean clutter_input_device_get_has_cursor (ClutterInputDevice *device);
|
2014-03-17 18:19:52 +00:00
|
|
|
CLUTTER_AVAILABLE_IN_1_2
|
2011-01-19 16:23:45 +00:00
|
|
|
void clutter_input_device_set_enabled (ClutterInputDevice *device,
|
|
|
|
|
gboolean enabled);
|
2014-03-17 18:19:52 +00:00
|
|
|
CLUTTER_AVAILABLE_IN_1_2
|
2011-01-19 16:23:45 +00:00
|
|
|
gboolean clutter_input_device_get_enabled (ClutterInputDevice *device);
|
event/x11: Rework the way we translate X11 events
This is a lump commit that is fairly difficult to break down without
either breaking bisecting or breaking the test cases.
The new design for handling X11 event translation works this way:
- ClutterBackend::translate_event() has been added as the central
point used by a ClutterBackend implementation to translate a
native event into a ClutterEvent;
- ClutterEventTranslator is a private interface that should be
implemented by backend-specific objects, like stage
implementations and ClutterDeviceManager sub-classes, and
allows dealing with class-specific event translation;
- ClutterStageX11 implements EventTranslator, and deals with the
stage-relative X11 events coming from the X11 event source;
- ClutterStageGLX overrides EventTranslator, in order to
deal with the INTEL_GLX_swap_event extension, and it chains up
to the X11 default implementation;
- ClutterDeviceManagerX11 has been split into two separate classes,
one that deals with core and (optionally) XI1 events, and the
other that deals with XI2 events; the selection is done at run-time,
since the core+XI1 and XI2 mechanisms are mutually exclusive.
All the other backends we officially support still use their own
custom event source and translation function, but the end goal is to
migrate them to the translate_event() virtual function, and have the
event source be a shared part of Clutter core.
2011-01-04 12:32:04 +00:00
|
|
|
|
2014-03-17 18:19:52 +00:00
|
|
|
CLUTTER_AVAILABLE_IN_1_2
|
event/x11: Rework the way we translate X11 events
This is a lump commit that is fairly difficult to break down without
either breaking bisecting or breaking the test cases.
The new design for handling X11 event translation works this way:
- ClutterBackend::translate_event() has been added as the central
point used by a ClutterBackend implementation to translate a
native event into a ClutterEvent;
- ClutterEventTranslator is a private interface that should be
implemented by backend-specific objects, like stage
implementations and ClutterDeviceManager sub-classes, and
allows dealing with class-specific event translation;
- ClutterStageX11 implements EventTranslator, and deals with the
stage-relative X11 events coming from the X11 event source;
- ClutterStageGLX overrides EventTranslator, in order to
deal with the INTEL_GLX_swap_event extension, and it chains up
to the X11 default implementation;
- ClutterDeviceManagerX11 has been split into two separate classes,
one that deals with core and (optionally) XI1 events, and the
other that deals with XI2 events; the selection is done at run-time,
since the core+XI1 and XI2 mechanisms are mutually exclusive.
All the other backends we officially support still use their own
custom event source and translation function, but the end goal is to
migrate them to the translate_event() virtual function, and have the
event source be a shared part of Clutter core.
2011-01-04 12:32:04 +00:00
|
|
|
guint clutter_input_device_get_n_axes (ClutterInputDevice *device);
|
2014-03-17 18:19:52 +00:00
|
|
|
CLUTTER_AVAILABLE_IN_1_2
|
2011-01-18 16:13:26 +00:00
|
|
|
ClutterInputAxis clutter_input_device_get_axis (ClutterInputDevice *device,
|
|
|
|
|
guint index_);
|
2014-03-17 18:19:52 +00:00
|
|
|
CLUTTER_AVAILABLE_IN_1_2
|
2011-01-18 16:55:14 +00:00
|
|
|
gboolean clutter_input_device_get_axis_value (ClutterInputDevice *device,
|
|
|
|
|
gdouble *axes,
|
|
|
|
|
ClutterInputAxis axis,
|
|
|
|
|
gdouble *value);
|
event/x11: Rework the way we translate X11 events
This is a lump commit that is fairly difficult to break down without
either breaking bisecting or breaking the test cases.
The new design for handling X11 event translation works this way:
- ClutterBackend::translate_event() has been added as the central
point used by a ClutterBackend implementation to translate a
native event into a ClutterEvent;
- ClutterEventTranslator is a private interface that should be
implemented by backend-specific objects, like stage
implementations and ClutterDeviceManager sub-classes, and
allows dealing with class-specific event translation;
- ClutterStageX11 implements EventTranslator, and deals with the
stage-relative X11 events coming from the X11 event source;
- ClutterStageGLX overrides EventTranslator, in order to
deal with the INTEL_GLX_swap_event extension, and it chains up
to the X11 default implementation;
- ClutterDeviceManagerX11 has been split into two separate classes,
one that deals with core and (optionally) XI1 events, and the
other that deals with XI2 events; the selection is done at run-time,
since the core+XI1 and XI2 mechanisms are mutually exclusive.
All the other backends we officially support still use their own
custom event source and translation function, but the end goal is to
migrate them to the translate_event() virtual function, and have the
event source be a shared part of Clutter core.
2011-01-04 12:32:04 +00:00
|
|
|
|
2014-03-17 18:19:52 +00:00
|
|
|
CLUTTER_AVAILABLE_IN_1_2
|
2011-01-18 16:13:26 +00:00
|
|
|
guint clutter_input_device_get_n_keys (ClutterInputDevice *device);
|
2014-03-17 18:19:52 +00:00
|
|
|
CLUTTER_AVAILABLE_IN_1_2
|
event/x11: Rework the way we translate X11 events
This is a lump commit that is fairly difficult to break down without
either breaking bisecting or breaking the test cases.
The new design for handling X11 event translation works this way:
- ClutterBackend::translate_event() has been added as the central
point used by a ClutterBackend implementation to translate a
native event into a ClutterEvent;
- ClutterEventTranslator is a private interface that should be
implemented by backend-specific objects, like stage
implementations and ClutterDeviceManager sub-classes, and
allows dealing with class-specific event translation;
- ClutterStageX11 implements EventTranslator, and deals with the
stage-relative X11 events coming from the X11 event source;
- ClutterStageGLX overrides EventTranslator, in order to
deal with the INTEL_GLX_swap_event extension, and it chains up
to the X11 default implementation;
- ClutterDeviceManagerX11 has been split into two separate classes,
one that deals with core and (optionally) XI1 events, and the
other that deals with XI2 events; the selection is done at run-time,
since the core+XI1 and XI2 mechanisms are mutually exclusive.
All the other backends we officially support still use their own
custom event source and translation function, but the end goal is to
migrate them to the translate_event() virtual function, and have the
event source be a shared part of Clutter core.
2011-01-04 12:32:04 +00:00
|
|
|
void clutter_input_device_set_key (ClutterInputDevice *device,
|
|
|
|
|
guint index_,
|
|
|
|
|
guint keyval,
|
|
|
|
|
ClutterModifierType modifiers);
|
2014-03-17 18:19:52 +00:00
|
|
|
CLUTTER_AVAILABLE_IN_1_2
|
event/x11: Rework the way we translate X11 events
This is a lump commit that is fairly difficult to break down without
either breaking bisecting or breaking the test cases.
The new design for handling X11 event translation works this way:
- ClutterBackend::translate_event() has been added as the central
point used by a ClutterBackend implementation to translate a
native event into a ClutterEvent;
- ClutterEventTranslator is a private interface that should be
implemented by backend-specific objects, like stage
implementations and ClutterDeviceManager sub-classes, and
allows dealing with class-specific event translation;
- ClutterStageX11 implements EventTranslator, and deals with the
stage-relative X11 events coming from the X11 event source;
- ClutterStageGLX overrides EventTranslator, in order to
deal with the INTEL_GLX_swap_event extension, and it chains up
to the X11 default implementation;
- ClutterDeviceManagerX11 has been split into two separate classes,
one that deals with core and (optionally) XI1 events, and the
other that deals with XI2 events; the selection is done at run-time,
since the core+XI1 and XI2 mechanisms are mutually exclusive.
All the other backends we officially support still use their own
custom event source and translation function, but the end goal is to
migrate them to the translate_event() virtual function, and have the
event source be a shared part of Clutter core.
2011-01-04 12:32:04 +00:00
|
|
|
gboolean clutter_input_device_get_key (ClutterInputDevice *device,
|
|
|
|
|
guint index_,
|
|
|
|
|
guint *keyval,
|
|
|
|
|
ClutterModifierType *modifiers);
|
|
|
|
|
|
2014-03-17 18:19:52 +00:00
|
|
|
CLUTTER_AVAILABLE_IN_1_2
|
event/x11: Rework the way we translate X11 events
This is a lump commit that is fairly difficult to break down without
either breaking bisecting or breaking the test cases.
The new design for handling X11 event translation works this way:
- ClutterBackend::translate_event() has been added as the central
point used by a ClutterBackend implementation to translate a
native event into a ClutterEvent;
- ClutterEventTranslator is a private interface that should be
implemented by backend-specific objects, like stage
implementations and ClutterDeviceManager sub-classes, and
allows dealing with class-specific event translation;
- ClutterStageX11 implements EventTranslator, and deals with the
stage-relative X11 events coming from the X11 event source;
- ClutterStageGLX overrides EventTranslator, in order to
deal with the INTEL_GLX_swap_event extension, and it chains up
to the X11 default implementation;
- ClutterDeviceManagerX11 has been split into two separate classes,
one that deals with core and (optionally) XI1 events, and the
other that deals with XI2 events; the selection is done at run-time,
since the core+XI1 and XI2 mechanisms are mutually exclusive.
All the other backends we officially support still use their own
custom event source and translation function, but the end goal is to
migrate them to the translate_event() virtual function, and have the
event source be a shared part of Clutter core.
2011-01-04 12:32:04 +00:00
|
|
|
ClutterInputDevice * clutter_input_device_get_associated_device (ClutterInputDevice *device);
|
2014-03-17 18:19:52 +00:00
|
|
|
CLUTTER_AVAILABLE_IN_1_2
|
event/x11: Rework the way we translate X11 events
This is a lump commit that is fairly difficult to break down without
either breaking bisecting or breaking the test cases.
The new design for handling X11 event translation works this way:
- ClutterBackend::translate_event() has been added as the central
point used by a ClutterBackend implementation to translate a
native event into a ClutterEvent;
- ClutterEventTranslator is a private interface that should be
implemented by backend-specific objects, like stage
implementations and ClutterDeviceManager sub-classes, and
allows dealing with class-specific event translation;
- ClutterStageX11 implements EventTranslator, and deals with the
stage-relative X11 events coming from the X11 event source;
- ClutterStageGLX overrides EventTranslator, in order to
deal with the INTEL_GLX_swap_event extension, and it chains up
to the X11 default implementation;
- ClutterDeviceManagerX11 has been split into two separate classes,
one that deals with core and (optionally) XI1 events, and the
other that deals with XI2 events; the selection is done at run-time,
since the core+XI1 and XI2 mechanisms are mutually exclusive.
All the other backends we officially support still use their own
custom event source and translation function, but the end goal is to
migrate them to the translate_event() virtual function, and have the
event source be a shared part of Clutter core.
2011-01-04 12:32:04 +00:00
|
|
|
GList * clutter_input_device_get_slave_devices (ClutterInputDevice *device);
|
|
|
|
|
|
2014-03-17 18:19:52 +00:00
|
|
|
CLUTTER_AVAILABLE_IN_1_2
|
event/x11: Rework the way we translate X11 events
This is a lump commit that is fairly difficult to break down without
either breaking bisecting or breaking the test cases.
The new design for handling X11 event translation works this way:
- ClutterBackend::translate_event() has been added as the central
point used by a ClutterBackend implementation to translate a
native event into a ClutterEvent;
- ClutterEventTranslator is a private interface that should be
implemented by backend-specific objects, like stage
implementations and ClutterDeviceManager sub-classes, and
allows dealing with class-specific event translation;
- ClutterStageX11 implements EventTranslator, and deals with the
stage-relative X11 events coming from the X11 event source;
- ClutterStageGLX overrides EventTranslator, in order to
deal with the INTEL_GLX_swap_event extension, and it chains up
to the X11 default implementation;
- ClutterDeviceManagerX11 has been split into two separate classes,
one that deals with core and (optionally) XI1 events, and the
other that deals with XI2 events; the selection is done at run-time,
since the core+XI1 and XI2 mechanisms are mutually exclusive.
All the other backends we officially support still use their own
custom event source and translation function, but the end goal is to
migrate them to the translate_event() virtual function, and have the
event source be a shared part of Clutter core.
2011-01-04 12:32:04 +00:00
|
|
|
void clutter_input_device_update_from_event (ClutterInputDevice *device,
|
|
|
|
|
ClutterEvent *event,
|
|
|
|
|
gboolean update_stage);
|
2010-02-17 18:21:50 +00:00
|
|
|
|
2012-02-27 16:31:53 +00:00
|
|
|
CLUTTER_AVAILABLE_IN_1_10
|
2011-10-10 15:45:20 +00:00
|
|
|
void clutter_input_device_grab (ClutterInputDevice *device,
|
|
|
|
|
ClutterActor *actor);
|
2012-02-27 16:31:53 +00:00
|
|
|
CLUTTER_AVAILABLE_IN_1_10
|
2011-10-10 15:45:20 +00:00
|
|
|
void clutter_input_device_ungrab (ClutterInputDevice *device);
|
2012-02-27 16:31:53 +00:00
|
|
|
CLUTTER_AVAILABLE_IN_1_10
|
2011-10-10 15:45:20 +00:00
|
|
|
ClutterActor * clutter_input_device_get_grabbed_actor (ClutterInputDevice *device);
|
|
|
|
|
|
2012-06-16 23:44:44 +00:00
|
|
|
CLUTTER_AVAILABLE_IN_1_12
|
|
|
|
|
void clutter_input_device_sequence_grab (ClutterInputDevice *device,
|
|
|
|
|
ClutterEventSequence *sequence,
|
|
|
|
|
ClutterActor *actor);
|
|
|
|
|
CLUTTER_AVAILABLE_IN_1_12
|
|
|
|
|
void clutter_input_device_sequence_ungrab (ClutterInputDevice *device,
|
|
|
|
|
ClutterEventSequence *sequence);
|
|
|
|
|
CLUTTER_AVAILABLE_IN_1_12
|
|
|
|
|
ClutterActor * clutter_input_device_sequence_get_grabbed_actor (ClutterInputDevice *device,
|
|
|
|
|
ClutterEventSequence *sequence);
|
|
|
|
|
|
2014-03-17 18:19:52 +00:00
|
|
|
CLUTTER_AVAILABLE_IN_1_10
|
2012-01-17 15:40:08 +00:00
|
|
|
gboolean clutter_input_device_keycode_to_evdev (ClutterInputDevice *device,
|
|
|
|
|
guint hardware_keycode,
|
|
|
|
|
guint *evdev_keycode);
|
|
|
|
|
|
2009-11-23 16:07:16 +00:00
|
|
|
G_END_DECLS
|
|
|
|
|
|
|
|
|
|
#endif /* __CLUTTER_INPUT_DEVICE_H__ */
|