-
-
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
controllers can't focus tracks table item if there is only one #9548
Comments
Commented by: daschuer I can confirm the issue with Mixxx 1.2.5 as well. |
Commented by: daschuer I do not have a recipe for an easy fix. I think I would start using gdb and investigate the call stack that is used when more tracks are there and a s new one is highlighted. Than I would use a one track table and repeat the test with a braekpoint a bit down in the call tree. Are you able to single step though the code? Maybe you can than find out, why it does not work with one track and fix it finally. |
Commented by: ronso0 So far I used gdb only to create crash reports. |
Commented by: ronso0 So far I've found out that the first table row is always soemhow focused but not selected/highlighted. In wtracktableview.cpp I can manually select the first row if there's only one, but that would only work for [Playlist],MoveSelection controls, not for Up/Down key presses (real or emulated in librarycontrol.cpp). The issue seems to be in qabstractitemview or qtableview respectively. |
Commented by: ronso0 #3049 that enforces a selection on FocusIn events of WLibraryTableView: |
Issue closed with status Fix Released. |
Reported by: ronso0
Date: 2018-12-15T14:49:33Z
Status: Fix Released
Importance: Low
Launchpad Issue: lp1808632
Tags: easy, library
Reproduce:
= one item/row in tracks table
= neither up/down arrows (keyboard) or [Library],MoveVertical or [..],ScrollVertical allow to focus the item
But pressing the right arrow key does select the row. It seems the leftmost table cell has 'focus' somehow but the row isn't selected.
master (2.3) 2018-12-15
The text was updated successfully, but these errors were encountered: