Check mod install status

[GoogleCodeExporter]

Briefly describe the proposed feature
Tests every open modfile, looking in its associated upk, to see whether the 
BEFORE or AFTER hex is installed.

Eventually extend this ability to allow testing of entire projects (right-click 
context menu perhaps).

What version of the product are you using? On what operating system?
v0.66 (unreleased)

Please provide any additional information below.

Original issue reported on code.google.com by miss.inv...@gmail.com on 25 Dec 2013 at 3:39

[GoogleCodeExporter]

A vote of support for this issue. I'd suggest three little lights in the 
project view, color-coded for "before" "after" and "neither"

Original comment by johnnyl...@gmail.com on 25 Dec 2013 at 9:54

[GoogleCodeExporter]

I currently have a utility function written and being tested. It operates at 
the level of a single modfile, and currently only has a menu command/keyboard 
shortcut to activate. It tests just the current active modfile, and colors the 
filename in the tab.

It is capable of reporting 5 different states : NO_UPK, ERROR, MIXED, BEFORE, 
AFTER.

BEFORE and AFTER, mean that either the BEFORE or AFTER hex fully matches what 
is present in the upk, and that the other does not. It does not mean that the 
file is valid to install.

MIXED is a case for when there are multiple BEFORE and AFTER blocks and some of 
each have matched. It would be a rare state for a single file but more common 
for projects.

ERROR means that a BEFORE/AFTER pair had neither found, or the number of 
BEFORE/AFTER blocks mismatched. 

NO_UPK simply means that there was no target UPK to compare to.

----

Next step is to allow for iteration over multiple files within a project or 
project subfolder. Current utility code committed to the r108 branch.

Original comment by miss.inv...@gmail.com on 26 Dec 2013 at 4:37

• Changed state: Started
• Added labels: Priority-Medium
• Removed labels: Priority-Low

[GoogleCodeExporter]

Functionality only works for changes to objects.

For modfiles attempting to change table entries (only current allowed option is 
changing a variable's type) it returns NO_UPK.

Original comment by miss.inv...@gmail.com on 29 Dec 2013 at 2:34

[GoogleCodeExporter]

Initial prototype for checking apply status within project pane, including 
subtree checking, committed to r120.

Testing of variable typechange operations still needs to be implemented.

Original comment by miss.inv...@gmail.com on 31 Dec 2013 at 7:32

[GoogleCodeExporter]

Added capability to test "typechange" operations. Will be committed in next 
update to trunk.

Original comment by miss.inv...@gmail.com on 31 Dec 2013 at 9:32

[GoogleCodeExporter]

Changes are considered complete, released in v0.75 (r126).

Original comment by miss.inv...@gmail.com on 2 Jan 2014 at 11:10

• Changed state: Fixed