Mixxx

For advanced Mixxx skinning, are these additional widget types needed?

Asked by jus

Currently struggling with implementing some feature for the Deere skin.

Looking for the following:

1. A widget that trigger visibility of another widget on mouse over. E.g. if you hover over the waveform, an extra widget becomes visible on the bottom, that holds some controls.

2. A kind of overlay widget listening for onclick mouse events, that triggers action with another widget, but does not block the underlaying controls. E.g. If you click in the text row widget that holds artist/BPM etc, it triggers a <nextcontrol> in a widgetgroup to switch to the next stack.

Maybe you have an idea how to solve this or workaround this with the existing skinning elements.

Question information

Language:
English Edit question
Status:
Expired
For:
Mixxx Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
jus (jus) said : 		#1

Upon further testing, i found another potentially useful addition.

3. An extension to wslidercomposed, where the slider (bg image) scales, depending on the value of the connected control. E.g. have a playposition slider, where the slider would allow to see how far you are in the track/sample (====----). This is useful if screen space is tight. We have something similar with rotating a single image around its axis in wknobcomposed,

Revision history for this message
RJ Skerry-Ryan (rryan) said : 		#2

For #3 -- is it a case that <Overview> doesn't currently cover?

Revision history for this message
jus (jus) said : 		#3

With <Overview> you can make the handle move left-to-right. But i thought about scaling according to progress, basically a progress bar. Could be helpful e.g. for sampler cells, where the extended view isn`t always necessary.

Revision history for this message
jus (jus) said : 		#4

for #2, i`ll use the following workaround for the time being:

Fake a click-able multi-state widget by stacking a transparent PushButton dummy (the trigger) on top of the individual WidgetGroups (the content). PushButton tracks the size of the active WidgetGroup and resizes. Notice that the trigger has the same TooltipId as the content.

Example:
Show/hide Cents display in Key widget
Show/hide BPM display in BPM widget

Revision history for this message
Launchpad Janitor (janitor) said : 		#5

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
RJ Skerry-Ryan (rryan) said : 		#6

.

Revision history for this message
Launchpad Janitor (janitor) said : 		#7

This question was expired because it remained in the 'Open' state without activity for the last 15 days.