On Tue, Mar 27, 2007 at 02:27:21PM -0400, Richard Heck wrote: > > Here's another idea. Basically, what I've done is added an optional > "setFont" argument to editXY, so we can call it with setFont = false > during mere mouse movements and still take advantage of its recursion > without messing up the font. setFont then has to be carried through the > whole editXY hierarchy. This seems like of silly, but it's probably just > a consequence of what Abdel suggested earlier: that editXY and > checkInsetHit may need re-factoring. editXY is doing two very different > things.
Couldn't you just walk the resulting cursor slice-by-slice and do the necessary font changes there? Andre'
