Version: 4:4.2.2-1 (using KDE 4.2.2) OS: Linux Installed from: Debian testing/unstable Packages In Kmail's composer when you right click a mispelt word with the auto-spellchecker active there is a separate submenu for suggested spellings. Because the suggested spellings are by far the most likely thing a user is looking for when they right click a misspelt word (it certainly is when I click one) it would be more efficient to reorganise the menus so the suggested spellings is at the top of the top level menu.
*** Bug 175941 has been marked as a duplicate of this bug. ***
So, what's the status on this ?
I've written a patch for fixing this. You can monitor/review it here: http://reviewboard.kde.org/r/2097/
Its an improvement, but is not possible to move the Suggestions from a submenu to the root menu as well?
Wouldn't that make it too crowded/long? I mean, I don't know why it exists in the popup right now but there has to be a UI reason for it, perhaps. Where do I get this clarified? I've updated the diff (r2) there with the top 'level' method as was requested - Its much like what OpenOffice.org does. Also added another screen-shot for the new patch.
On suggestion would be to put the top N (10?) items into the first menu, with a 'more..' submenu for the rest. This is a familiar UI paradigm to users (look at what FireFox does, for instance), and accomplishes the twin goals of making the suggestions quicker and easier to get too and not crowding the menu too much. Every time I have to correct a spelling at the moment in KDE4, I scream a little inside.
Hm, I failed to look at the suggestions-retriever earlier - looks like it only returns 10 items by default so no issues there! :)
Fixed. Committed patch to trunk. See: http://websvn.kde.org/?view=rev&revision=1047622
Is this a good candidate for going onto the existing 4.x branches too ?
Awesome, thank you so much! :)
*** Bug 163674 has been marked as a duplicate of this bug. ***
*** Bug 149989 has been marked as a duplicate of this bug. ***
*** Bug 202143 has been marked as a duplicate of this bug. ***