On Mon, Oct 20, 2003 at 09:10:51PM +0000, Angus Leeming spake thusly: > > Martin, could you provide me with a synopsis of the current status > please? I've read the flurry of mails and think I have a picture, but > it'd be good to have this from the horse's mouth, so to speak. > > I see from your commit that the code (text3.C) now takes care of > centering the inset in display() mode. Is this slated to stay? I see > that you have also removed the offset_ var from formula.[Ch]. Do you > plan to do something similar with insets in src/inset? > > Etc, etc, > Angus
Good question.
The situation is this:
For insets for which display() is true, the core does this:
1) break before
2) break after
3) prevent the row above the one containing the inset from stretching
('disp_inset' stuff)
4) center the row that the inset is on.
Because of 4), the offset_ variable and code is no longer needed in
formula.C. The inset will be centered, the cursor will follow the
centering, and so will the 'clickable area', without doing anything
special.
I have experimentally placed display() =true in footnote/marginnote
and floatinsets. I think eventually we want to make all collapsable
insets displayed *when open*.
As for insetinclude, insettoc etc. -- the "button insets", I wonder.
The current system, with center_indent_ and the button as a sensitive
box, works. But we need display() in order to make the line above the
inset not stretch. So once we have it, I suppose we could get rid of
center_indent as the inset will be centered anyway. But I would leave
the button box logic in place -- it's only three lines and it's IMHO
conceptually wise to distinguish inset and button. But that's just my
opinion.
Is there anything more specific that leaves you wondering?
- Martin
pgp00000.pgp
Description: PGP signature
