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
Return keyboard shortcut makes [Playlist], ToggleSelectedSidebarItem stop working #7061
Comments
Commented by: carl-barimore I've noted the same behaviour when using a Numark DJ2Go with the bundled Numark DJ2Go mapping (which also uses those three controls). The three controls all work fine in 1.11 development builds up to bzr3821 (14 April). From bzr3836 (23 April), ToggleSelectedSidebarItem no longer works. |
Commented by: rryan I'll take a look. |
Commented by: rryan Ah -- Ok. So I think this was caused by introducing keyboard mappings for Return.
The toggle-selected control works by faking a Return press on the sidebar widget. I don't have an explanation for why select-next/prev would stop working after that, but I can confirm that after removing the keyboard shortcut toggle-selected starts working again. |
Commented by: rryan A workaround is to fake a Left or Right press to to close/open, since we don't have shortcuts for those :P. But LibraryControl should probably just not fake keyboard presses. |
Issue closed with status Fix Released. |
Reported by: uklotzde
Date: 2013-05-30T18:13:38Z
Status: Fix Released
Importance: Medium
Launchpad Issue: lp1185926
Tags: 1.11, controls, midi, playlist
My Vestax VCI-300 controller script maps the following [Playlist] controls to buttons:
When starting Mixxx the SelectNextPlaylist/SelectPrevPlaylist can be used for sidebar navigation. But after toggling a sidebar item with ToggleSelectedSidebarItem all those engine controls become unusable. I've verified that the values are correctly set by the controller script, but the engine doesn't recognize any further value changes.
I think those controls worked in the development versions for 1.11, but there seems to be a regression in the 1.11 release version.
OS used for testing: Ubuntu 13.04 64-bit
The text was updated successfully, but these errors were encountered: