yoy wrote:

The new update is really screwed up. It seems to have made matters worse.


The scope of the update is very limited, and aside from a handful of scripting changes in the IDE there's been (to the best of my knowledge) only one change to the engine, to report exec errors more reliably.

Are any of the issues you're seeing reproducible in v2.2?

My substack "Prefs" no longer launches from the Edit menu. It appears that
both the main and substack have the same stack ID. Hmm...

Using stack IDs is tricky -- from the Transcript Dictionary entry for "ID":

   A stack's ID is equal to the ID that will be assigned
   to the next object created within that stack, so the
   stack ID is subject to change.

Why not use the stack's name to refer to it, or are you monitoring newly created objects?

Also when I close the .rev stack, 2.2.1 quits with an error everytime.

What is the error?

It also is raising a script alert on some of my scripts which worked fine on
lesser versions.

Thus far I'm finding error reporting to be more reliable in v2.2.1 than in v2.2, on par with v2.1.


What script errors are you seeing? Are the errors valid, perhaps an erroneous syntax not adequately caught by the engine in v2.2?

--
 Richard Gaskin
 Fourth World Media Corporation
 ___________________________________________________
 Rev tools and more:  http://www.fourthworld.com/rev

_______________________________________________
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution

Reply via email to