http://bugs.winehq.org/show_bug.cgi?id=34850
Bug #: 34850 Summary: Improve commctl32 TaskDialogIndirect stub to show "content" part in task dialog box (more detailed error messages for various apps/games) Product: Wine Version: 1.7.5 Platform: x86 OS/Version: Linux Status: NEW Severity: minor Priority: P2 Component: comctl32 AssignedTo: wine-bugs@winehq.org ReportedBy: focht@gmx.net Classification: Unclassified
Hello folks,
this is a bug split off from bug 34008 ("Bioshock Infinite won't start (needs D3D11CreateDevice implementation to support at least D3D_FEATURE_LEVEL_10_0)")
The bug reporter complains that the reason for the error can't be seen in message box Wine creates (as substitute for task dialog):
--- quote --- Bioshock Infinite shows an empty message box on launch and closes after pressing OK button. Nothing else is shown. After making a dirty hack in commctrl.c (replaced pTaskConfig->pszMainInstruction with pTaskConfig->pszContent) I can see the messagebox saying that I should have DX10/11 compatible hardware and DX11 runtime: http://i.imgur.com/OxHDoKI.png --- quote ---
This is actually true and I've also seen this for other apps that make use of TaskDialogIndirect.
Wine currently only uses "pTaskConfig->pszMainInstruction" for display which might not contain the essential information. Various apps put the real info in "pTaskConfig->pszContent".
MSDN: http://msdn.microsoft.com/en-us/library/windows/desktop/bb760544%28v=vs.85%2...
Article showing use of various parameters/options with screenshots:
http://www.codeproject.com/Articles/16806/Vista-Goodies-in-C-Using-TaskDialo...
Regards