I give basic programming lessons to 1st year students at univ using macros in LO. I have remarked a common problem that students have. In the module tree view, you can click on a module. The name of this module will have a blue background, giving the impression that this module has the view. But you actually need to double click to give it the view. I think this is very confusing. LO should: 1. Either not give a blue background to the module name until you actually double click it 2. Or allow to switch module view with just a simple click.
What is your OS? I do not see this blue background under Ubuntu. From my understanding: single click -> select double click -> open Status has been set to NEEDINFO, please set it back to UNCONFIRMED once requested information has been provided. Best regards. JBF
> What is your OS? I do not see this blue background under Ubuntu. My OS is debian but I see it also on Windows. The blue background is for the module name in the module tree view, I am not sure you read correctly my message. > From my understanding: > single click -> select > double click -> open That is the problem. You single click on a module which gets selected, but the view is still on the previous module. You have no straightforward way to see which module is opened.
[Automated Action] NeedInfo-To-Unconfirmed
(In reply to Frederic Parrenin from comment #2) > You have no straightforward way to see which module is opened. This is visible in the window's title. Reproducible.
I may be a bit biased here, since I've been using the Basic IDE for a long time. But I wouldn't expect that a module would be opened by simply clicking it once. Anyways, it would be nice to have the input from the UX team.
We discussed the topic in the design meeting. The situation is the same for the Stylist where modifying a style that is not currently active is a requirement (bug 94427). And the proposal there is to show the active item if not selected in gray (could also be a darker/lighter highlight color). In general we should either select a depending list of data or start some action on single click. As for the modules list we could open the file on single click.
Hi Frederic, * (In reply to Frederic Parrenin from comment #0) > 1. Either not give a blue background to the module name until you actually > double click it Traveling through the various libraries and modules can also be done with the key board: Up, Down, Right, Left, Enter. And the background color shows where you are navigating in the list. We have similar behavior in the Navigator and Stylist, indeed: (In reply to Heiko Tietze from comment #6) > The situation is the same for the Stylist where modifying a style that is > not currently active is a requirement (bug 94427). And the proposal there is > to show the active item if not selected in gray (could also be a > darker/lighter highlight color). Sounds as a sensible solution.
>> The situation is the same for the Stylist where modifying a style that is >> not currently active is a requirement (bug 94427). And the proposal there is >> to show the active item if not selected in gray (could also be a >> darker/lighter highlight color). > > Sounds as a sensible solution. I agree this should an acceptable solution. I can only confirm that the current situation is really problematic with my students which are usually not computer experts.
Dear Frederic Parrenin, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug