Re: [Scid-users] Tree windows

[Michal R. <mr...@kd...>]

2010-03-22 17:33:18, Alexander Wagner:

>> 1) Sometimes it get stucked leaving me with a waiting mouse icon
Agreed, specially when you use mouse wheel to scroll through the game.

> > When the user want to move back or forward and the tree windows is still
> > busy:
> > 1) cancel the current search and starts the new one
> > 2) schedule the new search but ends the current search too
> > My preference went to 2, considering that so results are computed and
> > cached.
I used first approach in ChessX. I agree with Alexander that it is more user 
friendly (less delay).

> Still, there might be an issue here with how the fill cache function
> works. I don't think that there is a side effect but you should be
> careful not to break it. 
If the cache is updated only after full, successful search, no break will 
happen.

BTW. is it possible to enable 'Auto-Save Cache Buffer" option by default? Now 
it seems the cache content is lost when one forgets to set it.
As we already have the option to set cache size, I suggest to just drop the 
option and always save cache (letting user to set a very small cache if he is 
concerned about disk space).

> Some in
> the opening where the tree is very helpful and should be updated, some
> in the middle or endgame where ther're just no games anymore. Do you see
> an automatic way to prevent Scid from continually updateing the tree here?
One idea is to store ply number of the last non-unique position in each game.
But, this will require quite expensive indexing when database is modified.

-- 
Michał Rudolf