Ya, that will work, but it's a hack, and not necessary to use a hack here - after all, there's a reason I provided so many explicit pointers, specifically to tutorial.nas:
http://gitorious.org/fg/fgdata/source/a ... torial.nasIf you want to override screen.log(), please just do it at the scope of the tutorial.nas file, and not globally - you can just add your own screen.log function to the top of the file, but you MUST use th e
var keyword when doing so.
That being said, it would be much cleaner to just patch/fix the corresponding line in tutorial.nas instead of overriding the whole screen.log() function:
http://gitorious.org/fg/fgdata/source/a ... l.nas#L411I suggest to introduce a tutorial_delay variable here, and make it property-configurable through either getprop() or a listener, so that it can be easily customized at runtime, and made persistent usiing the userarchive attribute.
Having a dedicated configuration dialog just for the tutorial system would sound like a good idea, and in the meantime, having a bunch of config properties should work, too.
But please don't override APIs in a system-wide fashion - or it will cause issues later on.
Finally, modifying screen.nas to allow messages to be optionally paused (as explained above) would seem like another straightforward option that should also come in handy.