Cannot move library cursor by mouse

Bug #1754889 reported by Aleš Černý
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Mixxx
New
Undecided
Unassigned

Bug Description

Blue track list cursor can be moved only by keyboard arrows, when I click on a track row by the mouse the field is only marked by white border, but blue cursor remains on current track. When I then press keyboard arrow up respectively down, blue cursor appears above respectively under the white marked field. Navigation through left panel (Tracks, AutoDJ, Playlists,...) works normal though. Replicable in all skins.

2.1.0-beta1 (build 2.1 r6519) on Windows 10

Revision history for this message
Bjoern K. (amusing-random-alias) wrote :

Same here. Mixxx 2.1 (current release version), Windows 10 x64 and x86.

The tracklist cursor is only available after pressing arrow up/down and when more than one search result or song is displayed in the library view.
When clicking on any item, there is just a border around it.

Putting a listed item to an available deck by drag & drop or double click still works without the cursor though.

Revision history for this message
kek001 (kek001) wrote :
Revision history for this message
Daniel Schürmann (daschuer) wrote :

Not sure, because https://bugs.launchpad.net/mixxx/+bug/1751482
Effects only the 32 bit version Mixxx.

@Bjoern K.: Can you verify if
http://downloads.mixxx.org/builds/2.1/release/mixxx-2.1.4-2.1-git6765-release-x86.exe
Works?

Revision history for this message
Aleš Černý (dnchl) wrote :

Here my latest report:

On 2.1.1. 32-bit (latest): OK
On 2.1.3. 32-bit (latest): The same bug as on 2.1.0-beta1 (build 2.1 r6519) as described

(I run 32-bit Mixxx version on Windows 10 64-bit due to sound card driver compatibility)

Revision history for this message
Daniel Schürmann (daschuer) wrote :

Interesting is the 2.1.4 our release candidate linked above.
Does it suffer the issue?

Revision history for this message
Be (be.ing) wrote :

Aleš, the link Daniel posted above in comment #3 is different from Mixxx 2.1.3. Please test that. If it works, we will release it as Mixxx 2.1.4.

Revision history for this message
Aleš Černý (dnchl) wrote :

Yes, the mixxx-2.1.4-2.1-git6765-release-x86.exe is OK. Thank you.
Do you know the source of the bug and why it came back?

Revision history for this message
Be (be.ing) wrote :

Thank you for confirming. We are not sure what the source of the bug was, but setting the Jenkins build server to clear its workspace before each build seems to have solved it.

Revision history for this message
Aleš Černý (dnchl) wrote :

Hey, just installed 2.2.0 (build 2.2 r6659) and the bug is back :(

Revision history for this message
Aleš Černý (dnchl) wrote :

2.1.8 (build 2.1 r6828) is OK though.

Checked 32bit versions.

ales

Revision history for this message
Daniel Schürmann (daschuer) wrote :

Thank you for the update.

Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/9173

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.