bug - tinted color is not revealed on the wheel

[darthpixel]

seq

- create an objA with some color

- create a clone objB and select it

- switch color tab to tint and set any (be brave)

- get back to wheel

 

wheel is not revealing the tint color (even if the top left line/fill colors are properly updated

this is IMO a bug as there is no info that this color is a tint

and the tint is not dependant color

[fde101]

I don't believe this is a bug.  It may or may not be a bug that you can apply a tint at all if you do not have a global color applied to the selected object.

The tint is a per-object offset from the applied color, while the color wheel represents the selected color itself (independent of selection).

If you want to change the color out from underneath the tint without losing the tint itself, you can do so by first defining the intended color as a global color in the document, then applying the tint to that (which I believe is its intended use case - it is really meant to be used with global colors rather than with colors which are selected directly).  If you edit the global color, the tint does remain as an offset from that global color.

This allows having multiple objects at different offsets from a single global color, such that editing that one color updates the underlying color for all of the objects which have tints of that color applied.

Selecting a color on the wheel replaces the color entirely, completely removing the tint.

 

Note that if you want to apply the tint to the color itself so that it is reflected on the wheel, you can do so by applying the tinted color to an opaque object then capturing the resulting color with the eyedropper (it will be an RGB color if using this approach, which might be important to note if you are working in CMYK or spot colors):

 

 

It would be nice actually to have an "Apply" button added to the Tint window that would automate this without the need for the opaque object workaround and to retain compatibility with CMYK.

 

Also, note that if this actually were a bug, you are reporting it in the wrong section of the forum - this area is for feature requests, there is a different section of the forum for bug reports.

[darthpixel]

i do understad what tints are (should be)
but the issue is that when you click on the object then your color tab is not revealing that this is neither tint nor its real color
the wheel presents "the base color" but it's not what the visible color of this object is

and there is no way to discover it (at least i don't see such info)

imo if the object color is tinted then color wheel should switch automatically to tint tab

[fde101]

1 hour ago, darthpixel said:

imo if the object color is tinted then color wheel should switch automatically to tint tab

It actually does switch when an object with a global color is selected, but not if you tint something that has its own local color.

As adding tints to objects with non-global colors is apparently possible, I do agree that would be a good improvement, but the fact that it does not currently do that does not appear to be a bug.

[darthpixel]

On 2/9/2023 at 1:44 PM, fde101 said:

the fact that it does not currently do that does not appear to be a bug.

imo the issue is "the secret knowledge"
it's like switching off the light in a livingroom by closing the hatch in a basement
it works and if you know it then you can live with it
but isn't it a bug?
if i select an object i expect either to see its color on the wheel or to see clear info that it's a tint

you know what i mean

this is misleading as hell and from a objective point of view it appears as a bug

now when i have the secret knowledge i can admit that this can be a "usability problem" but still...

[DWright]

This is not a bug as when a tint is applied the original base colour is not changing but rather white is added on top of the colour making the colour lighter which is why the wheel is showing the base colour.

[darthpixel]

On 2/27/2023 at 5:16 PM, DWright said:

This is not a bug 

please see it fron this side
i switch the light-switcher next to my entrance and in a result the garage door is opening

technically it's not a bug because it does what was desegned

but functionally it is a bug as it doesn't do what is usually expected

 

and this is kinda secret knowledge which is obvious once you know it
but still... it's not clear as there is no information what is happening and why

 

maybe it should be marked as a usability problem rather than a bug