I've been experiencing some odd behavior with updating bitmaps in CS5 - never happened in prior versions. I have some bitmap in the library - I change it in Photoshop - and then do properties > update in Flash to bring the change in. I save... come back the next day and I'll have the non-updated version back. I hit update again... save.. and this time it takes. I've not been able to repro this, but I've had it happen probably half-dozen times in the past week or two.
Anyone else seen this?
Not that it's easy but I find always saving images I use in flash to an actual file in a folder is a best practice. I can use those assets in other jobs and also I've never encountered this issue. I have encountered it the very few times I've copied a bitmap from Photoshop and pasted directly into Flash and then used the Edit in Photoshop option to update it.
I know it should work, but saving 24bit PNGs of all images to a folder has more than less been a lot better workflow rather than using the direct app transfer of bitmaps between apps. Consider it like having a backup bitmap just incase you need it.
You can use Edit in Photoshop, save in photoshop and it's auto-updated in Flash without even hitting Update. I didn't know if you knew that or were doing that, I was uncertain.
Can't say I've ever seen this bug. Updates for me have always stuck whether direct edit from Flash->Photoshop->Flash or from the filesystem. Perhaps try iterating your FLA (myfla_1.fla, myfla_2.fla, myfla_3.fla) and see if it still happens. That changes things. Then Save is literally not working on the filesystem rather than overwrite.
Europe, Middle East and Africa