Thanks, Ben, I forgot about the 2.7 "allowInterrupts = false" bug since I am not using it yet. In this case, *I* needed the reminder...
Jim Ault Las Vegas On 7/3/06 1:55 AM, "Ben Rubinstein" <[EMAIL PROTECTED]> wrote: > Jim's right to point to that thread - and the various strategies he mentions > are all good - but actually towards the end of the thread it was established > that the leading issue was that in 2.7.x, the global property > "allowInterrupts" has been set false by default - it should be 'true'. With > this property set to true, command-dot works as you expect (except in certain > cases with modal dialogs open, which led to the rest of the discussion above). > > As to giving a handler a maximumm time to finish, AFAIK there is no way to do > this from 'outside' the handler - ie as Jim hints, you'd need to build this > into your handler in some way. > _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
