Andre Poenitz wrote: > Hm, I think ParIterator + InsetList::iterator should suffice. > > The problem with the InsetText hidden in InsetCollapsable is that this > is not an inset, but some implementation detail which should be > completely invisible.....
I do not agree. What is it that forces conceptually an inset to be owned by some paragraph? Why insets cannot own insets? Think about tables for instances. IMO we should standarise the access of insets owned by insets, that's all. Regards, Alfredo.
