Bug 481743 - confusing edit mode options with multiple panels
Summary: confusing edit mode options with multiple panels
Status: RESOLVED DUPLICATE of bug 480044
Alias: None
Product: plasmashell
Classification: Plasma
Component: Panel (show other bugs)
Version: 5.93.0
Platform: Arch Linux Linux
: NOR minor
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: qt6, usability
Depends on:
Blocks:
 
Reported: 2024-02-24 01:02 UTC by Tammes Burghard
Modified: 2024-02-24 03:50 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tammes Burghard 2024-02-24 01:02:08 UTC
SUMMARY
***
Note that my system is in german and I only guess that the options in question are named "enter edit mode" and "quit edit mode". But I assume that they are unique enough so you get what I am referring to.

My observations (see below) let me assume that edit mode kind of works like a stack where you can stack the edit modes of different panels on top of each other. Instead, there should be only one edit mode and you should be able to choose which panel to focus on.
***


STEPS TO REPRODUCE
1. have a panel -> right click it -> enter edit mode
2. add a second panel -> right click it
3. enter edit mode
4. right click the first panel
5. quit edit mode
6. right click it again
7. quit edit mode

OBSERVED RESULT
3. the option is named "enter edit mode" even though I already am in edit mode (of the other panel)
5. this shows the configuration popup for the first panel
7. now it quits edit mode

EXPECTED RESULT
3. the option should be named something like "edit this panel"
5. this should actually quit edit mode and also there should have been an "edit this panel" option
7. correct, but inconsistent with 5.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.93.0
KDE Frameworks Version: 5.249.0
Qt Version: 6.7.0
Kernel Version: 6.7.6-arch1-1 (64-bit)
Graphics Platform: Wayland
Comment 1 fanzhuyifan 2024-02-24 03:50:33 UTC
This has been fixed in 6.1.

*** This bug has been marked as a duplicate of bug 480044 ***