Add Mixxx version tags in skins

Bug #1004589 reported by RJ Skerry-Ryan
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Mixxx
Confirmed
Low
Unassigned

Bug Description

We should make sure we are forward compatible.. specifically people have run into trouble with eq-kills (due to powerwindow) and I think beatloop_x_activate.

RJ Skerry-Ryan (rryan)
Changed in mixxx:
milestone: none → 1.11.0
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Daniel Schürmann (daschuer) wrote :

I think we should introduce a version tag

<Version>
    <MinimumMixxx>1.11.0</MinimumMixxx>
    <Skin>05</Skin>
</Version>

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

Hi RJ, Hi Skin designer, Hi Controller Guys,

my original power window button patch introduces a decoupling from the midi buttons and the GUI buttons.
I not sure if this was actually working but we should consider it again because of this bug.

See Bug #876139 and RJs comments in #11

For my feeling it is a good idea to let the skin designer decide a bout the GUI buttons behavior and the midi script writer (controller manufacturer) decide about the midi button behavior.

Mixxx itself should be as much tolerant as possible, to allow different button styles for the same control.

(I am afraid this software design a ideal case and not entirely possible, but we give a try)

I the end the end we can achieve that Mixxx 1.11 works with 1.10 skins like 1.10 does. The same might be possible for midi scrips.

What do you think?

Kind regards,

Daniel

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

I think I failed to do this... oops :(.

jus (jus)
Changed in mixxx:
status: Confirmed → Won't Fix
Revision history for this message
Sean M. Pappalardo (pegasus-renegadetech) wrote :

Updating for 1.12 since this is still a good idea.

Changed in mixxx:
milestone: 1.11.0 → 1.12.0
status: Won't Fix → Confirmed
summary: - make sure 1.10.x skins forward compatible with 1.11.x
+ Add minimum Mixxx versions for skins
summary: - Add minimum Mixxx versions for skins
+ Add Mixxx version tags in skins
Revision history for this message
Sean M. Pappalardo (pegasus-renegadetech) wrote :

We should add a <MixxxVersion> tag just like we have in controller presets (and assume 1.11 for ones with no tag) and add something to the tests to list the skins that have no or an old version tag so we're reminded to check them for forward-compatibility.

Revision history for this message
Owen Williams (ywwg) wrote :

skins already have <manifest> <version>1.12.0.01</version> -- is this not enough?

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

Version is the skin version, not the mixxx version (it's unused currently but I'd like to show it in a skin picker UI in the future).

Having a min Mixxx version tag in the manifest is probably worth doing. Unfortunately 1.11 won't be able to recognize that it can't read a skin but that way 1.12.0 will be able to tell that it can't read future skin versions that are incompatible.

jus (jus)
Changed in mixxx:
milestone: 2.0.0 → none
tags: added: polish usability
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/6481

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.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.