Trying to save images using Save For Web onto an NFS share using Photoshop CS4 11.0.1 in Mac OS 10.5.8 only works for one overwrite.
Steps to reproduce
Save a file using Save For Web to an NFS share
Save the same file again, choosing to overwrite
Save the file a third time, choosing to overwrite
Expected results
File saves successfully! No other software has a problem with this. Not even Photoshop itself, which can save PSDs over and over again without event. Only Save For Web is broken.
Despite this documentation to the contrary, Event.EXIT_FRAME does not exist in Flash Player 9/AIR 1.0. It was introduced in Flash Player 10/AIR 1.5. If you are writing a SWF that targets Flash Player 9, attempting to use the Event constant will fail, but if you hard-code the “exitFrame” string, it will appear to work—until you start getting complaints from people that still haven’t updated to Flash Player 10 that your events aren’t firing.
I suppose it raises a question about why one would ever choose to use the EXIT_FRAME event. According to Johannes Tacskovics, the EXIT_FRAME event occurs at the end of the lifecycle of constructing the current frame before it is displayed. This seems somewhat counter-intuitive, in that the name implies that the event would occur just before a frame is destroyed.
Either way, since I was looking for an event that would provide me with the ability to perform frame-exact synchronisation to MP4 video, this event was no more useful than ENTER_FRAME. (Adobe, for some reason, decided not to implement onCuepoint for MP4 playback.) Unfortunately, frame events like ENTER_FRAME don’t appear to correspond precisely to when a video frame is rendered, and Flash’s timers are not precise enough either, so the ultimate result was a player with overlays that were sometimes out-of-sync by one frame. Bad, but not disastrous. Still, it would be nice if there was a way to get frame-exact synchronisation with MP4s. Maybe someday…
I’ve run a problem multiple times now with Flash Player and animating the alpha property of an object that contains text. For some reason, when using “Anti-alias for readability” or “Custom anti-alias”, there is a noticeable jump in appearance between 0.78515625 (201/256) and 0.7890625 (202/256), as though it is actually changing the method that is used to blend the sub-pixels at that point. It is highly distracting, and makes it impossible to smoothly change the opacity of text fields. Here is an example that shows the abrupt change between these two alpha levels:
One solution is to change the anti-aliasing mode to “Anti-alias for animation”, but then the letterforms get muddy and pretty ugly to view. Another option is to change the layer mode to “lighten” or “darken”, but this only works in cases where the text is black or white.
Has anyone else discovered a real solution to this problem? I haven’t seen it discussed anywhere, but maybe my Google-fu is simply failing me.
