Ken Ray wrote:
I think my problem is that if I open a
button's script, and then delete the mouseup handler, then close the script
and reopen it, the mouseup handler has been reinserted. If the IDE would
honor my choice to remove the script of the object and not reinsert the
handler, I would be satisfied.
I figure you know this, but I'll mention it for the benefit of the
newcomers, since someone asked why the mouseUp handler doesn't block the
message.
The empty mouseUp handler is a "fake" script, and it doesn't really
exist. It is just a template that's displayed every time the editor
opens when there isn't any other script in there. (Not all objects
display the template script, but those that commonly use a "mouseup"
handler do.)
If you close the script editor without changing the template, the empty
handler is not actually inserted as a script. The template is just a
suggested guideline and if you don't change it, it is discarded when the
editor closes.
My own technique is: if I see the empty template, I ignore it. If I
really do want to block the script, I add a commented line in it like this:
on mouseUp
-- block
end mouseUp
Because I have changed the template, it is saved as an actual script.
For me, it's easier to ignore the empty ones and just change the ones I
really do want to function.
--
Jacqueline Landman Gay | [EMAIL PROTECTED]
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
