# Help and Advice **URL:** \ **Category:** Maker\ **Tags:** perspective, vision\ **Created:** [July 1, 2025, 12:37pm UTC](https://forum.inductiveautomation.com/t/help-and-advice/107981 "2025-07-01T12:37:05Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![dcamp1](https://avatars.discourse-cdn.com/v4/letter/d/dc4da7/32.png) [@dcamp1](https://forum.inductiveautomation.com/u/dcamp1)\ **Post date:** [July 1, 2025, 12:37pm UTC](https://forum.inductiveautomation.com/t/help-and-advice/107981/1 "2025-07-01T12:37:06Z")
Hello, I use Ignition "Vision" and have for years. I have all kinds of windows that monitor/control various equipment across our "Cellular Private Network". I'm trying to learn "Perspective" but, I'm finding it somewhat different in a lot of things, and I can't seem to find the answers by reading the manual and watching the tutorials in Ignitions web site. I'm hoping someone can suggest "maybe a better way" than just trying different things and see if they work. I'm open to anythings. Here's and example: I have 2 buttons that turn a motor on/off ( and that's because I could not figure out which component to use for a toggle operation. The toggle switch in the perspective component is not a good choice) What I would like to see is when the "START" button is pressed a "Label" would say "Running" an when the "STOP" button is pressed the "Label" would now say "Idle"! Where can I go to learn all about the different "Properties" each component has and how to work with them? Thanks for any advice/suggestions. I'm just trying to get my head around the different programming technique. ---
**Author:** ![bkarabinchak.psi](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bkarabinchak.psi/32/83567_2.png) [@bkarabinchak.psi](https://forum.inductiveautomation.com/u/bkarabinchak.psi)\ **Post date:** [July 1, 2025, 12:43pm UTC](https://forum.inductiveautomation.com/t/help-and-advice/107981/2 "2025-07-01T12:43:13Z")
Helpful primer if you haven't read yet > **[Perspective Component Properties | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.1/ignition-modules/perspective/working-with-perspective-components/perspective-component-properties)** > > Each Perspective component has a unique set of properties that can be set and modified within the Perspective Property Editor. A component property is simply a named variable with a distinct type that affects something about the component's behavior... Then you can come here and look up any given component's list of properties and meanings > **[Perspective Components | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.1/appendix/components/perspective-components)** > > This section covers all the built-in Perspective components. While a component is selected, you can use the Property Editor to alter the component's properties, which changes the component's appearance and behavior. Components are the building blocks... For your toggle component, on the second link I clicked input pallette (since its a thing that a user can click/adjust) > **[Perspective - Toggle Switch | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.1/appendix/components/perspective-components/perspective-input-palette/perspective-toggle-switch)** > > The Toggle Switch represents a bit: on (selected) or off (not selected). ---
**Author:** ![dcamp1](https://avatars.discourse-cdn.com/v4/letter/d/dc4da7/32.png) [@dcamp1](https://forum.inductiveautomation.com/u/dcamp1)\ **Post date:** [July 1, 2025, 4:46pm UTC](https://forum.inductiveautomation.com/t/help-and-advice/107981/3 "2025-07-01T16:46:37Z")
Thanks so much, I will read all of them. ---
**Author:** ![dcamp1](https://avatars.discourse-cdn.com/v4/letter/d/dc4da7/32.png) [@dcamp1](https://forum.inductiveautomation.com/u/dcamp1)\ **Post date:** [July 2, 2025, 4:57pm UTC](https://forum.inductiveautomation.com/t/help-and-advice/107981/4 "2025-07-02T16:57:26Z")
Ok, with all the help from this forum I'm finally making headway. Using the Makers Edition trying to learn perspective. I have an Opc-Ua server setup that is communicating with my Micro820 plc. I have a View with just a couple of buttons "Start" and "Stop" all they do is turn a "Bit" on and off in my plc. Now I have a "Run" bit in my plc setup as my motor so as an example when the start button is pressed the run bit turns on and when the stop button is pressed it will turn the run bit back off. I want to show the status of the "RUN BIT" on equal "Running" off equal "IDLE". So I need some type of a "Label" component that I can change text to read like this. 1 or true = Running 0 or false - Idle Now I would also like the background to change from "Green" when running to "Red" when Idle. Need some pointers I can't figure out what to use, I have been looking at the Label component but don't know how to make that work like I need. Thanks ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [July 2, 2025, 5:03pm UTC](https://forum.inductiveautomation.com/t/help-and-advice/107981/5 "2025-07-02T17:03:29Z")
**Expression** binding on the Label's `props.text`: ```python if({[default]path/to/Run}, "Running", "Idle") ``` Tweak if your tag provider is not called `default`. ---
**Author:** ![dcamp1](https://avatars.discourse-cdn.com/v4/letter/d/dc4da7/32.png) [@dcamp1](https://forum.inductiveautomation.com/u/dcamp1)\ **Post date:** [July 2, 2025, 5:31pm UTC](https://forum.inductiveautomation.com/t/help-and-advice/107981/6 "2025-07-02T17:31:32Z")
Thanks, I was able to get my Color correct also with binding. I'm beginning to understand how this all works. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [July 2, 2025, 5:34pm UTC](https://forum.inductiveautomation.com/t/help-and-advice/107981/7 "2025-07-02T17:34:44Z")
Note that my solution is not the **only** way to do this. Just the simplest for this case, IMNSHO. If you have more than two cases, you should consider the `case()` expression function, or perhaps a Mapping **transform**. (Some ways to solve problems are valid, but are foot-gun setups. Avoid the `tag()` expression function like the plague.) ---
**Author:** ![dcamp1](https://avatars.discourse-cdn.com/v4/letter/d/dc4da7/32.png) [@dcamp1](https://forum.inductiveautomation.com/u/dcamp1)\ **Post date:** [July 3, 2025, 1:00am UTC](https://forum.inductiveautomation.com/t/help-and-advice/107981/8 "2025-07-03T01:00:24Z")
Thanks for the advice, I will make note of it.