I have been able to reproduce the 'diagonal lines in table' drawing issue (which was one of two for which 'remove update()' got thumbs down) with 1.3.x.
So this is nothing introduced by the 'remove update' patch but some old issue that has been somehow covered so far (probably by the excessive updates and redraws). The other issue with this patch I know of is another drawing issue when table cells (sometimes, in nested tables) do not get their proper size on loading but only after the first time the cursor is put in there. This is, although "really not nice", strictly cosmetically and probably fixable by the same degree of excessive calls to metrics() as used now with update() [But I do not want to do this for obvious reasons] Tables remain usable with the patch as everything works in proximity of the cursor. So I propose to re-evalutate the 'remove update' patch as this removes quite a bit of "non-intuitive" code from the remaining mess. [The argument goes like this: A: 1. update() does not work as seen by the 1.3.x diagonal lines 2. nobody understands it anyway 3. update() is the core reason for a few owner_ back-pointerage 4. ... which makes the core a mess as such lead to non-trivial copy and assignment in insets. B: 1. metrics()/draw() conceptually works in theory 2. there are no known technical limitations 3. it works in practice as shown in math 4. it has recently simplified some code in insets/* A, B -> let update() die even if there is an intermediate set back like the mentioned drawing problems.] Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson or B. Franklin or both...)
