Senior Member
Join Date: Jan 2013
Location: Rochester, MN
Posts: 1,517
|
While the error message should be improved to at least suggest some course of action, the deeper issue (to me) is why a single check at startup locks the entire run of the program into not being able to talk to the server. Instead of locking out with an opaque error message, say you couldn't talk to the server and try the prerequisite(s) again if/when the user tries to log in.
(I had much longer versions of this post earlier this week, but this is enough backseat software design. :) Last edited by Parody; October 8th, 2015 at 06:57 AM. |
#31 |
|
|