Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When 'limits from PV' was used with a VImage (from PVA NTNDArray), the image axes would update to the size of the image whenever the PV sent a new value. But when the PV stayed constant and one would then perform operations that require a layout, like show/hide the toolbar, the image would be redrawn with the axes ranges from the model. The display would thus show the wrong axes until the PV sent another update.
Now the model axes are updated from the VImage, so the display sticks to the most recently received range from the VImage.
Similarly, when showing or hiding the toolbar, which changes the height of the image, the first update of the image would redraw in the old location on the screen.
Finally, the auto-scaling of the color bar failed when the value range was empty, for example all zeroes.