Hi everyone. Firstly thanks for the help this forum has already provided. I have been using Adobe products for over 18 years now, and one ever-present aspect of being an Adobe user has been the general poor support, seemingly untested updates/patches, incompatitbility with OSX and Apple GFX drivers, and most of all; known bugs which survive several major software updates.
One such bug is currently causing serious problems for me, and I could do with knowing how to work around it, or failing that, make adobe themselves aware enough to fix the problem for the next update or major release.
Dreamweaver will not refresh remote images in the design view. Ever. No amount of refreshing, right clicking, select sourcing, size resetting will fix it - I simply have to quit and restart Dreamweaver. As far as I am aware, this problem has existed in several if not all versions - I have always restarted the program to refresh remote images, and that was fine for making the odd HTML email, but now my day-to-day work has changed and its becoming a real problem.
Also - only a small one, but equally annoying - "Reset Size" is always greyed out for remote images. However, the little icon next the pixel dimension in the properties box works just fine. Its just that I've always been a right-clicker - I don't tend to use the properties box unless I really have to. This problem may only be present in CS5.5 on OSX.
Current setup: Mac Pro, OSX Lion, CS5.5 w/ all patches/updates.
I have seen around 12 discussions already detailing my first point, however all of them seem to have since died a death, or been mysteriously marked as 'answered' with no apparent solution. I appreciate that adobe would prefer you to use the site manager to define and manage local and remote sites, and to use the built in FTP to up/download files, but upon testing, it seems to make no difference. Also to be brutally honest, the site manager and FTP don't work very well compared to even freeware alternatives.
Any help or advice on the problem itself would be much appreciated, but I feel some assistacnce in getting Adobe to acknowledge these ancient issues would be more valuable to the general community.
Thanks in advance