Andre Poenitz wrote:
On Wed, Nov 22, 2006 at 03:59:42PM +0100, Abdelrazak Younes wrote:
OK, space is not a good idea. But what about different background colors?
Might work. But I guess you'll end up with situations where the cursor
is just on the border and if you have background colors independently
from the logical cursor positon
Indeed.
By the way, talking about screen size of formulas, it would be nice to
have a horizontal scrollbar for off-screen formula. Or use the same hack
as for the tables.
Go for it...
Another solution would be line breaks within a cell that are only stored
in the lyx file and get not exported (or turned into something harmless)
when exporting to .tex (the latter to give tex2lyx a hint). This
requires about change of a few dozen lines mainly in MathArray plus the
code for the 'end-of-line' insets but is more or less straightforward.
This way a user can break long lines by himself. This is also easier to
navigate than long scrolling lines.
Sound like an excellent solution. Could you do it?
Sure the formula navigation can (and should) be improved, but IMHO the pink
corners are not part of the problem.
Sure the current drawing strategy is the problem. It would be better to
just say to the frontend "Just draw the pink corners!" but this is not
possible ATM, and this is too much work to modify that.
Math drawing was historically never a performance bottleneck. In the old
updateInsetInInset times (with new mathed, i.e. 1.2.x) you could easily
draw a 50x50 math table but not a 50x50 real table. Mathed drawing
hasn't changed significantly since then. So I don't know why the pink
corners suddenly appear as preformance killer. In fact I doubt people
are poking into the right corner here.
You misunderstood the problem. Drawing math is not faster nor slower
than the rest. What's problematic is to have to redraw when navigating
with the mouse or the keyboard. We don't need to redraw for other
insets, only for mathed because of the pink corners. What is even worse
is that what we have to redraw the entire screen (but this last PB can
probably be optimized).
Abdre'
Andel
;-)
