redhexagonal

So when I change the Live theme, some of the objects in my patch change their colours, and UI elements become hard to see or invisible. Is there any logic to which elements change colour? 

It seems like changing from an object's default colours might lock that element's colour or might not, and I have no idea why.

So when I change the Live theme, some of the objects in my patch change their colours, and UI elements become hard to see or invisible. Is there any logic to which elements change colour? 
It seems like changing from an object's default colours might lock that element's colour or might not, and I have no idea why.

So when I change the Live theme, some of the objects in my patch change their colours, and UI elements become hard to see or invisible. Is t

themes-messes-up-colours

same here... for example if I put a bright color scheme in Ableton some of my texts in my M4L devices become dark. The problem is that my M4L devices have black background!

Just change the colour of the white text slightly and that will lock the colour for that element.. If an element is default colour Live changes it to the skin’s colour scheme.

Just change the colour of the white text slightly and that will lock the colour for that element.. If an  element is default colour Live changes it to the skin’s colour scheme. 

You can even change it back and it'll stay put. But you can never go back. Your background will still change and make text unreadable.

- use [live.colors], like in most of Max4Live's flagship devices. 

- set the background color of your device with view>inspector window>(un)locked patcher background color. Or just a big rectangle will work too.

It feels like a half implemented feature. Max is obviously aware of Live's colors, otherwise it wouldn't have this bug. It also has color palettes. It could have a "dynamic palette" which always matches Live's theme.

More complete solutions are:
 - use [live.colors], like in most of Max4Live's flagship devices. 
 - set the background color of your device with view>inspector window>(un)locked patcher background color. Or just a big rectangle will work too. 

In Live 10 it does feel a bit inconsistent. I usually cycle through each live stock theme and if the colors change I would change it back and save the device. This mostly worked, but sometimes it would be stubborn.

In Live 11, you can set the color to be fixed or dynamic.

If you are dynamically creating objects via Javascript, this is strategy I used...

It would be nice to simply have an attribute we could set to allow objects to be fixed or dynamic, but this got the job done for now.

Set  up a live.colors object to bang a message that calls a function within  your Javascript object. It didn't seem to matter, but I put a small 10ms  delay on mine.

Use the setattr method to re-establish the color attributes of the dynamically  created objects. You can essentially copy and paste the color settings you set before.  However, through testing, you may need to add some more. For example, for a textbutton object, "textcolor", "textovercolor"  and "textoncolor" seem to be the combination that kept things  consistent across ableton 10 and 11 for me.

Once things are working as expected, build some kind of protection to ignore the function call when the dynamic objects have not been generated. I used a gate on live.colors that doesn't open until the device is fully  loaded. I also have an if statement within the function to check if  certain variables exist.

My dear, The behavior you're experiencing when changing the Live theme in a patch is likely determined by the specific design choices made by the developers of the software or framework you're using.

When you switch to a different theme, the colors of various objects and UI elements may change to maintain visual consistency and adhere to the design principles of the new theme. However, the specific logic behind which elements change color can vary depending on the implementation.

To understand the specific logic behind the color changes in your patch, you may need to refer to the documentation or resources provided by the software or framework you're using. These resources might explain the design principles and guidelines followed by the theme, as well as any customization options available to you.

My dear, The behavior you're experiencing when changing the Live theme in a patch is likely determined by the specific design choices made by the developers of the software or framework you're using.
When you switch to a different theme, the colors of various objects and UI elements may change to maintain visual consistency and adhere to the design principles of the new theme. However, the specific logic behind which elements change color can vary depending on the implementation.
To understand the specific logic behind the color changes in your patch, you may need to refer to the documentation or resources provided by the software or framework you're using. These resources might explain the design principles and guidelines followed by the theme, as well as any customization options available to you.

When changing the Live theme in a patch, the behavior of how objects and UI elements change their colors can be influenced by several factors, including the theme's design, the default settings of the objects, and how the software handles color changes.

Live themes are designed to provide a cohesive visual experience throughout your patch. However, the specifics of how objects' colors change when you switch themes can vary based on the default colors of the objects and the logic implemented in the theme.

Default Object Colors: Objects within your patch might have default colors assigned to them. When you switch to a new theme, these default colors could be overwritten by the theme's color scheme. This might result in the object's appearance changing according to the new theme's design.

Theme Customization: Live themes often include predefined color palettes and rules for color changes. Some objects might adhere to these rules more strictlyh, resulting in noticeable color changes, while others might retain their original colors to ensure better visibility.

Visibility Considerations: Some UI elements might become hard to see or invisible due to the contrast between their original colors and the new theme's colors. Themes are often designed to ensure readability and accessibility, but the specific contrast between UI elements can vary.

Themes messes up colours