JDK-6278099 : Native file, page and print dialogs can't be modal blocked on Windows
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 6
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows,windows_xp
  • CPU: generic,x86
  • Submitted: 2005-05-31
  • Updated: 2011-07-01
  • Resolved: 2011-07-01
Related Reports
Duplicate :  
JDK-6179142 - Should consider hierarchy changes for Print and File dialog windows peers
Duplicate :  
JDK-6322803 - Dialog TOOLKIT_MODAL does not block null-parent FileDialog
Relates :  
JDK-6573191 - PIT : ApplicationExcludeDialogTest throws java.lang.NullPoiinterException : null pData
Description
Native windows dialogs can't be blocked by any modal dialogs. That is a rare case as such dialogs are application-modal and usually get processed immediately (no other dialogs are shown when these are active), but it doesn't contradict AWT Modality Spec and should be fixed.

###@###.### 2005-05-31 11:27:57 GMT
Comments
EVALUATION This bug should be fixed as a part of 6179142.
01-07-2011
EVALUATION AwtWindow::_ModalDisable and AwtWindow::_ModalDisableByHWnd methods are supposed for blocking usual AWT dialogs, i. e. dialogs, that have a peer objects attached and that are descendants of AwtDialog. Native windows dialogs are outside AwtDialog hierarchy (and even outside AwtObject hierarchy) and have no required pData, so they always stay unblocked. ###@###.### 2005-05-31 11:27:58 GMT
31-05-2005