-
Enhancement
-
Resolution: Unresolved
-
P3
-
6, 7
-
generic, x86
-
windows, windows_xp, windows_7
For some reason WFileDialogPeer and WPrintDialogPeer extend WWindowPeer,
but, in fact, they are not a real subclasses for it, because they don't
implement number of its methods and also don't have HWND associated with
this peer (they just show nativa dialogs).
This introduce the problem for maintanace because every time we change
something in WWindowPeer or higher (e.g WComponentPeer) we should check if
such changes are applicable for these classes too (usually they are not).
Perhaps we should change our hierarchy so these classes do not extend WWindowPeer,
but implement appropriate peer interfaces.
###@###.### 10/14/04 13:20 GMT
but, in fact, they are not a real subclasses for it, because they don't
implement number of its methods and also don't have HWND associated with
this peer (they just show nativa dialogs).
This introduce the problem for maintanace because every time we change
something in WWindowPeer or higher (e.g WComponentPeer) we should check if
such changes are applicable for these classes too (usually they are not).
Perhaps we should change our hierarchy so these classes do not extend WWindowPeer,
but implement appropriate peer interfaces.
###@###.### 10/14/04 13:20 GMT
- duplicates
-
JDK-6532709 FileDialog appears at wrong location
- Closed
-
JDK-6278099 Native file, page and print dialogs can't be modal blocked on Windows
- Closed
-
JDK-6469731 Windows: getLocationOnScreen throws NPE for a page dialog
- Closed
- relates to
-
JDK-7009114 GTK FileDialog lies about it's Bounds
- Closed
-
JDK-6573321 KFM 'activeWindow' property is not handled correctly for native dialogs, Windows
- Closed