Increasing the delay might work, as a workaround.
Oh god. Is this an engine bug or an IDE bug? Surely "go next" isn't broken?
I'm pretty sure it's in the IDE. I haven't had it happen when using go next/go previous in a script.
5) Forget it, now the problem isn't happening. It was a moment ago. I hate this intermittent kind of bug.
Yes, isn't it fun (not ;-). Makes them damn hard to fix. -- jeanne a. e. devoto ~ [EMAIL PROTECTED] http://www.jaedworks.com _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
