avoid useless loadings of ImageServers#1957
avoid useless loadings of ImageServers#1957carlocastoldi wants to merge 1 commit intoqupath:mainfrom
Conversation
It always occured when closing the object classifier's window and when executing a CLI script
Based on qupath#1957 - attempts to fix more instances, and use `ImageData.close()`.
|
Thanks @carlocastoldi could you please review #1959 and see if it fixes the issue for you? I rarely use these tools & don't have a quick way to test them. I think the other PR handles more cases, and relying on If the other PR looks good to you, I'd merge it and close this one. |
|
Hi @petebankhead, thanks for taking the time to improve the proposed change. I expect the script to run through all images smoothly & fast. If run on IntelliJ, I also put a breakpoint to I think we can merge #1959 and close this! P.S. will QuPath 0.6 have point releases or has the development shifted to a pace that is more incremental? |
|
Thanks @carlocastoldi ! No plans for a v0.6.1 release at this time, hoping instead to make v0.7.0 much sooner. But this may change if there are enough bug fixes to justify a new release before v0.7.0 is ready. |
2 participants
QuPath 0.6.0 always loaded some
ImageServerjust to then close them right after.This occurred when closing the object classifier's window and when executing a CLI script.
Actually, I expect these precautionary
getServer()→close()to have slipped through in other parts. These two cases jumped to me because CLI scripting and object classifiers are tools that I regularly use.Related to #1489 and #1579