Abdelrazak Younes wrote:
Richard Heck wrote:
(iii) remember layout base class _and_ module in BufferParams. Maybe
the solution is to have a global TextClassModule along the global
TextClassList instead of having local copies of TextClass? Or
integrate the module access to the TextClassList itself?
Changes to BufferParams don't help. The problem is in CutAndPaste,
where we keep a copy of the TextClass in use with a given selection.
Yes, the copy is in fact in the temporary Buffer created in
put/pasteClipbaord. I understand that passing the TextClass is not nice
but maybe the solution is to store the temporary Buffer instead of
discarding it?
In effect, this would mean that this:
typedef limited_stack<pair<ParagraphList, textclass_type> > CutStack;
is replaced by this:
typedef limited_stack<Buffer> CutStack;
IIUC, the TextClass problem would vanish by itself, won't it?
Maybe it is worth it?
Abdel.
