Commit Graph

8555 Commits

Author SHA1 Message Date
dacb515e27 evdev: Port evdev input backend to libinput
Instead of having its own evdev input device processing implementation,
make clutter's evdev backend use libinput to do input device processing
for it.

Two GObject parameters of ClutterInputDeviceEvdev (sysfs-path and
device-path) are removed as they are not used any more.

Before ClutterDeviceManagerEvdev had one virtual core keyboard and one
virtual core pointer device. These are now instead separated into seats,
which all have one virtual core keyboard and pointer device respectively.

The 'global' core keyboard and pointer device are the core keyboard and
pointer device of the first seat that is created.

A ClutterInputDeviceEvdev can, as before, both represent a real physical
device or a virtual device, but is now instead created either via
_clutter_input_device_evdev_new() for real devices, and
_clutter_input_device_new_virtual() for virtual devices.

XKB state and button state is moved to the seat structure and is thus
separated per seat. Seats are not a concept exposed outside of clutter's
evdev backend.

Signed-off-by: Jonas Ådahl <jadahl@gmail.com>

https://bugzilla.gnome.org/show_bug.cgi?id=720566
2014-02-27 09:57:29 +01:00
488639eb63 x11: Avoid invalid ClutterInputDevice pointers in the device list
Due to the way add_device() invariably adds to the master/slave device
lists, while keeping ClutterInputDevices 1:1 with device IDs, it may
leave invalid pointers in the list if add_device() is called multiple
times for the same device ID. There are two situations where this may
happen:

1) If devices are disabled and later enabled: devices are added invariably
   to the master/slave lists on constructed(), but then on XIDeviceEnabled
   they'd get added yet again.
2) Racy cases where the ClutterDeviceManager is created around the same time
   XIHierarchyEvents are sent. When getting the XIDeviceInfo on constructed(),
   these devices may already appear as enabled, even though XIDeviceEnabled
   is seen through XIHierarchyEvents processed in the event loop sortly after.

   This last case can be seen when starting gnome-shell on a different tty,
   and entering in the one it's been spawned on, clutter initialization
   happens around the same time devices are added back because of the tty
   switch, and multiple extra ClutterInputDevices are created.

https://bugzilla.gnome.org/show_bug.cgi?id=724971
2014-02-25 10:18:20 +01:00
c4372249e2 Updated Serbian translation 2014-02-24 22:45:32 +01:00
856342caad Updated Hungarian translation 2014-02-23 16:29:28 +01:00
cee480bd1a Updated Czech translation 2014-02-22 13:14:34 +01:00
f8cfb5dd07 Updated Lithuanian translation 2014-02-21 22:13:07 +02:00
bde9ea04e0 Updated Brazilian Portuguese translation 2014-02-21 14:52:30 +00:00
2639395533 stage-cogl: Fix buffer_age code path
Currently we where checking whether the damage_history list contains
more or equal then buffer_age entries. This is wrong because we prepend
our current clip to the list just before the check.

Fix that to check whether we have more entries instead of more or equal.

https://bugzilla.gnome.org/show_bug.cgi?id=724788
2014-02-20 12:00:20 +01:00
75f2b1c5c2 Post-release version bump to 1.17.5 2014-02-19 13:30:45 +00:00
7fe74f58cb Release Clutter 1.17.4 (snapshot) 2014-02-19 13:24:22 +00:00
5b3a1f75ca docs: Ignore clutter-test-utils.h
The API is public, because we need it in the conformance test suite, but
it's still a work in progress.
2014-02-19 13:20:41 +00:00
15dd607120 docs: Add missing symbols to the API reference 2014-02-19 13:07:30 +00:00
8935ee4a78 Add missing exported symbols 2014-02-19 13:04:09 +00:00
0f5db3dafa [l10n] Updated Italian translation. 2014-02-16 12:21:14 +01:00
320b3fe4d4 Added uk translation 2014-02-14 20:37:43 +02:00
197d170364 stage_cogl: Don't scale the current_damage when adding to the damage_list
Otherwise we will union the scaled rectange with the clip_region which is
unscaled causing us to redraw a larger area.
2014-02-14 13:16:52 +01:00
f01716f9bc Updated Spanish translation 2014-02-14 10:19:07 +01:00
32b3d27bb9 GestureActions: Add per-action thresholds
Instead of relying on the dnd drag threshold, add per-action
horizontal and vertical thresholds. Use them in the swipe action
as well.

https://bugzilla.gnome.org/show_bug.cgi?id=724242
2014-02-13 18:53:24 +01:00
54e2657cb0 GestureActions: Set threshold-trigger-edge at right time
It was set during the _init(), and swiftly overridden with the
default value in construct. Do it in constructed() instead.

https://bugzilla.gnome.org/show_bug.cgi?id=724242
2014-02-13 18:53:24 +01:00
094f196bb5 Updated Norwegian bokmål translation 2014-02-12 20:29:41 +01:00
f7ac4e77de Updated Norwegian bokmål translation 2014-02-12 20:29:05 +01:00
f73b4d334a actor: Extend :scale-[xyz] factors in the negative range
The corresponding methods accept negative values already.

