On Sun, Mar 09, 2008 at 05:05:56PM +0100, Stefan Schimanski wrote: > > Am 09.03.2008 um 16:04 schrieb Abdelrazak Younes: > >> Stefan Schimanski wrote: >>> Am 09.03.2008 um 15:03 schrieb Abdelrazak Younes: >>>> Stefan Schimanski wrote: >>>>> Hi! >>>>> Can anybody summarize the situation and issues to switch to >>>>> InsetMathMbox? >>>> >>>> This would be the solution for all text in math purpose. There are a >>>> number of bugs related to the fact that text in math are not real Text >>>> object. >>>> >>>> Last time I tried, InsetMathMbox needed some work in order to be >>>> complete; essentially metrics and drawing code. >>>> >>>> Having this in 1.6 would be a great step forward. >>> I am playing around with it. The main problem right now is that Text >>> objects need a buffer object assigned, e.g. for Text::write. Some math >>> macros use mbox insets, but they are buffer independent (= global). I >>> just tried to create a dummy Buffer for those cases, but get some crashes >>> now. >> >> No, you should instead implement Inset::setBuffer() in the proper math >> inset (the one that contains the InsetMathMbox). > > I am not so sure this exists at every moment. I talk about math macros, the > globals ones. There is a global table for that. Maybe one has to think > about how to store them without the need of a buffer.
They should be per-buffer. Having them global is a long standing bug... Andre'
