# Changing the color or build in images of components **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [August 4, 2023, 7:58pm UTC](https://forum.inductiveautomation.com/t/changing-the-color-or-build-in-images-of-components/77479 "2023-08-04T19:58:30Z")\ **Posts on this page:** 1\ **Showing post:** 10
**Author:** ![aaronrai24](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/aaronrai24/32/87248_2.png) [@aaronrai24](https://forum.inductiveautomation.com/u/aaronrai24)\ **Post date:** [August 5, 2023, 2:11am UTC](https://forum.inductiveautomation.com/t/changing-the-color-or-build-in-images-of-components/77479/10 "2023-08-05T02:11:28Z")
To add on to this you can still use style classes in a similar way by using 'stub classes'. This allows you to still have the luxury of selecting your style class from the selector, but the liberty to add your own CSS in the stylesheet. > [@Create a style class that i can bind to with non-dialog properties?](https://forum.inductiveautomation.com/t/create-a-style-class-that-i-can-bind-to-with-non-dialog-properties/76603/5): > > Would require embedding a full CSS parser in the Java side of the application. Not impossible, but not a high priority. You could make a 'stub' style class (with no actual effects) so that it shows up in the selector, and then do all of the actual CSS authoring in the stylesheet. The big downside there is maintenance burden. I'm personally in favor of the idea of allowing arbitrary CSS editing inside a style class (with a one-way operation to convert the builder into a plain text input), but I… As mentioned this isn't the from a maintenance standpoint and why I prefer to create custom perspective themes. --- _[View the full topic](https://forum.inductiveautomation.com/t/changing-the-color-or-build-in-images-of-components/77479)._