- User Since
- Apr 8 2020, 4:55 AM (12 w, 3 d)
May 7 2020
Too bad I can't; it's been no more than a month since I began my study into KDE applications. I'd love to test out if someone provides a genius solution, though.
May 5 2020
I second the as-an-option proposal. Hey, why not automatically increase the line height when CJK characters are detected?
May 4 2020
lg is, in fact, the ISO standard. However, log_10 is the least ambigious. The length looks fine. We have a x*10^y after all.
Use this as parent of QShortcut
Thanks :D see you at libksane!
So I tested this, great improvements regarding line height can be seen:
May 1 2020
Of course it's possible, by using <sub>:
No, I do not have commit rights. I actually changed the email on bugzilla recently (but not on phabricator as it seemed impossible to do so w/o sysadmin's manual intervention), so to avoid confusion, it's email@example.com. The name should be "Frederick Yin". Thanks!
Apr 28 2020
Apr 27 2020
I would set the shortcut directly to the button with setShortcut(...)
Apr 25 2020
@sars As you said, I assigned ctrl+p and ctrl+s to preview and scan respectively in libksane along with tooltips (i18n will need to catch up with this, I think). I used QShortcut; poke me if there's a better way. The snippet looks like this:
Apr 23 2020
I have obtained the source of libksane and located the strings. Should I try binding Ctrl+C to the button? If I did, how do I include the fresh build of libksane in (also freshly built) skanlite?
Apr 10 2020
Some janitor work from a minor annoyance tracing back to 2017.
Apr 9 2020
- Remove confusing comments and unnecessary KIO::StatJob
Apr 8 2020
Cool, got it. Will revise that tomorrow.
All unit tests (i.e. one) passed, and I have tested this on all save-as cases I can think of. Thank you for reviewing this patch!