tracking down freeze based on timing, maybe?

[Scott Rossi]

Without knowing what's happening in your handlers, there's not really any way to guess at what might be going on, but you might try using the flushEvents function to ignore extra or unwanted click events.

Dated looking doc reference here: http://docs.runrev.com/Function/flushEvents

Regards,

Scott Rossi
Creative Director
Tactile Media, UX/UI Design

> On Dec 13, 2015, at 9:23 AM, Matt Maier <blueback09 at gmail.com> wrote:
> 
> I can make my program freeze if I click the trackpad button really fast.
> 
> If I click the button down, then wait, then up, it doesn't freeze. I used a
> log to find out all of the handlers it got through before it froze. Most of
> the time it logs through all of the related handlers and then freezes up
> after they're all done, but every now and then it stops logging in the
> middle of a handler.
> 
> So I suspect that whatever's causing the freeze might be something
> happening either in parallel with my handlers, or something my handlers
> leave behind that eventually (after they end) builds up until it causes a
> freeze.
> 
> The sequence is basically:
> some mouse message
> - handler 1
> -- handler 2
> - handler 1
> end mouse message
> 
> Any suggestions for tracking down what's causing the freeze? It's not
> happening inside of the handlers I wrote. Instead it's happening after all
> of my handlers are finished, and then only if I click the button as fast as
> possible instead of slowly down-up.
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode