> From: Bob Arnson [mailto:[EMAIL PROTECTED]
>
> J. J. Farrell wrote:
> > At the moment I'm setting these SetupAPI parameters to
> > NULL. I'm guessing from Bob's message that I can solve
> > this problem by passing a handle to the Installer UI
> > window instead of NULL. Does this sound right? I know
> > almost nothing about Windows UI programming, so my
> > main question is: how should a C deferred custom
> > action get hold of a handle to the installer UI window
> > for passing to these SetupAPI routines?
>
> Possibly. I thought there was a WiX function that returned the
> active installer window but I can't find it at the moment. You
> might want to check out GetForegroundWindow.
Thanks Bob. I ended up with
hWindow = FindWindow("MsiDialogNoCloseClass", NULL);
To find the Installer's UI window. The class name varies with
the style of the window, but a call of this sort should be able
to find a window associated with the Installer. Passing this
handle to the SetupAPI functions solved my problem of pop-ups
appearing behind the Installer UI window.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
