color swatch auto-names

[thomaso]

In the list view of the swatches pane any new swatch gets an auto-name with its defined values.

Unfortunately these names don't auto-change when the color definition got changed by the user. This results in wrong swatch names, both for global and non-global swatches.
To avoid wrong names the user has to rename any swatch manually after changing its color. To fix the name it needs several clicks to the manual renaming option window.

Suggestions:
– auto-change a swatch name when its color definition got changed
– enable renaming on double-click the swatch name

 

 

p.s.: in the actual renaming option window a hint appears: "This is not an undoable operation." – Why does it warn me that I can undo this operation?

[fde101]

This is not a bug, but it is an undesirable behavior.

It should be in the discussions and suggestions forum, not in the bug forum...

I do agree there is plenty of room for improvement here.

[Old Bruce]

1 hour ago, thomaso said:

Suggestions:
– auto-change a swatch name when its color definition got changed
– enable renaming on double-click the swatch name

p.s.: in the actual renaming option window a hint appears: "This is not an undoable operation." – Why does it warn me that I can undo this operation?

 

auto-change a swatch name: I think this would cause so many problems, I have a global colour and I change it to a better shade Now I Don't Know its Name.

enable renaming on double-click the swatch name: Current method is Control click.

"This is not an undoable operation.": I think you are just having some fun here.

[thomaso]

1 hour ago, Old Bruce said:

Now I Don't Know its Name. 

May be you use "ideas" as names, not values? I can imagine that you might get irritated if your color for instance "sky blue" or "green 4" would get a different name by the application. What I meant are names with values only, as shown in my screenshots: I changed a blue into a yellow - but the name (values) remain as blue. This might become disturbing especially if you use global colors and use to alter them. I showed it with this two very different colors to make it more obvious. In reality the color change might be more subtil and a wrong name not such obvious.

 

1 hour ago, Old Bruce said:

I think you are just having some fun here. 

No, I am wondering, why this menu does tell me. It gives the impression I have to be careful. Usually you can undo every change you do in a file – and therefore a warning would make sense only when an undo would NOT be possible.

[Old Bruce]

49 minutes ago, thomaso said:

a warning would make sense only when an undo would NOT be possible.

4 hours ago, thomaso said:

"This is not an undoable operation." – Why does it warn me that I can undo this operation?

That is exactly what it says. You can not undo that operation.

Your other point regarding colour values as names I now understand. You have a valid point which conflicts with my way of working. We'll have to figure something out for that.

 

[thomaso]

24 minutes ago, Old Bruce said:

You can not undo that operation. 

But no, Yes, we can!

However, even if a simple "undo" would not undo, I still could undo by re-rename it

[walt.farrell]

5 minutes ago, thomaso said:

even if a simple "undo" would not undo, I still could undo by re-rename it

True, but you'd have to accurately remember and retype the complete original name. Still, that's not an undo, just a rename

[thomaso]

I'd do it shorter – IF a simple undo would not work:
I'd hit command-c before renaming it. And command-v as re-rename process. No typing at all

[Jim_A]

+1 for swatch names automatically updating when the colour values are changed.

This is a useful feature for print production, especially when global colours are used. 

[Old Bruce]

7 hours ago, Jim_A said:

+1 for swatch names automatically updating when the colour values are changed.

This is a useful feature for print production, especially when global colours are used. 

I really don't like automatic but I do see the value of your desire for it, how about we split the baby and have an auto rename button or check-box for you folks who want it and I get to name things after projects or people's favourite colour and have it stick forever. Check-box would be best I think, set it and forget it.

[thomaso]

4 hours ago, Old Bruce said:

how about we split the baby and have an auto rename button or check-box

It's even easier:
1. auto-re-naming happens only if a name shows the color values, and
2. once a swatch got named with custom name by the user it will not become renamed even if the values get changed.

The current solution automatically assigns a first name of the swatch and names with color values, but will result in incorrect names as soon as the user changes color values without manually changing the name.

 

[thomaso]

On 11/15/2018 at 9:47 PM, fde101 said:

This is not a bug, but it is an undesirable behavior. 

Hm? A swatch gets a name from the application. If the automatic name is no longer correct, then it is wrong. A wrong auto-name is a bug.

It would not be an error if the name was a user-defined name entered by the user.

Compare: You create a new textframe. Its properties appear automatic in the transform palette. If you drag the frame to change size or position then its properties in the transform palette will auto-change, too. – Would you call it just "undesirable" if you would have to type its correct properties in the transform text fields – after you have changed values by dragging?