impishfae
Joined: 19 Jun 2006
Posts: 125
Location: Australia
|
 Posted: Thu Aug 03, 2006 8:52 am Post subject: Changes to parsing errors |
|
|
Once a fortnight there seems to be a post in the 'questions' area with the oh so FAQ "My log doesn't parse, it just returns a
| Code: |
| Nothing in the log matched the parse patterns |
error"
I'm not sure on the full set of causes for that error, but the only thing I've seen is a nonexistent member list.
So, *before* we parse a log file, can we do a check:
= Do we have access to a member list:
- Are we connected to a server and if so, is its member list empty
- If we're not connected, is our local member list empty
- If not connected, no local member list, is our 'add unknown members' on...
= If member list exists, carry on parsing
= If no member list available, pop up a dialog box:
"No member list found. The log parse will fail. To correct this, you can either connect to an EQDKP installation with a member list, populate your local list manually, or turn on the 'automatically add unknown members' configuration option." or something.
Alternatively, and much quicker, just change the text on that error dialog to say "nothing in the log matched the patterns. The most likely causes for this are that your member list is empty. You will need to populate it first either by connecting to a server, adding members manually, or using the 'automatically add unknown members' configuration option and reparse the file" so that the user has a better clue on the situation.
And yes, this is a 1.4.1 idea.  |
|
