Version: (using KDE 3.5.9) Installed from: SuSE RPMs Run Kate. Search for something, A for example. Search for B. Search for C. Call search (find again). Look at the combobox. Open it, you will see: C B A C is selected. Using your keyboard only, please move to B. Close/cancel the dialog. Call find dialog again. C should be selected. DO NOT open the combobox. Get to "B". Surprise! :-) Current behaviour is 100% counter-intuitive, please provide _uniform_ keys to navigate the combobox.
And (again) I cannot deduce from this report what exactly the problem is.
Did you repeat the steps? The keys used are not the same, why did I wrote about uniform navigation keys after all?
On Thu, Apr 10, 2008 at 05:54:43AM -0000, Maciej Pilichowski wrote: Hej Maciej, > Did you repeat the steps? The keys used are not the same, > why did I wrote about uniform navigation keys after all? Please stay polite, we all want that this bug get fixed... A better description of the bug would be: KHistoryCombobox uses Key_UpArrow to get to the next item in history, however all normal combo boxes (e.g. QComboBox/KComboBox) use Key_DownArrow. Example: The combobox has the items A <- current item B C In Q/KComboBox you have to press Key_DownArrow to get to entry B, in KHistoryComboBox you have to use Key_UpArrow. I guess when we change the behaviour here, we'll break it somewhere else, for this reason I'll let somebody with more knowledge decide what to do... Ciao, Tobias
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!