Created attachment 81089 [details] autocorrect righ-clik menu new GUI proposal this is a clone of previous issue report I file in OOo bug-tracker in 2009 and that was never considered by OOo devs ( https://issues.apache.org/ooo/show_bug.cgi?id=101714 ) DESCRIPTION when you type a wrong word and right click on it and go trough the autocorrect menu, LibO suggests you some alternative typing, if you find the desired one you click on it and you set an association that is recorded. Next time you type the mistake it will be automatically retyped. unfortunately sometimes you don't find the desired typing among LibO's suggestion. In that case you may manually set the autocorrect association entering the autocorrect replacement table from the Tools menu. my proposal is to add some kind of a form field in the right click autocorrect menu, just below the typing suggestions. The user should be able to manually type in that field the desired typing and set the error/autocorrect association. (if you don't understand what i mean see the attached screenshot example i made with some graphic editing software) in this way you could enter a custom autocorrect entry without opening the whole autocorrect replacement table. This would be a time saver.
Good idea, but I think not need. Very few people are interested.
@Igor Gnatenko I'm reverting the version number to 3.3 since this issue affects every LibO release and not only 4.1.0.1 as you modified (you should always select the firs LibO release where the issue is present) I also REOPEN the bug report since RESOLVED WORKSFORME is a completely wrong label. this is an enhancement request, the fact you don't need it doesn't allow you to say it's RESOLVED. you should better read bug triaging procedures.
Should be in UNCONFIRMED status as it hasn't been independently confirmed
@Joel this is not a bug-report but rather an enhancement request for a feature which is not present in LibO. just give a look yourself: the right-click autocorrect suggestions menu has no input field (see my mock screenshot), which I'm asking to add is this enough to label this report as NEW?
setting it back as NEW. I know this is not an indipendent confirmation, but anybody can easily see that such a feature does not yet exist in LibO.
(In reply to comment #5) > setting it back as NEW. > I know this is not an indipendent confirmation, but anybody can easily see > that such a feature does not yet exist in LibO. Yes, this is not present in LibO.
(In reply to comment #6) > Yes, this is not present in LibO. I submitted too early.. What I wanted to say additionally is that adding a entry box into a pop-up menu is problematic. Only something like "add custom" could be added, which then triggers a dialog to enter a custom autocorrect entry. This is something that could be done easily. Regards, Tomaž
(In reply to comment #7) > (In reply to comment #6) > > Yes, this is not present in LibO. > > I submitted too early.. What I wanted to say additionally is that adding a > entry box into a pop-up menu is problematic. Only something like "add > custom" could be added, which then triggers a dialog to enter a custom > autocorrect entry. This is something that could be done easily. > > Regards, Tomaž it's not what I had in mind, but your proposal seems a good comprimise. IMHO that "add custom" should stay at the bottom of the autocorrect suggestions list and should be separated by those words by an horizontal separator line.
... and it would be cool if after clicking the "add custom" the replacement table would open copying that word in the "replace field"
(In reply to comment #7) > I submitted too early.. What I wanted to say additionally is that adding a > entry box into a pop-up menu is problematic. Only something like "add > custom" could be added, which then triggers a dialog to enter a custom > autocorrect entry. This is something that could be done easily. Fully agree with this suggested solution. Also agree with the last two comments by tommy27. The idea is clear now and workable. Now let's pray that an angel picks this up. :-)
as discussed in latest comments an "add custom" menu item triggering a dialog to insert a new autocorrect entry would be a good alternative solution if inserting an "entry box" in the pop-up menu is too complicated. adding UI expert to CC list. @Ivan do you think it's something feasible?
thanks to the fix from Jay in Bug 92341 (target 5.1.0) there's no need to keep the current report open. the original proposal was probably too complex to implement (see comment 7) and the current solution is a good compromise for me. so I set status to WONTFIX