delta/mutter.git/src/org.gnome.Mutter.RemoteDesktop.xml, branch document-button-values

Document button values in the RemoteDesktop api

2021-05-01T00:40:21+00:00

I spent some time trying to pass X11 button values
and was a bit miffed that it didn't work. So lets
document the expected values to minimize future
frustation.

remote-desktop/session: Add CapsLockState and NumLockState properties

2021-03-04T17:39:08+00:00

Will be used by remote desktop services that want to try to affect the
end result of these. We cannot let it set these directly, as these needs
to be done using virtual key events to not cause issues in all the XKB
state tracking, so remote desktop services try to deal with this
themself if they need to.

Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/1342
Part-of:

remote-desktop: Clarify the type of keycode for NotifyKeyboardKeycode()

2021-02-23T08:18:05+00:00

The API for NotifyKeyboardKeycode() does not mention what type of
keycode is expected to be submitted.
So, clarify in the API that the keycode to submit is expected to be an
evdev keycode.

Part-of:

remote-desktop: Fix typo in API description

2021-02-23T08:18:05+00:00

For NotifyKeyboardKeycode() the API user submits keycodes instead of
keysyms.

Part-of:

remote-desktop: Document NotifyPointerAxis() more explicit

2021-02-17T20:47:00+00:00

Currently, the documentation for NotifyPointerAxis() just mentions that
a smooth scroll event is emitted.
However, this is not entirely correct. For each NotifyPointerAxis(),
mutter emits an emulated discrete scrolling event based on the
submitted accumulated smooth scrolling deltas.
Additionally, it doesn't mention how the motion deltas need to be
interpreted.

So, document the NotifyPointerAxis() notification better by mentioning
the emulation of discrete scroll events, how these discrete scroll
events are calculated and how the motion deltas need to be interpreted.

Part-of:

remote-desktop/session: Added boiler plate for clipboard integration

2021-02-05T16:44:27+00:00

Nothing is hooked up, it only does basic sanity checking i.e. whether
the clipboard was enabled when interacting with it. No actual clipboard
integration is hooked up yet.

This also syncs org.gnome.Mutter.RemoteDesktop.xml from
gnome-remote-desktop.

Part-of:

remote-desktop: Allow using custom scroll source for NotifyPointerAxis

2021-01-11T09:12:53+00:00

Currently, the NotifyPointerAxis method always assumes that the scroll
source is CLUTTER_SCROLL_SOURCE_FINGER.
This is however not always true and in some cases a remote desktop
client needs to submit a PointerAxis event with a custom axis step.
This is for example the case with high resolution mouse wheels, where
the NotifyPointerAxisDiscrete method is unsuitable.
In such cases NotifyPointerAxis needs to be called, but with the
intention that the scroll source is still a mouse wheel.

To solve this situation, don't assume the scroll source always to be
CLUTTER_SCROLL_SOURCE_FINGER.
Instead, add further flag options to NotifyPointerAxis, which allow a
remote desktop client to choose the scroll source.
This way a remote desktop client can choose what scroll source is the
most suitable one for the current scroll event.

Part-of:

Fix typo in RemoteDesktop dbus api

2019-05-22T14:21:57+00:00

https://gitlab.gnome.org/GNOME/mutter/merge_requests/586

remote-desktop, screen-cast: Add version number to D-Bus APIs

2018-02-23T11:33:31+00:00

In order to let applications gracefully handle version mismatches, add
a version property to the APIs. Also add a warning on the APIs that
these are not meant for public consumption.

remote-desktop: Add support for discovering supported device types

2018-02-23T11:33:31+00:00

This is so that application will not try to send touch events when
touch is not supported.