JDK-6359035 : Apply WinXP visual styles to AWT native dialogs
  • Type: Enhancement
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 5.0,6,7
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: windows,windows_xp
  • CPU: generic,x86
  • Submitted: 2005-12-05
  • Updated: 2011-03-07
  • Resolved: 2011-03-07
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6 JDK 7
6u10Fixed 7 b02Fixed
Related Reports
Duplicate :  
JDK-6178745 - Include javaw.exe.manifest to enable native controls with XP visual styles
Relates :  
JDK-5049340 - AWT applications should look like native GUI applications
Relates :  
JDK-4587653 - AWT needs to provide API or properties to support Windows XP Themes
Relates :  
JDK-6578583 - Regression: Modality is broken in windows vista home premium from jdk1.7 b02 onwards.
Relates :  
JDK-6582346 - javaw launcher does not display MessageBox after change to the resource files.
Relates :  
JDK-6482911 - fix for 6359035 doesn't work in appletviewer
Relates :  
JDK-6707836 - make/sun/awt/make.depend needs to be regenerated after CR 6359035
Relates :  
JDK-6625814 - All Deployment native Dialogs should take native windows look and feel.
Relates :  
JDK-6542975 - Crash in awt.dll when WM_IME_NOTIFY message is handled, Win32
Relates :  
JDK-6994393 - javaw.exe is missing 'Microsoft.Windows.Common-Controls' dependency in assembly
Relates :  
JDK-6743433 - IM candidate window is not shown until window is deactivated and reactivated again
Description
This CR is a part of larger one: 5049340 (AWT applications should look like native GUI applications). It seems that 5049340 requires much investigation, while applying visual styles to native dialogs only is a relatively simple task.
Comments
EVALUATION According to MSDN (see http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwxp/html/xptheming.asp) AWT should use a special manifest file to all the AWT applications to look fine on WinXP. This manifest can be either linked into awt.dll or simply put into the same folder where executable file (java.exe) is. As the second way requires some end-user actions, the manifest is to be linked into the library at the build time. Second, when the manifest is linked, a new version of common controls library (comctl32.dll) is automatically used. That means that AWT should now use another window subclassing schema (see http://msdn.microsoft.com/library/default.asp?url=/library/en-us/shellcc/platform/commctls/userex/subclassingcontrols.asp).
05-12-2005