"Tom Hawtin" <usenet@[EMAIL PROTECTED]
> wrote in message
news:45fda250$0$8717$ed2619ec@[EMAIL PROTECTED]
> Chris Uppal wrote:
>>
>> Another thought is that the tablet's Java implementation may have the
AWT
>> method Component.coalesceEvents() available for override in your custom
>> Component. I have never tried it myself, but it looks as if you can
>> override
>> that to control what events are coalesced.
>
> Looking at the 1.6 EventQueue source (which is quite different from
1.5),
> you might need to use coalesceEvents as if it were your event listener.
> Also note, rather unusually coalesceEvents is not necessarily invoked in
> the EDT.
>
> Tom Hawtin
Thank you both for your replies: I will look into this.
As to my application possibly not being able to keep
up with mouse movements: although my application has
hardly anything other to do than to process those mouse
movements (i.e. storing them but also drawing a small
line segment connecting the last point with the current
point of the stroke being drawn), this seems quite
possible to me.
If I am not mistaken, the C# low-level Ink handling
system actually takes in an entire stroke before
handing the complete stroke to the application...
Also I vaguely remember having read a comment
stating that in order to have really high-quality
digitizer data for a stroke one needs to handle
the incoming digitizer data with a "real-time"
priority thread. - But maybe there is a medium-quality
way, instead of just a low- or a high-quality
way of capturing an ink stroke? - And medium-quality
just might be good enough for me, and my pupils...
Regards, and thanks again for your replies,
Christian
|
