awips2/cave/com.raytheon.viz.gfe/help/TextProductUserGuide/Slide141.html
root 9bb8decbcf Initial revision of AWIPS2 11.9.0-7p5
Former-commit-id: 133dc97f67 [formerly a02aeb236c] [formerly 9f19e3f712] [formerly 06a8b51d6d [formerly 9f19e3f712 [formerly 64fa9254b946eae7e61bbc3f513b7c3696c4f54f]]]
Former-commit-id: 06a8b51d6d
Former-commit-id: 377dcd10b9 [formerly 3360eb6c5f]
Former-commit-id: 8e80217e59
2012-01-06 08:55:05 -06:00

16 lines
1.4 KiB
HTML

<html>
<head>
<meta http-equiv="content-type"
content="text/html; charset=ISO-8859-1">
<title></title>
</head>
<body>
<center>
<h2> Text Formatter User Guide</h2>
<h3>141. Help and Feedback - Exercises</h3>
<hr>
<a href=Slide140.html>Previous Slide</a> <a href=Slide142.html>Next Slide</a> <br><img SRC=Slide141.JPG border=1><br></center>
<p><p><big>Here are some suggestions for organizing your Local 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. "Overrides from AreaFcst", "Overrides from ConfigVariables", "Overrides from FirePhrases", "Overrides from Region". Be sure and comment the lines you are changing! FSL has a Patches page with sections of code to include in your Local file to allow you to fix bugs before the next release is issued. Put this code in it's own section and then clear out that section with each new release. 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.<br><br><br></big>
</body>
</html>