The inverse of the transformation matrix that transforms user space to surface space (i.e. device space) can transform coordinate input to the coordinate system the user (programmer) is working in.
 
Depending on the scale of the transformation it's possible for the result to be inaccurate to a degree that the result is inaccurate, but that can easily be cured with a function that returns the input coordinates in surface space, which uses should use if the scaling factor of their transformation from user space to surface space is large enough.
 
-Mike
 


On Wed, Jun 19, 2019, 22:38 Rene Rivera via SG13 <sg13@lists.isocpp.org> wrote:
On Mon, Jun 17, 2019 at 7:31 PM Tony V E <tvaneerd@gmail.com> wrote:
I can only imagine that mouse/touch input needs to be in the same coordinate system as the drawing. 

It almost never is at the device level. Although the higher level APIs users are accustomed to do commonly transform to "drawing" coordinates.

--
-- Rene Rivera
-- Grafik - Don't Assume Anything
-- Robot Dreams - http://robot-dreams.net

--
SG13 mailing list
SG13@lists.isocpp.org
http://lists.isocpp.org/mailman/listinfo.cgi/sg13