# Adding Power Chart's property sections to runtime from editor

**URL:** <https://forum.inductiveautomation.com/t/adding-power-charts-property-sections-to-runtime-from-editor/87721>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [March 21, 2024, 8:38pm UTC](https://forum.inductiveautomation.com/t/adding-power-charts-property-sections-to-runtime-from-editor/87721 "2024-03-21T20:38:56Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![furkan\_yuce](https://avatars.discourse-cdn.com/v4/letter/f/df788c/32.png) [@furkan\_yuce](https://forum.inductiveautomation.com/u/furkan_yuce)\
**Post date:** [March 21, 2024, 8:38pm UTC](https://forum.inductiveautomation.com/t/adding-power-charts-property-sections-to-runtime-from-editor/87721/1 "2024-03-21T20:38:56Z")

</div>

greetings friends,  
I'm very new for ignition. I just trying to find a way that how can I show the property editor's parts of powerchart to chart settings in perspective runtime?  
for instance : PROPS\>timeAxis\>tickCount\>tick\>label\>format--------\>directly Chart Settings

---

<div class="post-metadata">

**Author:** ![furkan\_yuce](https://avatars.discourse-cdn.com/v4/letter/f/df788c/32.png) [@furkan\_yuce](https://forum.inductiveautomation.com/u/furkan_yuce)\
**Post date:** [March 21, 2024, 8:45pm UTC](https://forum.inductiveautomation.com/t/adding-power-charts-property-sections-to-runtime-from-editor/87721/2 "2024-03-21T20:45:11Z")

</div>

![forTopic_1](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/a/da6db3f454cfe7fe4c3f4046d1ff42a99d4660e4.png)

---

<div class="post-metadata">

**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\
**Post date:** [March 21, 2024, 8:47pm UTC](https://forum.inductiveautomation.com/t/adding-power-charts-property-sections-to-runtime-from-editor/87721/3 "2024-03-21T20:47:08Z")

</div>

Perspective (capital 'P') doesn't have a runtime. It's not a compiled application.

You could create dropdowns, radio groups or checkboxes with the properties you want to set and use a Property Binding (bidirectional) to the chart properties to be controlled.

---

<div class="post-metadata">

**Author:** ![furkan\_yuce](https://avatars.discourse-cdn.com/v4/letter/f/df788c/32.png) [@furkan\_yuce](https://forum.inductiveautomation.com/u/furkan_yuce)\
**Post date:** [March 21, 2024, 8:52pm UTC](https://forum.inductiveautomation.com/t/adding-power-charts-property-sections-to-runtime-from-editor/87721/4 "2024-03-21T20:52:19Z")

</div>

Dear Transistor(capital 'T'),  
so I will bind a button with it I want to see. Is it only one way as I undersood?

---

<div class="post-metadata">

**Author:** ![Ryan\_Ahlstrom](https://avatars.discourse-cdn.com/v4/letter/r/ecb155/32.png) [@Ryan\_Ahlstrom](https://forum.inductiveautomation.com/u/Ryan_Ahlstrom)\
**Post date:** [March 21, 2024, 8:56pm UTC](https://forum.inductiveautomation.com/t/adding-power-charts-property-sections-to-runtime-from-editor/87721/5 "2024-03-21T20:56:05Z")

</div>

You can create bi-directional bindings.

---

<div class="post-metadata">

**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\
**Post date:** [March 21, 2024, 9:02pm UTC](https://forum.inductiveautomation.com/t/adding-power-charts-property-sections-to-runtime-from-editor/87721/6 "2024-03-21T21:02:20Z")

</div>

> [@furkan\_yuce](#):
>
> ... so I will bind a button with it ...

A button doesn't give you options. Dropdowns, radio groups and checkboxes do.  
The bidirectional binding means that the dropdown, etc., will update if the property is changed elsewhere - either in Designer or in the Power Chart settings editor.

---

<div class="post-metadata">

**Author:** ![furkan\_yuce](https://avatars.discourse-cdn.com/v4/letter/f/df788c/32.png) [@furkan\_yuce](https://forum.inductiveautomation.com/u/furkan_yuce)\
**Post date:** [March 21, 2024, 9:09pm UTC](https://forum.inductiveautomation.com/t/adding-power-charts-property-sections-to-runtime-from-editor/87721/7 "2024-03-21T21:09:04Z")

</div>

> [@Transistor](#):
>
> A button doesn't give you options. Dropdowns, radio groups and checkboxes do.  
> The bidirectional binding means that the dropdown, etc., will update if the property is changed elsewhere - either in Designer or in the Power Chart settings editor.

button was just an example for the components. a "time axis" could be a button for open a popup and it can fill inside with dropdowns,radio groups and so on.

---

<div class="post-metadata">

**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\
**Post date:** [March 21, 2024, 9:17pm UTC](https://forum.inductiveautomation.com/t/adding-power-charts-property-sections-to-runtime-from-editor/87721/8 "2024-03-21T21:17:41Z")

</div>

OK, but you wouldn't bind the button to the properties. The button would have an event.

Your problem with the popup is that you will now be trying to control properties of a component on another view.

1. You'll need to pass the current properties values into the popup as parameters so you can display the current values.
2. When a selection is changed you'll have to use a Message Handler to send the values back to the original view. This will take some study and time.

A better option might be to have an expanding flex container on the main view with the controls in that.

> **[Component Message Handlers | Ignition User Manual](https://docs.inductiveautomation.com/docs/8.1/ignition-modules/perspective/scripting-in-perspective/component-message-handlers)**
>
> In Perspective, Component Message Handlers are the preferred way to pass parameters between components or Views. Doing this involves the system.perspective.sendMessage function. There are typically two steps involved:
