Version: unspecified (using Devel) OS: Linux Atm moment entering numbers in the Check interval line edit is either not possible or has to be done in a not logical way. Reproducible: Always Steps to Reproduce: - Launch Kmail-mobile - Click on your Imap account - Open the 'Actions' tab - Click on 'Account' - Click on 'Edit account' - Click in the 'Check interval:' line edit and try to enter '2' minutes as value Actual Results: It does not work. The only way to enter a number is to not hold the number key (blue arrow) which is not at all logical with the way to enter number in the rest of the applications. Also entering one as a value is impossible Expected Results: Entering a number should done the usual way (holding blue arrow key + number key) and entering 1 as a value should be allowed too. N900, 4:4.5~20100914.1175313-1maemo1.1174921
SVN commit 1180493 by ervin: There's a separate checkbox now to disable the interval checking altogether so no need to have a special value for "Never". Which incidentally ended up to be 1 (that was the mistake). BUG: 251376 M +0 -3 setupserverview_desktop.ui M +0 -3 setupserverview_mobile.ui WebSVN link: http://websvn.kde.org/?view=rev&revision=1180493
I fixed the "1" case. For the number entering where you shouldn't hold the blue arrow key... That's actually something coming from the Maemo input method or the Qt/Maemo integration, so somewhat out of our reach. Funnily I find it handy that you don't have to use the blue arrow when inputing in a field which only accepts integers anyway. ;-)
I retested this today and it is partially corrected now: Entering '1' as a check interval works fine now but it is still not possible to enter a number holding the blue arrow key and pressing a number. At moment the only way to enter a number is still to directly press on a number (without holding the blue arrow key). This may be because this is a digit only field but I still find this behaviour inconsistent with the rest of the app. Can anyone confirm that this is really a bug? I am reopening for now and will close if it is not considered as a bug after all. N900, 4:4.5~20100929.1180953-1maemo1.1180919
This is intentional I think, all number-only fields on the N900 (not just in our apps) behave like this.
Yep, that's why I said it's "something coming from the Maemo input method or the Qt/Maemo integration"... We can't really fix it IMO. Or that would be some Maemo specific workaround (boiling down to creating our own spinbox). We definitely don't want to go down this path IMO.
Thx for the confirmation then I am closing this bug. N900, 4:4.5~20100930.1181183-1maemo1.1180919