Bug 224076 - Filter out accessibility notifications source unless accessibility-related notifications are turned on in the Accessibility KCM
Summary: Filter out accessibility notifications source unless accessibility-related no...
Status: CONFIRMED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_notify (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Olivier Goffart
URL:
Keywords: usability
: 404945 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-01-24 19:38 UTC by bluescreenavenger
Modified: 2024-10-27 16:19 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bluescreenavenger 2010-01-24 19:38:00 UTC
Version:            (using KDE 4.3.4)
OS:                Linux
Installed from:    Ubuntu Packages

When a user wants to enable an accessibility notification from the notifications KCM, such as "A lock Key has been deactivated" They enable it, but they wont get a pop up when they deactivate num lock. 

They don't know that they have to go to the Accessibility KCM, go to the Modifier keys tab, and check "Use KDE's system notification mechanism whenever a modifier or lock key changes its state" for the notification to actually be sent.

If they are configuring it from the Accessibility KCM, its not as confusing. But if they go to the Notifications KCM, its not straightforward
Comment 1 bluescreenavenger 2018-12-30 05:42:05 UTC
I think this info might still stand. I like the locking key notifications. From the notifications KCM, if I set "A lock key has been activated" there is no obvious thing telling me that I need to go to the Accessibility KCM, to check "Use Plasma notification mechanism for modifier or locking key state changes." ...However NOW from the Accessibility KCM, there is a sweet "Configure Notifications" button, so it's more obvious for users that discover the Accessibility KCM first, (but not the Notifications KCM)
Comment 2 Patrick Silva 2019-03-01 23:16:48 UTC
*** Bug 404945 has been marked as a duplicate of this bug. ***
Comment 3 Patrick Silva 2019-03-01 23:24:56 UTC
I did not know that I have to install "Accessibility" kcm to use settings under "Acessibility" event source in "Notifications" kcm...

I think that "Accessibility" event source should only be available in Notifications kcm when "Accessibility" kcm is installed and "Use KDE's system notification mechanism whenever a modifier or lock key changes its state" option is checked in "Modifier keys" tab.
Comment 4 Nate Graham 2019-11-14 19:00:06 UTC
(In reply to Patrick Silva from comment #3)
> I think that "Accessibility" event source should only be available in
> Notifications kcm when "Accessibility" kcm is installed and "Use KDE's
> system notification mechanism whenever a modifier or lock key changes its
> state" option is checked in "Modifier keys" tab.
That makes sense to me.
Comment 5 Nicolas Fella 2024-10-27 16:19:13 UTC
The accessibility KCM is always installed since it's part of plasma-desktop