output extensions

From Wiki

Jump to: navigation, search
(Created page with "<onlyinclude> ====...log_..._bar==== {{Ex/inival|1.0.0.1|whole numbers between +/-65534|has a variable syntax and can be specified as many times as necessary. The parts are A_log...")
 
Line 20: Line 20:
 
====*...function_overlay_tint====
 
====*...function_overlay_tint====
  
<onlyinclude>
+
</onlyinclude>

Revision as of 13:59, 4 January 2013

...log_..._bar

Introduced around 1.0.0.1, this extension has a variable syntax and can be specified as many times as necessary. The parts are A_log_B_C_bar where A_ B_ and C_ are optional. The simplest form, log_bar sets the bar which non-debug log events must pass below (less than or equal to) in order to be included in the log or console output.

There is more than one log and more than one bar per log, in fact there are probably hundreds. You can set a particular log's bars via A_. Eg. SOM_MAIN's log is main.log, so main_log_bar will set the bars for only SOM_MAIN. With B_ you can set the bars for events originating in a single "translation unit" or any units which match B_ up to the end of B_; all legal non-alphanumeric characters are treated as underscores. Finally C_ can set particular kinds of bars. Eg. log_debug_bar sets the debug bars only, which is useful because debug bars are unaffected by default. The default setting for bars is 0, except for debug bars which default to -1. Values are limited to whole numbers between +/-65534.

Note: The A_log_B_C_bar syntax is actually shorthand. It has some deficiencies. For example, log_som_debug_bar is ambiguous, because it can mean the debug bars for translation units beginning with "som" or it can mean the "som.debug" translation unit. The match is greedy, so it will mean the latter, and the former will be impossible to specify. This is a strong argument for removal of som.debug.cpp. A longform syntax has been devised but is not yet implemented as of SomEx ver. 1.0.0.1.

A "translation unit" is a source code object, like SomEx.cpp. SOM_EX should include a comprehensive detailing of logging and console output.

do_missing_file_dialog_ok

Introduced around 1.0.0.1, this extension in the affirmative disables the pop-up dialog which normally reports when files accessed by Sword of Moonlight do not exist. For games not created with Sword of Moonlight Ex this is very handy, because they are likely to have a great deal of missing files. For games created with the aid of Ex it is probably a good idea to satisfy all of the pop-ups, and to not turn this on, just in case a player discovers a missing file, so that they may report it. It's not a bad idea to leave this extension commented out in your games Ex.ini file with a comment letting players know that they can hide the pop-ups if they find any and they become annoying. You might even consider mentioning this in any literature that comes with your game. Values are limited to binary statements.

*...function_overlay_contrast

*...function_overlay_eclipse

*...function_overlay_mask

*...function_overlay_tint