ask 2 times when selecting midi maps through keyboard

Bug #370945 reported by vladimir prieto
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Mixxx
Fix Released
Low
Unassigned
1.7
Fix Released
Low
RJ Skerry-Ryan

Bug Description

this is a not a critical bug.

when using only keyboard to access preferences and then select a new midi map, it ask "for sure" 2 times. doing this by mouse, it ask only one time.

Changed in mixxx:
assignee: nobody → Albert Santoni (gamegod)
importance: Undecided → Low
milestone: none → 1.7.0
status: New → Confirmed
assignee: Albert Santoni (gamegod) → nobody
milestone: 1.7.0 → none
status: Confirmed → New
Revision history for this message
Albert Santoni (gamegod) wrote :

Can you please list some explicit steps in order to reproduce the problem?

When I do this, I only get asked once:
1) Open MIDI bindings dialog by clicking on the name of my MIDI device in the preferences
2) Hit tab a couple of times to select the "Load Preset" combobox.
3) Hit the down arrow on my keyboard once to select the BCD3000 mapping.

At this point, it immediately asks me if I want to load that mapping. This behaviour is slightly broken because if you wanted to select anything other than the top element, if would try to load the mapping for each element you scrolled through in the list. We sort of need a "load preset" button for after the selection in the combox is done, but I won't fix that right now.

Regardless, the problem I listed above doesn't quite sound like what you're talking about. Can you elaborate more?

Thanks.

Revision history for this message
vladimir prieto (vladimirprieto) wrote : Re: [Bug 370945] Re: ask 2 times when selecting midi maps through keyboard

On Sun, May 3, 2009 at 12:20 PM, Albert Santoni <email address hidden> wrote:

> Can you please list some explicit steps in order to reproduce the
> problem?

ok, in fact is very close that the ones you describe...let's c:

> 1) Open MIDI bindings dialog by clicking on the name of my MIDI device in
> the preferences

i do the same but with keyboard, by hit arrows, tabs...

> 2) Hit tab a couple of times to select the "Load Preset" combobox.

the same...

> 3) Hit the down arrow on my keyboard once to select the BCD3000 mapping.

yeah...but before hit the down arrow, i hit space bar to show the complete
list. then i hit down arrow. when cursor is over my midi mapping i hit
enter.

after that, it ask me to load that mapping, i hit yes (keyboard) and then it
ask me again.

try it and tell me if you get the same

--
Vladimir Prieto Muñoz
http://vladimir.prie.to
http://www.micontrol.cl

Revision history for this message
vladimir prieto (vladimirprieto) wrote :

> Can you please list some explicit steps in order to reproduce the
> problem?

ok, in fact is very close that the ones you describe...let's c:

> 1) Open MIDI bindings dialog by clicking on the name of my MIDI device in the preferences

i do the same but with keyboard, by hit arrows, tabs...

> 2) Hit tab a couple of times to select the "Load Preset" combobox.

the same...

> 3) Hit the down arrow on my keyboard once to select the BCD3000 mapping.

yeah...but before hit the down arrow, i hit space bar to show the complete list. then i hit down arrow. when cursor is over my midi mapping i hit enter.

after that, it ask me to load that mapping, i hit yes (keyboard) and then it ask me again.

try it and tell me if you get the same

Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

Looked into this a bit, apparently the activate() signal of the QComboBox fires twice when you use the keyboard. This happens with the dialog box and without, so it isn't some weird interaction between the dialog and the QComboBox.

This seems to be related to us setting the dialog box index back to 0 at the end of slotLoadMidiMapping -- if I turn that off then the problem doesn't occur.

Revision history for this message
Sean M. Pappalardo (pegasus-renegadetech) wrote :

RJ: so is that a fix or does that break something else?

Revision history for this message
Sean M. Pappalardo (pegasus-renegadetech) wrote :

This problem is gone as of v1.7.2 on Linux and Windows in my testing. Vladimir, please test with Mixxx 1.7.2 and let us know if you still have the problem.

Changed in mixxx:
status: New → Fix Committed
RJ Skerry-Ryan (rryan)
Changed in mixxx:
status: Fix Committed → Fix Released
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/5160

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.