X8 Ultimate Save pops up the Save As dialog

[lorathecrafter]

I just upgraded to X8 and started editing jpeg files created by my camera. Unfortunately, when I click 'Save' (or press Ctrl+S), the 'Save As' dialog pops up. When you are editing many files in a row it gets very annoying. X7 Pro didn't do it.

I tried to search for an option in the Preferences to get rid of this but didn't find anything useful. I enabled the auto-preserve feature but that didn't help.

Is it possible to avoid popping up the dialog when I just want to save a jpeg without changing its name or location?

[narrowgauge]

I'd say it's a coding error and needs reporting to Corel. (I can't find any settings for changing it.)

[Ken Berry]

I've just confirmed this also happens in my X8 but not X7. I will report it to Corel.

[hartpaul]

Same here on Win 7 . Works OK in PSP X7 and not in PSP X8.
I even tried in window mode hitting the X (to close the file) and then hitting the Enter key to accept the default save. In X7 it saves while in X8 it defaults to the Save As dialog box.
Also minimising each image worked on and then using Windows > Close All and Save Selected also diverts to the Save As dialog box. Good reason for people to continue using the older versions of PSP until Corel get their act together.

[trueblue]

I do believe this is their new design of saving an image! You are able to apply compression and further options. Once the image is saved, the Save As window will not show again.

[narrowgauge]

Simone at customer support replies that this issue was reported to the development team last Friday (14th August) but can't say when it will be fixed. The case has been passed on to the engineering queue she says, which is counting reports.
Seems to me that the error is pretty basic and shouldn't be dependent on the number of users reporting it to get it fixed.

[lorathecrafter]

Thanks.

Hope it will be fixed in the foreseeable future

[trueblue]

Simone at customer support replies that this issue was reported to the development team last Friday (14th August) but can't say when it will be fixed. The case has been passed on to the engineering queue she says, which is counting reports.
Seems to me that the error is pretty basic and shouldn't be dependent on the number of users reporting it to get it fixed.

We were told by the devlopment team that this feature is by design.