From: Michal R. <mr...@kd...> - 2007-09-12 08:59:34
|
Marcin Kasperski, =C5=9Broda, 12 wrze=C5=9Bnia 2007: >> * Tree window is not open immediately, so sometimes user >> doesn't know what is happening >This probably depends on the database size and machine speed, I >am recently using splitted databases so I did not observe such >problem. But maybe some progress window would make sense. Before, Tree window was always shown first and tree data were computed late= r.=20 Probably it can be done the same way here. >> * It is easy to get wrong tree for current database if there >> is only one open >??? I will try to find a way to reproduce it. >> There is one more feature request which is still not possible >> with current setup: to easily get opening tree for given >> player. You need to find his games, copy them to clipboard, >> switch to clipboard and create tree from there >Ahh, this is feature which Chess Assistant calls 'prepare for >your opponent'. Fairly useful when one wants to check what is >the future opp playing. In case of scid one could approximate it >if it was possible to restrict the tree to the filter (although >this feature is useful enough to be given own name and menu >pos...) Right. Limiting tree to filter was my old suggestion, but Shane refused to= =20 implement it then. This can be used to check, for example, opening tree onl= y=20 for strong players or only for games with ECO code matching the opening we= =20 are studying (thus speeding up tree calculation) =2D-=20 Michal Rudolf |