| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Update NEWS.
|
|
|
|
|
|
|
|
|
|
| |
intltool is unmaintained nowadays while upstream gettext gained
support for formats like GSettings schemas and .desktop files,
and offers a mechanism to teach it about other XML formats not
yet supported out of the box which we can use for the rest.
So there's nothing stopping us, just make the switch ...
https://bugzilla.gnome.org/show_bug.cgi?id=769073
|
| |
|
|
|
|
|
|
|
| |
We tried to resolve non-introspected types; lets skip those. We didn't
have a vfunc scope on a for-each loop; declared it synchronous.
https://bugzilla.gnome.org/show_bug.cgi?id=769800
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
An empty argument list means "unspecified arguments", and not
"no arguments" like it does in C++. If an implementer of Mutter
plugins uses gcc -Wold-style-definition, as configured by
AX_COMPILER_FLAGS_CFLAGS, they will get warnings about this.
Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk>
Reviewed-by: Florian Müllner <fmuellner@gnome.org>
Bug: https://bugzilla.gnome.org/show_bug.cgi?id=769971
|
|
|
|
|
|
|
|
| |
The scale will have been set to 1 no matter what when initializing the
MetaOutput since it at the time didn't have an CRTC assigned to it.
Now, when we assign the CRTC to the output, we need to update the scale.
https://bugzilla.gnome.org/show_bug.cgi?id=769505
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=769505
|
|
|
|
|
|
|
| |
Instead of reading all the different state in one huge function, split
it up into logical chunks, making it easier to read.
https://bugzilla.gnome.org/show_bug.cgi?id=769505
|
| |
|
|
|
|
|
|
|
| |
Those have no backing libinput_device, and configuration does not
apply to those.
https://bugzilla.gnome.org/show_bug.cgi?id=765009
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is somewhat gross at the moment, because we're after all mimicking
real keyboard events, we can only lookup keycodes that are available
in the current map, and the control of levels is rather limited.
Eventually, we want to implement the text_input protocol, handle these
events separately to MetaWaylandKeyboard, so event->key.keyval is
is guaranteed to be the final result. Until then, this is the farthest
we can get.
https://bugzilla.gnome.org/show_bug.cgi?id=765009
|
|
|
|
|
|
|
|
| |
Evcodes don't cut it when we have something already specifying the
character to be printed, despite the current group/level. This API
allows some more control on the intended output.
https://bugzilla.gnome.org/show_bug.cgi?id=765009
|
|
|
|
|
|
|
| |
This includes adding documentation and introspection annotations,
and marking the functions as extern.
https://bugzilla.gnome.org/show_bug.cgi?id=765009
|
|
|
|
|
|
|
| |
The seat core keyboard/pointer will be "master", the ones created through
ClutterVirtualInputDevice will be "slaves".
https://bugzilla.gnome.org/show_bug.cgi?id=765009
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=765009
|
|
|
|
|
|
|
|
| |
libinput does it for us, but only for physical devices. When we add
virtual devices to the same seat, we need to track button press count
ourself.
https://bugzilla.gnome.org/show_bug.cgi?id=765009
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=765009
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=765009
|
|
|
|
|
|
|
| |
We are still single seated, so until we are properly multi seated its
always the main seat.
https://bugzilla.gnome.org/show_bug.cgi?id=765009
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=765009
|
|
|
|
|
|
|
| |
We notify per seat; so lets move the logic there. Touch and tablets to
follow later.
https://bugzilla.gnome.org/show_bug.cgi?id=765009
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=765009
|
|
|
|
|
|
| |
Split out ClutterSeatEvdev functionality into a separate file.
https://bugzilla.gnome.org/show_bug.cgi?id=765009
|
|
|
|
|
|
|
|
|
|
| |
Virtual input devices aim to enable injecting input events as if they
came from hardware events. This is useful for things such as remote
controlling, for example via a remote desktop session.
The API so far only consists of stumps.
https://bugzilla.gnome.org/show_bug.cgi?id=765009
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We do some things when binding to a socket fails (closing the fd,
logging, unlinking files, ...) those might affect errno in some
or other way, so it might no longer be EADDRINUSE even if we later
try to make those non fatal.
It seems better to check errno soon after the failure, and don't
rely on it in any way at a later point. All error paths in
bind_to_abstract_socket() also have early logging, which also might
help figure out better the point of failure when the socket fails
to be created.
https://bugzilla.gnome.org/show_bug.cgi?id=769578
|
|
|
|
|
| |
Check the unix_fd, which is the one just created, the abstract_fd
is already checked above.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Set ClutterStageViewCogl as parent of MetaRendererView, since that is
the actual parent.
https://bugzilla.gnome.org/show_bug.cgi?id=768976
|
|
|
|
|
|
|
|
| |
Allocate the offscreen stage view framebuffers up front; otherwise they
may get allocated after the viewport calculated by the stage is set,
which would cause the viewport to be incorrect until recalculated.
https://bugzilla.gnome.org/show_bug.cgi?id=768976
|
|
|
|
|
|
|
| |
Initially the viewport and projection is not calculated and should thus
be marked as dirty.
https://bugzilla.gnome.org/show_bug.cgi?id=768976
|
|
|
|
|
|
|
| |
Only paint the per monitor stage views when enabled, otherwise bad
things happen.
https://bugzilla.gnome.org/show_bug.cgi?id=768976
|
|
|
|
|
|
|
| |
Shouldn't just update them when they change; they also need to be
set when initializing.
https://bugzilla.gnome.org/show_bug.cgi?id=769179
|
|
|
|
|
|
|
| |
Two settings were set twice on the same device. Now instead group the
generic update functions together, removing the redundant calls.
https://bugzilla.gnome.org/show_bug.cgi?id=769179
|
|
|
|
|
|
|
|
|
|
|
| |
If have_native_backend is not set, we might end up with:
Native (KMS) backend:
instead of:
Native (KMS) backend: no
in the configure summary
https://bugzilla.gnome.org/show_bug.cgi?id=769305
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Support changing the mouse and trackball acceleration profile. This
makes it possible to for example disable pointer acceleration by
choosing the 'flat' profile.
This adds an optional dependency on gudev. Gudev is used by the X11
backend to detect whether a device is a mouse or not. Without gudev
support, the accel profile settings has have effect for mouse devices.
Trackball still uses the "strstr" approach, since udev doesn't support
tagging devices as trackball devices yet.
https://bugzilla.gnome.org/show_bug.cgi?id=769179
|
|
|
|
|
| |
This way the "libinput Scroll Method Enabled" property manipulation
is made clearer.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add support for setting edge-scrolling separately from two-finger
scrolling. We now have 2 separate boolean settings for those, with the
Mouse panel in gnome-control-center allowing to set only one of those at
a time, but nothing precludes both being set in the configuration.
We need to handle:
- two-finger-scrolling-enabled and edge-scrolling-enabled settings both
being set.
- those 2 settings being change out-of-order
- two-finger-scrolling being set on a device that doesn't support it
- edge-scrolling-enabled on a device that doesn't support it
And the combinations of one touchpad supporting just one of edge
scrolling and two-finger scrolling and another vice-versa.
https://bugzilla.gnome.org/show_bug.cgi?id=768245
|
|
|
|
| |
We use API recently added in that version.
|
| |
|
|
|
|
| |
Future versions of gettext will fail if this header is missing.
|
|
|
|
|
|
|
|
| |
Instead of continuing eventually crashing with a segmentation fault due
to a missing renderer, make MetaBackend an GInitable, and gracefully
handle the failure to fully create the backend with an EXIT_FAILURE.
https://bugzilla.gnome.org/show_bug.cgi?id=769036
|