-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
store selected table item index when switching library features #9547
Comments
Commented by: daschuer I cannot confirm this with the current master using mouse. |
Commented by: ronso0
The second issue is that the track selection is gone (while the scroll position is kept) when I focus the table again via controller or Tab key. If I press Up/Down keys or scroll with controller encoder, the first track is selected which makes the scroll position jump to the top. I think I'll split this one into multiple bugs. |
Commented by: ronso0 I updated the report, it now just describes the scroll position jump when using a controller. The other aspect of this is in lp:1810810 |
Commented by: daschuer I can confirm this. I t happens also if you use the up and down keys on keyboard. |
Commented by: ronso0 the reason seems to be that the first table cell is somehow focused and the selection jumps there when keys or selection controls attempt to move it. noticed with https://bugs.launchpad.net/mixxx/+bug/1808632 I'm trying to save/restore also the selection focus it when re-activating a library view. |
Commented by: daschuer It this fixed now or in progress by one of the related PRs? |
Issue closed with status Fix Committed. |
Reported by: ronso0
Date: 2018-12-14T06:20:37Z
Status: Fix Committed
Importance: High
Launchpad Issue: lp1808472
Tags: library, usability
scenario:
(for example to create or rename a playlist/crate)*
= tracks table switches to respective library feature
(damn! lp:1810810)
= table shows correcct scroll position
= scroll position jumps to top of the list
master (2.3) 2018-12-14
The text was updated successfully, but these errors were encountered: