Glimmr Automap

version 2/101030 by Erik Temple

  • Home page
  • Beginning
  • Previous
  • Next



  • Chapter: Debugging

    Glimmr Automap, like all other Glimmr extensions, includes a debugging log. This chapter includes basic information about the debugging tools, as well as those specific to GLAM; for more information, see the documentation for Glimmr Drawing Commands.

    To use the debugging log, enable this use option:

        Use Glimmr debugging.

    Now Glimmr functions will announce themselves, as well as the particular extension that generated them (e.g., Glimmr Canvas-Based Drawing, Glimmr Drawing Commands, etc.) as they fire. Be warned that, under normal usage, Glimmr generates a lot of debugging information, and can quite thoroughly gum up a game's output. There are a few things we can do to mitigate this:

        1) The Glimmr Debugging Console extension can be included to segregate Glimmr logging output into its own window.

        2) We can set up our own alternate text-buffer window and direct log output there by setting the "console output window" variable, e.g.:

            The console output window is my-text-window [a text-buffer g-window].

        3) We can also send console log output to the transcript, while not printing it anywhere else. To do this, we include this code in our story file (it must be placed *after* the inclusion of GLAM):

            To say >console:
                say echo stream of main-window.
        
            To say <:
                say stream of main-window;
                say run paragraph on.

        This will only work when a transcript is actually being written. To ensure that we do not forget to initiate one, we can include something like this:

            When play begins:
                try switching the story transcript on.