Bug 470008 - Elisa doesn't honor double click to open
Summary: Elisa doesn't honor double click to open
Status: RESOLVED INTENTIONAL
Alias: None
Product: Elisa
Classification: Applications
Component: general (other bugs)
Version First Reported In: 23.04.1
Platform: Neon Linux
: NOR minor
Target Milestone: ---
Assignee: Matthieu Gallien
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-05-19 16:00 UTC by Greg Lepore
Modified: 2023-05-19 20:27 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Greg Lepore 2023-05-19 16:00:59 UTC
SUMMARY
***
My KDE system is set to select on single click and open on double click, however Elisa opens on single click when adding music via the Files section.

STEPS TO REPRODUCE
1. Open Elisa
2. Change to Files view
3. Single click on a folder

OBSERVED RESULT
Folder is opened

EXPECTED RESULT
Folder is selected


Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Kernel Version: 5.19.0-41-generic (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 2600 Six-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2
Comment 1 Nate Graham 2023-05-19 20:27:09 UTC
This is true, and technically it's a "file view" that you would expect to respect that setting. So I can see where you're coming from.

On the other hand, the entire reason for double-click to exist in the first place is to make it easier to select items by clicking them once so you can then perform actions on them. But these folders have no actions which can be performed on them when selected, aside from the ones that appear on hover, so it wouldn't actually make sense to respect the setting. Therefore, we have to weigh the following:

- On one hand, it's inconsistent with other file views that to respect the setting.
- On the other hand, because this file view has no "selected" state, respecting the setting would have no benefit outside of increasing consistency and would introduce the drawbacks of slower interactions and inconsistency with other grid views within the app.

So in this case we made the judgment that the latter concern carried more weight.

Hope that helps to explain the situation.