Posted by: DavidW
« on: June 09, 2020, 10:15:54 AM »I'm trying out the MODDER flag with my current project, and I'm getting a few false positives:
(1) It flags a warning when a string is in memory from some non-setup.tra tra loaded using WITH_TRA or LOAD_TRA - it just assumes they're from setup.tra. (I suspect that's a documentation issue rather than a problem with MODDER itself - the real function is that it flags whenever a string isn't included in the tra files loaded in the local USING command.)
(2) It also flags a warning - but doesn't mark the component as INSTALLED_WITH_WARNINGS - when I compile a dialog, or EXTEND_TOP a script, and there are no dialog lines at all present. It does the same when I COMPILE a script with no dialog lines present - but only if it's an inline baf file.
Not a big deal in either case but I thought you'd like to know.
(1) It flags a warning when a string is in memory from some non-setup.tra tra loaded using WITH_TRA or LOAD_TRA - it just assumes they're from setup.tra. (I suspect that's a documentation issue rather than a problem with MODDER itself - the real function is that it flags whenever a string isn't included in the tra files loaded in the local USING command.)
(2) It also flags a warning - but doesn't mark the component as INSTALLED_WITH_WARNINGS - when I compile a dialog, or EXTEND_TOP a script, and there are no dialog lines at all present. It does the same when I COMPILE a script with no dialog lines present - but only if it's an inline baf file.
Not a big deal in either case but I thought you'd like to know.