ladiko wrote:
in the case of reshacker "%comspec% /c" isnt needed, cause it doesnt produce an output to stdout. this is also the reason why there is no > %Working_dir%\whatever.log. reshacker produces a reshacker.log as output and that is read after reshacker has finished. this means we can call reshacker without %comspec%.
Yes, I know ResHacker produces its own log; as you see, there's no comspec call in my test code above. However, it overwrites rather than appending, which makes reading the log a bit difficult.
I come to wonder if this detailed log is really necessary or it's just a debugging help. After all, the most important thing is having the actions performed as designed. Still, it would help if CMDret would return some kind of error code, either for success or for failure, so we could further know what actions to take. Relying on a line of text in another application's log does not look very reliable to me.
Also let's not forget about GoRC; I haven't tested that one yet so dunno if it produces its own log and if we can rely on it for success/failure recognition. What's it useful for, anyway? Just for .rc to .res conversion? I'd rather have the script export the original VersionInfo through ResHacker, delete the original (codepage 1033), modify the export through a File parsing loop and then import it back also through ResHacker. This would take GoRC out of the picture - one less trouble.
What do you say, does that sound reasonable?
Login
Register
FAQ
Search
