Joost wrote:
> What Scid could do is produce a warning when you try to leave scid
with games in the clip base (like it warns you when you leave scid
with an unsaved game in a regular base). Personally I do not feel the need
for such dialog, but I have only 1
opinion on this :-)
Yeah... there ~is~ a little problem with losing games to the clipbase.
I guess is just another part of Scid's learning curve.
Other ideas/fixes i can think of is to automatically save the PGN of last game
edited
to a $HOME/.scid/data/last, alter clipbase to be disk resident in
$HOME/.scid/data,
or rename "clipbase" to "temp base" or something better reflecting it's
transciency.
Perhaps Joost's suggestion is best, with an added option "Confirm Clipbase
Changes on Exit", which can be deselected once user has become familiar withÂ
how it all works.
Steve
------------------------------------------------------------------------------
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world?
http://p.sf.net/sfu/oracle-sfdevnlfb
_______________________________________________
Scid-users mailing list
Scid-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/scid-users
