Bug 145269 - Simple clicking a module gives the impression that this module has the view
Summary: Simple clicking a module gives the impression that this module has the view
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: BASIC (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: BASIC-IDE
  Show dependency treegraph
 
Reported: 2021-10-22 08:44 UTC by Frederic Parrenin
Modified: 2023-01-13 11:15 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frederic Parrenin 2021-10-22 08:44:50 UTC
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.
Comment 1 Jean-Baptiste Faure 2021-10-22 13:29:13 UTC
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
Comment 2 Frederic Parrenin 2021-10-22 16:04:43 UTC
> 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.
Comment 3 QA Administrators 2021-10-23 03:45:27 UTC Comment hidden (obsolete)
Comment 4 raal 2022-10-07 16:32:15 UTC
(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.
Comment 5 Rafael Lima 2022-12-12 20:55:48 UTC
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.
Comment 6 Heiko Tietze 2022-12-16 08:09:41 UTC
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.
Comment 7 Cor Nouws 2023-01-13 11:00:09 UTC
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.
Comment 8 Frederic Parrenin 2023-01-13 11:15:25 UTC
>> 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.