AndersI wrote:Hah, it must have fallen under the radar pretty fast as *I* never forget anything. No Sir
Oh! There you are! Sorry, I didn't see you sitting over there.
wallyweb wrote:is there any way to have the program write the name of the patch version used to create the new/updated cfg?
Do you mean adding a comment inside the .cfg file? What use would you have of this? As it is now,
TTDPC informs you about the version of the TTDPatch it's set up to configure. And what would be the 'creating version' of a cfg that's been in use since Stonehenge and just been updated with new switches? Or are you just interested in the
highest version number that's been involved in the cfg?
... Just a line at the top of the cfg something like "// r1777" to show which patch
TTDPC used to create it. Perhaps better yet, in view of our comments below, a text entry field where the
TTDPC user could enter a comment line. This could even be used by a coder or a dev who is troubleshooting a grf or the patch.
If the change log for the latest nightly does not imply that a switch has been removed or newly created I tend not to touch my ttdpatch.cfg files.
I knew it! Stonehenge is not an ancient astronomical tool but rather an ancient PC system for our ancestors to play TTDPatch!
I suppose
TTDPC isn't perfect when you want to go back and forth between versions - the simple fix for this is to keep the full TTDPatch installations in separate folders, each with a cfg of their own, each with a
TTDPC shortcut of their own. That way you never need to go
back in the cfg (it
must be best, as that's how I do it...).
On a related note, for having multiple patch cfg's, being able to save with an alternate name would be handy.
On an old PC such as mine there isn't much room left for a second installation. (That's also my excuse for not having OTTD yet
) Well, I do have my PC cut up into a bunch of virtual drives so I suppose I could entice PartitionMagic to rob Peter to pay Paul. Actually, I like to have separate patch cfg's for each train set as they occasionally require different settings. I keep a folder of uniquely named patch cfg's and set my shortcuts to find them.
Code: Select all
G:\MPS\ttdpatchw.exe -C G:\MPS\patchcfg\ttdpatchnars.cfg -Xn G:\MPS\1NARS\narsvalgrfw.cfg
Saves on valuable hard drive space you know.
I suppose you'd like to be able to
open alternately named files, too?
You DO understand!
I'm not so keen on this. TTDPC isn't an config file organizer, it's a tool to edit the current TTDPatch configuration. Maybe I could write an organizer too, but I think there already exists one (or more). I'm not playing many different configurations at the same time myself, so the problem hasn't shown up for me.
I most definitely do not consider
TTDPC a file organizer. Its a TTDPatch configuration file parser/editor with a save function. I'm suggesting an enhancement to the save function ( "Save As") as well as a comment entry line.
As mentioned before, these are merely suggestions.
TTDPC is excellent as it is. Thanks for looking at these.
Nothing good or new ever happens without a bit of dialogue.
I 've got a PIII and it can see up to 127GB HD. But if OS can see the rest you don't care/don't need to upgrade the BIOS (Not that you could, PC companies care to make money not to help customers. Same applies to my PC (COMPAQ). No BIOS update.) You first install the OS in what space your BIOS can see and then under the OS use the rest Gigs to create other partitions. (XP without SP1 (does anyone use XP without SP1? 
) does not recognize hard drives over 128 GB as they don’t support 48-bit LBA addressing (Windows 95 doesn’t support >32 GB, and Windows 98 doesn’t support >128 GB). Buy a new HD! 