Groups | Blog | Home
all groups > flash (macromedia) > september 2003 >

flash (macromedia) : Copy and paste frames bug in Flash 2004 Professional


drailer
9/12/2003 10:21:01 PM
In general I think the update is great. It probably worth the price alone for being able to find and replace fonts. hehehe

Anyway, one bug I've found that is driving me nuts is that after just a few copy/paste frames I get the spinny rainbow disc of "busy" in mac OSX... and then the big crash and work is gone. I used to use copy/paste frames effortlessly before. Now I've got to save first, apparently.

I'm wondering if that kind of thing weighs heavily on RAM if it is remembering 100 undos. Perhaps I will scale that down.




Caroling
10/30/2003 8:52:33 AM
Where do you find "Copy frames"? My Edit menu doesn't even have the
command anymore. When I select a series of frames in the timeline, and
say "Convert to symbol", the new symbol has all the frames pasted into a
single frame. This is especially frustrating when trying to copy all the
frames on several layers. The only alternate is "Edit/Copy" and that
does the same thing. It copies all the frames but merges them.

[quoted text, click to view]

--
Caroling
10/30/2003 9:37:01 AM
I found the menu command. It is under Edit/Timeline/Copy Frames. Along
with a whole menu of stuff. I couldn't find that in the Help with a
search or in the contents. Just trial and error. I'm on Mac OS X 10.2.8
and haven't had any crashes with 2004 yet. Hope you survive the flames
and the setbacks.

[quoted text, click to view]

--
drailer
10/30/2003 3:23:47 PM
Actually I just use the key command for that which is command + option and c for copy frames followed by command + option and v for paste frames. That's what it is for mac, anyway. Still not too sure what this is about. Sadly this issue plus the font "bumpage" issue where a font in MX is suddenly raised a couple irritating pixels in MX 2004 for no good reason... plus the fact that I don't have time to dissect my current flash projects to find case sensitivity issues (etc) have left me using MX until I have time to make the transition.

Despite reading several articles where people were flamed by "real" programmers, (regarding the case sensitivity issue) I still have to say, that all in all I can't make the transition right now; is that a user issue? Think specifically of people like me: I learned to program ON Flash... If my coding is sloppy, it is only because Flash brought me up this way. I am Macromedia's creation as much as Flash itself is.


AddThis Social Bookmark Button