Although (I found this out recently) the recommended way to do a macro script
definition is to have the rollout defined and called in the scope of the macro, if
you define the rollout outside the macroscript, you can access the rollout's
variables globally. I can see where this may be an issue if you are not explicitly
loading the script, I work with many scripters and we use each others functions
and tool features by keeping things global. We maintain a "loader script" that
helps enforce dependencies.
