Re: FLASH: Tween Bug?

[Byron Canfield]

John,


At 04:06 PM 1/3/99 -0500, you wrote:

>Hi Bryon and all,

>

>> I've posted a new file at http://www.canfieldstudios.com/flash3/tweenbug/

>Note the MIME isn't set


------------

Yes it is. I just tested it further with Netscape 3.0, 4.07, and 4.5 and it

works fine. Note, this is not a local server for me, so I am accessing it

just like everybody else.

------------

>

>>  which contains a third version that has had no elements moved,

>>  but with the stage smaller, from the outset. The distortion of

>> the "a" still occurs, so that blows THAT theory, and lends credence

>>  to the idea that some sort of control handles must be fully contained

>>  within the stage to shape-tween properly (or something else entirely)

>Shape tweening isn't affected any different as to whether it is in or

>out of the normal stage area.

>

>Your problem is basic. The A is not (auto) hinted properly.

>

>All shape morphing is auto-hinted by Flash. As I have said before the

>same identical object may require manual hinting if it is moved (or

>created) to a different position even though it didn't require it in the

>other position.

>

>The 2 basic solutions should solve your problem:

>1) Apply manual hinting.

>2) Separate the components into separate layers

>In the extreme you may have to both separate and hint.

>

>The problem is probably caused by the way Flash calculates and rounds

>off the position of the object and auto-hint points.

>

>You may want to consider this a bug but it is a regular and expected

>proceedure in creating shape tweens in Flash 3. Those Flashers who

>create a lot of Shape Tweens know they may have to separate or hint and

>don't know until they try whether something is needed or not.


I do indeed, consider this a bug. Yes, I expect it -- that goes without

saying. That does not remove it from classification as a bug.


Secondly, I can understand some rounding problems if the position of such

an object was moved and or created in such a way as to be a division of the

common pixel unit, say one created at (12.4,13.7) and the other at (24,14),

but in the case I demonstrated, the difference in positioning (whether

moved or created in that position) is exactly 12 pixels -- no left-over

decimal values. In other words, no rounding should be occurring there. If

there is, THAT is a bug.


In fact, things that do not work consistently or predictably are, by

definition, bugs. This falls in that category and I fail to understand why

you feel it necessary to attempt to "declassify" it as such.



--------------

Byron Canfield, Canfield Studios (http://www.byronc.com)

President, Seattle Coreldraw Artists Network (http://www.corelsea.org)


------------------------------------------------------------------------

To UNSUBSCRIBE send: unsubscribe flasher in the body of an

email to

list-managershocker [dot] com

.  Problems to:

ownershocker [dot] com

N.B. Email address must be the same as the one you used to subscribe.

For info on digest mode send: info flasher to

list-managershocker [dot] com