Talk:TADDaemon
From TrainzOnline
(Difference between revisions)
Jamesmoody (Talk | contribs) (Blanked the page) |
(rv vandalism, page and message blanked inappropriately) |
||
| Line 1: | Line 1: | ||
| + | ==Flawed design== | ||
| + | If this is true about the shut-down, you need to modify it so ''there is a busy indication'' visible in widows and a popup reminder message requiring a Button click to leave Trainz screens... telling the user to not shut down window until and unless the TADDaemon tab closes is good programming. Leaving people guessing when they may need to reboot is shitty programming. | ||
| + | * Another case of shitty programming: Both ASSETS.* files were killed and Zero length on my tower July 3rd by an unexpected line surge, causing a hard computer shut down. Please note, the CM 3.3 version running had been up CONSTANTLY for over 36 hours, with no activity asked for or requested. I never got back to look at it. IT WAS TOTALLY IDLE AND '''''should never have'' updated anything!''' | ||
| + | |||
| + | WHAT USE IS A BACKUP THAT IS OPEN AT THE AME TIME AS A SOURCE/USE FILE! | ||
| + | # You should start Trainz renaming Assets.bku to a safe name | ||
| + | # COPYING the current unchanged Assets.tdx (ONLY ONCE IT'S '''about to be''' CHANGED!) to the Assets.bku name in the cache. | ||
| + | # Then play with Assets.tdx and leave the .BKU alone. | ||
| + | You programmers need to leave windows files with the right time stamps in general. There is no excuse to be affecting modification time WHATEVER unless CM is writing the file with an auto-fix. CM doesn't do that and shouldn't outside of Hot fixes and service packs. // <b>[[User:Fabartus|Fra]]</b><font color="green">[[User talk:Fabartus|nkB]]</font> 14:05, 5 July 2013 (EST) | ||
Revision as of 11:55, 20 August 2013
Flawed design
If this is true about the shut-down, you need to modify it so there is a busy indication visible in widows and a popup reminder message requiring a Button click to leave Trainz screens... telling the user to not shut down window until and unless the TADDaemon tab closes is good programming. Leaving people guessing when they may need to reboot is shitty programming.
- Another case of shitty programming: Both ASSETS.* files were killed and Zero length on my tower July 3rd by an unexpected line surge, causing a hard computer shut down. Please note, the CM 3.3 version running had been up CONSTANTLY for over 36 hours, with no activity asked for or requested. I never got back to look at it. IT WAS TOTALLY IDLE AND should never have updated anything!
WHAT USE IS A BACKUP THAT IS OPEN AT THE AME TIME AS A SOURCE/USE FILE!
- You should start Trainz renaming Assets.bku to a safe name
- COPYING the current unchanged Assets.tdx (ONLY ONCE IT'S about to be CHANGED!) to the Assets.bku name in the cache.
- Then play with Assets.tdx and leave the .BKU alone.
You programmers need to leave windows files with the right time stamps in general. There is no excuse to be affecting modification time WHATEVER unless CM is writing the file with an auto-fix. CM doesn't do that and shouldn't outside of Hot fixes and service packs. // FrankB 14:05, 5 July 2013 (EST)
