dicompyler icon indicating copy to clipboard operation
dicompyler copied to clipboard

Make "Loading Patient Data..." dialog non-modal

Open GoogleCodeExporter opened this issue 10 years ago • 3 comments

What steps will reproduce the problem?
1. Load a large DICOM RT image set
2. "Loading Patient Data..." appears with a progress bar
3. It is system-modal and cannot be minimized or cancelled so stays in front of 
all windows.

What is the expected output? What do you see instead?
The dialog should be non-modal or even app-modal. Ideally it should have a 
Minimize button or if possible even a Cancel button to cancel loading an 
excessively large image set

What version of the product are you using? On what operating system?
0.4a3, Windows 7 64bit Enterprise

Please provide any additional information below.
This is a usability issue

Original issue reported on code.google.com by [email protected] on 15 Dec 2011 at 5:53

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

GoogleCodeExporter avatar Jun 10 '15 15:06 GoogleCodeExporter

Thanks for submitting this problem report.

The dialog should be app-modal but for some reason it is not. This occurs on 
all platforms. Another option that I have toyed around with is placing the 
progress bar within the status bar. This can potentially solve the issue as 
well.

Regarding the cancel button, some thought needs to be put into it, as 
processing the data needs to be stopped by the main thread. Additionally, other 
plugins use the same progress dialog and would also need to be updated.

Original comment by bastula on 23 Dec 2011 at 3:06

  • Changed state: Accepted

GoogleCodeExporter avatar Jun 10 '15 15:06 GoogleCodeExporter

The status bar will definitely be an improvement.

I tried to open some DICOM RT files (from Pinnacle3) that basically got stuck 
in the loading phase and I had to use Task Manager to kill dicompyler. 

Original comment by [email protected] on 23 Dec 2011 at 7:05

GoogleCodeExporter avatar Jun 10 '15 15:06 GoogleCodeExporter

Regarding dicompyler getting stuck - it probably had an exception that occurred 
with DVH calculation - see this thread on the dicompyler discussion group: 
http://groups.google.com/group/dicompyler/browse_thread/thread/f2059acbbb8ef2c3

I have written an exception handler that will catch the error and allow users 
to submit a report. This will be part of the next version.

Original comment by bastula on 23 Dec 2011 at 8:53

GoogleCodeExporter avatar Jun 10 '15 15:06 GoogleCodeExporter