Re: [flasher] Issues with 5.0a update for Mac OS??

[Catherine Kunicki]

I have also noticed that the view of the frames (scale) will not adjust. I

had one movieclip which would only go from something like 125 percent down

to 66 percent and would never land back at 100 percent. This was persistent

- I could go out and edit another movie clip and back to edit the stage and

then back to the badly scaled movie and the wrong scale would  persist.

Normally though, editing another movie by doubleclicking it in the library

would reset the scale on the other ones.

I also - in edit in place - sometimes lose the stage and can't click back to

it unless, again, I  doubleclick another movie in the library.


most of this is inconsistent and can easily be cleared up by restarting

flash. The other - awful problem - I have had is freezing as soon as any

sound happens in my .swf in the authoring environment or player. I solved

this by removing my external speakers (Harman Kardon Sound Sticks) from the

Mac, but I wish I didn't have to.  I am not sure whether this is due to

Flash or the Sound Sticks, since there are issues with both. However, Flash

is the only application which is causing this freeze to happen. I'd point

the finger at QT Sound Manager extension here, since that's the only common

bond between Flash sound problems with and the Mac OS problems with the

Harman Kardon Sound Sticks.



Catherine


>

From: "Triskelian Design and Training" <kjacksontriskelian [dot] com>

> Just wanted to let everyone know of two potential issues with the Updater

> (Minor compared to the fix).

> 

> I taught a class the last three days and as usual the MACs had the most

> problems. The updater did seem to solve the Sound issue but they are still

> flaky on memory. 70-120MB of RAM allocated and they freeze? The other issue

> we had was that one of the machines repeatedly refused to update the

> Clipboard. (Not blaming the Update but hadn't seen it happen before) The

> other machine changed the view of the frames and would not go back until we

> went out and came back in. It ignored the settings. Only bring them up

> because we hadn't seen either of the issues prior to the update. Both were

> solved with closing the program and restarting.

> 

> As to the memory issues, they are still there although perhaps slightly

> better. It's reminiscent of CorelDraw during the 3-5 versions.

> 

> Kevin Jackson