Request 1 Problem description: when a cell comment needs to be edited, it is always necessary to - first check "show" - double click into the comment to enable editing - edit - right click into the cell (of the comment) and uncheck show to hide the comment Solution add an EDIT function to the context menu which opens the comment for editing with out a double click on it close editing when cursor is clicked somewhere outside the comment. This will increase productivity Request 2 add the possibility to automatically have the intinals of the author of the comment.entered at the beginning of the cell text, followed by a colon and position the cursor at the beginning of the next line Note: I saw several enhancement request for cell comments, and would like to suggest that these are all dealt as one task. Operating System: Windows XP Version: 4.0.3.3 release
So, first thing first, please make the second enhancement request a separate report - we try to keep 1 report to 1 issue so that it's easy for developers to track and assign tasks. For the first point, are you saying that with the button the workflow would be: --first check "show" --single click on comment --click on this new button that you are requesting --right click into the cell (of the comment) and uncheck show to hide the comment It seems like the same # of steps to me. Maybe I'm missing something, please explain further and we will try to get it into a confirmed status. Without "single click on comment", the button would be useless as you don't know which comment you want to edit. So still 4 steps yes? And maybe more work as you have to move the mouse to the button after single clicking on the comment to select it Marking as NEEDINFO - please explain further how it would save time and then mark the bug as UNCONFIRMED - I'm expecting that I'm just not understanding fully your suggestion so the more detail the better (within reason of course)
As per Joel's request: Assumption in both cases: a cell comment exists already Currently 1 - right click cell 2 - select SHOW 3 - click into cell and do changes 4 - right click cell 5 - deselect SHOW 6 - click to next working spot Enhancement request 1 - right click cell 2 - select EDIT (the new function opens the cell and places cursor at the end of the text already in the cell) and do changes 3 - click to the next working spot and cell comment closes automatically I hope the request is now clearer.
As per Joel's request I opened another report for the second enhancement in this report. Please find it under https://www.libreoffice.org/bugzilla/show_bug.cgi?id=64999
Thank you for reporting this enhancement request! I can confirm that this is a valid enhancement request on: Version: 4.3.0.0.alpha0+Build ID: daa57a101a20e0b37db7090796ad002b8d192b9b Date: Sun Dec 15 23:07:57 2013 +0100 Platform: Ubuntu Linux 13.10 x64 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + As I've been able to confirm the enhancement request I am marking as: New (confirmed) Enhancement Low - workaround, saves one step (double clicking) Keywords - Whiteboard Status - ProposedEasyHack + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material
Thanks Joel, for regarding the request as an valid one and let's hope that there is a dev with enough time to tackle the topic in 2014. Thanks to all who work on LibO and best wishes for a great new year!
In order to limit the confusion between ProposedEasyHack and EasyHack and to make queries much easier we are changing ProposedEasyHack to NeedsDevEval. Thank you and apologies for the noise
Migrating Whiteboard tags to Keywords: (needsDevEval) [NinjaEdit]
To reflect to the original report: It is not necessary to show the comment first to edit it. The "Edit comment" command in the context menu edits the comment directly (back in the day it was named "Insert comment" somewhat misleadingly, but it also edited existing comments). Show or hide does not need to change for that. Also recent bug 158514 adds similar functionality to the Navigator, for more efficient workflows.