Also ports it away from KToolInvocation.
I don't really see why it would have to start that early in the process?
Details
Details
- Reviewers
davidedmundson - Group Reviewers
Plasma Plasma Accessibility - Commits
- R119:6df845ee5373: Make KAccess a regular startup application
- Enabled screen reader, logged in, plasmashell would still talk to the screen reader
Imho using QProcess to restart it on save is fine since user clicking Save expecting to reload the settings and it's a background process anyway, so no need to bouncy cursor
Some feedback from people more knowledgable in Accessibility would be appreciated :)
Diff Detail
Diff Detail
- Repository
- R119 Plasma Desktop
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Comment Actions
Please double check wayland startup is ok. The kcminit had a X-KDE-OnlyShowOnQtPlatforms=xcb; guard
Orca situation should be fine
/home/david/projects/qt5/qtbase/src/platformsupport/linuxaccessibility/dbusconnection.cpp: dbusWatcher = new QDBusServiceWatcher(A11Y_SERVICE, c, QDBusServiceWatcher::WatchForRegistration, this);
Comment Actions
Autostart doesn't appear to respect that property and I don't think we just want to check KService::noDisplay() *but* kaccess appears to launch and even screen reader works.