>Terry's suggested use of the idle handler will probably draw another >response about 'avoid idle" but there are times like these when it >is useful. What is needed is a better way to handle it. Under >HyperCard I wrote a set of XCMDs/XFCNs to manage a "task space" >efficiently and make it easy to add and remove tasks without the >fiddles and inefficiency which grow when you try to script "on >idle". I am busy at work at the moment but should be able to post >some scripts this evening for doing it directly in Rev. >Incidentally, "send message in <N ms>" is very useful but there are >times when you just want to act in time complementary to the user's >activity, rather than forcing the action at a given time, and idle >can be useful for this if used sparingly. So, Michael, Terry's >suggestion is good and if you'll give me a few hours I hope to give >you a better way of doing it. >
Or you could use a repeat loop in a mouseDown handler... _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
