Don't touch it. Things blow up.

[SilverNexus]

When loading my trunk crossfire client in Ubuntu 10.10 (updated it to r18432 yesterday), I accidentally clicked on the client window before the metaserver window fully loaded.
As a result, the metaserver window did not load at all.
So, I force quit it and loaded it again, being careful not to click on the client window too early.
As a result, it worked perfectly.
Am I coming to the correct conclusion, or has my client somehow not updated when it was supposed to, and this is really already fixed?

[karl]

The crossfire clients that are simply ./configure try to access the internet. If no internet connection, the code seems to trytrytrytry..... without an usable usleep value to prevent it eating up the cpu. As a result, the client does not respond at all and has to be killed like

Code: Select all

kill -9 `pidof gcfclient-MY_HARRY`

.
Somehow this leaves a bad impression .

If a local crossfire server is running , these clients autoconnect to it, but after saving on a bed to reality, the internet lookup with the unresponding GUI and high cpu usage, that would be somehow dangerous to the hardware and stability of the operating system on a single core machine , occurs again .

Q: Why using the gui without connecting first ?
A: To change the *.glade layout .