In article <664797.8163...@web59804.mail.ac4.yahoo.com>,
"little.forest" <little.for...@ymail.com> writes:
> "Additionally, you can't have more than one NewDialog control event
> on a button, even if the conditions are mutually exclusive."
At one point I found this buried in the MSI documentation; I don't
recall where it was offhand, but we had a series of dialogs with
complex conditional transitions between them. Occasionally, buttons
would just cease to work and the dialog sequence was hung.
Eventually we tracked it back to this constraint. Once we went the
route of using a property to specify the target dialog and changed
everything to only a single NewDialog event per control, then
everything worked properly again.
The annoying thing is that it will *appear* to work until it doesn't
and there's no unifying principle as to when it will work and when it
won't. Its a little more work to do things through the property, but
it is guaranteed to work every single time that way.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/>
Legalize Adulthood! <http://legalizeadulthood.wordpress.com>
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
