Martin Vermeer wrote:
> One question: should it also not happen if the inset is, e.g., an
> insetERT in in-line mode, i.e., shorter than the text width? I can
> see why you have a problem with it aestetically, but how to be
> consistent?
'Consistent' here means 'allow the inset to decide how it should be
displayed'.
> BTW what about text.C
>
> 742 if (!in || in->isChar()) {
> 743 // some insets are line separators too
> 744 if (pit->isLineSeparator(i)) {
> 745 point = i;
> 746 chunkwidth = 0;
> 747 }
> 748 continue;
> 749 }
>
> this breaks after an inset which announces itself to be a line
> separator. Could we put code here to break before it as well?
Why not if it cures the current problem.
Rename the function 'breakLineAfter' and add a function
'breakLineBefore' or some such and all should be clear for posterity
too ;-)
--
Angus
