I've done something similar, but while I don't have a solution to your 'double-click Next' issue, I can suggest how my validation works.
On the 'Next' control button I have a pair of Punlished Events for true/false as you do, but only one is "NewDialog". The REGISTRATIONCODEVALID="false" case publishes a "SpawnDialog" event that has a string saying something like "Invalid key!" and an "OK" button control that has a published event of "EndDialog". This just gives the user a pop up that they can't avoid until a valid key is entered. Works a treat. Cheers, Gareth -- View this message in context: http://www.nabble.com/Condition-display-of-dialog-tf3399345.html#a9478182 Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------- 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
