Quote:
Originally Posted by Andreas Raht
It's only a problem for all our Linux users because OOTP uses lower-case letters only and on Linux it will not find files which are not 100% lower-case. On Linux, the file system is case-sensitive.
|
Gotcha. I did not realize that about Linux. I know some teams like to insert capitals into the middle of their names (IronPigs, BayBears, etc.) and reflecting that in their file names was useful to me in keeping all that straight in my mind. But making it all lower-case is obviously more critical.
Quote:
You're right, if we have a logo file with color codes, we do not need the color codes on the jerseys or caps files.
Only if the logo stays the same, but the jerseys changes and the team colors, too? Well probably that never happened.
|
Here are my concerns:
- if the logo, jersey and cap files were to all offer conflicting color codes, for whatever reason, then to whom does OOTP 'listen' to first? There's no guarantee that the desired color codes will be followed. If OOTP looks to the logo file for the color codes first, then the color codes might as well just be applied to the logo file and be done with it.
- I fear that applying the color codes to multiple files will only increase the chances of typing errors creeping in. If only applied to the one file, then not only will it help minimize this, but also make it easier to track down the error if/when it happens. (In my case,
when it happens.
)
In your example, if for whatever reason a team revamped their uniforms and colors but kept the same logo, then you would just create a duplicate of the logo and change the years and color codes accordingly in the file name. At least, that's how I would approach it.