Ticket #1194 (closed defect: fixed)
Opened 2012-05-22T09:58:23-05:00
Last modified 2012-10-10T14:57:19-05:00
QuitProgram has annoying issue
| Reported by: | bdezonia | Owned by: | curtis |
|---|---|---|---|
| Priority: | major | Milestone: |
|
| Component: | Display API | Version: | |
| Severity: | serious | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | #1510 |
Description
The quit program sequence can be annoying. If you start IJ2, open a sample image, then close the image, and then close IJ2 it asks you whether you really want to quit as if an image is open.
Debugging shows that the WindowMenuService has more than one window assigned when a sample image is open. One, such as "boats.gif", maps to the dataset created when the legacy plugin creates the image. The other, called "outputs", matches the List<ImageDisplay> that LegacyPlugin returns as an output (which contains "boats.gif"). Closing the window removes one entry but not both.
There is some logic mismatch between DisplayPostProcessor::handleOutput() and the result of the display.canDisplay("outputs") test in DefaultDisplayService::createDisplay(). Somehow we should only record the one display.
Alternatively WindowMenuService might need to get better at seeing that outputs refers to boats.gif and since that is all it is outputs should be removed as well. This seems less clean.
Change History
comment:1 Changed 2012-07-12T17:01:14-05:00 by curtis
- Milestone changed from imagej-2.0.0-beta3 to imagej-2.0.0-beta4
comment:3 Changed 2012-09-07T11:00:46-05:00 by bdezonia
- Blocking 1457 added; 1345 removed
- Milestone changed from imagej-2.0.0-beta4 to imagej-2.0.0-beta5
comment:4 Changed 2012-10-03T13:00:31-05:00 by bdezonia
- Status changed from new to closed
- Resolution set to fixed
The above specified quit sequence now works without issue. Not sure who fixed it when but closing this ticket.
comment:5 Changed 2012-10-10T13:27:46-05:00 by curtis
- Milestone changed from imagej-2.0.0-beta6 to imagej-2.0.0-beta5-new