View Single Post
Old 16 March 2014, 11:20   #6
mark_k
Registered User
 
Join Date: Aug 2004
Location:
Posts: 2,481
Quote:
Originally Posted by Toni Wilen View Post
So tablet.library basically is a wrapper for input.device tablet stuff? I assumed it was something more complex.
Well maybe TriMedia (co-)developed the spec which Commodore later supported in Intuition V39. So at least on Intuition V39+, tablet.library could be a kind of wrapper around that.
Quote:
Originally Posted by Toni Wilen View Post
Do you mean A0 is IntuiMessage received by the application which tablet.library may or may not modify? Or is it completely generated by tablet.library?
I'll look at the code in DPaint/OpalPaint again, but I was probably wrong about tablet.library modifying the passed IntuiMessage.

A couple of possible uses for the IntuiMessage argument by tablet.library:
- Look at the time values (Seconds, Micros). When updating the TabletData structure, interpolate recent position readings so the position data written to the TabletData is (an approximation of) what it would have been at that time.
- On Intuition V39+, check whether the IntuiMessage has eim_TabletData non-zero. If so, copy the values from that TabletData structure.
mark_k is offline  
 
Page generated in 0.04786 seconds with 9 queries