-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Color preferences improvements #2589
Changes from 4 commits
a653006
29158a5
7e1be9e
30aaea8
3b66047
d990c5e
c53f7c1
b4d3fa5
04ed468
a171d13
68742d9
f9714bb
539d4da
7b15170
5d4321f
75b3af5
edc4af6
3ab4f63
5cb7e2f
326008d
b267a44
4176013
9c5cd43
fa3cac9
089fc08
61ecb24
37a57b7
3d68315
73ee264
8e95102
5f601ce
e9c2d34
74b47c3
441b069
f1a7c73
989d335
2a8f635
d5e217a
61f5a71
f189fee
4030280
4b3f9b4
a82bf80
cfce951
f29e3b8
3126268
9db6ad2
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -6,7 +6,7 @@ | |
<rect> | ||
<x>0</x> | ||
<y>0</y> | ||
<width>524</width> | ||
<width>656</width> | ||
<height>333</height> | ||
</rect> | ||
</property> | ||
|
@@ -29,27 +29,41 @@ | |
<item row="0" column="0"> | ||
<widget class="QLabel" name="labelHotcueColors"> | ||
<property name="text"> | ||
<string>Hotcues:</string> | ||
<string>Hotcue Palette</string> | ||
</property> | ||
</widget> | ||
</item> | ||
<item row="0" column="1"> | ||
<widget class="QComboBox" name="comboBoxHotcueColors"/> | ||
<widget class="QComboBox" name="comboBoxHotcueColors"> | ||
<property name="sizePolicy"> | ||
<sizepolicy hsizetype="Expanding" vsizetype="Fixed"> | ||
<horstretch>0</horstretch> | ||
<verstretch>0</verstretch> | ||
</sizepolicy> | ||
</property> | ||
</widget> | ||
</item> | ||
<item row="1" column="0"> | ||
<widget class="QLabel" name="labelTrackColors"> | ||
<property name="text"> | ||
<string>Track:</string> | ||
<string>Track Palette</string> | ||
</property> | ||
</widget> | ||
</item> | ||
<item row="1" column="1"> | ||
<widget class="QComboBox" name="comboBoxTrackColors"/> | ||
<widget class="QComboBox" name="comboBoxTrackColors"> | ||
<property name="sizePolicy"> | ||
<sizepolicy hsizetype="Expanding" vsizetype="Fixed"> | ||
<horstretch>0</horstretch> | ||
<verstretch>0</verstretch> | ||
</sizepolicy> | ||
</property> | ||
</widget> | ||
</item> | ||
<item row="2" column="0"> | ||
<widget class="QLabel" name="labelAutoHotcueColors"> | ||
<property name="text"> | ||
<string>Auto hotcue colors</string> | ||
<string>Cycle hotcue colors</string> | ||
</property> | ||
<property name="buddy"> | ||
<cstring>checkBoxAssignHotcueColors</cstring> | ||
|
@@ -62,7 +76,7 @@ | |
<string>Automatically assigns a predefined color to a newly created hotcue point, based on its index.</string> | ||
</property> | ||
<property name="text"> | ||
<string>Assign predefined colors to newly created hotcue points</string> | ||
<string>Select consecutive palette colors for new hotcues</string> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The palette colors aren't necessarily consecutive as they can be in any order depending on the "Assign to Hotcue Index" column. However, I'd suggest we remove this option completely - see PR #2578, There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think it is very usable to have this option separate from the palette editor. |
||
</property> | ||
</widget> | ||
</item> | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now it's a bit cumbersome so set a single default color for a large palette because you'd have to remove all the other numbers in the index column by hand. It's also a bit confusing because we now have numbers for the built-in track color palettes, too. The previous situation was probably also confusing, so I'm not sure which one is better. If we keep this change I think we need a context menu item to unset all indices in the palette editor.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The idea was to have always the coloumn populated with the cue numbers and enable the use via the box.
So you only need to edit the column if you are not fine with this. This should effect virtually no one, isn't it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's say I have a palette with 10 colors. One of the colors is red. If I want all my new cues red, I have to set "assign to hotcue number" to 1 for red and an empty value for all others. Before, I could just double click next to the red color and type 1. Done.
Now I have to the the same and then delete the numbers from all other rows.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should be move into the paletteditor(model) classes. If there are no assigned hotcue indices, we could display grey placeholder values in the "assign to hot cue numbers" table (the placeholder values are not saved) . As soon as you set one value eyplicitly, the placeholder values should disappear.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting. That was not self explaining to me. I have actually tried to add all cue numbers to red like 1, 2, 3 ... but it fails.
A combobox with all palette colors + color by number for default cue color will be IMHO quite easy to understand compared to that.
I like to avoid to bothering the user with the palette editor if he just want to select the default color.
Does this work for you as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree that setting the default color via the palette editor causes too much friction, however let's keep this out of this PR as I have an idea for that that I'd like to try in a separate PR after this one has been merged.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you implement this? The current change also prevent reordering the palette with no indices set. Also, palette could be big so you should check if
i
is less than the number of hotcues.