Re: [Scid-users] Some Bugs/Inconveniences

[Alexander W. <a.w...@ph...>]

Pascal Georges wrote:

Hi!

>            - Once I start an older version of Scid (3.6.26 e.g.) the
>              current cvs ignores my setting to use Classic mode and
>              comes up in docking mode. This seems to overwrite some
>              parts of the configuration by other defaults btw.
> 
>         Quite logical.
> 
> 
>     What do you mean by "quite logical"?
> 
>     3.6.26 uses the same config as 3.7, why does windowing mode switch
>     just cause an older version was started and why should 3.7 overwrite
>     parts of its own config just as a 3.6.26 was started in between?
>     Shouldn't 3.7 just use the config of 3.6.26 and only append new
>     settings if there were one?
> 
> When you start an older version, config file is overwritten. Then the 
> new version goes back to its default settings for values that are not 
> present in older version, and docked is on by default.

Ah. Hm. Well. I'll have to disable it in this case each time
or get Scid to leave out autosaving of options. But now the
classical window settings seem to be stored separately so
they come up nicely again. Therefore it's just a restart.
(I feel it would be more logical if the default would be the
classical mode, but this is another story ;)

I also played around with the docking mode, as it was on by
default again. My usual window setup would be represented by
something like

set ::docking::layout_list(1) {{.pw vertical} {TPanedwindow {{.pw.pw0 
horizontal} {TNotebook .tb1 .fdockpgnWin} {TPanedwindow {{.pw.pw0.pw3 
vertical} {TNotebook .nb .fdockmain} {TNotebook .tb4 .fdockbaseWin}}} 
{TPanedwindow {{.pw.pw0.pw5 vertical} {TNotebook .tb6 .fdocktreeWin1} 
{TNotebook .tb2 .fdockccWindow} {TNotebook .tb7 .fdockanalysisWin1}}}}}}

I stored this to slot 1, but Scid crashes upon startup once
it tries to build this up again. (No, it does not really fit
on the screen in docking mode at 1400x1050, some windows are
too thin. I just tried to see if it would be possible at
all. ;)

In a more simple layout (inspired by some well known GUI)

set ::docking::layout_list(1) {{.pw vertical} {TPanedwindow {{.pw.pw0 
horizontal} {TPanedwindow {{.pw.pw0.pw6 vertical} {TNotebook .nb 
.fdockmain} {TNotebook .tb7 .fdockbaseWin}}} {TPanedwindow {{.pw.pw0.pw3 
vertical} {TPanedwindow {{.pw.pw0.pw3.pw8 horizontal} {TNotebook .tb9 
{.fdockpgnWin .fdocktreeWin9}}}} {TNotebook .tb2 {.fdockanalysisWin1 
.fdockanalysisWin2}}}}}}}

the sizes of the docks seem not to restore properly. E.g.
the database switcher was scaled to show only the height of
the icon boxes, so that I can get an almost full size board
but it was restored much to large vertically. As this layout
contains two analysis tabs: wouldn't it make sense to halt
engines if they are restored to a dock upon starup?

BTW: Would it be sensible to store window layouts in a
separate file? This would e.g. allow to exchange them
easily. Wouldn't it make sense in case an engine is loaded

BTW/2: I think I have added all stuff necessary to get
Correspondence Chess and Input Engine console to work as
docks as well. If I get it right I should just use
::createToplevel and ::setTitle instead of the direct calls
to wm, while I should leave the usual calls for dialogues.

-- 

Kind regards,                /                 War is Peace.
                             |            Freedom is Slavery.
Alexander Wagner            |         Ignorance is Strength.
                             |
                             | Theory     : G. Orwell, "1984"
                            /  In practice:   USA, since 2001