Chris Millsap db3ffab832 Possible fix to issue #1951 ... (Code formated to be submitted for pull request) -- Indentation was off. SAME FIX AS BEFORE When two instances of Torque3D are running on the same network, one as a hosted server and the other as a client, the client is unable to connect to the server. The program now can open a socket. This was obviously a typo. To find the error I just searched for keywords containing socket, open, open socket, and opensocket till I found the correct file. The other error was in how the program processed “non fatal” errors. I just outputed the error to the main console and devised that the socket should not be closed for a WSAEWOULDBLOCK error 10035 "It is normal for WSAEWOULDBLOCK to be reported as the result from calling connect on a nonblocking SOCK_STREAM socket, since some time must elapse for the connection to be established." Read about the WouldBlock error: https://msdn.microsoft.com/en-us/library/windows/desktop/ms740668(v=vs.85).aspx Use of dbgSetParameters ( port , password ): http://docs.garagegames.com/tge/official/content/documentation/Reference/Console%20Functions/TorqueScript_Console_Functions_2.html#dbgSetParameters_.28_port_.2C_password_.29		2017-04-11 14:51:29 -04:00
..
bin	style.css changes for Project Manager modules	2013-05-01 17:08:43 -04:00
lib	squish update (primarily to add additional formats for later usage)	2017-03-30 20:44:35 -05:00
source	Possible fix to issue #1951	2017-04-11 14:51:29 -04:00