On Wed, 18 Apr 2001, Juergen Vigna wrote:
> In my profile the top was GetCellInset() and I thought probably we should
> have some sort of iterator over this (but I don't know how to realize one
> which would work), maybe this would be faster.
yes, this is what I get too ...
> > p.s. can't at le
On 18-Apr-2001 John Levon wrote:
> Time for me to go back to the code then ... fwiw on a 27x27 table, the getMaxWidth
> of InsetTabular and its children appeared right at the top of the profile ...
In my profile the top was GetCellInset() and I thought probably we should
have some sort of itera
On Wed, 18 Apr 2001, Juergen Vigna wrote:
> On 18-Apr-2001 John Levon wrote:
>
> > just a quick question - am I right in thinking one of the factors
> > in tabular's slowness is the constant searching through the entire
> > tabular for a cell inset equal to the one being looked for in GetCellIns
On 18-Apr-2001 John Levon wrote:
> just a quick question - am I right in thinking one of the factors
> in tabular's slowness is the constant searching through the entire
> tabular for a cell inset equal to the one being looked for in GetCellInset ?
The search is only done if the_locking_inset !
just a quick question - am I right in thinking one of the factors
in tabular's slowness is the constant searching through the entire
tabular for a cell inset equal to the one being looked for in GetCellInset ?
Also, what's the resizing algorithm ? Is it similar to that described
for HTML tables
