On Mon, Dec 03, 2001 at 02:14:40PM +0000, John Levon wrote: > > Can anybody please explain me the concept of "inset locking"? > > I think of it as focus.
Ok. > An inset that is locked demands that many operations should be requested > of it first. For example, updates on insets. Does anything needs this kind of focus that is _not_ in immediate neighbourhood of the cursor? If so, why isn't the cursor used for such things? > The top-level is bv->theLockingInset(). For example, entering the > non-red-box part of a top-level insettabuler sets the tabular as the > locking inset. So if I look at all the insets as some kind of tree, the "interesting spot" is someway down a path from the root to a leaaf, and bv->theLockingInset() is some kind of short cut on that path? > All "containing" insets each have a the_locking_inset member as well - > this indicates the contained inset that is locked, if one exists. One > example would be a red-boxed cell - here an InsetText is > InsetTabular::the_locking_inset, and (I think) bv->theLockingInset() is > the InsetTabular. ... and introduces some kind of "back reference" which is usually a pain to maintain and to get right? > The stuff is confusing ... That's why I am asking. Andre' -- André Pönitz .............................................. [EMAIL PROTECTED]
