Quote:
|
Originally Posted by ger
There's no sanity checking (yet?) on the existance of eq2_recent.ini. Whether or not you run it from a command prompt or via the front end, if you don't specify a valid eq2_recent.ini file (or have one in the same location as preset_parser.exe) you'll end up parsing an empty file. I'll fix that as soon as I figure out how to get VB and VC++ to access the same file at the same time (so that the output from preset_parser.exe ends up in a text box in presets.exe)
|
It seems like it would be easiest to just have the parser in the UI/Custom Directory.
The end-user could create a short-cut and place it on the desktop.
I also doubt many people will run the program from the command prompt.
I love the new front end for the parser.
This mod has gone from complicated as hell to for the end user to, 'almost' fool proof.
I'll adjust the inctuctions to include the additional file names.
And then finalize them once you decide on the placement and installer.
Personally I keep all my mods in the /UI/Custom directory.
and will probably keep the parser in there as well.
The Custom Directorys can't be nested.
If the program is run from the custom directory, and the files are output to the same directory
you can avoid any problems with people who have there directorys named something other than 'Custom'
And the parser now does appear to give the option to output the files wherever the user prefers.