Re: #6091 Remarks
Austin Donnelly wrote: > Something like (dx*dx + dy*dy) > thresh might be a better condition, no? > Yes ;) Thank you. No one particular value of "Thresh" would please everybody, it would give rise to a "snap to an invisible grid" effect, so a setting mechanism for this value should extrude into preferences. Though for very precise positioning, one can resort to the "Move Tool" and cursor keys, and, perhaps dispense with a preference setting (for now) and retain a relatively large area threshold. I haven't tried this to see if it improves the situation. A matter for this coming weekend. Be good, be well Garry
Re: #6091 Remarks
On Monday, 27 Nov 2000, Garry R. Osgood wrote: [...] > 3) An approach that I did not try runs along the line of changing >the compression strategy of gtkutil_compress_motion() so that it >rejects any motion event where a x*x + y*y - (x +dx)*(x +dx )- (y >+dy)*(y +dy) delta is less than a pre-set difference. Such a >filter is applied to all motion events. This may be a bit radical >this close to the Fabled 1.2 Release. This particular formula is flawed: it would result in filtering out _all_ events if you were to move the stylus in a circle around the origin. Something like (dx*dx + dy*dy) > thresh might be a better condition, no? Austin
