On Wed, Nov 22, 2006 at 04:19:00PM +0100, Abdelrazak Younes wrote:
> >No. If the nicefrac is in an array I expect that pressing "down" in the
> >numerator goes to the next row of the array and not to the demoninator.
> >More specifically, I expect that the cursor goes to the inset in the next
> >row that is at the same x position. If it is not in an array I expect the
> >cursor to go out of the formula. If the down button would go right, how
> >would I be supposed to really go down?
>
> By pressing down twice.
So in
aaaa\nicefrac{|bbbbbbbb}{ccccccc}ddddddd
<Down> should end up in
aaaa\nicefrac{bbbbbbbb}{|ccccccc}ddddddd
rather than
aaaa|\nicefrac{bbbbbbbb}{ccccccc}ddddddd
?
I'd like to see you handle the user's outcry...
> XML could help us for that because we won't need to do the logic
> calculation inside LyX. The logic would be embedded in the format.
You can't handle a tree suddenly faster just because you use XML.
> >That is then an implementation problem. I don't see why it needs to be like
> >that. IIRC the brutefind methods were introduced as a fallback hack and
> >never intended to be really used, because the normal find methods should
> >always work.
>
> So, anyone remember is there was any plan to replace that.
There was/is no such plan. bruteFind is essential part of the up/down
navigation that can not be aboandoned without sacrificing much of what
mathed makes easy to use.
> The problem here is that sometimes we need something that is not on
> screen but that we should have calculated anyway. This happens for
> example when you have a formula that is only half displayed at the
> bottom of the screen. I am not sure how this is handled by the
> CoordCache but it seems that only what is on screen is in the CoordCache
> (I might be wrong here).
And if this is true (which I doubt btw), it is a rcent development. The
CoordCahce Traditionally held full (outer) paragraphsa, and there is no
formula spanning several (outer) paragraphs, so there is (was) no way
that a formula is partaiily cached.
Andre'
