<html>
<!-- BEGIN WEBMAIL STATIONERY -->
<head><style type='text/css'>
p {
margin: 0px;
}
</style></head>
<body>
<!-- WEBMAIL STATIONERY noneset -->
<P>Thanks for the help. Klaus Major's "pass" command does the job (but it has to be "pass <theCustomPropertyName>", not "pass setProp").</P>
<P> </P>
<P>Further experimentation suggests that the MC Help file's stipulation that "when you set an object's property from within a setprop handler, setprop messages are not sent" applies ONLY if the setProp handler is in that object's own script. If (as I tried to do) you set a property from within a setProp handler in the script of a stackInUse, another setProp message DOES get sent, with recursion problems. So the "validation" use of setProp suggested in the Help stack (i.e., a "setProp percent" handler receives as a parameter the value that the property was set to, and then checks and possibly modifies that value) cannot be used "globally"; it can only be used for the object in whose script that setProp handler appears.</P>
<P> </P>
<P>David Epstein</P>
<P> </P>
<P>Klaus major wrote: </P>
<P> </P>
<P> > Hi David, <BR>> <BR>> > MC 2.5's help stack says that "when you set an object's property from <BR>> > within a setprop handler, setprop messages are not sent." Is this <BR>> > true? <BR>> > <BR>> > Here's my handler: <BR>> > <BR>> > setProp beenChanged whether <BR>> > put the short date into fld 3 <BR>> ###set the beenChanged of this stack to whether -- (without this, <BR>> the setProp handler intercepts the calling command, and the property is <BR>> not set) <BR>> pass setprop ## ;-) <BR>> > end setProp <BR>> <BR>> > When some other handler commands "set the beenChanged of this stack to <BR>> > true", my setProp handler gets called. But when I watch the message <BR>> > watcher, it appears that the second line of my setProp handler is <BR>> > recursively calling the setProp handler, and I get a "recursion limit <BR>> > reached" error. <BR>> > <BR>> > I realize that I could easily avoid resorting to a setProp handler at <BR>> > all, but I was tempted by the ease with which I thought it would allow <BR>> > me to add some behavior I had not thought of when I first wrote a lot <BR>> > of handlers that "set the beenChanged of this stack." Having come <BR>> > this far, I would like to understand how to use setProp properly. <BR>> <BR>> See above, simply "pass"ing the "setprop" will finally SET THIS PROP :-) <BR>> <BR>> Hope this helps. </P>
<!-- END WEBMAIL STATIONERY -->
</body>
</html>