Quote:
|
Originally Posted by JScones
The easiest fix is for you, and anyone else writing to the log file, to write a non-zero number to the "Type" key. I can then add one line to SH3Cmdr to ignore any entry where Type <> 0.
|
This won't do, as Sh3 will not display entries with Type <> 0
Quote:
|
Originally Posted by JScones
But, whilst this workaround is very simply, I won't be in a position to release an updated version of SH3Cmdr for a few weeks at the earliest (although I could possibly provide just the updated SH3Cmdr.exe file to anyone who's using SH3Gen).
|
I' say it would be already very nice if we could have a fix with the next version of Sh3Cmdr, whenever it's released. Sh3Gen is still Beta, and the reason is to identify / solve this kind of problem. In any case I'm glad that you offer your help to make the two apps compatible.
I'm also indebted to Ref for being the first one to report this problem. I have offered him my help for a manual fix, which is in fact pretty simple. Every one else with this problem is invited to contact me for the manual solution.
Quote:
|
Originally Posted by JScones
And also, this fix (presumably) won't exclude the extra text from displaying in the relevant Patrol Log summary displayed in SH3 - is this an issue (I assume SH3 will still present the entries OK, but is this what you/users really want)?
|
Yes. That's why I will have to offer a 'remove Sh3Gen entries from patrol log' function anyway. It could be run after the patrol, before Sh3Cmdr is used. I just don't want it to be a must. It should be no problem if the user doesn't mind the extra entries.
As far as Cmdr is concerned, I think the check for entries
without EntryTitle might be better.
Something like:
try
{
EntryTitle = ClgFile.Read("Log entry " + index, "EntryTitle");
//proceed with reading the entry
//...
}
catch
{
//EntryTitle doesn't exist, so entry will be skipped
}