1 Reply Latest reply on Oct 1, 2009 6:48 PM by pixlor

    asynchronous saving anytime in this millennium?

    JenMQui

      I know when Fireworks CS4 was released one of the listed features was asynchronous saving. But then it went away, something not right with the engineering perhaps. I can understand if there is a bug and Adobe sends out a patch to make it work better. What I can not understand or tolerate is how Adobe can sell a feature, one that was quite time saving & made-up for other performance hits, and take it away without fixing the problem as soon as possible. CS4 was released too long ago for this not to be fixed and working by now. — I would be cautious to purchase another copy of this software in the future because the features that were sold with the package have still not been delivered. I'm sorry, though I can not respect a company who sells something and never delivers it. Why has engineering not fixed this already?