[wix-devs] Burn standard c++ boostrapper accessibility
Rob Mensching
rob at firegiant.com
Sat Feb 23 17:41:36 PST 2019
It's not a dialog class because the window isn't a dialog. It's a window with custom rendered controls by thmutil.cpp.
I suppose you could try changing the class to a dialog if that helped (and worked).
I don't really understand your second question.
-----Original Message-----
From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> On Behalf Of Sean Farrow via wix-devs
Sent: Friday, February 22, 2019 2:47 PM
To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
Cc: Sean Farrow <sean.farrow at seanfarrow.co.uk>
Subject: [wix-devs] Burn standard c++ boostrapper accessibility
Hi all,
Pertaining to my thread regarding burns accessibility, I've done some digging and noticed that the standard C++ bootstrapper creates a window with a class as follows:
static const LPCWSTR WIXSTDBA_WINDOW_CLASS = L"WixStdBA"; Is there any reason this isn't a dialog (class #32770)?
This is partly why the native C++ bootstrapper isn't as accessible as it could be.
Secondly, I was wondering where the controls for the theme are actually laid out programmatically on the window create in the CreateWindow procedure?
Cheers
Sean.
____________________________________________________________________
WiX Toolset Developer Mailing List provided by FireGiant http://www.firegiant.com/
More information about the wix-devs
mailing list