Okay, this was not threading related at all. Here's my commit message that describes what was going on:
--
After calling JHVJP2View's setRegion() it is in general not guaranteed that
getRegion() will just return the newly set region. Instead, JHVJP2View will
return the last region for which all available data was downloaded. The zoom
scale info bar used this "old" information.
This fix adds a method getNewestRegion to JHVJP2View and makes ZoomController
use this new method.
NOTE: The special behavior of JHVJP2View's getRegion() seems to be needed
for JHV: Directly changing getRegion() to always return the newest region
resulted in very awkward JHV behavior.
Okay, this was not threading related at all. Here's my commit message that describes what was going on:
--
After calling JHVJP2View's setRegion() it is in general not guaranteed that
getRegion() will just return the newly set region. Instead, JHVJP2View will
return the last region for which all available data was downloaded. The zoom
scale info bar used this "old" information.
This fix adds a method getNewestRegion to JHVJP2View and makes ZoomController
use this new method.
NOTE: The special behavior of JHVJP2View's getRegion() seems to be needed
for JHV: Directly changing getRegion() to always return the newest region
resulted in very awkward JHV behavior.