Re: Hacks so I can daily-drive breakinsets3?
"Jürgen Spitzmüller" <[email protected]> Sun, 05 Jul 2026 10:07:19 +0200
| Newsgroups | gmane.editors.lyx.devel |
|---|---|
| Message-ID | <[email protected]> |
Am Samstag, dem 04.07.2026 um 21:52 +0200 schrieb Jean-Marc Lasgouttes via lyx-devel: > The problem is that there has to be enough room on the line for the > label. But one does not know where to break the line before knowing > which line should have the label on it. That makes things more > difficult. But if you say: * the longest INSETROW gets the label, and if there are multiple with the same length, the first of those this would almost always produce what I have proposed. And I would assume it is not very different from what we have now with non-flowing conglomerate insets, is it? > So I anticipate that having the label on the first line is easier > because it is deterministic. But I may be wrong and there may be > properties of the line breaking algorithm that makes life easier. You definitely know better, but I would think it could get tricky if the first line is very short. > Then I have the `small' issue that an inset in my model is > - an INSETBEGIN row element (the little corners on the left) > - one or more (when the inset is broken) INSETROW elements that point > to a row of text > - an INSETEND row element (little corners on the left) > > The spacing has to be added to the INSETBEGIN/END element and > actually depends on the INSETROW element (is the text there smaller > than the label string?). Therefore, getting the spacing right may be > tricky. > But I can make it work eventually. Do you know the length of each INSETROW element at this point? If so, it does not sound too hard (says the person who doesn't have to code it ;-) > > I am not sure whether what I write makes sense to you, but it helps > me to write down these ideas. Absolutely. -- Jürgen -- lyx-devel mailing list [email protected] https://lists.lyx.org/mailman/listinfo/lyx-devel