In article <[EMAIL PROTECTED]>,
<[EMAIL PROTECTED]> writes:
> I was under the impression that while it is only permitted to *trigger*
> one "NewDialog" operation, it is permitted to include definitions for
> several trigger operations as long as the conditions under which the
> separate dialogs are shown are mutually exclusive.
That's what I thought too, but I've had it fail even when the
conditiosn were all mutually exclusive.
Fortunately its not that hard to change the way you're managing the dialog
transitions by using a property to hold the name of the target dialog
for NewDialog. Why continue using something that works by accident when
the change to make it work by design is easy?
Isn't there an ICE that checks for multiple NewDialog control events
on a single control?
--
"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/>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
