| Summary: | EDITING: Enhancement: display the error message in full text of "Explanation" | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | bugquestcontri |
| Component: | Calc | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED INVALID | ||
| Severity: | enhancement | CC: | gerard.fargeot |
| Priority: | medium | ||
| Version: | 3.6.6.2 release | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | BSA | ||
| Crash report or crash signature: | Regression By: | ||
| Attachments: | mock up of "best version" | ||
|
Description
bugquestcontri
2013-06-15 00:27:07 UTC
Question: After filing the "bug report" I open it and set the right field of "importance" to "enhancement". Is this appreciated, of no meaning or even disturbing? Please advice. The meaning of error is displayed in the status bar when the focus is on the cell. Is this enough for you or do you maintain this enhancement request ? Created attachment 80868 [details]
mock up of "best version"
Thanks for the hint with the status bar. I never saw.
This is then a part of the story and a nice solution.
I created a mock-up of my "best version". Maybe this could be implemented in the future to provide more information. For me personally the information in the status bar is good an helps me typically to make corrections. But I thought mainly about less Calc-Formula experienced people. Fot them the "best version" should be very helpful.
Dear Bug Submitter, Please read the entire message before proceeding. This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of FDO It is fine to close this bug. I made a separate enhancement request. |