You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue1
In this case, img1 will be the active image. Then if I do img0.set_channel(20) and/or img0.set_polarization(Polarization.Q) without img0.make_active(), we will see indeed in the image list widget, the channel index and polarization string are updated. However, the rendered image is not. We need to do img0.make_active() first to re-render the raster image. I suggest in set_channel and set_polarization we internally make the target image as "active" before setting channel/polarization. In the scripting interface when there are multiple image loaded, it is non-trivial which one is currently "active" I suppose.
Issue2
In the above snippet, if I comment out time.sleep(5), even if we do img0.make_active() first before setting channel and polarization, we do not see img0 got re-rendered. I suspect this is an sync/async issue.
The text was updated successfully, but these errors were encountered:
I'm concerned that making an inactive image active as a side effect of changing the channel / polarization is unexpected behaviour, and I would rather not do it by default.
I wonder if there's a way to force re-rendering in the frontend without making the image active.
with the following snippet there are two image re-rendering issues
Issue1
In this case, img1 will be the active image. Then if I do img0.set_channel(20) and/or img0.set_polarization(Polarization.Q) without img0.make_active(), we will see indeed in the image list widget, the channel index and polarization string are updated. However, the rendered image is not. We need to do img0.make_active() first to re-render the raster image. I suggest in set_channel and set_polarization we internally make the target image as "active" before setting channel/polarization. In the scripting interface when there are multiple image loaded, it is non-trivial which one is currently "active" I suppose.
Issue2
In the above snippet, if I comment out time.sleep(5), even if we do img0.make_active() first before setting channel and polarization, we do not see img0 got re-rendered. I suspect this is an sync/async issue.
The text was updated successfully, but these errors were encountered: