Tween Bug?

Here's the scenario: I have a main flash movie that has some
buttons and a container. When you click a button, a MovieclipLoader
loads an external swf. Both files were originally created with
Flash 7 and previously had very little actionscript. Mainly just
some stops, gotos and code for a preloader. The swf being loaded
previously had some static content and worked fine. Now I want it
to load an xml file and fade in some text, but the actionscript
tweens don't work. If I play the swf by itself, it works fine.
However, when I load it into the main movie the tweens don't work.
Right now, for testing purposes, I have the text load with _alpha =
100 and wait a couple frames before the tween script. When the
tween script starts everything being tweened disappears. I figure
it has something to do with the fact that they were Flash 7, and
maybe something isn't being imported right? But even if I publish
them as Flash 7, the tweens don't work. I've embeded all the fonts
too. Even non-text (images, shapes, etc) won't tween. They just
disappear. I've googled this and searched the forums, but I can't
find anything. So, any suggestions would be greatly appreciated.
Thanks,
-Ryan

Just as information the Tween class uses the _root timeline
to generate an onEnterFrame event to animate objects. If you
mistakenly used the onEnterFrame on the _root to create another
thing like a loader for example. That might be erasing the
tweenings. Try using the onEnterFrame on an empty movie
clip.

Similar Messages

Is there a bug in the as3 tween class

Is there a bug in the as3 tween class that causes tweens to stop before completing. I read that there is and that a 3rd party tween class should be used. I'm just starting out learning as3 and experimenting but this would be good to know when I move onto more complex projects.
Also the solution for this was to make your function global. Does this simply mean place your function in the top level of your movie.
I have done research on this topic but I found many conflicting answers.
Any assistance is welcome thanks in advance.

the tween declaration (if you need one) must be placed within the scope of the function. so, if the below function f() is defined in a movieclip, you can use any of the 3 (but don't use the last):
///////// most common use ////////////////////////////////////////
var t:Tween;
function f(){
t=new Tween(...)
/////// next most common use /////////////////////////////////////////
//no declaration needed because the tween is not referenced anywhere outside the function so need not be assigned a variable
function f(){
new Tween(...)
/////////// least common, not good coding, but possible ////////////
// var t:Tween; // declared on the root timeline, for example
function f(){
MovieClip(root).t=new Tween(...)
p.s. please mark correct/helpful answers

Is it flash bug? Tween Class

I've been working on a bit big project. I've some components on the stage. There are basically 4 frames. Each frame has some components. What I've done is, I've used tween class. Workflow is something like this:
Frame 1:
--used Tween class to get fade effect for List component.
--used Tween.MOTION_FINISH event to fire an event when it is finished.
--when it is finished, applied eventListener
--on Change event, remove eventListeners and use Tween class again to get reverse fade effect.
--again used Tween.MOTION_FINISH event to fire an event when finished.
--in that evenHandler, gotoAndStop(2);
Frame 2:
//similar
Frame 3:
//similar
and so on.. now, what happens, is, if i play with my scene, sometimes tween class failed to work. sometimes it does not display List component, sometimes it displays List component with alpha 0.2. sometimes it happens with movieClip also. Is it flash bug or problem with my code?

probably a coding problem. the most common error that seems like a flash bug would be to define a tween within a function body allowing flash to gc that tween, possibly before it starts and/or completes.

Bug with tween

hi
i created a classic tween on the timeline (not with actionscript), which moves a movieclip. if i change any property of that movieclip from actionscript, that layer stops updating, even if i change the value to its initial value.
can i access that tween on the timeline from actionscript?
do anyone knows why this happens?

Although this isn't explicitly documented anywhere, this is quite normal behaviour for flash.
Imagine it as like this: If you do a motion-tween on the timeline, Flash takes full control of that movieclip. So if you interrupt it by setting any property to another value, Flash immediately lets loose of the movieclip, because it doesn't know how to continue with the animation. The nested movieclips are not affected by this, they will continue their animation, because for them, the start and end of the animation is still well defined.
So you can never do a motion-tween on the timeline and actionscript animation on the same movieclip instance at once.
But, as my predecessor mentioned, you can:
Animate the movieclip purely with AS,
Animate the movieclip purely with AS - while nested Movieclips still run on motion-tweens on the their timelines.
Animate the movieclip purely as a motion-tween on a timeline - while nested Movieclips are animated with Actionscript

Loosing my tweens

Hi all
I think I posted about this before when Flash 8 first came,
but I never got any answers. So now that Flash 8 is on its way out,
I'm thinking someone else has come across this problem and has
figured out a fix for it at this point.
I have some old Flash files, possibly from the Flash MX era.
And they were built in kind of a cluegy (kind of like a lot things
were from that era). Mainly a lot of lazy-man approaches to Flash
production, lots of weird things grouped together on stage, nothing
labeled properly, everything kind of pieced together just to get it
to work, stuff like that.
So now we want these files edited. And the problem I'm
finding is that when I make my changes and republish, a lot of the
animation tweens, both shape and motion, lose their tween.
Literally the only things you would see are those spots where
there's keyframes on the timeline, where it tweens, it disappears.
So it looks like anything that's supposed to have an animation, it
kind of flickers.
Now this doesn't happen in the fla file, you can see the
tweening there. But in the republished swf files, that's where you
see this "flickering".
Now the other odd thing is, if you see something flicker, you
go back into the fla and look what's going on, but you do nothing,
then republish...magically, whatever you looked at is tweening the
way its supposed to. But then, you take that approach and do that
to everything you see flickering, republish thinking everything is
great, and sure enough, the things you thought you fixed before are
now flickering again.
So this just seems to be a bug of some sort in Flash 8, and
there's no reliable way to fix this that I've ever seen, aside from
rebuilding these things using the same artwork, but I don't want to
do that (some of these project are ******* huge).
So if anyone has any suggestions (maybe its just a publish
setting I'm missing or something) feel free to let me know.
Thanks
Chris

If you converted from one system to another, and your 10.4 system and data is on another hard drive, you can still recover it. Is there another system with 10.4 still on it? Or do you have the hard drive that has 10.4 and it's data on it? If another system has the data on it, you can hook them up putting your 10.4 system into target disk mode (hold the T key down when you boot it). If you only have the 10.4 hard drive, or even if it's in a system, you could mount it into an external hard drive case and then use it with your new system. Without knowing more details, it's hard to know exactly what to recommend.
If you've run out of space on your 10.5 system, remember you need at least 10% of the capacity free for systems usage, otherwise the system performance will be affected.

3d motion tween load problem

Hey all,
I'm having a problem which has made me struggling for two days. I hope i can get some new ideas for my problem here.
I created a fla which includes several 3d motion tween in CS5.5, when it's compiled it works perfect. But when i try to load this swf into my main project, images get blurry and distorted. Below is the screenshot of the situation. The first one is the correct one, and second one is loaded into main project. I read that scaling 3d tweens might cause such problems and tried to fix it by two solutions. As first, i tried to retransform the tween by: myContainer.transform.matrix = new Matrix(); but didn't work out. As second, i tried to rescale the stage which mentioned as a solution is some blogs.
And i don't know if it is some kind of bug as mentioned here: http://forums.adobe.com/message/2258767
I'd really be glad if i can get some ideas, thanks all.

anyone?

Image gallery tweening issue

Hi,
I use this smooth, nice (and simple) image gallery, and I am very happy with it. However sometimes some of the images stops when rolling in, and I have to press Fw again to jump to the next one. I can't figure out where the bug lies, as I mentioned it appears rarely but it blows up the whole thing.
Maybe somone could take a look at it:
Thanks!
import fl.transitions.Tween;
import fl.transitions.easing.*;
import flash.utils.Timer;
import flash.events.TimerEvent;
var currentImg:uint = 0;
image_2.x=-1500;
var imgArrayFw:Array = new Array(image_2, image_1, image_3, image_4, image_5, image_6);
var imgArrayBw:Array = new Array(image_2, image_1, image_3, image_4, image_5, image_6);
buttonFw_btn.addEventListener(MouseEvent.CLICK, doNextTween);
function doNextTween(e:MouseEvent):void
    imgArrayFw[currentImg].x = -imgArrayFw[currentImg].width;
    var myTween:Tween = new Tween(imgArrayFw[currentImg], "x", Strong.easeInOut, imgArrayFw[currentImg].x,0, 2, true);
    addChild(imgArrayFw[currentImg]);
addChild(buttonFw_btn);
addChild(buttonBw_btn);
currentImg = (currentImg+1)%imgArrayFw.length;
buttonBw_btn.addEventListener(MouseEvent.CLICK, doPrewTween);
function doPrewTween(e:MouseEvent):void
    imgArrayBw[currentImg].x = imgArrayBw[currentImg].width;
    var myTween:Tween = new Tween(imgArrayBw[currentImg], "x", Strong.easeInOut, imgArrayBw[currentImg].x,0, 2, true);
    addChild(imgArrayBw[currentImg]);
addChild(buttonBw_btn);
addChild(buttonFw_btn);
currentImg = (currentImg+1)%imgArrayBw.length;

I'd recommed never using the included Tweening classes and start using a good tweening engine like TweenLite/TweenMax from greensock.com. The Adobe ones are slow and problematic - one of the issues they have is tweens stopping like you described. It should be pretty simple to swap out to using tweenlite and once you do, you'll find the syntax much easier.

Differences Between Final Keyframes of Tweens

Check this out... it's something I never really noticed
before. Or never paid it much attention anyway, and thought what I
was seeing was just buggy behavior (going back to at least Flash
5). Now I realize it's some sort of actual distinction between
keyframes at the end of a tween (maybe it is a bug).
Screenshot
See how the top one has a distinct keyframe with a vertical
line on the left, and the bottom one doesn't have the line? I can't
find anything on this online.
I also haven't been able to figure out how the difference
arises. It seems almost random and I've tried quite a few things,
but can't find a pattern. It will even happen when the keyframes
and tweens are created exactly the same way with exactly the same
objects.
It wouldn't bother me except there is one key behavior issue.
The blank keyframe after the upper one works as expected. However,
the blank keyframe after the bottom one isn't really blank. If I
put any object in there, it becomes the same object that is in the
keyframe before it.... and I can't even swap it, it's stuck as the
same object from the keyframe before it.
Anybody know what's going on here?

Hmmm - can you send me this exact FLA? This has always and
only been associated with the Sync
feature. Basically, Flash turns this on but only if you
create a motion tween by using the contect
menu (right click) selection. if you apply a motion tween via
the properties panel then Sync is NOT
on be default. This vertical line is a visual indicator that
Sync is not on (think of it as a wall
stopping the syncing of frames with nested frames in the
symbol being tweened).
Chris Georgenes
Adobe Community Expert
www.mudbubble.com
www.keyframer.com
www.howtocheatinflash.com
randykato wrote:
> Chris,
>
> Thanks for the reply - but that's not it. I've checked
the properties (for the
> beginning keyframe, ending keyframe, and tweened frames
in between) and they
> are all the same. Sync is checked for both tweens, and
all the tweens in
> question.
>
> There does seem to be some correlation though.... and
here's where it's
> getting even more complicated.... The issue I have with
a blank keyframe
> following the no-line end keyframe does go away if I
uncheck Sync for that
> tween. However, the vertical line line does not show up
to reflect the change.
> There are also lots of others that have the line even
though Sync is checked,
> and the line doesn't disappear if it's unchecked.
>
> I just noticed something else. All the no-line end
keyframes will show the
> vertical line when selected on the timeline if the frame
to the left is also
> selected (regardless of whether Sync is checked or not).
But, they won't show
> it when selected as a single frame (when selected it
turns all black, but you
> can see the extra 1px line there when you compare them)
or if the selection
> doesn't include the frame to the left.
>

Possible bug on JavaFX Scaled Translation

Hello,
I'm experiencing some strange behaviour in following situation:
I have a stage, containing a group G that scales down all of it's children (I'm developing for a HD Screen on a non-HD screen, so i need to scale the app in order to actually see it). This works just fine, but at the moment, I add another Group as a child of G and translate this group, G will be translated too.
However, if I do not scale G, this does not happen. Here is some source code that will reproduce this behaviour on Windows XP and JavaFX 1.0:
package test;
import javafx.stage.Stage;
import javafx.scene.Scene;
import javafx.scene.text.Text;
import javafx.scene.text.Font;
import javafx.scene.text.TextOrigin;
import javafx.scene.text.TextAlignment;
import javafx.scene.paint.Color;
import javafx.scene.Group;
import javafx.scene.shape.Rectangle;
import javafx.animation.Timeline;
import javafx.animation.Interpolator;
import javafx.scene.paint.Paint;
var mainMenu:Group = Group {
    content: [
        Rectangle {
            x: 10
            y: 20
            onMouseClicked: removeMainMenu
            width: 100
            height: 40
            fill: Color.ORANGE
        Text {
            content: "Klick me!"
            font: Font { name: "Verdana" size: 30 }
            textOrigin: TextOrigin.TOP
            x: 10
            y: 20
var stage = Stage {
    scene: Scene {
        width: 600;
        height: 600;
        content: Group {
            scaleX: 0.5;
            scaleY: 0.5;
            content: [
                Rectangle {
                    x: 0
                    y: 0
                    width: 600
                    height: 600
                    fill: Color.RED
                mainMenu
function removeMainMenu(e) : Void{
    Timeline {
        keyFrames: [
            at(0ms) {
                mainMenu.translateX => 0.0 tween Interpolator.EASEOUT;
            at(300ms) {
                mainMenu.translateX => -100.0;
    }.play();
}So my questions would be:
1: am I right and this is a bug or is the behaviour right and I the problem here? ;)
2: What could i do, in order to get this scenario to work correctly?
Best regards,
newcron

Do not know why, but it works with transforms attribute:
var stage = Stage {
    scene: Scene {
        width: 600;
        height: 600;
        content: Group {
            transforms: Scale{ x: 0.5 y: 0.5 }
            //scaleX: 0.5;
            //scaleY: 0.5;
            content: [
                Rectangle {
                    x: 0
                    y: 0
                    width: 600
                    height: 600
                    fill: Color.RED
                mainMenu
}

Ghosting occurs in shape tweens in clips with scale9Grid active.

Why does ghosting occur in shape tweens? Is this some kind of rendering bug? I seem to keep running into stuff like this
(sorry, first post had image that was not cropped properly by MSPaint and had tons of white space; I fixed it)
--Background (feel free to skip if TL;DR): My SkinnedButton class supports states for DEFAULT, ROLLOUT, ROLLOVER, PRESS, RELEASE, RELEASEOUTSIDE, TRACKOVER, TRACKOUT, DRAGOVER, DRAGOUT, DRAGDROP, plus all variations of SELECTED_* states in addition to a "selectedMask" and "focusMask" display objects that are automatically arranged, docked, and made visible to suit not only the button state, but also (at least in the case of "focusMask") taking into account the manor in which it entered a particular state (via keyboard, via mouse, via assignment, what the drag source origin was, exact origin clip, custom tracked drag source, whether a drag even began, was cancelled, etc.). It dispatches events for all of these states and has fallback chains for any that are missing, since they're all classified into simple states out, over, and down. For example, if no RELEASE state is defined (can be either property named "mc_release" or "release" label on "skin" MovieClip), then it will progressively fall back to ROLLOVER, ROLLOUT, and finally DEFAULT until one is defined. The bare minimum for a functional button is to define a clip for the default state.
So anyway, I wanted to animate my "release" state by having the button collapse and expand, and I discovered this odd ghosting behavior. This is just a simple reproduction of the problem with no special logic, just a shape tween on a clip with scale9Grid active. It appears as though Flash isn't re-rendering the bottom most shape as its exposed by the tweened shape on the layer above:ShapeTweenGhosting.fla - Google Drive
I suspect this is occurring because of the active scale9Grid, since the ghosting goes away when you turn it off, but then the button is all distorted. Turning on cacheAsBitmap exhibits the same behavior. Again, it's not a performance issue, it's just incorrectly rendering. I don't see any documentation stating shape-tween animations are not allowed in clips with scale9Grid applied. The shapes themselves appear to be rendering correctly based on the scale9Grid (i.e. without distortion), but the ghosting is a problem.
Here is an even more pronounced example with a large shrinking and expanding oval shape:
ShapeTweenGhosting2.fla - Google Drive

I posted a bug here: Bug#3767678 - Ghosting occurs in shape tweens in clips with scale9Grid active
Continued experimentation revealed it occurs on the y axis too, and depends on how much you scale the clip.
At 99%, 100%, and 101%, no ghosting is observed. At 110%, it occurs a little bit. At 120%, the ghosting is very pronounced. I suspect the problem is arising due to inaccurate calculations of the redraw regions, which may not be taking into account certain scaling factors, perhaps such as stroke widths; however, I reduced all stroke widths to zero (hairline), and the ghosting still occurred, so something is not quite right.

Strange tween behaviour when copying movie clips among documents

Does anyone else encounter this? If you have a movieclip that contains a motion tween which is split in the middle, copying the movieclip that contains it to another document may make the animation un-editable or even break it (as in some of the flash banners I'm producing).
It seems like all transformation points get shifted randomly and Flash somehow tries to "knit" them together again.
This also happen if you chose "save and compact" and may break your animation if it's more complicated.
I have recorded a video which shows this behaviour:
http://www.youtube.com/watch?v=N7nT7wza4GA
I also filed a bug report for that and hope it could be reconstructed. But seeing it in a video just illustrates the problem even better.

Hi there,
Unfortunately this (the copy nested split tweens across files) is a known issue. However, if you use copy frames instead of copy you shouldn't see this issue.
However, I haven't seen the save and compact problem even with the large complex files -- that shouldn't be touching anything to do with the spans. Are you able to reproduce this consistently or have some steps I can try?
Thanks!
Jen.

Flash CS4 Bug saving to external drive?

I discovered last week when teaching my Flash class that in saving FLAs to my USB drive, and THEN testing/publishing, the AS3 code was ignored in the resulting SWF?EXE files. I duplicated the situation with multiple computers, mutliple external drives and multiple FLA files. I even tried it at differnt locations (home and campus). The problem is only related to CS4 with Actionscipt 3. Both CS3/AS3 and CS4/AS2 test/compile as one would expect. Save the CS4/AS3 file to the internal C: drive and then test/publish everything works fine. Go figure! WHy would the save location make any difference? I thought perhaps it was a PATH environment variable issue, but putting the external drive path in the PATH statement caused no effect.
Here's the information I'm providing to my class tonight. Anyone else encountering the same? BTW, I upgraded to release 10.0.2 but to no avail.
THE PROBLEM:
I think I discovered a pretty major bug in Flash CS4. When creating an ActionScript 3 file (with scripts written on the timeline) and saving the FLA source to an external drive (such as a USB thumb drive) and then testing (Control > Test Movie) or publishing (File > Publish), the AS3 code is ignored in the resulting SWF or EXE. If you save the file to the C: drive and then test/publish, it works fine. I tried this on several computers with several different FLA files and differing script, with several devices including a network drive – all with the same result.
I posted the problem to the ActionScript forum at adobe.com and contacted tech support (via email) but have yet to receive any useful feedback.
SOLUTIONS:
OPTION 1: Save your FLA to the hard drive before testing. You can create a temporary folder on the desktop of the campus computers or should have access to C:\TEMP. So save your files there and at the end of you session, be sure to copy the files (both the FLA and any published files) to your USB for safekeeping. When updating your FLA, first copy it to the internal C: hard drive, then make changes and test, etc.
OPTION 2: AS3 code written to an external .AS file does work when compiled. But this really is beyond the scope of this class and adds a lot of complexity.
OPTION 3: Use Flash CS3 – works fine in CS3, but of course you can’t use any of the cool new CS4 features such as new motion tweening, and inverse kinematics (IK bone structures).

Susan,
Would the File > Archive Project do what you want?
Don S.

Bug with 3D animations

I noticed a bug when trying to animate movieclips in 3d space:
Basically the bug occurs when trying to tween a movie-clip in 3d space across a z range that is greater than 5000 or so, which then results in very odd behavior (see end of movie above). What strikes me as especially odd, is that the whole tweening rate is messed up when this occurs, it's as if the program decides to only tween half of the distance that I give it.
I know I can workaround the problem by just scaling the object as well while it's moving, but that's besides the point. It was the very first thing I tried in CS5 and took me less than 5 minutes to find. I doubt i'm the only one.
=Edit=
So it seems the exact value is 5760. that's the largest distance flash will tween an object in the z direction. Also, it doesn't matter where that range is, for example I can go from 0 to 5760 or 4000 to 9760, both work just fine. This means I can work around this problem by creating two seperate tweens, but that really shouldn't be necessary, and is very bothersome considering how the new tween system works, it automatically tries to add a new keyframe to the current tween, where the limit still applies.
Best,
-Johannes

Yeah, you're right. I guess I was expecting too much of flash, after all it's not After effects, which would probably be much more suited to what I want to do here.
Even still, it makes me very warry of upgrading from cs3 when, simply by messing around, I get graphical glitches like this:
which was the result of taking a tweened movieclip animation and placing it inside a graphic to duplicate the effect.
Seems I just have a talent for trying things that adobe didn't originally intend flash to do.
-Johannes

A continuous bug in Flash CS5 and CS5.5

When you creating a classic-tween and you add an ease to it using the ease editor – it works fine, BUT! If you want to insert a keyframe inside that tween range it totally messes the spacing! It’s a tremendous bug which keeping me and many other animators I know away from those versions.
I truly hope that in Flash CS6 that continuous bug will be gone and finally I will be able to upgrade my old Flash cs3!

The forums are not the place to post bugs/wishlist items.... Adobe rarely visits here. Use the link below, though it is probably too late for CS6 since CS6 appears to be on the verge of release - you can probably get a trial version of it and see for yourself.
Adobe - Wishlist & Bug Report
http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

Insert keyframe in classic tween doesn't preserve curve data in CS5?

In earlier versions of Flash (CS3 and CS4) this technique I am about to describe works perfectly. Since Flash CS5 came along, it stopped working. I have no idea how to get it to work again. Here's what I want to accomplish:
Draw a circle shape on the stage, convert it to a movie clip, add a new keyframe on frame 15, while on frame 15 select the circle movie clip and move it a good distance away from its original position, right click on, frame 8 and choose "create classic tween". With the classic tweened timeline selected, select the "edit tween" button in the properties panel to create a custom easing curve. I made my own easing curve that eases in and out to make the result more obvious when I describe what is now broken in Flash CS5. With onion skinning turned on, and the entire range of animation selected, you can easily see what the curve is doing to the movie clip.
Below are screen captures of the timeline, curve editor window with my custom curve, and the resulting circle tweening on the stage with onion skinning turned on.
This next step is where Flash CS5 breaks, and where Flash CS3 and CS4 work.
Select, the 8th frame on the timeline, and insert a keyframe. In older versions of Flash, the custom curve would stay true to what it was before you inserted the keyframe. The curve would be cut at the point where the keyframe was inserted and the first part of the curve would get assigned to the tween from frame 1-8(in this case), and the last chunk of the split curve would get assigned to the frames 8-15(also in this case), thus preserving the original tween. However, this does not happen anymore. Instead, it does half of what it's supposed to do.
Here's what it looks like when you add a keyframe at frame 8 with my example animation:
- first frame selected, looking at the curve editor window:
- this is exactly the same curve the entire span had (frame 1 - 15) before I added the keyframe on frame 8. The curve you should be seeing right now is the first half of this curve, not the whole thing. Next, let's look at the last section of the tween:
- with frame 8 selected, let's look at the curve for this tween:
- It's exactly what we'd expect, the last half of the original curve. Why didn't this happen to the tween in the first half? I don't know. Here's what the onion skin looks like before and after I insert the keyframe:
These onion skins should look exactly the same (except for the fact that there should be a bright green circle where the new keyframe is, for example, the middle ball, like you see in the second image), but if you look at the second one, you can see that the first half of the tween does not match, and that the last half does. When adding a keyframe anywhere in an existing tween, the original tween should remain preserved - the original curve should get split and distributed correctly to the new tween in front and behind the new keyframe.
I've tried using graphic symbols instead, I've tried playing with sync being on and off, i've tried it with using the built in easing (not custom easing curves), I've tried every method for inserting a keyframe that flash has to offer.. I can't figure out how to make it split the curve correctly. Has anyone else run into this problem? I do a lot of character animation, and this technique was my bread and butter, and now it's gone. I tried adapting to the new motion editor, but for character animation, the classic tween is so much faster.
Does anyone have a solution to this problem?
Thanks!
-Tyson

i reported it for a fix (or, at least, consideration for a fix) for the next version of flash pro which is undergoing beta testing. that won't show up in the link i gave you which is for non-beta testers.
i don't control whether it will be fixed or not but i know it will be addressed by the adobe engineers. i've reported about 4 issues that i've encountered via the adobe flash forums that i've reported and that have been fixed in the next version of flash.
it's too soon to tell what they engineers think about this report. currently, it's listed as "unverified" which means they haven't had time to see if they can duplicate the issue. we'll see. (i can duplicate it so its status as unverified will change, i'm sure.)
p.s. "flash authoring" is the place to report "flash pro" requests/bugs. i don't think it's obvious those are the same and have initiated a request to see if "flash authoring" can be changed to "flash pro".

Tween Bug?

Similar Messages

Maybe you are looking for