This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
howtos:toolcoding:common_history_and_background_checks [2010/09/14 16:32] marcus.williams |
howtos:toolcoding:common_history_and_background_checks [2010/09/14 18:09] shona.weldon |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | Many views require that a history be selected (if running in a simulator) and/or a background scenario picked in. In these cases a section of code near the top of the view is used to check that the required history and/or background is in place. | + | Many views require that a history be selected (if running in a simulator) and/or a background scenario be picked in. In these cases a section of code near the top of the view - following the object declarations - is used to check that the required history and/or background is in place. If not in place the code advises the user and quits. |
Common code sections are listed below. | Common code sections are listed below. | ||
- | |||
===== Simulator - history and background required ===== | ===== Simulator - history and background required ===== | ||
Line 18: | Line 17: | ||
endif | endif | ||
</code> | </code> | ||
+ | |||
+ | FIXME - do we have a best practice on the quit() return code? | ||