I'll try to resist the urge to SHOUT, but, as far as I can tell, the transcript dictionary has "piss poor" documentation of the mouse function. Is there any documentation available of how the mouse function actually works that would predict or explain the behavior of the mouse in the loop script mentioned by Ian Summerfield ? Anyone converting projects from HyperCard or SuperCard might encounter this issue and wonder what is going on. Or is this unexpected and unpredictable behavior simply punishment for "piss poor technique"? Will similar behavior occur with other functions, like keysdown(), optionKey(), etc.? Perhaps just removing the mouse function would be better than misleading or mystifying users about how it might work.
I'm sure there's better documentation somewhere that I just haven't found. Thanks for the clarification. Scott Saults >Date: Wed, 13 Feb 2002 10:58:55 -0700 (MST) >From: Scott Raney <[EMAIL PROTECTED]> >(snip) >Just my 2 cents on this issue: >IF YOU'RE USING THE MOUSE FUNCTION FOR NEW DEVELOPMENT, YOU'RE DOING >THE WRONG THING!!! >Apologies for the shouting and for sounding like a broken record on >this issue, but I can't emphasize enough that this is piss poor >technique and will bring you nothing but grief in the long run. If it >were up to me "the mouse" function would be removed from >(etc) _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution