Hey Trinity… haven’t gotten to use this often lately, but I seek to remind everyone always… the only stupid question is the one that goes unasked. Remember it, cause we all feel sometimes like we’re stupid, but we’re really not… just limited in knowledge.
To elaborate on Lostinbeta a little… just remember this.
a keyframe has a little dot in the middle of it, and it’s shaded in, where as a blank frame is solid white. Anything that you have on the timeline only exists where
A) there is a frame. if you see the standard background of the timeline itself in a frame then there isn’t any frame there at all.
B) the frame is shaded in some way, ie blue or grey,. not white.
B) either it is a keyframe, or there is a keyframe on the timeline prior to it, without any other keyframes interupting it.
This includes graphics, fills, strokes (lines), movie clips, sounds, etc.
The second question - a motion tween begins AND ends with a keyframe. ie, you need to select the last frame and hit F7 to make it a keyframe. You can then select that keyframe and apply the effect that you want to have occur throughout the tween.
I’m not sure what the effect is you’re discribing. :), but easing is a way of smoothing out the ins and outs of tweens. It’s on the “Frame” panel. To ease “in” means that the object’s effect gets faster as it runs from the keyframe where it is set, to the next keyframe on the timeline. To ease “out” is the opposite.
I have two motion tweens on the same line. Separated by a keyframe, as I’m supposed to I guess
At first they were both moving fine, but now the 2nd Tween is moving REAAAAAAALLY REALLY SLOW. the first Tween is normal speed but the second one is almost in Slow motion.
This was happening earlier while i was making a motion guide, but I didn’t know why so I just kept opening up a new stage and starting over LOL
remember that sometimes things can get a little glitchy in a Flash project. What i mean by that is that sometimes things will break, and it will not be apparent why something is acting the way that it is.
What lost said was right. Objects move slower when you add frames inbetween two keyframes (which have a motion tween between them.). If one of the motions is going really slow, but you didn’t add any frames inbetween it’s keyframes it could be that the motion tween got screwed up and will have to be rebuilt. Sometims from scratch.
I think that was the single most frustrating thing about learning the basics of Flash, for me. I know that now, when my fiance runs into these problems she gets infuriated with me when I solve in three seconds what she’s been working for an hour to fix. Sometime around the first year of working with Flash anyone should start to get a sense of when something is a repair issue, or a scrap and overhaul issue.
Sometime around the first year of working with Flash anyone should start to get a sense of when something is a repair issue, or a scrap and overhaul issue.
Hmm, I have been flashing for 5 months now and already know that. I think you are setting the bar high…lol
It probebly depends upon how hard you’re working with the program too. Took me a year, but I was learning html javascript, and image editing in that year as well. Maybe I’m just slow.
I agree… When you’ve done soemthing once or twice, you start to recognise patterns. Like with Flash 5 tellTargets, I knew that if I got an error come up on one of those, then it was most likely that I had a typo or a clip that wasn’t named in there somewhere.
Anyway, as far as tweens go, what the other guys have said is correct - the more frames you have for the length of the tween, the slower (but smoother) it will be. To get a smooth and fast tween, then you can play around with the fps (frames per second) rate.
But occasionally it will all go to pot for no apparent reason. No-one knows why. :-\
