string const iname = insetName(lyxCode());
LYXERR0("Inset: " << this << " LyX Code: " << lyxCode()
<< " name: " << iname);
- s << "LyX Code: " << lyxCode() << " name: " << iname;
+ s << "LyX Code: " << lyxCode() << " name: " << from_ascii(iname);
LATTEST(false);
throw ExceptionMessage(BufferException,
from_ascii("Inset::buffer_ member not initialized!"), s.str());
}
-void Inset::forOutliner(docstring &, size_t) const
+void Inset::forOutliner(docstring &, size_t const, bool const) const
{
}
// if the derived inset did not explicitly handle mouse_release,
// we assume we request the settings dialog
if (!cur.selection() && cmd.button() == mouse_button::button1
- && clickable(cmd.x(), cmd.y()) && hasSettings()) {
+ && clickable(cur.bv(), cmd.x(), cmd.y()) && hasSettings()) {
FuncRequest tmpcmd(LFUN_INSET_SETTINGS);
dispatch(cur, tmpcmd);
}
// Allow modification of our data.
// This needs to be handled in the doDispatch method of our
// instantiatable children.
- // FIXME: Why don't we let the insets determine whether this
- // should be enabled or not ? Now we need this check for
- // the tabular features. (vfr)
- if (cmd.getArg(0) == "tabular")
- return false;
flag.setEnabled(true);
return true;