# Progress Bar Issue

**URL:** <https://forum.inductiveautomation.com/t/progress-bar-issue/2080>\
**Category:** Ignition\
**Created:** [July 26, 2010, 4:48pm UTC](https://forum.inductiveautomation.com/t/progress-bar-issue/2080 "2010-07-26T16:48:21Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kyle\_Chase](https://avatars.discourse-cdn.com/v4/letter/k/9de0a6/32.png) [@Kyle\_Chase](https://forum.inductiveautomation.com/u/Kyle_Chase)\
**Post date:** [July 26, 2010, 4:48pm UTC](https://forum.inductiveautomation.com/t/progress-bar-issue/2080/1 "2010-07-26T16:48:21Z")

</div>

I have a progress bax with the min/max/value properties bound.

Max is bound to PID/{1}/Max  
Min is bound to PID/{1}/Min  
Value is bound to PID/{1}/PV

When I open the screen sometimes, the progress bar does not follow the actual value. After some time, it eventually changes.  
 ![](https://us1.discourse-cdn.com/inductiveautomation/original/1X/452c6ac3c15c172bacab6ccc2945898c998951fb.png)

---

<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:47pm UTC](https://forum.inductiveautomation.com/t/progress-bar-issue/2080/2 "2010-08-05T17:47:58Z")

</div>

This is a tricky one. Those 3 bindings are running when the window opens up in an arbitrary order. So, if the value binding goes first, but the value is out of bounds compared to the serialized values of min/max (the current min/max bindings haven’t run yet), it will be lost. It will only come back it later if the value tag changes.

We either need to

1. have bindings know about some sort of dependency order - or-
2. alter the progress bar and similar components to work in a “lenient” mode where the out-of-bounds value is “remembered” and can be used after the min/max come in.

---

<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 18, 2010, 8:33pm UTC](https://forum.inductiveautomation.com/t/progress-bar-issue/2080/3 "2010-08-18T20:33:35Z")

</div>

Ok, for 7.1.6 all “bounded-range” components that exhibited this problem (Cylindrical Tank, Fill Level Indicator, Progress Bar, and Slider) all work in the following way:

The value property can now exceed the min and max values. When this is the case, the component will display an “out-of-bounds” quality overlay. This free-floating value will solve the race condition by allowing the value to become out of range temporarily before the min/max bindings kick in.