Quote:
|
Originally Posted by fredbass
I've got an idea. If you put out another version of Commander, just make it so a rollback is automatically done no matter what.
Issue solved.  |
Ah, but what if you want to generate a Personnel File that picks up the details of the changes SH3Cmdr made? For example, Flotilla name changes prior to Jan 1940? I always like to generate a Personnel File before rolling back as it provides the most accurate snapshot of my career at that point.
Anyway, to be honest, when I first started on SH3Cmdr back in April 2005, I didn't expect it to be as popular as it has become. I also didn't expect the humble first version to expand to include what it does now. And more importantly, I didn't expect SH3 to evolve the way it has. In other words, if I had my time again, I would develop SH3Cmdr *totally* differently - the concept of rolling back would be nothing like it is now. Indeed, SH3Cmdr would employ a method which I use in my commercial software, which has none of these rollback issues.
To that end, any changes I make to SH3Cmdr now are really only bandaids - and I hate bandaids. Having SH3Cmdr auto-roll back could be done reasonably easily, but it would go against programming principles. And to be done right would require a total rehaul of SH3Cmdr...something which simply isn't an option for me.
I think the current solution is the best compromise...at least for me.
