TDE
/
kompose
3
1
Fork 0
Code Issues 2 Pull Requests Releases Wiki Activity
Labels Milestones
New Issue

Keyboard desktop navigation misbehaves when "Show empty desktops minimized" is on #10

Open
opened 3 years ago by blu.256 · 0 comments
blu.256 commented 3 years ago
Collaborator

Mentioned in PR #9:

If I enable "Layout empty virtual desktops minimized" in the settings and I have windows only on destop 1 and 2 (top row), then moving down from virtual desktop 2 ends up in desktop 3 instead of 4. Viceversa (3 -> 2 when going up) also happens. And Ctrl+J/Down arrow from virtual desktop 4 goes to desktop 1. This does not seem to happen when that option is not enable or when there are windows on all desktop, so no desktop is minimized.

Confirmed with 4 and 20 virtual desktops, so it supposedly covers the whole range.

Problem is probably in the implementation of either of the getNeighbour() functions defined in komposelayout.cpp.

Mentioned in PR #9: > If I enable "Layout empty virtual desktops minimized" in the settings and I have windows only on destop 1 and 2 (top row), then moving down from virtual desktop 2 ends up in desktop 3 instead of 4. Viceversa (3 -> 2 when going up) also happens. And Ctrl+J/Down arrow from virtual desktop 4 goes to desktop 1. This does not seem to happen when that option is not enable or when there are windows on all desktop, so no desktop is minimized. Confirmed with 4 and 20 virtual desktops, so it supposedly covers the whole range. Problem is probably in the implementation of either of the `getNeighbour()` functions defined in `komposelayout.cpp`.
blu.256 changed title from Keyboard desktop navigation misbehaves when "Show empty desktosp minimized" is on to Keyboard desktop navigation misbehaves when "Show empty desktops minimized" is on 3 years ago
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
r14.1.x
master
r14.0.x
issue/10
Labels
Apply labels
Clear labels
GE/need-info
General - need additional info from contributor PR/keep-branch
Pull request - do not delete branch after merging PR/not-ok
Pull request - need fixing PR/rfc
Pull request - request for comments PR/update-trans
Pull request - update to translation files needed PR/wip
Pull request - work in progress RS/R14.0.x
Related to R14.0.x series RS/R14.1.x
Related to R14.1.x series SL/critical
Severity level - critical SL/major
Severity level - major SL/minor
Severity level - minor SL/normal
Severity level - normal SL/regression
Severity level - regression from previous version SL/trivial
Severity level - trivial SL/wishlist
Severity level - wishlist request ST/duplicate
Status - duplicate of another issue ST/invalid
Status - invalid report ST/notourproblem
Status - not our problem ST/rejected
Status - rejected ST/wontfix
Status - won't fix ST/worksforme
Status - works for me, unable to reproduce
No Label GE/need-info PR/keep-branch PR/not-ok PR/rfc PR/update-trans PR/wip RS/R14.0.x RS/R14.1.x SL/critical SL/major SL/minor SL/normal SL/regression SL/trivial SL/wishlist ST/duplicate ST/invalid ST/notourproblem ST/rejected ST/wontfix ST/worksforme
Milestone
Set milestone
Clear milestone
No items
No Milestone
Assignees
Assign users
Clear assignees
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: TDE/kompose#10
Write Preview
Loading…
Cancel
Save
There is no content yet.
Delete Branch '%!s(<nil>)'

Deleting a branch is permanent. It CANNOT be undone. Continue?

No
Yes