Richard Heck <[EMAIL PROTECTED]> writes:
> OK. So what sorts of insets ought to be allowed in InsetOptArg? Or
> what sorts ought to be excluded?
I do not know really.
JMarc
Jean-Marc Lasgouttes wrote:
[EMAIL PROTECTED] writes:
+ // FIXME At present, these are being enabled and disabled according to
+ // whether PASSTHRU has been set in the InsetLayout. This makes some
+ // sense, but there are other checks that should really be done. E.g.,
+
On Mon, 08 Sep 2008 10:23:52 +0200
[EMAIL PROTECTED] wrote:
> Martin Vermeer <[EMAIL PROTECTED]> writes:
> >> > BTW, I do not understand why this stuff is done in InsetCollapsable
> >> > instead of InsetText.
> >> Me either. Probably goes back to who knows when.
> > Try move it and you'll find ou
Martin Vermeer <[EMAIL PROTECTED]> writes:
>> > BTW, I do not understand why this stuff is done in InsetCollapsable
>> > instead of InsetText.
>> Me either. Probably goes back to who knows when.
> Try move it and you'll find out what the reason is if any...
Very wise advice :)
Any chance to se
On Fri, Sep 05, 2008 at 11:05:32AM -0400, Richard Heck wrote:
> Jean-Marc Lasgouttes wrote:
> > [EMAIL PROTECTED] writes:
> >
> >> + // FIXME At present, these are being enabled and disabled according to
> >> + // whether PASSTHRU has been set in the InsetLayout. This makes some
> >> + // se
Jean-Marc Lasgouttes wrote:
[EMAIL PROTECTED] writes:
+ // FIXME At present, these are being enabled and disabled according to
+ // whether PASSTHRU has been set in the InsetLayout. This makes some
+ // sense, but there are other checks that should really be done. E.g.,
+
[EMAIL PROTECTED] writes:
> + // FIXME At present, these are being enabled and disabled according to
> + // whether PASSTHRU has been set in the InsetLayout. This makes some
> + // sense, but there are other checks that should really be done. E.g.,
> + // one should not be able to i
