summaryrefslogtreecommitdiff
path: root/plugins/a11y-keyboard
AgeCommit message (Collapse)AuthorFilesLines
2020-09-05a11y-keyboard: Add support for togglekeys-backend settingColomban Wendling1-5/+23
2020-09-05a11y-keyboard: Delay registration of the pluginColomban Wendling1-1/+5
Delay registration of the a11y keyboard plugin to run after the non-a11y keyboard one to avoid numlock state change conflicts.
2020-09-05a11y-keyboard: Add sanity checks on beep sequence preferencesColomban Wendling1-6/+9
2020-09-05a11y-keyboard: Manually beep for togglekeysColomban Wendling1-0/+63
This allows a customizable and possibly different beep sequence when a togglekey is enabled or disabled. This is very useful for the user to know for sure whether the feature got enabled or disabled. Back in the days of buzzers, XKB was supposed to use different sounds for each of those, but this is no longer the case now in the vast majority of setups the beeps are intercepted and use a single recorded sound. XKB beeps are also unfortunately not configurable, although they possibly should be on paper: in theory, one could alter the bell used by listening to `XkbBellNotify` events, which provides a way to discriminate bells through a name. Unfortunately XKB's togglekeys seems to suffer from a bug (?) for a long time, in that it will always ring the `AX_IndicatorOn` bell if there is *at least one* indicator on at the moment the bell is rung, and `AX_IndicatorOff` if and only if *all* indicators are off. This makes it virtually useless as it is not possible to discriminate between an indicator getting turned on or off in most cases, especially with NumLock which often stays always on. Given this behavior dates at the very least as far back as X.org 1.16 which is from 2014, it probably is not very realistic to rely on a fix. So instead implement togglekeys on our end by listening to the `XkbIndicatorStateNotify` events.
2020-08-15add G_GNUC_UNUSED in some unused parametersPablo Barciela2-7/+7
2020-08-08a11y-keyboard: Don't show UI for unavailable feature in the pref dialogColomban Wendling1-0/+15
2020-08-08a11y-keyboard: Don't create a dummy object if AT-SPI is not availableColomban Wendling3-39/+25
Instead guard the caller to only use it if available.
2020-08-08a11y-keyboard-atspi: Switch to a final type and reduce boilerplateColomban Wendling2-42/+28
2020-08-08a11y-keyboard: capslock-beep: Try and detect non-buggy libatspi2Colomban Wendling1-10/+7
Try and avoid the workaround for buggy libatspi2 if we can know the version we're using has it fixed.
2020-08-08a11y-keyboard: capslock-beep: Don't ring on CapsLock itselfColomban Wendling1-26/+8
Ringing when a locking modifier gets enabled/disabled is already taken care of by the `togglekeys` settings, so don't provide redundant functionality and allow better settings granularity.
2020-08-08a11y-keyboard: Refactor in the hope the AT-SPI bug gets fixedColomban Wendling1-32/+31
2020-08-08a11y-keyboard: Add support for ringing the bell when CapsLock is activeColomban Wendling6-1/+357
2020-07-16msd-a11y-keyboard-manager: implicit declaration of function 'd'rbuj1-4/+4
2020-07-13build: Use MATE_DEBUG_CHECK macrorbuj1-13/+6
2020-06-27add git.mk to generate .gitignoretamplan1-0/+2
2020-04-06use MATE_COMPILE_WARNINGS from mate-commonrbuj1-5/+9
2019-12-22avoid redundant redeclarationsPablo Barciela2-6/+2
2019-08-30switch to use gettextWu Xiaotian2-5/+6
2019-08-02plugins a11y-keyboard: fix deprecated g_type_class_add_privateWu Xiaotian3-18/+6
2019-07-11plugins: drop libXxf86 dependencyraveit651-1/+0
The X server hasn't implemented it in over 10 years. and it was dropped from debian since a long time. fixes https://github.com/mate-desktop/mate-settings-daemon/issues/284
2018-09-30Add support for org.mate.accessibility-keyboard.stickykeys-latch-to-lockColomban Wendling1-1/+6
2018-08-22a11y-keyboard-manager: replace deprecated gdk_error_trap_push/popraveit651-15/+27
2018-01-30require GTK+ 3.22 and GLib 2.50monsta1-13/+0
2018-01-26Add support for HiDPI displays (#208)Victor Kareh1-0/+5
* Support font size and mouse cursor auto-scaling for HiDPI displays * Fix where DPI is getting scaled * Remove ceil for scaled DPI
2018-01-09plugins: G_GNUC_UNUSED in unused but needed variablesPablo Barciela1-2/+2
Fixes build warnings
2017-12-02Fix: big fonts by default with "org.mate.desktop.font-rendering.dpi"Pablo Barciela1-21/+6
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1517547
2017-08-14gtk 3.22: avoid deprecated gdk_screen_get_width/height_mmZenWalker1-0/+13
2017-08-14avoid deprecated gdk_screen_get_width/heightZenWalker1-4/+8
2017-07-27msd-a11y-preferences-dialog.ui: clean up deprecationsraveit651-35/+69
2017-07-27ally-keyboard: fix help linkraveit651-1/+1
2017-07-27don't use deprecated gtk_show_uriraveit651-0/+7
2016-11-20move to GTK+3 (>= 3.14), drop GTK+2 code and --with-gtk build optionmonsta1-12/+0
and require libmatekbd and libmate-desktop >= 1.17
2016-10-26build: require XInput unconditionallymonsta1-10/+1
as done in g-s-d six years ago: https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=5b2a28376a3aa81d865679e8c91d2f6beb8af799
2016-01-09a11y-keyboard: remove useless codemonsta2-115/+0
it either does nothing or only calls parent functions taken from https://git.gnome.org/browse/gnome-settings-daemon/commit?id=5ec1584de2b32b55098e579e403ac37d94ccef03 https://git.gnome.org/browse/gnome-settings-daemon/commit?id=6808c3fe13c855dc17cf6048801f8e8a2ee634e2
2015-12-02GTK3: use gdk_error_trap_pop_ignored() when appropriateWolfgang Ulbrich1-0/+12
taken from: https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=544526d
2015-09-04Switch to org.gnome.SessionManagerClement Lefebvre1-3/+3
2015-08-07a11y-keyboard: drop deprecated property from ui fileMonsta1-1/+0
2015-07-28a11y: don't use ancient properties (deprecated in GTK+ 2.22)Monsta1-2/+1
2015-01-13a11y-keyboard: fix crashMonsta1-9/+9
fixes https://github.com/mate-desktop/mate-settings-daemon/issues/70
2013-08-01Replace ghelp: with help: for user-guideinfirit1-1/+1
2013-04-06Init libnotify in mate-settings-daemon, not in pluginsStefano Karapetsas1-4/+0
2013-02-26two more fixes for libnotifyElan Ruusamäe1-2/+0
** (mate-settings-daemon:27918): WARNING **: /usr/lib64/mate-settings-daemon/liba11y-keyboard.so: undefined symbol: notify_notification_attach_to_status_icon ** (mate-settings-daemon:27225): WARNING **: /usr/lib64/mate-settings-daemon/libxrandr.so: undefined symbol: notify_notification_new_with_status_icon liba11-keyboard change done similarily to GNOME, just removing it: https://github.com/GNOME/gnome-settings-daemon/commit/e1ab570b0dce479ba235e5542ea07d1b5bafc4c9
2013-02-18use libnotify 0.7, not libmatenotifyElan Ruusamäe2-19/+17
2012-12-15[plugins] Fix some deprecations (GTK2/GTK3)Jasmine Hassan1-1/+0
a11y-keyboard: gtk_dialog_set_has_separator(), deprecated in GTK+ 2.22 common|mouse: prefix GDK key constants with _KEY (GTK3)
2012-12-06[plugins] cleanup macro magic in plugin.hJasmine Hassan1-0/+5
And instead, use glib macros (since 2.14) http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=0dda56c4462e070dabdab68092b6574b5e894181
2012-10-17fix 64bit-portability-issueStefano Karapetsas1-1/+1
2012-10-12fix incorrect FSF addressraveit657-8/+8
2012-10-01migrate to gsettingsmate-settings-daemon-1.5.0Stefano Karapetsas2-435/+260
2012-02-21gsd to msd complete rename patch by NiceandGently; file rename commithaxar7-0/+0
2012-02-21gsd to msd complete rename patch by NiceandGently; code changes commithaxar8-214/+214
generated by cgit v1.2.1 (git 2.18.0) at 2024-05-27 22:48:49 +0000