"File Save" does "Save-As" instead

[LeviFiction]

Technically they broke it and then attempted to fix their breaking.

Also, no one is suggesting that it doesn't need to be fixed. Just that it's possible to work with until it is fixed. Again holding SHIFT to hit the save button prevents the dialog from popping up. If it's still too much by comparison you can use a quick and easy script that saves and then closes the current document all in one key press making it faster than in X2. Again, only meant as a workaround until it can be fixed. No point in not offering potential options that don't require you to have an older version of PSP to work with.

Yes it needs to be fixed. And I like the ideas presented in this thread. I hope they listen.

[JoeB]

Any extra clicking and navigation to extra areas is a pain and takes extra time. Currently I select the crop tool once and as each image is saved and disappears from the screen the next image already has the crop rectangle present .
Currently:
1. select crop tool (with preset already chosen) = navigate and 1 click
2. adjust crop rectangle
3. Hit enter
4. Hit Red X = navigate and 1 click
5. Hit Enter
Total 2 navigates 2 clicks 2 enters. (the left index finger remains over the Enter key so don't even have to look down at the keyboard.)
6. repeat from 2 to 5 (So second image is one less navigate and click as don't have to go to the crop tool each time)

With a script
1. navigate to script bar and click Start = navigate and 1 click
2. Adjust crop rectangle
3. Hit Enter
4. hit Enter (Save As dialog)
5. Navigate to Yes ( file already exists so overwrite) and 1 click
6 Repeat from 1 (so each image has the same number of operations = no saving in time)
Total 2 navigates, 2 enters, 2 clicks so the same, but have to navigate to the script bar each time to get the crop to show. So no real saving.

I'm presently trying to complete a project so don't have time immediately to try creating the script I was envisioning. However, with a script to do everything except adjusting the crop tool and execution mode turned off I'm not sure why you have to keep hitting Enter, etc. Again, I haven't tried to create the script yet and am certainly not a script expert, but that's my initial thought. I'll see if time permits this weekend to try creating one. In the meantime, maybe someone like LeviFiction can say whether or not it's even feasible. As I said, however, it is possible that the Pause Script might be necessary to do this but again I won't know that until I have had time to try it.

EDIT: One thought did come to mind regarding a possible script, however. If the crop tool is still active after one image closes it will (should) move to the next open image. This could cause an issue if the script starts by calling the crop tool. So the script would likely have to end by calling another tool so that clicking the script to start it on the next image could then call the crop tool from whatever tool the previous run of the script had called.

[LeviFiction]

I don't see a need for the pause script. Just a script that saves and closes the current image specifically for hartpaul's case. I really don't see the point of pausing at all. But using "SelectTool" to select the crop tool will not throw any errors if the crop tool is already selected so that's not a problem at all if you did use the pause script.

Very simple script. Just simply recorded it's not even a custom script.

Code: Select all

from PSPApp import *

def ScriptProperties():
    return {
        'Author': u'',
        'Copyright': u'',
        'Description': u'',
        'Host': u'PaintShop Pro',
        'Host Version': u'18.00'
        }

def Do(Environment):
    # EnableOptimizedScriptUndo
    App.Do( Environment, 'EnableOptimizedScriptUndo', {
            'GeneralSettings': {
                'ExecutionMode': App.Constants.ExecutionMode.Default, 
                'AutoActionMode': App.Constants.AutoActionMode.Match, 
                'Version': ((18,0,0),1)
                }
            })

    # FileSave
    App.Do( Environment, 'FileSave', {
            'WorkingMode': 0, 
            'GeneralSettings': {
                'ExecutionMode': App.Constants.ExecutionMode.Silent, 
                'AutoActionMode': App.Constants.AutoActionMode.Match, 
                'Version': ((18,0,0),1)
                }, 
            'DefaultProperties': []
            }, App.TargetDocument)

    # FileClose
    App.Do( Environment, 'FileClose', {
            'GeneralSettings': {
                'ExecutionMode': App.Constants.ExecutionMode.Silent, 
                'AutoActionMode': App.Constants.AutoActionMode.Match, 
                'Version': ((18,0,0),1)
                }
            }, App.TargetDocument)

Again, not intended as a fix or solution. Just a work around until Corel gets their act together. Meant to handle the issues people are experiencing and cases demonstrated to us.

Here's a video demonstrating the script in action

https://drive.google.com/file/d/0B8FlFL ... g3cDg/view

[Kathy_9]

How do you avoid the unexpected indent error?

[LeviFiction]

Depends on where you get the error. What line does it say the error is on? This is a direct copy and paste from my code editor and I get no such errors so I can't tell you. Though usually this comes from either using the wrong spacing in the code somewhere. Examples of incorrect spacing include the wrong number of spaces or using a mixture of tabs and spaces. I never use tabs. I always use 4 spaces per indent.

[JoeB]

Excellent work Levi! Here I was thinking of a more complicated script that worked with the present Save peculiarities and you simplified the whole thing by completely circumventing them. Great stuff! And while only a workaround until Corel fixes things, once again I would like to suggest that the script be posted in the Scripting group just because it is a script that people might find useful while browsing that group.

[Kathy_9]

Depends on where you get the error. What line does it say the error is on?

Executing RunScript
File "<string>", line 1
from PSPApp import *
^
IndentationError: unexpected indent
Executing RunScript
File "<string>", line 1
from PSPApp import *
^
IndentationError: unexpected indent
Executing RunScript
File "<string>", line 1
from PSPApp import *
^
IndentationError: unexpected indent

[JoeB]

I don't get any such error. Are you sure you didn't accidentally put a space at the beginning of the script, maybe in front of from PSPApp import?

[JoeB]

I have tried the script and it works for me as a Save workaround. However, now I know why I was thinking of a more complicated script. As I mentioned to hartpaul, I was thinking of automating the whole process, starting with calling the Crop tool, allowing the user to adjust the crop, then hitting the script again to complete all of the other steps, including closing the image and then opening the Crop tool on the next open image. That would help him save those extra steps of hitting enter, etc.

[Kathy_9]

I don't get any such error. Are you sure you didn't accidentally put a space at the beginning of the script, maybe in front of from PSPApp import?

Positive that I did not add a space; accidentally or otherwise. Of course, that doesn't mean that I didn't do something else wrong.

Here are the steps I took:

Clicked on Select All
Right-click "Copy"
Opened Notepad and immediately clicked Ctrl+V
Saved as a .pspscript file in Scripts Restricted

It must be something I'm doing wrong because this is not the first script this has happened to.

[LeviFiction]

I just did what you did Kathy, and it has all of the text indented 4 spaces more than they should be. So the first line actually starts four spaces in when there should be no spaces at all. And the same with the rest of them. Also because it saves you may have to run it in Scripts-Trusted and not restricted.

I've uploaded the script to the scripts board so we can stop taking up space on this one.

[JoeB]

I did Select All and copy also, and opened X8 then opened a test script I keep for this purpose and selected the button to edit the script. That opens the script in Notepad also as the editor, and I pasted the the script there and saved it with a new name. The selected save Encoding mode is ANSI. There were no spaces added. Could it be that you two have a different encoding mode selected that might be causing the issue? I also have Word Wrap selected as a default option. There aren't a lot of available options in Notepad.

[LeviFiction]

It added the spaces upon paste, not save. It did this in both Notepad and Notepad++.

[JoeB]

It added the spaces upon paste, not save. It did this in both Notepad and Notepad++.

Can't help I'm afraid. I opened Notepad++, came back here, did Select All, right-click copy, back to Notepad++, right-click paste, and no extra spaces. I'm on Windows 8.1 if that makes any difference. I've done this procedure with various scripts I've come across on this forum (sometimes right-click copy and sometimes Ctrl+C) and never had this issue with any of them.

[hartpaul]

Thanks guys for spending time on trying to do workarounds.

My workaround is to continue using PSP X2 where I do my first save using Save As and change the Compression. Then all other saves use that compression til I change the compression again.
At least various versions of PSP can be installed and work together without conflicting.
The script that has been worked on is limited in that it does not allow any other variations . eg say during the cropping I note that some of the images need a levels adjust and some others a red green blue correction.
This is not possible in a script which expects the same operations each time with some variation in the settings for that operation, but not some operations left out and others added.
So until Corel gets it right (and it was right back in X2 so all they would need to do is look at the code from there to correct it), I will still use older versions where it was right.

If Corel continue to persist in making unwarranted changes and breaking things that worked then I will probably not update as often. (have two purchases of each version from X4 upwards so that will save me bit)