Post a reply to the thread: Reset variables and a few other issues
Click here to log in
What's the name of our main installation product (in uppercase letters), directly followed by the current year?
You may choose an icon for your message from this list
Will turn www.example.com into [URL]http://www.example.com[/URL].
Re: Reset variables and a few other issues Hi Tom, The "Development Build" is available now: http://www.lindersoft.com/forums/showthread.php?t=32094 Friedrich
Re: Reset variables and a few other issues
Re: Reset variables and a few other issues BTW, we'll try to make a "development build" available tomorrow. If you are interested, you can then check the enhanced event handling and RTF print fix. Friedrich
Re: Reset variables and a few other issues RTF print bug fixed. Thanks again for bringing this to our attention. --- FIX : (sync from SB8) [SB#105111] Runtime: Under certain circumstances, the "Readme" or "License Agreement" Print button printed the wrong RTF text. --- Friedrich
Re: Reset variables and a few other issues Excellent, thanks! Tom
Re: Reset variables and a few other issues I think it behaves as expected in the latest internal source code now: CHANGE : (sync from SB8) [SB#105131] Runtime: A "Custom Dialog Wizard" did not fire an $EVENT:ONUPDATE$ event when the user pressed the 'Next' button after going back from the next dialog. CHANGE : (sync from SB8) [SB#105132] Runtime: A "Custom Dialog Wizard" receives an $EVENT:ONREOPEN$ event when the user presses the 'Back' button. Friedrich
Re: Reset variables and a few other issues Thank YOU so much This is definitely a bug!!!! If you go 'Back' two dialogs then 'Next' to go to the dialog that should fire the update event and press 'Next' again then it works as expected. Argh! We'll fix this. Thanks again Friedrich
Re: Reset variables and a few other issues Whew... figured out a workaround. It seems that no defined event is fired when you press next, but an event = 0 is. So, code under the dialog can execute if it is not in IF EVENT:ONUPDATE structure. My workaround is that I've defined a 'save' variable for the reg code prior to the loop, and within the dialog I ignore events and just test for the current value vs the saved value. If it is different, it does all the required logic and resets the 'save' variable to match the new value. Works for me in my initial tests... Thanks ever so much for the usual excellent support! Tom
Re: Reset variables and a few other issues Hi Tom, Interesting... I can reproduce this here. IMO, this is a bug. Item in review Friedrich
Re: Reset variables and a few other issues Hi Tom, Hmm, no event in this case? I'll check this Friedrich
Re: Reset variables and a few other issues > But if the user clicks "Next" then you have an event to do whatever is > required (in the next dialogs) That's the key point: I don't get an event when the user presses next after going back and changing the entry control. No event is fired, so none of the logic for setting up the rest of the script behavior is executed. It just proceeds to the next dialog, leaving everything as it was as if the user never went back and made the change. Sorry if this seems convoluted... Thanks, Tom
Forum Rules