On Mon, Dec 03, 2001 at 04:04:38PM +0100, Juergen Vigna wrote:
> > inset->updateInset(some_other_inset)
> > AND
> > inset->updateInsetInInset(some_other_inset)
> > but that's just an implementation detail I think. I would prefer just to
> > hand off updateInset(some) to the locking inset and have done.
>
> #:O) well I really had to smile with the above code. See we call the
> function updateInsetInInset(some_other_inset) because it's just what it
> does. You can also call it updateInset(some_other_inset), but IMO that the
> actual name actually does tell us better what we do there!
>
> Maybe you confuse BufferView::updateInset with UpdatableInset::updateInsetInInset.
> Could that be?
Actually, I've confused myself by thinking that inset->updateInset() exists,
when in fact it is text->updateInset(). What I couldn't work out was why
we were passing "inset" in this case - the answer is that it's text->updateInset
and it needs to know the inset ...
regards
john
--
"Faced with the prospect of rereading this book, I would rather have
my brains ripped out by a plastic fork."
- Charles Cooper on "Business at the Speed of Thought"
