Skip to content
Snippets Groups Projects
Select Git revision
0 results
Search by author
  • Any Author
0 authors
  1. Dec 22, 2024
  3. Dec 21, 2024
    • Gaël Bonithon's avatar
      Apply .clang-format file · 240de52d
      Gaël Bonithon authored
      240de52d
    • Gaël Bonithon's avatar
      Preliminary cleanup · 28787015
      Gaël Bonithon authored
      28787015
    • Gaël Bonithon's avatar
      Sort includes · a7b16cba
      Gaël Bonithon authored
      a7b16cba
    • Gaël Bonithon's avatar
      clang-format: Add file · 5b7d070e
      Gaël Bonithon authored 
      Related: orage#32, xfce/xfce4-dev-tools!101
      5b7d070e
    • Gaël Bonithon's avatar
      wayland: manager: Fix activated/deactivated signal emission · e89fd941
      Gaël Bonithon authored 
      Following the addition of the Wayland implementation of GSListener, we
now need these signals to be emitted only once, and at the time
indicated by their name. This also implies some corrections to the
values returned by the functions emitting or connected to these signals.
      e89fd941
    • Gaël Bonithon's avatar
      wayland: Use ext-idle-notify protocol · 47207d77
      Gaël Bonithon authored
      47207d77
    • Gaël Bonithon's avatar
      wayland: Make sure text entry of unlock dialog is grabbed · b6ab5816
      Gaël Bonithon authored 
      The ext-session-lock protocol imposes nothing on the compositor
concerning the focus of lock surfaces. In particular, there is no
guarantee that the user will be able to click on a surface to give it
focus, even if the protocol suggests this.

More generally, it's not certain that we receive pointer events on lock
surfaces, and even when we do, we don't necessarily have a reliable way
of knowing which surface is under the pointer at any given time.

At first glance, then, it seems that the only thing we can do to ensure
that the unlock dialog has indeed the focus, is to display it on the
lock surface to which the compositor has given the focus when creating
all the surfaces. This is what the Wayland implementation of
find_window_at_pointer() does in this commit.

However, the active surface may have changed by the time the dialog is
displayed, particularly when user activity takes place just after
surfaces have been created. In this case, we cancel the dialog display,
and another user activity will re-trigger its creation (in practice,
this simply adds a small latency).

Next, we need to add a focus recovery timeout at plug level, in case
focus is lost when exiting text entry, for example by pressing the tab
key (for some reason, pressing this key doesn't automatically return you
to text entry once you've reached the last button in the action area, as
on X11).
      b6ab5816
    • Gaël Bonithon's avatar
      wayland: Use ext-session-lock protocol · 032ec7a7
      Gaël Bonithon authored
      032ec7a7
    • Gaël Bonithon's avatar
      Remove -x11 suffix from file names that do not contain an X11 impl · 3a6d4aca
      Gaël Bonithon authored 
      gs-grab-x11.c is X11 only and gs-window-x11.c mixes X11 and Wayland.
This also aligns file names with class names.
      3a6d4aca