> Actually, I think that FICS is just closing the connection
> if it does not receive any input for a certain ammount of
> time. I can't give you the pointer but it is AFAIK even
> documented somewhere. While this is no issue at all if you
> play on FICS it is a problem if you only observe a game, and
> these Grandmasters take so much time these days ;)
>
> I normally solve this by just sending a "." from time to
> time that causes input as amigious command and the timeout
> is reset. In the case in question I just left the room "to
> come right back" but it took a bit longer than expected so
> FICS hooked me off.
>
> A way to work arround this problem would be to emulate my
> "dot-sending". E.g. an "observe" checkbox that results in
> silently sending a byte to FICS from time to time to and
> dropping FICS response to stop it from cluttering the
> console.
>
I watched a game today relayed by FICS and did not get any trouble (more
than 1 hour of inactivity on my side). My guess is that the freeze you
encounter is related to a drop of connexion (Wifi, ISP). I shut down my
ethernet connexion, and Scid's UI is no longer refreshed, which seems
normal. So I have to find a workaround for that.
Pascal
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Scid-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/scid-users
