Former-commit-id:a02aeb236c
[formerly9f19e3f712
] [formerlya02aeb236c
[formerly9f19e3f712
] [formerly06a8b51d6d
[formerly 64fa9254b946eae7e61bbc3f513b7c3696c4f54f]]] Former-commit-id:06a8b51d6d
Former-commit-id:8e80217e59
[formerly3360eb6c5f
] Former-commit-id:377dcd10b9
1 line
No EOL
839 B
Text
1 line
No EOL
839 B
Text
Here are some suggestions for organizing your Override file into sections that will make trouble-shooting and understanding your Customizations easier. Put all the code that you are overriding in one section, perhaps labeled by the source of the overridden code e.g. $B!H(BOverrides from AreaFcst$B!I(B, $B!H(BOverrides from ConfigVariables$B!I(B, $B!H(BOverrides from FirePhrases. Be sure and comment the lines you are changing! Sometimes you might find it useful to override methods and insert print statements to trouble-shoot a problem you might be having. This is an excellent way to track problems and also learn how the code works. However, be sure and put this code in a separate section and clear it out after the problem is fixed so that you will not miss upgrades and bug fixes to this code in subsequent releases. |