Quote:
|
Originally Posted by Jaxel
Ah... thats a pretty neat idea.... but alas, I am OCD! Redundant data controlling violates the whole theory behind the way I program. And I wish for Ger to program a way to set the volume settings with the parser program... it sorta kills two birds with one stone.
|
I understand. Things have calmed a bit, but orignally it appeared there were going to be a growing number of preset-parsers out there.
Version control was going to be a mess, and you can image it could be more confusing for users to have to select which version they want each time they ran the thing.
It seemed to me. for the end user the easiest solution was to have a single parser.period.
That way the authors have complete control of the styles or location of there buttons, and the file the perset-parser spits out, is basically invisible.
Seriously you talking about VERY LITTLE code to have one control, activate another control.
Compared to the amount of work it took for Ger to create the parser, and maintain it. Which will be futher complicated by additional versions.
as far as your programming style.
It seems to me that the method I present is much more robust and will work for everyone.
Compared to one version for one mod.