On 30/09/2008 08:47, Abdelrazak Younes wrote:
On 30/09/2008 00:11, Pavel Sanda wrote:
Richard Heck wrote:
i tend for 3. solution but would like to hear your opinions.
I prefer 2, kind off. This can be done completely in the frontend
using
simple string comparison techniques and session management. Each
time a
toc reset is requested, save in the session the strings of all the
nodes
that are not collapsed. When the model is reset, restore uncollapse
all
nodes that present the same string. This method will not be 100%
correct
but it will be just fine for most cases because only the current code
tipically changes, all others nodes keep the same strings.
I'd second that. And I'd think it wouldn't be that hard, actually.
the obvious disadvantages of 2:
- it would slows the current editation even more (note that current
trunk
needs 12 (!) reset calls after 1 character change in section (some
sample
in userguide).
There should be only one. And there was only one last time I touched
at this.
I just checked and there is only one reset of TocModels. I guess you are
talking about the individual TocModel reset? Of course, there is as much
reset as there are models.
Abdel.
