2/15/2018 Updated.
-Add some support for switches.
-Worked on trapping more errors.
-Switched over (not completely, but for the most part) to an MDB file system instead of a .CFG file. Keep your API key handy, you'll need to re-enter it when you run this one.
-Got rid of separate files for the Readme and the making map stuff. All is in the Readme.PDF file now. See the end of that file for more info on changes.
1/21/2018 And here's a new one yet again. This one adds error checking to the map loading, and gives you a log you can look through to help find any problems.
1/20/2018 New version just put up at 4:35 pm Eastern.
Adds new codes, better handles the old ones, and A way to indicate blocked crossing.
This ones good enough it's earned itself the title of Version 1.00!!!!
It now understands tracks that send no track number (it calls them track 1, and your map should be labeled the same) as well as lowercase CP codes, which flips the on/off indication.
It handles alphanumeric track numbers as well, A - Z.
Get this one folks, it's worth it.
1/19/2018 If you're having trouble with the cfg file, download the program again and give it a try. If you still have trouble, delete the CFG file and let it make another one.
Things are moving pretty fast right now, as I get feedback from everyone. Love it!
There will be a new version sometime today, and I'll post it here when it's ready. Stay tuned!
1/18/2018 Updated the ZIP file. Added ability to flip which side Occupied tracks show up on. I found 2 out of 4 layouts I tried were backwards. Don't know why yet, but this should help in the meanwhile.
Cleaned up the config file procedures.
A few things I'm working through.
The CFG file system is not working like it should. In particular, if you load a different map it doesn't always take you where you want to go. I have it working well here this morning, and I'll update the download file later today when I'm sure I have it nailed down.
Meanwhile, if you're having any difficulties with it, just delete the included CFG file and let it make a new one.
One user is having problems with the signals apparently going to the wrong CP. That's my focus right now. I 'think' it's related to several CP's that have very similar names, but that's just a guess at this point. If that's happening to you, well, I'm working on it. Check back later to see if I have a fix for it.