Skip to content

Auto assign hotcue color#2122

Merged
uklotzde merged 2 commits intomixxxdj:masterfrom
Holzhaus:auto-assign-hotcue-color
Jun 1, 2019
Merged

Auto assign hotcue color#2122
uklotzde merged 2 commits intomixxxdj:masterfrom
Holzhaus:auto-assign-hotcue-color

Conversation

@Holzhaus
Copy link
Copy Markdown
Member

@Holzhaus Holzhaus commented May 26, 2019

This adds the ability to assign hotcue colors automatically (based on the index), similar to what Serato does.

Currently missing:

  • Translations

@Holzhaus Holzhaus marked this pull request as ready for review May 26, 2019 14:21
@Holzhaus
Copy link
Copy Markdown
Member Author

By the way, I'm unsure what the preferred naming scheme for control objects is. Is this documented somewhere? I see both PascalCase and lowercase_with_underscores being used.

@uklotzde uklotzde added this to the 2.3.0 milestone May 26, 2019
@uklotzde
Copy link
Copy Markdown
Contributor

As far as I know we must not update the translation files locally. Those generated files are fetched from Transifex.

@Holzhaus
Copy link
Copy Markdown
Member Author

As far as I know we must not update the translation files locally. Those generated files are fetched from Transifex.

I followed step 1-4 of the procedure described in wiki to update the translation templates for Transifex.

@daschuer
Copy link
Copy Markdown
Member

Yes, @uklotzde is right. We updated the translation templates directly from the master branch.
Doing it in feature branches may introduce merge conflicts.

Can you please remove the last commit and force push?

git reset --hard HEAD^1
git push -f

@Holzhaus Holzhaus force-pushed the auto-assign-hotcue-color branch from 23191fe to b37b64a Compare May 26, 2019 22:52
@Holzhaus
Copy link
Copy Markdown
Member Author

@daschuer Ok, done.

Comment thread src/preferences/dialog/dlgprefdeckdlg.ui Outdated
@uklotzde
Copy link
Copy Markdown
Contributor

Nice addition! Just a minor comment about spelling. A native speaker may double check this.

@Holzhaus Holzhaus force-pushed the auto-assign-hotcue-color branch from b37b64a to 167f537 Compare May 29, 2019 13:17
@Holzhaus
Copy link
Copy Markdown
Member Author

Holzhaus commented Jun 1, 2019

@uklotzde @daschuer Let me know if you want me to change anything else before merge. In particular, should I use a lowercase_with_underscore or PascalCase name as control object key?

@uklotzde
Copy link
Copy Markdown
Contributor

uklotzde commented Jun 1, 2019

I think PascalCase is fine since most properties in the [Controls] section already use it.

this, SLOT(slotJumpToCueOnTrackLoadCheckbox(bool)));

// Automatically assign a color to new hot cues
m_bAssignHotcueColors = m_pConfig->getValue(ConfigKey("[Controls]", "AutoHotcueColors"), false);
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought about enabling this feature by default to let users notice. But on the other hand that might confuse and distract existing users. Let's be conservative and let users discover it for themselves.

@uklotzde
Copy link
Copy Markdown
Contributor

uklotzde commented Jun 1, 2019

LGTM. Thank you very much!

@uklotzde uklotzde merged commit 00f279d into mixxxdj:master Jun 1, 2019
@Be-ing
Copy link
Copy Markdown
Contributor

Be-ing commented Jun 9, 2019

I don't understand the purpose of this new option. As far as I can tell there is no way for users to specify what hotcue gets assigned to what color unless they do that manually for each hotcue, so what is the benefit of assigning hotcues to random colors with this option?

@uklotzde
Copy link
Copy Markdown
Contributor

The colors help to visually distinguish different hot cues. The assigned color follows the predefined color palette which is reasonable and convenient. If you want to assign different color you have to edit the cue point manually as before.

@Holzhaus
Copy link
Copy Markdown
Member Author

@Be-ing Assigning different colors automatically is what Serato does by default, too. This feature comes in handy when using a hardware controller with colored performance pads, where you don't have a number printed on the pad. IMO it makes it much easier to remember what hot cue is used for what.

Editing a hot cue point to assign a color manually takes quite a bit of time and can be difficult to do with a DJ controller. And sometimes you only need different colors for different hot cues, but do not care which particular color an individual cue point has.

@ferranlala ferranlala mentioned this pull request Jun 30, 2019
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants