>>>>> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>> The complications, if I'm not mistaken, are due to the use of a >> combobox and the need to track what's in it. Almost all of the new >> code is devoted to that. >> Abdelrazak> Yes. Note that the xforms frontend had radio buttons, and the combox was an 'innovation' of the qt2 frontend. I do not remember what the rationale was. Abdelrazak> No need to rewrite the labels: if "use default alignment" Abdelrazak> is checked, then the relevant radio button will be set, Abdelrazak> even thought disable. So we don't need to append (default) Abdelrazak> to the label. I think we should go that way. This could work. Or the default entry could be set in italics. >> This one kind of puzzles me. I grepped the code and the only >> substantive occurrence of it is in lyxlayout.C, in >> readAlignPossible. But since AT_LAYOUT is pushed onto the stack at >> the beginning of that routine, LYX_ALIGN_NONE can never be >> returned. So it will never be the layout of anything. Abdelrazak> Anyone has additional info? It is used in tabular inset, when there is no alignment. Otherwise, I think it is not useful for paragraphs. Actually, I think ALIGN_LAYOUT and ALIGN_NONE should be the same thing. >>> This one I don't understand: case LYX_ALIGN_SPECIAL: return >>> "Special"; >>> >> There are no substantial occurrences of this in the code. >> Abdelrazak> If it is not used, we should ditch it. Any comment anyone? It seem not used indeed. The only possible case of SPECIAL alignment I am aware of could be for captions: they are centered when smaller than a line, block-justified otherwise. JMarc
