On Tue, Mar 30, 2004 at 03:12:22PM +0200, Jean-Marc Lasgouttes wrote:
> Andre> Not really. In fact, I'd drop insetAllowed at some point of
> Andre> time and rather 'allow' any kind of inset nesting but
> Andre> render/export 'illegal' combinations in some special way
> Andre> ('Inset type foo not a
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
Andre> On Sun, Mar 28, 2004 at 08:27:18PM +0200, Alfredo Braunstein
Andre> wrote:
>> This is bunch of unsorted fixes mostly to C&P crashes.
>>
>> + add InsetText::insetAllowed with default to true (the main text
>> is an InsetText). Would
On Sun, Mar 28, 2004 at 08:27:18PM +0200, Alfredo Braunstein wrote:
> This is bunch of unsorted fixes mostly to C&P crashes.
>
> + add InsetText::insetAllowed with default to true (the main text is an
> InsetText). Would this produce any undesired side-effect?
Not really. In fact, I'd drop insetA
This is bunch of unsorted fixes mostly to C&P crashes.
+ add InsetText::insetAllowed with default to true (the main text is an
InsetText). Would this produce any undesired side-effect? This solves the
problem of insets silently dissapearing on paragraph break
I will apply this if there are no obj
