>>>>> "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
Martin> I suppose the speed-up patch exposed this bug, i.e., that a Martin> tabular cell with a non-fixed width does not transmit a Martin> sensible mi.base.textwidth to any textinsets it contains. Now Martin> that we use this (or the derived maxwidth_) to decide how much Martin> space to give to a Wide inset, this becomes visible. And do you think it would be too difficult to fix the real cause? Martin> Attached the tabular background patch for 1.4 (still not Martin> applied) This part is OK. Martin> with code added to fix this problem (first chunk). The code is Martin> ugly (deciding how much space the stuff in the cell needs, and Martin> then giving a little more) but seems to do the trick. There is still something wrong: in an empty tabular, if I insert a note inset, it the cell will be larger than what the inset needs. if I begin to type inside the inset, the extra space remains until some point where it brutally disappears. What seems to happen actually, is that the inset is drawn with the button above, but its width is computed as if the button was on the left (as it should). The point when the extra space disappears corresponds to the situation where the button should indeed be on top. JMarc
