Skip to content
Snippets Groups Projects
  1. Oct 12, 2022
    • Enrico Weigelt's avatar
      configure.ac.in: configure option to enable poswin · c00e6132
      Enrico Weigelt authored
      
      The position window is currently just a debug helper, that can only be
      enabled by explicitly passing extra CFLAGS (-DSHOW_POSITION).
      
      Some distros already do that, but that's rather invasive from distro pov
      (using such undocumented tricks isn't actually a clean approach), and
      users asked for this as a general feature.
      
      A trivial solution is adding a configure option for that. It still needs
      to be enabled at compile-time, but at least needs less special hacks
      and easier to maintain by standard distro build machineries.
      
      Signed-off-by: default avatarEnrico Weigelt, metux IT consult <info@metux.net>
      c00e6132
  2. Oct 05, 2022
  3. Oct 04, 2022
  4. Aug 27, 2022
  5. Aug 02, 2022
  6. Jul 25, 2022
  7. Jul 15, 2022
  8. Jul 04, 2022
  9. Jul 01, 2022
  10. Jun 25, 2022
  11. Jun 09, 2022
  12. Jun 07, 2022
  13. Jun 05, 2022
  14. Jun 04, 2022
  15. Jun 02, 2022
  16. Apr 28, 2022
  17. Apr 25, 2022
  18. Apr 24, 2022
  19. Apr 19, 2022
    • Olivier Fourdan's avatar
      poswin: Fix location with client-side decorations · 4a08afa7
      Olivier Fourdan authored
      
      The location needs to take the client-side decorations when computing
      the window position.
      
      Signed-off-by: default avatarOlivier Fourdan <fourdan@xfce.org>
      4a08afa7
    • Olivier Fourdan's avatar
      compositor: Damage window when adding the opaque region · 0bacec27
      Olivier Fourdan authored
      
      When mapping a new window for the first time, the client may set an
      opaque region prior to draw anything.
      
      As opaquere regions are meant to hint the compositor that anything
      underneath doesn't need updating (as hidden behind an opaque region,
      precisely), xfwm4 would leave that region untouched.
      
      However, when using double buffering as with xpresent, it means that
      content of the different buffers may end up being different if there is
      any damage occurring underneath the opaque region, before the client
      itself has painted anything.
      
      As the buffers alternate quickly, the content behind the opaque region
      will show alternatively which is ugly (although technically correct).
      
      To avoid that issue, when setting the opaque region first, make sure to
      damage the whole window so that the content of the different buffers
      remain updated even if behind the opaque region.
      
      Signed-off-by: default avatarOlivier Fourdan <fourdan@xfce.org>
      Closes: xfce/xfwm4#583
      Fixes: 50d34206 - Damage opaque region if changed
      0bacec27
  20. Mar 31, 2022
  21. Mar 26, 2022
  22. Mar 17, 2022
  23. Mar 12, 2022
  24. Mar 11, 2022
  25. Mar 08, 2022
  26. Mar 06, 2022
  27. Feb 25, 2022
Loading