Common dialogs in Windows 7 vs. XP or Vista
The common dialog for file opening has changed in Windows 7 as shown in the table below: V32 V64 W764 ...
Forum Discussion
Hi all,
We were also hamstrung by this but found a workaround - for us anyway i.e. app being tested is built with Delphi 2007. We stepped in to the VCL source and found the use of Windows 7 (also Vista) dialogs depended not only on o/s version (WinMajorVersion >= 6) but on themes being enabled and a global variable Dialogs.UseLatestCommonDialogs being true.
We disabled themes (by choosing the Windows Classic Theme and found we were able to get access to the properties we used to under XP.
The actual test, in the Delphi unit Dialogs is:
if (Win32MajorVersion >= 6) and UseLatestCommonDialogs and ThemeServices.ThemesEnabled then ... (use W7 dialog)
We found that we can set the variable UseLatestCommonDialogs in app startup code viz
Dialogs.UseLatestCommonDialogs := False;
but haven't tested it yet.
We're still considering the ramifications of either of these solutions - whether, for example, we're throwing out the baby with the bathwater by forcing our testing to be effectively against an XP UI or by requiring a code change to make the app testable.
We would appreciate any comments from the community on this aspect
Regards, sjwalter
We were also hamstrung by this but found a workaround - for us anyway i.e. app being tested is built with Delphi 2007. We stepped in to the VCL source and found the use of Windows 7 (also Vista) dialogs depended not only on o/s version (WinMajorVersion >= 6) but on themes being enabled and a global variable Dialogs.UseLatestCommonDialogs being true.
We disabled themes (by choosing the Windows Classic Theme and found we were able to get access to the properties we used to under XP.
The actual test, in the Delphi unit Dialogs is:
if (Win32MajorVersion >= 6) and UseLatestCommonDialogs and ThemeServices.ThemesEnabled then ... (use W7 dialog)
We found that we can set the variable UseLatestCommonDialogs in app startup code viz
Dialogs.UseLatestCommonDialogs := False;
but haven't tested it yet.
We're still considering the ramifications of either of these solutions - whether, for example, we're throwing out the baby with the bathwater by forcing our testing to be effectively against an XP UI or by requiring a code change to make the app testable.
We would appreciate any comments from the community on this aspect
Regards, sjwalter
