Richard,
Thanks, (grinning) I had fun with frapper.
I did do a send in time message from a mouseDown that then checked
for both mouseDowns and mouseUps during repeats and if neither
existed then it stopped the loop. That part was fine and worked like
a charm. The part that would have been less complex would have been
the figuring out what the target was/is at any given moment. I had to
do all kinds of checks to keep it right, whereas if the mouseDown,
over the target and then up on a new target message didn't go back to
mouseDown but rather to the target it was over then my job would have
been real smooth. It worked but was more complex than needed.
This approach left mouseMove open for other things in the program
which I needed too.
I am afraid at this point (after I signed the new NDA) I would need
to have whoever looked at the project sign an NDA (maybe they would
go for this).
With the recent thread describing what Rev can't do I wanted to show
some of the things it could do.
Tom
On Dec 6, 2005, at 6:18 PM, Richard Gaskin wrote:
Thomas McGrath III, before get started I want to thank you for
posting your pics to frappr. Your two pictures are a great
compliment to one another: one looks like the serious philosopher,
the other like a kid having so much fun he might burst. Good
stuff. :)
This hit home with me, as I've wrestled with mouse-message issues
myself in some apps:
_______________________________________________
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
