PSP 2023, 2021, 2018 - 1st existing picture bug

[Shokakusan]

So I prefer to use NOTEPAD++ instead of plain old notepad. After installing a trial of PSP 2023, I changed the Python Source Editor (File \ Preferences \ File Locations and find Python Source Editor). At this point when I drag and drop an existing picture onto PSP 2023, make a change, and type Ctrl-S (to save), PSP 2023 incorrectly prompts me with the Save As window. It should simply save the changed picture (and for all subsequent existing pictures, PSP2023 does just save the changed picture).

So I tried changing back to Windows NOTEPAD (C:\WINDOWS\NOTEPAD.EXE) and found that the problem still exists after re-starting PSP. When I save a change to the 1st existing picture, I get prompted as if it were a new file (confusingly, after getting prompted to Save As a new file, I get prompted to over-write the existing file). As further research into this bug, I have even reset PSP as well as re-installed PSP to see this same bug re-appear after I change the Python Source Editor (even by simply over-typing NOTEPAD.EXE).

What is astonishing to me is that this bug has existed since PSP 2018 (I currently have PSP 2021 and I re-installed my old copy of PSP 2018 to verify). I guess that nobody changes the Python Source Editor (frankly, the ability to save scripts and re-use them is extremely useful to me, thus I use a more powerful editor than Windows notepad).

The work-around for this problem is to open PSP and leave it open all the time. As my PC has generous memory (32GB RAM), that works for me, but I wish that Corel would fix this bug.

I would like to upgrade to PSP 2023, but I am reluctant to upgrade--what other bugs have not been fixed?

[LeviFiction]

This is not a bug, it's supposed to work this way now, and has nothing to do with the Python Source Editor (I use VS Code myself for the intellisense code completion)

I don't remember when but at one point PSP changed how they do JPG default compression. Which annoyed people and through several changes arrived at the current "Choose your default settings on first save" model. Which uses SaveAs regardless of file type to let you choose the default settings. All subsequent "Save"a default to those settings.

[Shokakusan]

I am not sure that I follow what you are saying, LeviFiction.

When I re-downloaded PSP 2021 (as well as when I downloaded a trial of PSP 2023), if I edit an existing picture without customizing the Python Source Editor, and save it, PSP just saves it without any prompted windows.

Once that I customize the Python Source Editor, edit an existing picture, and save it, PSP prompts with the Save As window. As you say, at that point, editing any further existing pictures will just save the changes until I restart PSP.

I can understand prompting for Save As when creating a new picture, but for an existing picture, I think that PSP should just re-save the file--if I want to change the JPG compression, I can explicitly use Save As for an existing file. Prompting with Save As for the 1st existing picture after each restart of PSP (no matter how long ago Corel change this) sounds like a bug to me.

Am I missing something?

[LeviFiction]

I have PSP 2020 and 2023 installed, I have not changed the Python editor. I open a JPG file and hit Save. It runs Save As. This is normal. I haven't change the default editor in the current installations. It's not contingent on the python editor being changed. It's not a bug. It's how it's designed to work.

Here is a video showing this: https://drive.google.com/file/d/1ruJSv4 ... sp=sharing

I open PSP, show that the python editor is still Notepad (it's a recent install)
I open a JPG
perform an edit
Hit Save
It opens the Save As dialog
I do this with both 2020 and 2023.


When I say PSP wants to know what level to save JPGs at, I mean for the entire session. All JPGs when you hit Save will use this compression level. Because compression levels between different JPG engines are not equal. Level 20 with PSP may be level 10 with another. So rather than assuming you want to save an individual JPG with the same level it was originally saved with (which might be different and freak people out when it goes from 5MB to 200kb when the only change you made was to bump up the vibrancy) it'll use a default for all JPGs during that session that you're forced to pick.

If anything the bug is that it doesn't do it consistently and simple things like can break it. For example if I open a PNG and hit Save, this prevents the Save As dialog from showing up when saving edits to a JPG. It's a poorly designed feature, but not a bug.

[JoeB]

@LeviFiction, I have been following this thread and maybe I'm missing something. If I read the OP's last post correctly, if he edits an existing image and hits Save it just saves. If he then customizes the Python Editor and then follows the same procedure as previously (i.e., edits an existing image and hits Save, he gets prompted with the Save As dialogue, which did not happen when he edited an existing image and hit Save prior to changing the Python editor. Perhaps I misrread your reply but I didn't see where it addressed that specific workflow where the only thing that seems to have changed was the Python editor and suddenly the Save As dialogue appears when hitting Save after editing an existing image.

[LeviFiction]

@JoeB - even so my video demonstrates that changing the Python library is unnecessary for this to happen. And their first claim indicated they hadn't realized it was happening previously and made the connection to a very recent change they made.

The second post is vague and can be interpreted differently. I did not interpret it the way you did. I cannot replicate the bug with that workflow either. And they're description still sounds exactly like the default behavior and not a bug related to changing the Python editor.

My steps in replicating your interpretation of their claims:
1) I reinstalled PSP.
2) I opened a JPG file
3) I made a change (ppi resolution)
4) I hit Save - the Save As dialog appeared.

So I then started over
1) I reinstalled PSP (different computer to speed up the test)
2) I opened a PNG image (if the first image is a JPG I always see the Save As when hitting Save for the first time) It's the only way I can avoid the Save As dialog.
3) I changed the resolution and hit Save
4) I changed the PSP editor
5) I opened a JPG (through drag and drop)
6) Changed the resolution
7) Hit Save. No save as dialog.

I cannot replicate the issue and it sounds like the default behavior to me.

[JoeB]

Thanks for the clarification! I just brought it up in case the OP might make the interpretation that I did - because he and I seemed to be on the same track from what I read - and bring it up anyway.

[Shokakusan]

LeviFiction, I owe you an apology - I stand corrected. Only when I went back to re-install PSP 2018, did I see that saving the 1st existing .jpg file just saved the file. Re-installing 2021 and a 2023 trial, it performed as you said (regardless of changing the Python Source Editor).

Given that "... at one point PSP changed how they do JPG default compression. Which annoyed people and through several changes arrived at the current "Choose your default settings on first save" model. Which uses SaveAs regardless of file type to let you choose the default settings. All subsequent "Save"a default to those settings.", I will live with this behavior as it is today.

For my two cents (and it isn't worth much at this late date), this behavior is strange given that PSP remembers changes to the default JPG compression across each restart of PSP.

Anyway, this behavior is NOT related to changing the Python Source Editor and looks to have been introduced sometime between 2018 and 2020. As strange as it might seem to me, as a prior developer for a software company, I can't imaging that Corel will want to re-visit this issue--consider this closed.

P.S. Thanks, JoeB for helping out.