can't create new mapping with wizard from scratch

Bug #1945109 reported by Owen Williams
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
Confirmed
Medium
Unassigned

Bug Description

I have a controller that is not supported by Mixxx. I'd like to start mapping by using the midi mapping wizard, but the Wizard button is disabled unless a mapping is selected. This is a paradox. A simple workaround would be to create a new preset called "Blank Midi Mapping" with nothing configured. (easy starter bug!)

Revision history for this message
ronso0 (ronso0) wrote :

Confirmed. I noticed it with the MIDI Through, though:
* enable MIDI Through, Apply
= Wizard button is not activated
* close + open preferences
= Wizard button enabled

Changed in mixxx:
status: New → Confirmed
importance: Undecided → Medium
milestone: none → 2.4.0
Revision history for this message
ronso0 (ronso0) wrote :

maybe this and https://bugs.launchpad.net/mixxx/+bug/1945108
are related to incorrect isDirty(), see
https://bugs.launchpad.net/mixxx/+bug/1920844
([unchanged] mapping is reload when clicking Okay in any other page)

tags: added: controllers preferences
Revision history for this message
Be (be.ing) wrote :

Is this on the main branch or 2.3? I am pretty sure we solved a regression with this during the 2.3 beta period, but it's plausible that refactoring on the main branch created a separate regression.

Revision history for this message
ronso0 (ronso0) wrote :

I noticed it on main.

btw the bug occurs also the other way around:
disable a controller, Apply and the Wizard button is still enabled and would also start the wizard (after being prompted to Apply the 'changes')

Revision history for this message
ronso0 (ronso0) wrote :

After a quick check I think it's just that the Wizard button needs to be updated in slotApply, not just in slotUpdate.

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/10540

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.