On 10 December 2010 14:22, Denis Dzyubenko <[email protected]> wrote: > On 8 December 2010 00:44, Daniel Stone <[email protected]> wrote: >>> > The min/max of the major/minor (aka width/height) is actually not that >>> > important >>> > - they are all calibrated in devices coordinates, so using the same scale >>> > for >>> > all of x/y/major/minor gives you the best result. >>> >>> well I still do not know what _is_ the scale. Actually I am not using >>> MTAbsX/Y right now - I mainly rely on the root_x/root_y properties. >> >> Right, so that would explain why you're getting screen-scaled >> co-ordinates ... if you want unscaled, look at the x and y valuators >> attached to the event, rather than root_{x,y}, which is by definition in >> screen co-ordinate space.
ah now I see the email where you said that you found that bug and it is fixed in your branch. Sorry for the noise. -- Best regards, Denis. _______________________________________________ Mailing list: https://launchpad.net/~multi-touch-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~multi-touch-dev More help : https://help.launchpad.net/ListHelp
