summaryrefslogtreecommitdiff
path: root/plugins/a11y-keyboard/msd-a11y-keyboard-manager.c
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 Barciela1-5/+5
2020-08-08a11y-keyboard: Don't create a dummy object if AT-SPI is not availableColomban Wendling1-2/+14
Instead guard the caller to only use it if available.
2020-08-08a11y-keyboard: Add support for ringing the bell when CapsLock is activeColomban Wendling1-1/+24
2020-07-16msd-a11y-keyboard-manager: implicit declaration of function 'd'rbuj1-4/+4
2020-07-13build: Use MATE_DEBUG_CHECK macrorbuj1-13/+6
2019-12-22avoid redundant redeclarationsPablo Barciela1-3/+1
2019-08-02plugins a11y-keyboard: fix deprecated g_type_class_add_privateWu Xiaotian1-6/+2
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-09plugins: G_GNUC_UNUSED in unused but needed variablesPablo Barciela1-2/+2
Fixes build warnings
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 codemonsta1-65/+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
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äe1-17/+15
2012-10-12fix incorrect FSF addressraveit651-1/+1
2012-10-01migrate to gsettingsmate-settings-daemon-1.5.0Stefano Karapetsas1-186/+124
2012-02-21gsd to msd complete rename patch by NiceandGently; file rename commithaxar1-0/+1347
generated by cgit v1.2.1 (git 2.18.0) at 2024-11-14 16:14:08 +0000