On Mon, Apr 15, 2002 at 03:14:19PM +0200, Juergen Vigna wrote: > Well yes it works on Buffer change now, but the values are still wrong, > you just compensate them in the edit() call now! Practically you would > have to use the x/y code you use in ::insetButtonPress()! So if I get > edit(bv, 0, 0, 0) then it's the start of the inset! > > You didn't understand the "relative" x/y problem I explained in my first > mail, isn't it?
Not exactly probably. > I try it with other words a math inset in the middle of a row (which say > starts at x position 200) will have as x position in the call to edit AND > insetButtonPress 0 if I press BEFORE the first character INSIDE the inset. Does this mean, mathed can be ignorant to any outside positioning? I.e. I can assume all parameters send to mathed methods are 'normalized', i.e. assume an origin of the inset in (0,0)? This would be nice... Ok, then all the xo_/yo_ handling in mathed is Wrong, since it stores absolute values everywhere, not relative to the inset's origin. This is not exactly my doing and maybe was not even possible to do otherwise until this recent change of yours that allowed me to remove this awful hack for cursor positioning... But the question is: How important is it to get this right? I probably would have to touch a dozen math insets to switch from absolute positions to relative... Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
