Dialogs have always been a hobgoblin in the Windows platform. Developers are constantly faced with an unacceptable choice. One option is to use the built-in dialog and pretend Ok/Cancel or Yes/No are really appropriate prompts for the user. The other is to create their own dialog from scratch, which seems like a waste of time for what should be a simple prompt.
Windows Vista addressed this with the Task Dialog. This dialog provides a framework that covers most dialog scenarios while maintaining consistency across applications. But it also introduces a new problem in that it is not backwards compatible with Windows XP.
Hedley Muscroft tackled this problem by creating a wrapper/emulator for the Task Dialog. When running on Windows XP, the application will use his hand-rolled clone which supports most of the Task Dialog functionality. On Vista, it automatically switches to the built-in dialog.
/filters:no_upscale()/sponsorship/topic/25afca57-6bcb-4c42-9a70-fbea10ce4fc7/MicrosoftLogoRSB-1678874949003.png)
/articles/asp-dotnet-minimal-apis/en/smallimage/logo-1678972581766.jpg){kind=logo}
/articles/functional-dotnet-development/en/smallimage/Fsharp-vs-Csharp-is-one-more-functional-than-the-other-small-1676023056578.jpg)
/articles/dotnet-grpc-json-transcoding/en/smallimage/logo-1674822319367.jpg){kind=logo}
/articles/Dotnet-Seven-MSMQ-Alternatives/en/smallimage/logo-1670585778128.jpg){kind=logo}
/articles/polygot-microservices-dapr-aks/en/smallimage/logo-1666079703389.jpg){kind=logo}
/articles/dotnet-trends-2022/en/smallimage/InfoQ-Trends-Report-1663778620252.jpeg)
/presentations/staff-plus-open-source/en/smallimage/alex-porcelli-s-1679038616213.jpg)
/presentations/java-compiler-intermediate-representation/en/smallimage/chris_seaton-s-1679038354209.jpg)
/articles/technology-carbon-impact/en/smallimage/logo-1678865261490.jpg){kind=logo}
/articles/lambda-migration-k8s-jobs/en/smallimage/logo-1678732894614.jpg){kind=logo}
Community comments