Version: v0.7 (using KDE 3.0.9 (KDE 3.1 RC1)) Installed from: compiled sources Compiler: gcc version 2.95.4 20011002 (Debian prerelease) OS: Linux (i686) release 2.4.19 Start a local server with another port than the default Go back to the new game dialog Go the the server settings --> default port number (but the server is listening on the right number)
*** Bug 55752 has been marked as a duplicate of this bug. ***
This is some kind of KGame/QSocket bug. It's a bit more complex, so it will require some time to be fixed. Problem is that QSocket is asynchron so when connectToHost() returns it is not yet connected. KGame does not yet use the connected() signal unfortunately. Only after that signal has been emitted QSocket returns a valid port number. The workaround is to store the port as a global static variable in the startup widget once we start to connect, but I want to commit that fix only once I have a real fix for this (which requires patching libkdegames) CU Andi
I have now committed an update to both, boson and KGame which fixes this bug. To fix the asynchron-problem we can easily use signalClientConnected(). KGame::port() in a recent KGame version will provide the correct port, for older KGame versions we use a hack (thanks to Qt, which allows that :)). CU Andi