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). even now is editation and movement with outliner significantly
slower.
OK I can reproduce a slowdown in debug mode when the slide is set to the
maximum. No slowdown in release mode though. I always let the slider to
the minimum personally but I can understand that the flashing toc reset
is annoying when the slider is set to the maximum. One simple solution
would be to disable toc update until the tree is completely reconstructed.
Abdel.
