On 19/02/13 23:52, Robert O'Callahan wrote: > I think my idea for an anti-flood state makes this unnecessary.
There are two distinct use cases: 1. You only care where the mouse currently is. 2. You need to know both where the mouse is and how it got there. We really have to choices: A. Provide an API that allows applications to specify whether they are type 1 or type 2. It could be implicitly done by including a mouse event history array. B. Automatically prevent flooding (as per roc's suggestion) C. Both of the above. Option A fixes most cases but adds more complexity to the API (although not much). Poorly written applications or slow systems may still end up flooding. Option B will mostly fix the problem but will waste CPU cycles if your application is type 1. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