https://bugzilla.gnome.org/show_bug.cgi?id=706311
2014-02-10 18:35:12 +00:00
dd08b6fd98 docs: Explicitly mention that Transition is abstract
https://bugzilla.gnome.org/show_bug.cgi?id=710232
2014-02-10 18:32:36 +00:00
92c0c77947 conform/color: Add more test coverage
https://bugzilla.gnome.org/show_bug.cgi?id=662818
2014-02-10 18:01:38 +00:00
33ebe92fdb color: Fix documentation of 'hsla()' parsing
The documentation for the s and l components is incorrect; these have to
be percentage values and must have a '%' character right after the
number.

Based on a patch by: Pablo Pissanetzky <pablo@trickplay.com>

https://bugzilla.gnome.org/show_bug.cgi?id=662818
2014-02-10 17:54:06 +00:00
2662788bbc build: Add -Werror=logical-op
Caught a couple of checks that evaluated to always true.

https://bugzilla.gnome.org/show_bug.cgi?id=711540
2014-02-10 17:43:16 +00:00
d157602924 timeline: Fix bad logic in check
https://bugzilla.gnome.org/show_bug.cgi?id=711540
2014-02-10 17:43:16 +00:00
dd034cccad x11: Fix bad logic in axis check
https://bugzilla.gnome.org/show_bug.cgi?id=711540
2014-02-10 17:43:16 +00:00
a1378e0833 Updated Aragonese translation 2014-02-09 13:28:11 +01:00
54ac92bd83 [l10n] Updated Italian translation. 2014-02-09 12:36:03 +01:00
3324470916 Updated Indonesian translation 2014-02-09 03:39:40 +00:00
9e3b355a70 Updated Galician translations 2014-02-07 01:32:28 +01:00
419da5f035 Updated Serbian translation 2014-02-03 21:21:48 +01:00
edc155a74d Updated Traditional Chinese translation(Hong Kong and Taiwan) 2014-02-02 20:05:16 +08:00
b9bc36e72e Updated Brazilian Portuguese translation 2014-02-02 00:43:18 -02:00
692f39ad57 Updated Czech translation 2014-01-26 17:31:29 +01:00
f6b5a04507 Updated Hebrew translation
Signed-off-by: Yosef Or Boczko <yoseforb@src.gnome.org>
2014-01-26 04:33:03 +02:00
0dc4986f66 text: Fix the implementation of delete_chars()
The internal delete_text() implementation takes a start and an end
position, whereas the public delete_chars() method takes a number of
characters to delete starting from the current cursor position.
2014-01-24 18:49:18 +00:00
c2324849fc conform/text: Add verbose output 2014-01-24 18:49:00 +00:00
67e4636f89 conform: Re-enable text tests
The ClutterText tests were ported to the new testing API, but they were
not enabled.
2014-01-24 18:48:34 +00:00
c76e63f0c7 build: Fix rules for examples data
Apparenly we need to EXTRA_DIST the image and JSON data.
2014-01-24 12:11:38 +00:00
796c869c13 Updated Spanish translation 2014-01-23 18:17:50 +01:00
75155b9d96 Revert "cookbook: Temporarily disable the scribbler example"
This reverts commit 515a8fcfb5.

The exported symbols regexp used by Cogl-Path has been fixed.
2014-01-23 12:46:51 +00:00
762e9a05e4 Bump the Cogl dependency
In order to build the cookbook examples, we need a version of Cogl-Path
that correctly exports all its symbols; this has been fixed in Cogl only
after the 1.17.2 snapshot was made.
2014-01-23 12:45:48 +00:00
f1ffbd50b7 Post-release version bump to 1.17.3 2014-01-23 12:45:20 +00:00
a5b04f58a0 Release Clutter 1.17.2 2014-01-23 12:28:19 +00:00
07efb5d9bb build: Remove .gitignore on distclean
Fixes distcheck.
2014-01-23 12:28:19 +00:00
773e544c51 settings: Make unscaled-font-dpi override font-dpi
The :unscaled-font-dpi property is used to override the existing
:font-dpi value when running on high DPI density displays; since it's a
write-only property we don't need to have a separate storage, nor we
need to choose between :font-dpi and :unscaled-font-dpi depending on
whether or not either has been set. If we select which one to use
between :font-dpi and :unscaled-font-dpi when computing the font
resolution, we end up breaking the code that relies on changing
:font-dpi directly on a per-Settings basis.
2014-01-23 12:17:09 +00:00
696a536b26 settings: Add CLUTTER_DPI_SCALE
Like we do for the windowing surfaces, we should have a run time knob
(in the form of an environment variable) to allow changing the scaling
factor of the font resolution.
2014-01-23 12:17:09 +00:00
30d1e47c4e x11/stage: Store new size on unrealized resize()
If the StageX11 is asked to resize itself while not being realized, then
we just need to store the new size and return.
2014-01-23 12:17:09 +00:00