further incompatibilities with Rev

[Richard Gaskin]

A new incompatibility has arisen between the 14-year-old MC IDE and the 
latest version of Rev:  If you've used MC's Resource Mover to copy the 
answer dialog, ask dialog, etc. into your stack, when you hand that 
stack to a client to open in Rev they're greeted with an error dialog 
warning them that stacks with those names are already in memory.

While we've already spent more time than I would prefer accomodating 
Rev's new behaviors, it may be simpler for us to simply accept being 
forced into doing the extra work of integrating the Resource Mover with 
the Standalone Builder as Rev does to accomodate its new behaviors.

What are the pros and cons of copying resources only into standalones?

Of course the long-term solution is to get rid of the uniquely 
Transcript limitation of stack name conflicts, as requested in 
<http://support.runrev.com/bugdatabase/show_bug.cgi?id=1061>.

But in the meantime how can we best accomodate others in our workflow 
who use Rev?

-- 
  Richard Gaskin
  Fourth World Media Corporation
  ___________________________________________________________
  Ambassador at FourthWorld.com       http://www.FourthWorld.com