Skined buttons should give a better visual feedback

Bug #907364 reported by Daniel Schürmann
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Mixxx
Fix Released
Low
jus
1.10
Won't Fix
Low
jus
1.11
Fix Released
Low
jus

Bug Description

This is a snippet from Deere Skin:

<State>
 <Number>0</Number>
 <Pressed>btn_hotcue1_1_over.png</Pressed>
 <Unpressed>btn_hotcue1_1.png</Unpressed>
</State>
<State>
 <Number>1</Number>
 <Pressed>btn_hotcue1_1.png</Pressed>
 <Unpressed>btn_hotcue1_1_over.png</Unpressed>
</State>

State 0 is displayed when hotcue is not active (gray); State 1 in active State (red)
When mouse button is pressed the image is toggled. So while using the mouse, the user has no explicit feedback about the state of the hotcue itself.

Solution proposal:
We should provide two alternative images for active-pressed an inactive-pressed state.

I have played around with Gimp and have made some images slightly darker for the pressed state. This leads to a significant better user experience.

Questions:
It is worth to solve this issue for all skins?
It is a good Idea just making the buttons darker for the pressed state?
Should we provide a programmatic way to do this like reading a gamma value from Skin?

@jus: What do you think?

Related branches

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

In lp:~daschuer/mixxx/daschuers_trunk I have a set-up for testing this issue with Deere1280x1024-SXGA.

You may test it on the first deck with beatloop 1 and 2, hotcue 1 and 2, Cue, play and reverse.

Compiled packages can be found here:
http://builds.mixxx.org/builds/experimental-daschuers_trunk/

Note: the push-button is patched with Bug #906310

Revision history for this message
jus (jus) wrote :

I agree we should change the appearance of the buttons in response to a mouse event in a consistant way.

So with a little planning which buttons to change ( we have some simple two-state buttons and some 4-state buttons) this should be fairly easy to do. I would go the route of updating the skins graphics, this would be the easiest way with the existing code. Automatically changing buttons gamma values sounds interesting too, but i cant say how that would interfere with Mixxx color scheme architecture that some skins make use of (Outline)

Targeted to 1.10.1 since it is basically a bug fix.

tags: added: gui usability
Changed in mixxx:
status: New → Confirmed
importance: Undecided → Low
milestone: none → 1.10.1
assignee: nobody → jus (jus)
jus (jus)
Changed in mixxx:
milestone: 1.10.1 → none
Revision history for this message
jus (jus) wrote :

lp:~jus/mixxx/skin-button-feedback has now an updated Deere1280x800-WXGA skin against current lp:mixxx/1.11 with added 3rd and 4th button state graphics. Buttons should now give a better visual feedback about the actual buton state. All buttons are covered except the mini toggle buttons in the grid next to the waveform overview.
Please test. Thanks.

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

Thank you Jus!
Looks and works really good.
Testet lp:~jus/mixxx/skin-button-feedback # 3431.

(While testing I am come over Bug Bug #1007950 "visual feedback for CUE Button like CDJ", but that's a different story. )

jus (jus)
Changed in mixxx:
status: Confirmed → In Progress
tags: added: skin
jus (jus)
Changed in mixxx:
status: In Progress → 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/6200

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.