Jean-Marc Lasgouttes wrote: > Could this be an artefact of the autoOpen feature (where insets are > both open and closed at the same time)? > > Do you have an easy way to disable autoopen and see whether this helps?
Yes (commenting out insetcollapsable.C: 132). This changes the situation insofar as the cursor does not enter the closed collapsable anymore. However, it still crashes, now even *with* my fix, although it doesn't crash directly on the cursor down action, but on the next action following. So I guess autoOpen is not to blame, albeit it probably hides another hidden problem. Jürgen
