Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
When enabling org.mate.interface window-scaling-factor-qt-sync (default), m-s-d will attempt to set QT_SCALE_FACTOR during the init phase.
When disabled, the user can then choose to control this env var elsewhere.
|
|
This change is a super hacky way of supporting the fallback desktop background (without caja) on HiDPI displays. It does this by doing two things: using a new function that scales up the background surface; and by loading settings using an updated function that triggers a redraw.
|
|
|
|
|
|
|
|
|
|
This changes how the media-keys manager determines successful
key-bindings from KeyRelease to KeyPress so that it does not conflict
with third-party applications that want to use modifier keys as global
key-bindings. We've already done this change for general keybindings and
marco.
It also cleans up a bunch of deprectation warnings.
|
|
Also fix build warnings on xsettings
|
|
|
|
|
|
Also set QT_* env variables during init, and restart marco, mate-panel, toggle desktop icons when changing scales
|
|
This change allows for Xft/Gdk settings to be changed dynamically for
the scaling factor and font DPI. It also has an optional auto-detection
algorithm for the most appropriate settings to use for different screen
sizes and resolutions. The auto-detect is re-triggered whenever the
screen size changes.
|
|
|
|
|
|
* Support font size and mouse cursor auto-scaling for HiDPI displays
* Fix where DPI is getting scaled
* Remove ceil for scaled DPI
|
|
|
|
|
|
Fixes build warnings
|
|
this requires https://github.com/mate-desktop/mate-desktop/commit/b133f518f6f2310093fd3b5248049c7048cfb8d4
closes https://github.com/mate-desktop/mate-desktop/issues/296
|
|
format ‘%lld’ expects argument of type ‘long long int’, but argument has type ‘long int’
|
|
passing argument 3 of ‘g_queue_find_custom’ from incompatible pointer type
|
|
because warnings like "xxx is deprecated: Not available before 2.44" look stupid
|
|
|
|
|
|
|
|
The work began with:
https://github.com/mate-desktop/mate-settings-daemon/commit/788babedafaf59d8b7a36cb0ef3b0b1f0e5f732c
This commit reverts:
https://github.com/mate-desktop/mate-settings-daemon/commit/7f887e614812ccb86f5d784e2db58bede8daa712
And it applies an alternative to fix the deprecated functions:
gdk_screen_get_width
gdk_screen_get_height
|
|
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1517547
|
|
|
|
|
|
Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: assertion
'window->update_and_descendants_freeze_count > 0' failed
inspired from:
https://git.xfce.org/apps/xfce4-terminal/commit/?id=eff5e2d
|
|
avoid deprecated:
gdk_screen_get_monitor_geometry
gdk_screen_get_monitor_at_point
|
|
|
|
|
|
m-s-d needs gsetting schema for globalmenu support
from mate-desktop
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
When setting `KeyPressMask` as a reportable event for all windows, the
keybinding for `Fn+F7` in Xrandr seems to fail. This change adds, rather
than overrides, the `KeyPressMask` as a reportable event for the
corresponding window.
Fixes #180
|
|
* Request keyboard event reports from global keybindings of other windows
This allows mate-settings-daemon to honor global keybindings whenever
a different application has keybindings that seem conflicting, but are
usually not.
For example, an application defining a `Super_L` keybinding
and MATE having defining a shortcut that uses the `<Mod4>` key. They are
the same physical keyboard, but one is a modifier and the other is not.
Without requesting keyboard reports from other windows, the `<Mod4>`
shortcuts are swallowed whenever there is a `Super_L` shortcut
elsewhere.
* Remove KeyReleaseMask as the keybindings_filter only looks at KeyPress
* Guard against BadWindow errors
|
|
|
|
|
|
|
|
This menu was not noticed back in 2015 when support for custom panel menu themes was added
|