Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
quote:
Originally posted by: SiamJai
Geez. With all this complaining about a text issue, one could not help but feel like it's Microsoft Word we're talking about here. ;)
I wonder whether Fireworks is used for graphics at all anymore. Also wondering whether MS Word developers have to deal with so many complaints about bugs in its native image editing feature.
Copy link to clipboard
Copied
quote:
Originally posted by: pixlor
I'm sorry? People do use Fireworks to make buttons for navigation, images with text call-outs, logos, and many other graphics where text is involved. Graphics includes more than just photos.
Copy link to clipboard
Copied
quote:
Originally posted by: SiamJai
quote:
Originally posted by: pixlor
I'm sorry? People do use Fireworks to make buttons for navigation, images with text call-outs, logos, and many other graphics where text is involved. Graphics includes more than just photos.
Lorraine, of course text is part of a normal Fireworks workflow. I simply find it perplexing how a text bug - a patchable one at that - could make Fireworks "totally unusuable" to some users. I'm using CS4 every day, presumably the same version that many others use, and my workflow is just fine - and yes, it frequently does include text, not only photos. :-)
The current temporary fix that Adobe has provided introduces a single additional click to the text workflow to realign all shifted text. Is that such a big deal that it's worth four pages of complaints? And it's saddening to see that by page four, the thread pretty much degenerated to 2-post users breaking into temper tantrums and all-caps threats.
Truth is, all that was needed to be said and reported has already been done. There are proper channels to convey grievances to Adobe directly, and this user-to-user forum is not one of those.
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
I wonder how many people with the same problem read all this and then don't bother replying. I was about to just close the page and thought, no, if people don't say they're annoyed by the same problem then it won't get fixed. So here's another disgruntled user, having upgraded from CS3 to CS4. Wasted ages yesterday with this stupid text bug. I'm amazed to find this thread on the forum this morning and see that it hasn't been fixed after six months or so. I guess Adobe know there's no real competition...
Copy link to clipboard
Copied
The engineering team does not want to just post a "band-aid" for this problem. They are doing their best to create a complete fix, and are working hard to do so.
See this post and keep an eye on it for the patch announcement.
http://blogs.adobe.com/sarthak/2009/03/fireworks_cs4_updater_work_in.html
HTH
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Hi All,
An updater is being planned for Adobe Fireworks CS4 which will address the text bounding box jumping issues. The issue of internal error on startup due to various reasons is also being targeted from this patch. The patch is in a soon to be released stage.
..Sarthak
Copy link to clipboard
Copied
Update tomorrow!
http://blogs.adobe.com/fireworks/2009/05/fireworks_cs4_1003_updater_new.html
Copy link to clipboard
Copied
Now available:
http://blogs.adobe.com/sarthak/2009/05/fireworks_cs4_update_1003011_i.html
--
Nadia
Adobe® Community Expert : Dreamweaver
--------------------------------------------------
Unique CSS Templates |Tutorials |SEO Articles
http://www.DreamweaverResources.com
--------------------------------------------------
Book: Ultimate CSS Reference
http://www.sitepoint.com/launch/005dfd4/3/133
---------------------------------------------------
Copy link to clipboard
Copied
All is quiet here
Hopefully, the fix did well for everyone, as it did for me on my two machines.
THanks Adobe
h