| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
gdk_x11_display_set_window_scale() affects the interpretation of the
Xft/DPI XSETTING - it is substituted inside GDK with the value of
Gdk/UnscaledDPI xsetting. However, this change is not propagated to
GTK+ and from GTK+ back to gdk_screen_set_resolution() until the
main loop is run.
Fix this by handling the screen resolution directly in gdk/x11.
This requires duplication of code between GDK and GTK+ since we still
have to handle DPI in GTK+ in the case that GdkSettings:gtk-xft-dpi
is set by the application.
https://bugzilla.gnome.org/show_bug.cgi?id=733076
|
|
|
|
|
|
|
| |
This reverts commit 2b95d1a34ed7cd70ea3eaaa9b7d8add200b5a9d2.
Conflicts:
gdk/gdkscreen.c
|
|
|
|
|
|
|
| |
Unless GDK_RGBA=0 is set, this will be the RGBA visual.
The new function is called gdk_screen_get_preferred_visual().
https://bugzilla.gnome.org/show_bug.cgi?id=630217
|
|
|
|
|
| |
These report the internal scaling factor, mapping from UI pixels
to hardware pixels.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The function returns the part of a monitors area that should be
used for positioning popups, menus, etc. The only non-trivial
implementation atm is in the X backend, all the other backends
just return the full monitor area. The X implementation is
currently suboptimal, since it requires roundtrips to collect
the necessary information. It should be changed to monitor
the properties for changes, when XFixes allows to monitor
individual properties.
https://bugzilla.gnome.org/show_bug.cgi?id=641999
|
| |
|
|
|
|
|
| |
And, since we've decided to keep the structs private, there is
no point in having the standard GObject clas macros anymore either.
|
|
At the same time, move some more class and instance structs
out of public headers.
|