Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Critical
-
Resolution: Done
-
Affects Version/s: 5.0.0.M3
-
Fix Version/s: 5.0.0.M3
-
Labels:None
Description
Request to let usage reporting modal dialog is opened first and then it is covered by bigger Runtime Detection Dilaog. Usage dialog is modal and nothing can be pressed and changed in Runtime Detection dialog. Sometimes I even didn't notice usage dialog and it was confusing because runtime detection dialog just didn't respond to mouse events.
There should be a way to show such dialogs one by one and not all at once blocking each other.
Gliffy Diagrams
Issue Links
- blocks
-
JBIDE-9710
new respin of M3
-
- Closed
-
- cloned to
-
JBIDE-9712
Runtime Detection Dialog during first start gets over modal dialog with request to let usage reporting.
-
- Closed
-
- is related to
-
JBDS-1673
Installer should align with runtime detection
-
- Closed
-
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
Issue is still present on MacOsX 10.6 with jbdevstudio-product-eap-macosx-cocoa-5.0.0.v201109152227R-H32-M3.jar. Reopening.
Jaroslav Jankovič
added a comment - Issue is still present on MacOsX 10.6 with jbdevstudio-product-eap-macosx-cocoa-5.0.0.v201109152227R-H32-M3.jar. Reopening. Moving to M4 since M3 is out now.
the patch was the best I could do for m3. it was only fixing stuff for windows. we need a better solution and I therefore cloned it to JBIDE-9712 and will try to find a proper solution in that issue.
Closing this issue again.
Andre Dietisheim
added a comment - the patch was the best I could do for m3. it was only fixing stuff for windows. we need a better solution and I therefore cloned it to JBIDE-9712 and will try to find a proper solution in that issue.
Closing this issue again. A patch for windows was committed. This issue moved to JBIDE-9712.
Andre Dietisheim
added a comment - A patch for windows was committed. This issue moved to JBIDE-9712 . Verified as part of JBIDE-9712. Closing
Radim Hopp
added a comment - Verified as part of JBIDE-9712 . Closing 
I tend to think that the dialog to search for runtimes should be modal, too.
Fiddling around I found out that the fact that the latter dialog inhibits the former one from getting inputs is due to Dialog#setBlockOnOpen(true) in the Dialog super constructor. I therefore set both dialogs to be modal and not to block on open.
The result is the following (in my environment):
Both dialogs are able to get user inputs (mouse, keyboard), but the workbench behind it still does not react to user inputs.