Frankly, I'm amazed that this kind of a bug can even exist. Did you just try it in v1.1.1 or did you know about it since prior to 2.0 (and has someone reported it already)?
For Rev 2.01 to crash under this circumstance is simply inexcusable. This renders my project (and all of the time and effort I've spent brainstorming with my customer) worthless until the problem is fixed or Rev can provide a reasonable work-around.
I don't mind "cat-skinning" (as in "more than one way...") but this is ridiculous.
Barry
On Wednesday, Jul 23, 2003, at 20:14 America/Denver, [EMAIL PROTECTED] wrote:
Date: Wed, 23 Jul 2003 19:54:50 -0600 Subject: Re: How to crash Rev 2.01 in OSX From: David Kwinter <[EMAIL PROTECTED]>
On 7/23/03 7:48 PM, "Barry Levine" <[EMAIL PROTECTED]> wrote:
to see if the problem was introduced in v2.
Problem exists in 1.1.1 as well, not another problem with 2.0 though I don't
blame you for half-expecting it to be ; )
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
