Use either the Progress Changed() or Run Worker Completed() events to pass the info back to the UI.I have a JProgress Bar in a JDialog that is not being updated.If I'd just thought about it like a regular directive with two-way binding, it would have been clear (as you described here, and as is documented if I'd just stopped over-thinking it)!I'm only a couple weeks into angular, still tripping myself up on what's "magic" and what's "plain old code".And tips or examples of this working in a dynamic fashion?So for some reason, ng-value alone appears to not update the binding inside the "progressbar" directive scope when it recalculates the value attribute. This doesn't seem like the right fix, but I don't want to go too far down this rabbit hole without an extra set of eyes on it.At first I see a blank dialog (first image) then nothing till the end (2nd image).I am using a thread to update, but still isn't happening.
in the demo: Monitor Demo Project/src/components/Progress Monitor there is no progress bar component in the layout, yet there it is.Isn't the idea that the width of the meter should track the current value on the progressbar?If I set a static value on the progress bar, the width is set, but it never changes in response to dynamic progress updating via ng-value.I didn't realize that the binding in the directive would cause the value attribute to be $parsed, so assumed I had to use ng-value to do that lifting. value="" is a special attribute already, hence the existence of ng-value="".I was allowing ng-value to update the value attribute, but the directive had already bound to a non-existent attr upon initialization, so never got the value, even though ng-value was updating it on the parent. In retrospect, I ascribed too much magic to ng-value.I didn't realize that the binding in the directive would cause the value attribute to be $parsed, so assumed I had to use ng-value to do that lifting. I think adding to my confusion was that I was assuming that this behavior was decorating the standard HTML5 "progress" element, so I'd wrongly convinced myself that there was magic I needed. Adding to the confusion, however, was that ng-value DOES in fact update the value attribute on the progress element. If ng-value had just ignored it for a non-input element, I would quickly have realized.But I was bewildered about why "value" was getting updated, but not properly bound into the directive.I have it display, but it's just blank and does not update. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. I'm calling a dll to ssh to a linux server, run some commands, and redirect the output to the user on a listview and label.Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S. I'm not sure how to run the other items in the background and then display them on my main form.(The thingy at the left edge of the first image is a bit of a component that is 'underneath' the dialog box, ie the interior of the dialog seems to be transparent at that point) "The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years.I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing.