I don't get it out of my mind.
It looks like changes on lines in the %code% can influence the behavior of the events in the dialog.
See Scott's reply in Mike's thread.
http://msgboard.alphasoftware.com/al...ad.php?t=85788
First question Is that true?
Then: Why? maybe a more open question: Why not?
Just take Ira's event watcher here (Thanks for making this tool Ira!!)
Enter some input in Name and in Number and give focus to Name and push the Clear Events button.
Now delete the contents of Name with the Delete button. you will see that there are two 'change' events passing. I wish someone could explain.
It is weird but maybe preferable to the trap event 'changing' instead of the event 'change' because of the arise of the additional unexpected 'change'-events but that is not a valid reason.
Who can point me to the documentation to know what really happens? What am I missing in Lesson 6 Introduction to Dialog Box Events wiki
Who knows examples that demonstrates the operation?
I also used a lot of time to understand but not fully succeed.
Xdialog is not debug-able because it causes and shows every changes in focus. We must use trace.writeln() in our sript to see the names of the various events in the trace window.
I did but without progress.
I very much would appreciate a video made by Selwyn or an explanation (from Martin?) for this specific item.
e.g.
What are all the different types of the events;
How to prevent unexpected 'change' results.
The info on alphawiki and alphahelp are OK for starters but enough to say: Eureka!
It looks like changes on lines in the %code% can influence the behavior of the events in the dialog.
See Scott's reply in Mike's thread.
http://msgboard.alphasoftware.com/al...ad.php?t=85788
First question Is that true?
Then: Why? maybe a more open question: Why not?
Just take Ira's event watcher here (Thanks for making this tool Ira!!)
Enter some input in Name and in Number and give focus to Name and push the Clear Events button.
Now delete the contents of Name with the Delete button. you will see that there are two 'change' events passing. I wish someone could explain.
It is weird but maybe preferable to the trap event 'changing' instead of the event 'change' because of the arise of the additional unexpected 'change'-events but that is not a valid reason.
Who can point me to the documentation to know what really happens? What am I missing in Lesson 6 Introduction to Dialog Box Events wiki
Who knows examples that demonstrates the operation?
I also used a lot of time to understand but not fully succeed.
Xdialog is not debug-able because it causes and shows every changes in focus. We must use trace.writeln() in our sript to see the names of the various events in the trace window.
I did but without progress.
I very much would appreciate a video made by Selwyn or an explanation (from Martin?) for this specific item.
e.g.
What are all the different types of the events;
How to prevent unexpected 'change' results.
The info on alphawiki and alphahelp are OK for starters but enough to say: Eureka!