That's interesting. I find Fireworks' Optimize/Image Preview settings to be “sticky”—that is, the settings of the last saved file or the last opened file are remembered for the next new file. So there is no default, per se, but if you save a file, its optimization settings will also be saved. And those settings will carry over into the next new file that you create.
I think that's what's happening, anyway.
I'm using Fireworks CS6 on Mac OS 10.6.8 (Snow Leopard).
Thanks for the response Groove. To tell the truth, I was laboring under the same apparent delusion. I am all about speed, using keyboard shortcuts where possible, inventing shortcuts where none exist, etc., so you can imagine my frustration at having to slow down and move the cursor when I don't think I should have to. Maybe it works on a Mac, but not a PC.
My procedure is to drag a pre-sized photoshop image into FW. Do what I'm going to do with it, do the keyboard shortcut for export, (Control>shift>x) and the export dialog box jumps up with the gif settings. Export the image, usually as a jpg, to whatever site image folder I am working on, close the image file and save as a png in a resource folder. Am I following a flawed procedure>?
Not sure what you mean by "drag"... I do find the Export settings somewhat responsive to the original file type, so that a JPEG being opened in Fireworks will tend to default to a JPEG Export setting. (Are you opening JPEGs, GIFs, or something else?)
But going back to my previous comment, it might be helpful to Save the file after exporting to "lock in" a preferred setting for the next file. On the other hand, I think that exporting should also serve to "lock in" a preferred setting, without the need to save. So I'm not sure about this.
I did notice this: In the user library Application Support folder for Fireworks CS6, there's a folder called Export Settings that includes a text file called "last-settings" that apparently does nothing but record the last settings used in the Optimize/Image Preview panel. Again, I think that either saving or exporting a file should trigger a rewriting of this file's contents.
This just reiterates what I've already suggested regarding "sticky" Optimization settings, but it's nice to see it in print:
Note that the remembered settings will be applied to new documents. It doesn't really specify what happens when opening a pre-existing, non-Fireworks document, such as a JPEG. (Presumably this might depend in part on the application that originally created the file.)