# Figma SVGs and Property Editor

**URL:** <https://forum.inductiveautomation.com/t/figma-svgs-and-property-editor/91945>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [June 17, 2024, 12:44pm UTC](https://forum.inductiveautomation.com/t/figma-svgs-and-property-editor/91945 "2024-06-17T12:44:52Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![Zachary](https://avatars.discourse-cdn.com/v4/letter/z/90db22/32.png) [@Zachary](https://forum.inductiveautomation.com/u/Zachary)\
**Post date:** [June 17, 2024, 12:44pm UTC](https://forum.inductiveautomation.com/t/figma-svgs-and-property-editor/91945/1 "2024-06-17T12:44:52Z")

</div>

Hi everyone, I've spent some time in the past few days lurking in these forms and reading up on implementing SVGs in Ignition Perspective. I am very new to all of this, so I apologize in advance if there are things I do not understand or do not know.

I've been trying to implement some custom SVGs I made in Figma and make it so that I can animate them according to information they take in.

Here is an example of one of my SVGs. A simple gauge.

![OEE](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/f/1f72f30b8f7154efa142301915c86a42ae830b5f.svg)

When I embed this in Perspective I get the following.

![Screenshot 2024-06-17 083725](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/b/6bf04613040aba0faea9dc24810106b3c2a1f613.png)

I want to be able to change the fill of this gauge. But it's not very clear to me how I would go about doing that. All I get is the D path and trying to edit that in the property editor has not been very giving.

Thank you in advance to anyone who can help me with this!

---

<div class="post-metadata">

**Author:** ![djs](https://avatars.discourse-cdn.com/v4/letter/d/e47774/32.png) [@djs](https://forum.inductiveautomation.com/u/djs)\
**Post date:** [June 17, 2024, 1:23pm UTC](https://forum.inductiveautomation.com/t/figma-svgs-and-property-editor/91945/2 "2024-06-17T13:23:15Z")

</div>

You have 2 svg elements, both of which are paths. The `d` property is the one containing the path "commands", and is the property you want to change in this case.

Learn a bit about how they work: [Paths - SVG: Scalable Vector Graphics | MDN](https://developer.mozilla.org/en-US/docs/Web/SVG/Tutorial/Paths). More specifically, look at either Bezier Curves or Arcs (since this svg is probably using one of the two.)

Once you understand the math and which numbers have to change, bind to the `d` property with an expression. Do whatever calculations you need in the expression and return a string with all the path commands.

---

<div class="post-metadata">

**Author:** ![Zachary](https://avatars.discourse-cdn.com/v4/letter/z/90db22/32.png) [@Zachary](https://forum.inductiveautomation.com/u/Zachary)\
**Post date:** [June 17, 2024, 1:35pm UTC](https://forum.inductiveautomation.com/t/figma-svgs-and-property-editor/91945/3 "2024-06-17T13:35:46Z")

</div>

Thank you!

This was one of the options I'm thinking of taking. As it seems I might not have any other way of going about changing the path dynamically. I appreciate the reply and help 👍

---

<div class="post-metadata">

**Author:** ![djs](https://avatars.discourse-cdn.com/v4/letter/d/e47774/32.png) [@djs](https://forum.inductiveautomation.com/u/djs)\
**Post date:** [June 17, 2024, 2:07pm UTC](https://forum.inductiveautomation.com/t/figma-svgs-and-property-editor/91945/4 "2024-06-17T14:07:48Z")

</div>

Because svgs from editors like figma or inkscape usually come with _funky_ numbers, I usually just create the path from scratch with round numbers that are easier to work with.

---

<div class="post-metadata">

**Author:** ![Zachary](https://avatars.discourse-cdn.com/v4/letter/z/90db22/32.png) [@Zachary](https://forum.inductiveautomation.com/u/Zachary)\
**Post date:** [June 17, 2024, 2:10pm UTC](https://forum.inductiveautomation.com/t/figma-svgs-and-property-editor/91945/5 "2024-06-17T14:10:10Z")

</div>

That is a great idea! I feel like I'm reading binary by looking at these paths 😅

---

<div class="post-metadata">

**Author:** ![lrose](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lrose/32/62724_2.png) [@lrose](https://forum.inductiveautomation.com/u/lrose)\
**Post date:** [June 17, 2024, 2:19pm UTC](https://forum.inductiveautomation.com/t/figma-svgs-and-property-editor/91945/6 "2024-06-17T14:19:20Z")

</div>

There is actually a full explanation about how to do this (completely within Ignition no third party software needed) here:

> [@Perspective, faster page](https://forum.inductiveautomation.com/t/perspective-faster-page/69885/35):
>
> Okay, I had a bit of free time today, so here is a complete SVG solution. You could do the Label as SVG text as well, or a gauge needle if you wanted, I haven't gone that far. Just a little example of the power of using the Ignition Designer to add SVG elements. I didn't include the label for the example. Note: All of this (outside of the calculations needed to find the points for the shape) was done inside of the designer (yes I can be somewhat of a masochist at times. rofl). First a s…

However, for the TL:DR (not really much of one really) 🤣

In that post, I use a script transform, which works well, but the same can be done with an expression (all be it a little ugly). The advantage is, an expression will be more performant.

(I don't have you're full path, so this is the path from my previous post)

```python
if({this.custom.value} = 100,
    //True Return default if value = 100
    "M0.7963 165.436 A150 150 0 1 1 299.2037 165.436 A10 10 0 1 1 " +
    "279.2567 164.4069 A130 130 0 1 0 20.7433 164.4039 A10 10 0 1 1 " +
    "0.7963 165.436",
    //False Return check if value = 0
    if( {this.custom.value} = 0,
        //True Return default if value = 0
        "M0.7963 165.436 A10 10 0 1 1 20.7433 164.4039 A10 10 0 1 1 0.7963 165.436",
        //False Return use calculated outside and inside stops
        toStr( 150 - 150 * cos(toRadians((200 * {this.custom.value} / 100) - 15))) + " " +
        toStr( 150 - 150 * sin(toRadians((200 * {this.custom.value} / 100) - 15))) + " A10 10 0 1 1 " +
        toStr( 150 - 130 * cos(toRadians((200 * {this.custom.value} / 100) - 15))) + " " +
        toStr( 150 - 130 * sin(toRadians((200 * {this.custom.value} / 100) - 15))) + " A130 130 0 " +
        if ( {this.custom.value} >= 95, "1 0 ", "0 0") +
        "20.7433 164.4039 A10 10 0 1 1 0.7963 165.436"
        )
    )

```

Honestly, that can be cleaned up significantly if you move the calculations out to properties of their own. For instance:

posRadians: `toRadians((200 * {this.custom.value} / 100 ) - 15)`  
outsideStopX: `150 - 150 * cos({this.custom.posRadians})`  
outsideStopY: `150 - 150 * sin({this.custom.posRadians})`  
insideStopX: `150 - 130 * cos({this.custom.posRadians})`  
insideStopY: `150 - 130 * sin({this.custom.posRadians})`

Then the main expression looks like:

```python
if({this.custom.value} = 100,
    //True Return default if value = 100
    "M0.7963 165.436 A150 150 0 1 1 299.2037 165.436 A10 10 0 1 1 " +
    "279.2567 164.4069 A130 130 0 1 0 20.7433 164.4039 A10 10 0 1 1 " +
    "0.7963 165.436",
    //False Return check if value = 0
    if( {this.custom.value} = 0,
        //True Return default if value = 0
        "M0.7963 165.436 A10 10 0 1 1 20.7433 164.4039 A10 10 0 1 1 0.7963 165.436",
        //False Return use calculated outside and inside stops
        toStr({this.custom.outsideStopX}) + " " +
        toStr({this.custom.outsideStopY}) + " A10 10 0 1 1 " +
        toStr({this.custom.insideStopX}) + " " +
        toStr({this.custom.insideStopY}) + " A130 130 0 " +
        if ( {this.custom.value} >= 95, "1 0 ", "0 0") +
        "20.7433 164.4039 A10 10 0 1 1 0.7963 165.436"
        )
    )

```

Note that you need to determine which direction to "close" the final arc dependent upon the value. In my case the break over threshold was 95% yours may be different.

---

<div class="post-metadata">

**Author:** ![Zachary](https://avatars.discourse-cdn.com/v4/letter/z/90db22/32.png) [@Zachary](https://forum.inductiveautomation.com/u/Zachary)\
**Post date:** [June 17, 2024, 2:40pm UTC](https://forum.inductiveautomation.com/t/figma-svgs-and-property-editor/91945/7 "2024-06-17T14:40:25Z")

</div>

Thank you! I read your previous statement. I think I'm starting to understand all of it 😅

I'm beginning to realize the extent of the work involved in animating SVGs like this in Perspective. It's certainly no small task. Especially thinking with the fact that I want to create much more complicated designs and SVGs

Again, thank you for your time!

---

<div class="post-metadata">

**Author:** ![lrose](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lrose/32/62724_2.png) [@lrose](https://forum.inductiveautomation.com/u/lrose)\
**Post date:** [June 17, 2024, 2:48pm UTC](https://forum.inductiveautomation.com/t/figma-svgs-and-property-editor/91945/8 "2024-06-17T14:48:35Z")

</div>

> [@Zachary](#):
>
> Thank you! I read your previous statement. I think I'm starting to understand all of it

The SVG syntax is among some of the most cryptic there is (it's nearly as bad as regex). I happen to do well with it because I have a back ground in G-code for CNC Machines. Anyway, it isn't linked in the other post, but I use the [Pocket Guide to Writing SVG](https://svgpocketguide.com/) as a primary resource. It's very well done.

> [@Zachary](#):
>
> Especially thinking with the fact that I want to create much more complicated designs and SVGs

Often when the SVG's get more complex then using groups and applying transforms to the entire group can make things significantly easier.

This is another example that is a bit more complex but the animation is actually not that complicated.

> [@How to add animation by HTML/CSS scripts in Perspective?](https://forum.inductiveautomation.com/t/how-to-add-animation-by-html-css-scripts-in-perspective/75523/14):
>
> Okay, so it took me longer than I wanted (my laptop died), but I finally did get around to completing this, and I have to say I'm pretty pleased with the result. This was a fun exercise and I learned something good along the way. I will give you a disclaimer though, other than a rough idea of what an Azimuth Propeller is, I don't know much else. So for instance, I have no idea what the yellow triangle is supposed to indicate and so I didn't add it. I made some assumptions on how I think the re…

---

<div class="post-metadata">

**Author:** ![Zachary](https://avatars.discourse-cdn.com/v4/letter/z/90db22/32.png) [@Zachary](https://forum.inductiveautomation.com/u/Zachary)\
**Post date:** [June 17, 2024, 3:09pm UTC](https://forum.inductiveautomation.com/t/figma-svgs-and-property-editor/91945/9 "2024-06-17T15:09:48Z")

</div>

Thank you!

I had a question about about the animation that you linked to. This might be a really silly question, and probably show my inexperience with all of this, but for that JSON file. Do you create that file in the Property Editor of your container?

---

<div class="post-metadata">

**Author:** ![lrose](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lrose/32/62724_2.png) [@lrose](https://forum.inductiveautomation.com/u/lrose)\
**Post date:** [June 17, 2024, 3:14pm UTC](https://forum.inductiveautomation.com/t/figma-svgs-and-property-editor/91945/10 "2024-06-17T15:14:47Z")

</div>

Not a silly question at all.

> [@Zachary](#):
>
> Do you create that file in the Property Editor of your container?

That is the JSON you get when you "Shift + Right Click" on the view and select Copy JSON.

To use it:

1. Create a Temp View to hold the JSON
2. Copy the JSON from the post.
3. "Shift + Right Click on the temp view in the Project Browser
4. Select Paste JSON

---

<div class="post-metadata">

**Author:** ![Steve\_Laubach](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/steve_laubach/32/60900_2.png) [@Steve\_Laubach](https://forum.inductiveautomation.com/u/Steve_Laubach)\
**Post date:** [June 17, 2024, 4:07pm UTC](https://forum.inductiveautomation.com/t/figma-svgs-and-property-editor/91945/11 "2024-06-17T16:07:55Z")

</div>

I found a pretty nice SVG gauge on Ignition Exchange. You can find it here:

> **[Ignition Exchange](https://inductiveautomation.com/exchange/2451/overview)**
>
> Discover, share, and download community made Ignition resources in collaboration with your organization or the Ignition community.

It's easy to re-apply it as it is built. It's pretty tricky to customize it to add dynamic capability. I modified a version of it to use styles to animate the alarm condition flashing because I prefer to handle that part in CSS rather than an expression binding off a timer.

Anyway, I think Ashwin M did a great job on this gauge and thought it might be useful to you.

---

<div class="post-metadata">

**Author:** ![msteele](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/msteele/32/77889_2.png) [@msteele](https://forum.inductiveautomation.com/u/msteele)\
**Post date:** [June 17, 2024, 4:49pm UTC](https://forum.inductiveautomation.com/t/figma-svgs-and-property-editor/91945/12 "2024-06-17T16:49:53Z")

</div>

Regarding Figma SVG export to Perspective SVG embed... any strategies to flatten the element structure? Figma will turn any group, component (embedded view equivalent), auto layout (flex container equivalent), etc into its own nested object, which can make it difficult to find specific elements in the SVG structure if you want to bind them. Yes, you can do bindings for particular items within the JSONified embedded SVG structure in Perspective properties.

I'm curious how things will change in 8.3. We've heard of an integrated drawing tool, but I'm even more curious if there's a chance to have something like embedded views but natively SVG. Imagine assembling SVGs rather than just views with embeds, flex repeaters, or a SVG canvas component like view canvas. Dreamy.

---

<div class="post-metadata">

**Author:** ![lrose](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lrose/32/62724_2.png) [@lrose](https://forum.inductiveautomation.com/u/lrose)\
**Post date:** [June 17, 2024, 4:54pm UTC](https://forum.inductiveautomation.com/t/figma-svgs-and-property-editor/91945/13 "2024-06-17T16:54:36Z")

</div>

> [@Steve\_Laubach](#):
>
> I prefer to handle that part in CSS rather than an expression binding off a timer

Definitely the way to go. And if you need it to be dynamic, you can use bindings to modify the styling as well. The last example I posted uses a CSS transform to rotate.

---

<div class="post-metadata">

**Author:** ![Steve\_Laubach](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/steve_laubach/32/60900_2.png) [@Steve\_Laubach](https://forum.inductiveautomation.com/u/Steve_Laubach)\
**Post date:** [June 17, 2024, 5:15pm UTC](https://forum.inductiveautomation.com/t/figma-svgs-and-property-editor/91945/14 "2024-06-17T17:15:43Z")

</div>

If you want to make this Exchange resource go from CSS styles instead of a blink animation, here you go.

I used these styles in advanced style sheet

```python
.psc-stroke-gray
{
	stroke: #CCCCCC
}

.psc-stroke-blink-red
{
	animation: blinkStrokeRed 1.3s linear infinite;
}

@keyframes blinkStrokeRed{
	0%, 50%{
		stroke: #FF0000
	}
	50%, 100%{
		stroke: #CCCCCC
	}
}

.psc-opacity-off
{
	opacity: 0
}

.psc-opacity-blink
{
	animation: blinkOpacity 1.3s linear infinite;
}

@keyframes blinkOpacity{
	0%, 50%{
		opacity: 1
	}
	50%, 100%{
		opacity: 0
	}
}

```

Then you just add the "classes" property in the right style locations to add the 2 blinking things. Also you want to unbinds the bindings to the blinker property and remove the blinker property to get away from the gateway scoped timer expression. Here's screenshots:

 ![Blink or invisible animation](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/4/34449b6d747ef17598da8e1d1c8de334816a10a8.png)  
 ![Circle Blink Animation](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/a/2a2443432cf99c3cc629cc0132b152ce9ab3e052.png)

I don't have time at the moment to help anyone troubleshoot this but this is probably enough to go on.

---

<div class="post-metadata">

**Author:** ![Zachary](https://avatars.discourse-cdn.com/v4/letter/z/90db22/32.png) [@Zachary](https://forum.inductiveautomation.com/u/Zachary)\
**Post date:** [June 17, 2024, 5:20pm UTC](https://forum.inductiveautomation.com/t/figma-svgs-and-property-editor/91945/15 "2024-06-17T17:20:20Z")

</div>

This is awesome, thank you!

---

<div class="post-metadata">

**Author:** ![Zachary](https://avatars.discourse-cdn.com/v4/letter/z/90db22/32.png) [@Zachary](https://forum.inductiveautomation.com/u/Zachary)\
**Post date:** [June 17, 2024, 6:54pm UTC](https://forum.inductiveautomation.com/t/figma-svgs-and-property-editor/91945/16 "2024-06-17T18:54:50Z")

</div>

I would love to have an extension of Perspective with Figma! I just cant imagine the work that would need to be involved to do something like that.

But to be able to easily design in Figma and then have it easily plug into Ignition would be awesome.