Ok, I am now convinced that drawing should be done by the macro and not the template and that the current "callback mechanism" is the main reason for the problems we see when drawing nested macros _and_ for the "cursor jump problem" (as well as this strange tmacro setup in mathed_parse) Doing everything in one shot is beyond my abilities. Changes tend to "leak" from math_macro* to mathed_parse to *inset* to *iter* ... . I tried it yesterday (not just once) but had to give up finally. And it is really frustrating to waste time this way. For the next assault I'd really like to have the "big guns" already in the right position, i.e. I'd like to have MathedIter, MathedXIter and MathedRowSt doing things I understand, and a couple of helpers with a simple interface. I'll attach a tiny patch that is basically the next step on the old track of general cleanup. I think we should stay on this track for a while and try to go for the bugs when we have the right equipment... Andre' -- André Pönitz ........................................ [EMAIL PROTECTED]
