> I also had a thought about the memory footprint for insettabular and the
> only possible solution I came up with to minimize it is to store the data
> inside a single paragraph as we did before. But do we really want to do
this.
Jürgen,
why not create a super class to do just this. TabularMemory or something?
> One idea also is to change the Tabular-Layout to do stuff like in all other
> Layouts (with ROAC buttons), would this be a good move? (This is not so
simple
> as then I would have to look at all the modifications we did with the
tabular
> layout and call all the TabularFeatures calls in one block. Any idea here to
> do this in a clean manner is welcome!
Easy! Create a temporary params struct which is changed by the dialog. On
apply(), compare the contents of the struct to those of the inset.params().
Only update the changes.
Do you really think that this is necessary? Admittedly, it's inconsistent to
have two different types of dialog (your's and all the others!), but your
popup is quite intuitive to use. On the other hand, having an Apply button
would mean minimise redraws of the table which seems to be quite important...
Angus
