Tested changing settings
Diff Detail
Diff Detail
- Repository
- R119 Plasma Desktop
- Branch
- kaccess-kconfigxt
- Lint
No Linters Available - Unit
No Unit Test Coverage - Build Status
Buildable 20000 Build 20018: arc lint + arc unit
Comment Actions
I read kaccess.cpp and commented on where the defaults diverge, there could be more. There's also some keys that have typos and/or don't match.
This shows quite impressively why having this stuff in a central place is useful :)
Given kaccess.cpp is what does the handling, ultimately its defaults will be what is being used, not the ones in the KCM.
| kcms/access/kaccess_settings.kcfg | ||
|---|---|---|
| 14 | lol Can you give this a better name, like "customBell" (Arts was the KDE 3 sound server) | |
| 18 | Likewise, customBellFile | |
| 47 | "stickied" is not a word but I can see that "stuck" implies something else | |
| 56 | The default is false | |
| 62 | "key" or whatever that k stands for? | |
| 77 | The default is false | |
| 81 | The default is false | |
| 85 | The default is false | |
| 98 | BounceKeysRejectBeep | |
| 122 | There is only kNotifyAccessX (note the X) | |
| 143 | This is actually being calculated referencing "interal" in kaccess code: mouseGroup.readEntry("MKTimeToMax", (5000 + interval / 2) / interval); | |
| 145 | The key is MKTimeToMax | |
| 149 | Defaults to interval | |
| 156 | profil*e* | |
Comment Actions
Since the other diff seems quite advanced already I am abandonning this one.
| kcms/access/kaccess_settings.kcfg | ||
|---|---|---|
| 56 | Well no : see defaults() "ui.stickyKeysBeep->setChecked(true);" or load() "keyboardGroup.readEntry("StickyKeysBeep", true)" | |
| 77 | No see default() " ui.slowKeysPressBeep->setChecked(true);" or load() | |
| 81 | No ui.slowKeysAcceptBeep->setChecked(true); | |
| 85 | Same. | |
| 98 | What do you mean ? | |
| 122 | What do you mean ? | |
| 143 | Yes and it the default value taking into account the default settings : int((5000 + 5/2) / 5) = 1000 | |
| 145 | No, there are two similar keys MK-TimeToMax and MKTimeToMax, hence your confusion. | |