|
|
Senior Member
Join Date: Jan 2013
Location: Rochester, MN
Posts: 1,516
October 8th, 2015, 05:15 AM
|
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
|
|
|
Senior Member
Lone Wolf Staff
Join Date: May 2005
Posts: 8,232
October 8th, 2015, 12:03 PM
|
Quote:
|
|
#32
|
|
|
Senior Member
Volunteer Data File Contributor
Join Date: Jan 2010
Location: Chicago, IL (USA)
Posts: 10,729
October 8th, 2015, 03:41 PM
|
Quote:
  
Hero Lab Resources: Pathfinder - d20pfsrd and Pathfinder Pack Setup 3.5 D&D (d20) - Community Server Setup 5E D&D - Community Server Setup Hero Lab Help - Hero Lab FAQ, Editor Tutorials and Videos, Editor & Scripting Resources. Created by the community for the community - Realm Works kickstarter backer (Alpha Wolf) and Beta tester.- d20 HL package volunteer editor. |
|
|
#33
|
|
 |
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
