Make InsetInfo active agin (aka the vengeance of the neverending saga)

This is a fixup to fc7fb6a564. The fix in there seems perfectly
correct (up to now), but for some reason, I could not refrain from
making InsetInfo not active. "What could possibly go wrong?", I heard
myself think.

Now I know: this causes an assertion error in InsetText::updateBuffer
because DocIterator::forwardPos does not enter the inset anymore.
This commit is contained in:
Jean-Marc Lasgouttes 2017-07-20 23:56:45 +02:00
parent fc7fb6a564
commit c7647eb394

View File

@ -100,8 +100,11 @@ public:
docstring layoutName() const;
///
Inset * editXY(Cursor & cur, int x, int y);
///
bool isActive() const { return false; }
/** FIXME: we would like to do that, but then InsetText::updateBuffer breaks
* on info insets. Do we need to run this method on InsetInfo contents?
* Having a InsetInfo that hides an InsetText is really annoying, actually.
*/
///bool isActive() const { return false; }
///
bool editable() const { return false; }
///