UIService.showUI() shows multiple instances of the same UI #460
Assignees
Labels
Comments
ctrueden
added a commit
to imagej/pyimagej
that referenced
this issue
May 5, 2023
It takes care to show the UI on the AWT event dispatch thread. If the UI is already visible, it raises the application frame instead of calling ij.ui().showUI() again, since SciJava Common currently has a bug when doing that where it hoses the UI (see scijava/scijava-common#460).
ctrueden
added a commit
to imagej/pyimagej
that referenced
this issue
May 5, 2023
It takes care to show the UI on the AWT event dispatch thread. If the UI is already visible, it raises the application frame instead of calling ij.ui().showUI() again, since SciJava Common currently has a bug when doing that where it hoses the UI (see scijava/scijava-common#460).
ctrueden
added a commit
to imagej/pyimagej
that referenced
this issue
May 5, 2023
It takes care to show the UI on the AWT event dispatch thread. If the UI is already visible, it raises the application frame instead of calling ij.ui().showUI() again, since SciJava Common currently has a bug when doing that where it hoses the UI (see scijava/scijava-common#460).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I found this with the ImageJ2 UI in napari-imagej:
Ideally,
UIService.show()would check if there is already a UI visible, and then, if it is, ensure that the application frame is also visible. This is what I was doing in napari-imagej, however it is a little hacky (why would the ImageJ2 UI be visible and the application frame not be?)Note that in napari-imagej, I also kill all
WindowListeners, and add my own that hides the window when the user presses the close button, instead of actually closing the window.The text was updated successfully, but these errors were encountered: