Jean-Marc Lasgouttes wrote:
> Juergen> Can I commit this? Even if there's still potential for
> Juergen> improvement, adding the insets to the coordCache is the most
> Juergen> important step.
>
> Yes.
I added a FIXME/warning because of the remaining positioning glitch, comitted
and downgraded th
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> Juergen Spitzmueller wrote:
>> It's even simpler. Cf. the attached.
Juergen> Can I commit this? Even if there's still potential for
Juergen> improvement, adding the insets to the coordCache is the most
Juergen> important
Juergen Spitzmueller wrote:
> It's even simpler. Cf. the attached.
Can I commit this? Even if there's still potential for improvement, adding the
insets to the coordCache is the most important step.
Jürgen
On Mon, 2005-09-19 at 16:22 +0200, Juergen Spitzmueller wrote:
> Martin Vermeer wrote:
> > Here's the explanation:
>
> Thanks. I still don't fully get it. I understand what you are doing, but I
> don't understand why this is necessary (even though I see *that* it is
> apparently necessary).
Sam
Martin Vermeer wrote:
> Here's the explanation:
Thanks. I still don't fully get it. I understand what you are doing, but I
don't understand why this is necessary (even though I see *that* it is
apparently necessary).
> (Actually this is relevant only for positioning *inside* this inset,
> i.e.,
On Mon, 2005-09-19 at 11:47 +0200, Juergen Spitzmueller wrote:
> Another day, another patch...
>
> The attached fixes the cursor positioning problems almost completely. The
> main
> fix is that nested math insets are now added to the cache.
>
> The change in Martins code in x2pos (which I don't
Another day, another patch...
The attached fixes the cursor positioning problems almost completely. The main
fix is that nested math insets are now added to the cache.
The change in Martins code in x2pos (which I don't really understand -- the
code, that is) assures that pos 0 of an inset is ac
