> How about having the custom action set a property if the condition is met, > and having the NewDialog event be conditioned on that property?
Hi Nir, What I ended up doing was creating a validate button which invokes a custom action which sets a hidden property enabling the next button. This provides the event for the dialog to queue on triggering a state change in the next button. This is sub optimal because the data can be changed after validation. I hide a secondary validation in the next dialog to catch this. It would be nice to tie up all the logic in the click action, maybe dynamically setting the next dialog for example. I might add a dialogue to review the settings which would have next disabled if the few requiring validation failed, this might be a better ui experience. Thanks for following up, jlc ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
