The client should display network connection status to
the user, preferably in the chat window. In particular,
connection failure (initially or during the game)
should be reported.
CliNet has always tried to print out errors connecting to
the chat window. However, in recent revisions, the chat
window is not initialized until after the client connects.
Ergo, the error messages printed to the chat box aren't
getting displayed.
Upon a failure to connect CliApp now sends the error
message to BOTH the chat box AND the java console. If we
think that it's really important to display errors that
are more in-your-face (which I think it is) then we'll
need to make an effort to initialize the chat box sooner.
Personally I think we should add a printErrorFatal method
to CliApp which prints out really bad errors, like unable
to connect or connection lost, to a pop-up window or
something like that.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=437080
CliNet has always tried to print out errors connecting to
the chat window. However, in recent revisions, the chat
window is not initialized until after the client connects.
Ergo, the error messages printed to the chat box aren't
getting displayed.
Upon a failure to connect CliApp now sends the error
message to BOTH the chat box AND the java console. If we
think that it's really important to display errors that
are more in-your-face (which I think it is) then we'll
need to make an effort to initialize the chat box sooner.
Personally I think we should add a printErrorFatal method
to CliApp which prints out really bad errors, like unable
to connect or connection lost, to a pop-up window or
something like that.
Logged In: YES
user_id=4941
I agree, but I'm not sure how much work it is to do a popup.
Eric, can you look into this? Also, how hard would it be to
draw the chat box earlier?