Bilal Elmoussaoui
d44f02ba64
mutter: Cleanup gi-docgen annotations
...
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2939 >
2023-05-22 15:47:37 +00:00
Corentin Noël
9132f984ce
mutter: Add missing nullable annotation when possible
...
Add missing (nullable) annotation when a possible NULL return value is expected.
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2362 >
2022-04-05 14:05:23 +02:00
Olivier Fourdan
445373d028
x11: Check for XCB reply
...
Now that mutter can survive Xwayland vanishing in mid-flight, we need to
actually check if the Xserver reply fetched though XCB is not NULL,
otherwise we may crash, that would be a shame.
Close: https://gitlab.gnome.org/GNOME/mutter/-/issues/1638
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1718 >
2021-02-09 19:06:22 +00:00
Jonas Ådahl
313e3e771c
Make meta_* logging utilities not require line break
...
Unlike g_* logging utilities, the meta_* counterparts behave like odd
printf() functions. Lets change that so they fit better into how logging
is done everywhere else.
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1466
2020-10-08 16:38:41 +02:00
Marco Trevisan (Treviño)
1d75d5aa2f
group: Free group if returning early
...
If we get an error when fetching the window attributes, the group isn't ever
free'd, so use an autopointer instead, releasing the stolen one.
https://gitlab.gnome.org/GNOME/mutter/merge_requests/1195
2020-04-12 21:40:20 +00:00
Jonas Ådahl
2f4a68c8c3
Clean up include macros mess
...
The order and way include macros were structured was chaotic, with no
real common thread between files. Try to tidy up the mess with some
common scheme, to make things look less messy.
2018-11-06 17:17:36 +01:00
Armin Krezović
98d912ba5f
Move stack tracking and guard_window outside of MetaScreen
...
Move stack, stack_tracker to MetaDisplay guard_window to MetaX11Display
https://bugzilla.gnome.org/show_bug.cgi?id=759538
2018-07-06 19:47:16 +02:00
Armin Krezović
9e5ea8def4
Move groups and window/group prop hooks to MetaX11Display
...
https://bugzilla.gnome.org/show_bug.cgi?id=759538
2018-07-06 19:47:16 +02:00
Armin Krezović
18779109de
Start populating MetaX11Display
...
- Moved xdisplay, name and various atoms from MetaDisplay
- Moved xroot, screen_name, default_depth and default_xvisual
from MetaScreen
- Moved some X11 specific functions from screen.c and display.c
to meta-x11-display.c
https://bugzilla.gnome.org/show_bug.cgi?id=759538
2018-07-06 19:47:16 +02:00
Jasper St. Pierre
352cac3850
group: Convert code to XCB to prevent errors
...
Windows can disappear at any time because X11 is really cool and good,
so just use XCB so we won't crash if the window disappears.
2015-08-05 13:39:23 -07:00
Jasper St. Pierre
aea71fbd01
group: Select for property notifies on group leaders
2015-06-27 00:53:22 -07:00
Jasper St. Pierre
25a16c3379
Remove trailing whitespace
2014-05-02 09:34:48 -04:00
Jasper St. Pierre
a1427c7130
Revert "Move MetaGroup to be X11-specific"
...
This reverts commit f940292cfe5a80290a5dae8a62e05fbcbab32a7f.
Turns out MetaGroup was public API and was used by gnome-shell.
Ugh.
2014-03-19 09:12:48 -04:00
Jasper St. Pierre
f940292cfe
Move MetaGroup to be X11-specific
2014-03-18 21:23:36 -04:00
Jasper St. Pierre
8f151842fb
Start moving X11 implementation to its own subdirectory
...
This is specifically about managing X11 windows, not necessarily
running as an X11 compositor. By that I mean that this code is
still used for XWayland windows, and event handling is still and
modesetting / monitor management is still in core/.
This is also a fairly conservative move. We don't move anything
like screen.c or bell.c in here, even though those are really
only for X11 clients.
2014-03-18 15:44:11 -04:00
