[
https://issues.jboss.org/browse/JBDS-1795?page=com.atlassian.jira.plugin....
]
Andre Dietisheim commented on JBDS-1795:
----------------------------------------
added a listener that would kick in as soon as the dialog gets hidden by another dialog.
It would then call shell#forceActive to bring it back to the front. It seems to work
initially but not any more later on. So this is the best we can do for M3 and we need to
find a better solution for M4.
Runtime Detection Dialog during first start gets over modal dialog
with request to let usage reporting.
-------------------------------------------------------------------------------------------------------
Key: JBDS-1795
URL:
https://issues.jboss.org/browse/JBDS-1795
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: runtime, Usage Reporting
Affects Versions: 5.0.0.M3
Reporter: Denis Golovin
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 5.0.0.M3
Attachments: forceUsageDialogActive-2.patch, forceUsageDialogActive.patch
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira