In article <1243528043.2048.1317665...@webmail.messagingengine.com>,
"Curtis Jewell" <lists.wix-us...@csjewell.fastmail.us> writes:
> I know MsiProcessMessage is what I want to do to check for that cancel
> button... (I'd make the call each time I recurse into AddDirectory) but
> what's opaque is what parameters do I use if checking for a Cancel
> button press is the only thing I want to do?
There are two ways you can approach this. You can just periodically
write something to the log file with MsiProcessMessage with
INSTALLMESSAGE_INFO and check the return value.
However, since your action takes quite a while, if you don't have some
sort of updated UI your user is going to think the UI is "hung" and
might do something stupid, like kill the process in the middle or
generate a support call.
So, the method I would suggest is to indicate progress of your CA by
publishing AcionData messages with INSTALLMESSAGE_ACTIONDATA instead.
If you know, or can determine when your action runs, how many steps
are needed in your custom action, you can also publish progress
messages to move the progress bar appropriately with
INSTALLMESSAGE_PROGRESS. Either of these is preferable because it
gives feedback to the user that things aren't "hung".
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://www.xmission.com/~legalize/book/download/index.html>
Legalize Adulthood! <http://blogs.xmission.com/legalize/>
------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, &
iPhoneDevCamp as they present alongside digital heavyweights like Barbarian
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
