Alfredo Braunstein wrote:
Andre Poenitz wrote:
That might be enough. But it's not clear to me if this causes problems
with cut and paste.
Sure there will problems, but right now we already have special handling
for e.g. and three hundred inset function or so taking a buffer
And what's the real problem with that? If DocIterator had a buffer_ member,
we could just pass around a DocIterator & to inset functions that need the
parent hierarchy.
Unfortunately, that isn't sufficiently general for this case. It's the
InsetCommandParams that need to know about the buffer, and they can be
created and used independently of any Inset.
Richard
--
==================================================================
Richard G Heck, Jr
Professor of Philosophy
Brown University
http://frege.brown.edu/heck/
==================================================================
Get my public key from http://sks.keyserver.penguin.de
Hash: 0x1DE91F1E66FFBDEC
Learn how to sign your email using Thunderbird and GnuPG at:
http://dudu.dyn.2-h.org/nist/gpg-enigmail-howto
