# \[NEW\] Theming Update: Major Visual Changes in Perspective

**URL:** <https://forum.inductiveautomation.com/t/new-theming-update-major-visual-changes-in-perspective/34020>\
**Category:** Ignition Early Access\
**Created:** [April 17, 2020, 11:41pm UTC](https://forum.inductiveautomation.com/t/new-theming-update-major-visual-changes-in-perspective/34020 "2020-04-17T23:41:06Z")\
**Posts on this page:** 1\
**Showing post:** 24

<div class="post-metadata">

**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\
**Post date:** [May 27, 2020, 6:23pm UTC](https://forum.inductiveautomation.com/t/new-theming-update-major-visual-changes-in-perspective/34020/24 "2020-05-27T18:23:03Z")

</div>

Yes.

A lot of users approached Perspective Styles form the beginning as a way to define broad-scope settings across components because Perspective themes were not fully developed and fleshed-out. This approach worked to move users along, but from a maintenance and adaptability perspective, this is the wrong approach.

Style settings and colors which are intended to be used throughout the project should be applied through a project’s theme, and Perspective Style Classes should be used in instances like one-offs, or when you want an appearance based on some property or state. In this way, Style Classes prevent you from needing to bind potentially dozens of individual style properties against a value.

In your case, you should provide an additional file of colors in the theme directory - `themes/custom_colors.css` with a color like `--kg-light-grey: #e7dbdb`(don’t add your color to the existing list of named colors) and make sure to import this file within the top-level theme files.

`themes/light.css` should look like this, as should the other themes you want to use your colors in:

```auto
@import "./light/index.css";
@import "./custom_colors.css";

```

Then, you can access your color anywhere on the project just as @paul-griffith suggested: `var(--kg-light-grey)`.

Binding the Style Class in use to the Alarm state is going to be a little trickier, but should be something like this:

 ![Screen Shot 2020-05-27 at 11.19.42 AM](https://us1.discourse-cdn.com/inductiveautomation/original/2X/d/d891f2b9117edda70fd73aad919640f7d1d1be55.png)  
Note that this binding is on the `classes` property, not `style`. In this example, “ActiveAlarm” is a Perspective Style Class at the top level of the Styles directory and houses style settings I want applied to components in the event a specified Alarm is in an active state.

---

_[View the full topic](https://forum.inductiveautomation.com/t/new-theming-update-major-visual-changes-in-perspective/34020)._