> > BTW, with my patch, big operators are now stored using symbolinset and
> > not bigopinset. The bigopinset inset should probably be removed. There
> > is still a problem that the bigoperators don't have displaylimits
> > positioning of super/subscripts but it shouldn't be hard to fix.
>
> The handling of super/subscripts is the very reason for the existence of
> that inset. I'd rather have a proper inset for that instead of "if"s all
> over the place...
The only difference I see between MathBigopInset and MathSymbolInset is
that the former return true in isScriptable(), and the latter returns
false;
So why not have
bool isScriptable() {
return sym_->type == BIGOPERATOR;
}
in MathSymbolInset ?
