Final Tally

[golden delicious]

And here's the TOAWpeek output dumped to a text file and then opened in Excel (colon delimited).

[golden delicious]

These screenshots speak for themselves. The only difference is that TOAW hides any equipment which doesn't appear as authorised strength in the OOB, whereas TOAWpeek here shows that an equipment type existed in a previous version of the scenario, had replacements assigned for it, and was then removed. Those replacements have been building up for 40+ turns but don't go anywhere.

This is potentially an extremely useful tool for a designer, AAR writer or just curious player. It was a LOT easier to use than the length of this thread would imply. I take my virtual hat off to kmitahj for this.

[kmitahj]

Thanks for sharing your results. That means it should be usable on Win7 platform too (with stipulations as described above) thought Win8 may be still disputable I think.

Numbers seem to look good but you right that ToawPeek is usually a bit more liberal deciding which equip. lines to print. Basically it prints a line for any equipment for which any of "OnHand", "Rate", "TotalsC" or TotalToe" values is non-zero (there is also --raw option to print lines for all equipmnet in the database as is but it is useful only for diagnostics I think). This behaviour can be of course adjusted if needed. Also if there are changes in output formating which may speed up incorporating data let me know I can't promise but will try to adjust it accordingly when times allows.
One thing I thought about would be adding option to write data straight to csv file which can be then directly opened by Excel or other spreadsheet programs for processing as needed sparing some unnecessary manual handling.

[golden delicious]

ORIGINAL: kmitahj

One thing I thought about would be adding option to write data straight to csv file which can be then directly opened by Excel or other spreadsheet programs for processing as needed sparing some unnecessary manual handling.

I could do this with a macro if I needed to do it regularly. It's very similar to a monthly report I had to run way back in my days at Xerox.

[Telumar]

[&o][&o][&o]

And where to get this tool?

[kmitahj]

ORIGINAL: Telumar

And where to get this tool?

Didn't post the link so far - mostly because its use requires some extra effort on user behalf first (unless one uses ancient Windows XP platform that is) but if you interested you should be able to download it here: https://www.dropbox.com/s/1aop65oquc8v8 ... k.zip?dl=0.
In case of problems with dropbox access (or having other questions) PM me with your address and I will send it to you directly.

[Telumar]

ORIGINAL: kmitahj

ORIGINAL: Telumar

And where to get this tool?

Didn't post the link so far - mostly because its use requires some extra effort on user behalf first (unless one uses ancient Windows XP platform that is) but if you interested you should be able to download it here: https://www.dropbox.com/s/1aop65oquc8v8 ... k.zip?dl=0.
In case of problems with dropbox access (or having other questions) PM me with your address and I will send it to you directly.

Thank you very much. Works as expected, though i've run into problems with Fabio's Eastern Front sce. - maybe it's because of too many lines of eqp items? Maybe best try yourself to see by yourself. Otherwise great work![&o]

ORIGINAL: kmitahj

One thing I thought about would be adding option to write data straight to csv file which can be then directly opened by Excel or other spreadsheet programs for processing as needed sparing some unnecessary manual handling.

+1 [:)]

[kmitahj]

ORIGINAL: Telumar
Thank you very much. Works as expected, though i've run into problems with Fabio's Eastern Front sce. - maybe it's because of too many lines of eqp items? Maybe best try yourself to see by yourself. Otherwise great work![&o]

Hi, thanks for comments. I downloaded 3.4 version of EF. Not sure if this is the same issue you encountered but the problem I noticed is that though the numbers seem to be ok ToawPeek produced much more equipment lines then visible in TOAW I&R panel. Some of these lines were very anachronic too. The reason is that until now ToawPeek by default displayed lines for all items which has any of OnHand, Rate, TotalsC (Assigned), TotalToe or Lost values non-zero. There seem to be quite a few non-zero left-overs on OnHand and/or Rate columns which triggered printing of items unrelevant for the scenario. These non-zero left-overs apparently can not be easily pruned from the scenario (they are not even visible inside standard TOAW editor, but they physically are still there all the same).
I have changed default way ToawPeek prints eqp. items so it shall now closely match items visible in Toaw I&R panel (one can use --paged option for help in visual verification of consistency between I&R panel and ToawPeek output). Old way of selecting items is still available by using -o (--old) option. Let me know if the change helped with issue you encoutered.

I also added --csv option for testing. With this option ToawPeek prints output in comma delimited format (csv) which may help importing data into spreadsheet program. Note that for now it still prints to console so one has to redirect output to file himself. If it turns out useful then next step would be adding option of writing directly to file specified in command line.

Updated ToawPeek exe (v. 0.3) is available at the location provided in post above.

[Telumar]

Thanks for the update. I didn't test much, but the normal standard function works perfectly, also with the EF scenario now. Only thing is that special characters like ä, ö, ü etc are not displyed correctly (see screenshot), but i think that's a minor issue that can be remedied easily.



EDIT: Don't get confused .. it's Windows 7, not 8, despite the style of the window. I just have a Win8 theme installed.

[kmitahj]

ORIGINAL: Telumar
Thanks for the update. I didn't test much, but the normal standard function works perfectly, also with the EF scenario now. Only thing is that special characters like ä, ö, ü etc are not displyed correctly (see screenshot), but i think that's a minor issue that can be remedied easily.

Hi, thanks for input. ToawPeek prints strings using UTF-8 encoding (addmitelly it does it more by accident - thanks to the way these strings are encoded internally inside TOAW rather then by my initial design [:D]) which is different then default console codepage. Usually 437 is set as default CP - this corresponds to good old DOS extended ASCII charset which includes frame/table-drawing chars (as can be noticed on the picture above). To see umlauts properly (as well as other latin diacritics) on the console use following command before running ToawPeek:

X:\Your\path> chcp 65001

65001 here is UTF-8 copdepage id. If wanting to restore later back to default simply use chcp again with 437 argument. Note that this command does not change the char (byte) stream generated by ToawPeek (and possibly redirected to file) - it only tells console how to interpret (display) it correctly.

Using UTF-8 makes the output independent of given system settings avoiding most of the copepage mismatch nightmares. It shall also allow unified handling of chars outside ofusual Latin1 set (polish letters for example). It is also widely supported by text oriented programs - all is needed is to select utf8 encoding when opening/importing file generated by ToawPeek. Even old-fashioned Notepad is able to open utf-8 encoded text files (others I tried: LibreOffice both Calc and Writer, Firefox, SciTE, MS Word Viewer and likely many others - including MS Office of course).