- User Since
- Jul 29 2015, 9:38 AM (198 w, 6 d)
Sat, May 18
Use const QString & instead of auto in range loop
Thu, May 16
Review D21238 created for the line start style.
Tue, May 14
Sat, May 11
Drop the combobox change
Fri, May 10
Use QOverload instead of static_cast
Thu, May 9
Tue, May 7
Sat, May 4
Use QStringLiteral with Unicode code points for line ending symbols.
Fri, Apr 26
Add tooltips to clarify the line ending style works only for PDF documents.
Thu, Apr 25
Place the symbols to left of ending style description for better alignment.
Wed, Apr 24
Merge the two commits (previous revision update had only the second change).
Add Unicode symbols to the line ending style. Didn’t find suitable symbols for ‘Right Closed Arrow’ and ‘Slash’.
Tue, Apr 23
Apr 5 2019
Wherever you're currently listed, remove your name and replace it with Atul's. :) The only place I can find it on Bugzilla. I've gone ahead and made @atulbi the default assignee for bugs to the Touchpad-KCM product.
Apr 4 2019
I happen to be the ‘accidental’ maintainer of the Touchpad KCM. I’d be more than happy to hand that hat over if you wish to maintain this code. :-D
Hey, I would be happy to take that responsibility.
Apr 2 2019
Got to Know a lot about how X works with input handling. XD
Feb 23 2019
How about "Trusted" for remembered devices that are authorized, and "Prohibited" for remembered devices that are not authorized?
"Remembered" would work only if it's clear what's being remembered (i.e. the settings). Maybe it could say "Settings remembered" or something?
Feb 10 2019
Feb 9 2019
Sorry about the wrong path in previous diff. Please find the updated one.
Dec 3 2018
Sep 26 2018
Jul 14 2018
May 27 2018
- "Two tap right, three middle" -> "Tap twice for right-click; three times for middle-click"
- "Two tap middle, three right" -> "Tap twice for middle-click; three times for right-click"
May 14 2018
I don't have commit access (or so I believe), would you commit the changes? Thanks.
May 11 2018
May 2 2018
Apr 28 2018
Feb 14 2018
I've also spent some time debugging this issue, and was perplexed why the property change event doesn't propagate. This fix should be backported if possible.
Sep 8 2017
Dec 28 2016
Might this change fix this issue? https://bugs.kde.org/show_bug.cgi?id=370588
Dec 8 2016
A query about the dbus calls in findTouchpads().
Sep 13 2016
Thanks for the review, but actually I am not convinced that this gets rid of the warning message. Sifting through the KF5 porting notes, I am not sure how this should be handled -- kded tries to load the plugin with just "name" and if not found it looks for "kded_name", which succeeds and emits this warning.
Any suggestions what should be the right approach with KPluginLoader? Should it be always fed with JSON plugin metadata?