# Progress Bar Problems

**URL:** <https://forum.inductiveautomation.com/t/progress-bar-problems/2077>\
**Category:** Ignition\
**Created:** [July 25, 2010, 11:48pm UTC](https://forum.inductiveautomation.com/t/progress-bar-problems/2077 "2010-07-25T23:48:19Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![RRNut](https://avatars.discourse-cdn.com/v4/letter/r/8e7dd6/32.png) [@RRNut](https://forum.inductiveautomation.com/u/RRNut)\
**Post date:** [July 25, 2010, 11:48pm UTC](https://forum.inductiveautomation.com/t/progress-bar-problems/2077/1 "2010-07-25T23:48:19Z")

</div>

I’ve noticed two problems with the progress bar:

1. If you copy a progress bar that has already been assigned to a tag, the copied version keeps the referance to the min max values of the original version. You can change the copied version and then once you save/commit the window then reopen window, the min max values match the go back to origal version.

2. The progress bar does not work with values less than 1. For example, say you need to display a decimal value that ranges between 0 to 1. The progress bar either displays 0 or 1 and nothing inbetween.

---

<div class="post-metadata">

**Author:** ![Travis.Cox](https://avatars.discourse-cdn.com/v4/letter/t/b9bd4f/32.png) [@Travis.Cox](https://forum.inductiveautomation.com/u/Travis.Cox)\
**Post date:** [July 26, 2010, 5:33pm UTC](https://forum.inductiveautomation.com/t/progress-bar-problems/2077/2 "2010-07-26T17:33:54Z")

</div>

1. When you tag onto a component more than one binding occurs. The progress bar’s value, min, max and tooltip get bound to the tag. All of the bold properties are bound. When you copy and paste the component you must change all bindings in order to point to the correct tag.

If you change a property value that is bound to something, then re-opening the window will revert the value back. Look for whether or not the property is bold or bound.

1. The progress bar’s value is an integer, so you cannot use a floating point value. However, you can bind the value to an expression converting the floating point value to an integer. You can scale it up.

---

<div class="post-metadata">

**Author:** ![RRNut](https://avatars.discourse-cdn.com/v4/letter/r/8e7dd6/32.png) [@RRNut](https://forum.inductiveautomation.com/u/RRNut)\
**Post date:** [July 27, 2010, 1:08pm UTC](https://forum.inductiveautomation.com/t/progress-bar-problems/2077/3 "2010-07-27T13:08:22Z")

</div>

Thanks for clearing that up. I now understand…

---

<div class="post-metadata">

**Author:** ![Carl.Gould](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carl.gould/32/7262_2.png) [@Carl.Gould](https://forum.inductiveautomation.com/u/Carl.Gould)\
**Post date:** [August 5, 2010, 5:50pm UTC](https://forum.inductiveautomation.com/t/progress-bar-problems/2077/4 "2010-08-05T17:50:29Z")

</div>

With regards to #2: You can “roll-your-own” floating point progress bar with a combination of the level indicator component + linear scale component.