Apply an action to all pages.

[PhilM]

If I test my Powershell script from within Windows Powershell ISE, it opens the Beta version instead of the regular version.
If I launch the script from the explorer from within Automation folder (in the regular version folder) ; then it works with the regular version.

Phil

[shijan]

Could those Powershell scripts become visible and launchable from within Photoline menu "Filter/Script" ?

Yes, put script file in special folder ~/Library/Preferences/PhotoLine/Automation

[PhilM]

Could those Powershell scripts become visible and launchable from within Photoline menu "Filter/Script" ?

Yes, put script file in special folder ~/Library/Preferences/PhotoLine/Automation

My script is in the "Automation" special folder.
But not listed in the Scripts menu : /Filter/Script.

[Martin Huber]

My script is in the "Automation" special folder.
But not listed in the Scripts menu : /Filter/Script.

PowerShell scripts don't work yet in the "Automation" folder.

Martin

[Martin Huber]

If I test my Powershell script from within Windows Powershell ISE, it opens the Beta version instead of the regular version.
If I launch the script from the explorer from within Automation folder (in the regular version folder) ; then it works with the regular version.

That's strange. On Windows, the registry contains entries that define which application is used for automation. PhotoLine writes these entries when being installed.
So automation should always use the latest PhotoLine version that you have installed.

You can overwrite the current entries by starting PhotoLine from command line with

Code: Select all

PhotoLine.exe /RegisterPerUser

Martin

[PhilM]

If I test my Powershell script from within Windows Powershell ISE, it opens the Beta version instead of the regular version.
If I launch the script from the explorer from within Automation folder (in the regular version folder) ; then it works with the regular version.

That's strange. On Windows, the registry contains entries that define which application is used for automation. PhotoLine writes these entries when being installed.
So automation should always use the latest PhotoLine version that you have installed.

You can overwrite the current entries by starting PhotoLine from command line with

Code: Select all

PhotoLine.exe /RegisterPerUser

Martin

I have re-installed Photoline 24.01 to be sure it is the latest.
I have also executed "RegisterPerUser".
And Powershell ISE still invoke PL Beta.

My VBS scripts work as usual with PL 24.01 no problem.


Philippe

[Martin Huber]

I have re-installed Photoline 24.01 to be sure it is the latest.
I have also executed "RegisterPerUser".
And Powershell ISE still invoke PL Beta.

Did you quit PowerShell ISE before reinstalling PhotoLine?

PowerShell ISE keeps the connection to PhotoLine active as long as it is running. So if you don't quit PowerShell ISE, it will still be using the old assignment:
- PL Beta is registered for automation.
- You start Powershell ISE and execute a script.
- PowerShell ISE creates a connection to PL Beta.
- You register PL 24.01.
- PowerShell ISE will still be using PL Beta.

So you have to quit PowerShell ISE before registering PL 24.01. Before changing the registration, make sure that no PhotoLine is running in the background (by using the Task Manager).

Martin

[PhilM]

I have re-installed Photoline 24.01 to be sure it is the latest.
I have also executed "RegisterPerUser".
And Powershell ISE still invoke PL Beta.

Did you quit PowerShell ISE before reinstalling PhotoLine?

PowerShell ISE keeps the connection to PhotoLine active as long as it is running. So if you don't quit PowerShell ISE, it will still be using the old assignment:
- PL Beta is registered for automation.
- You start Powershell ISE and execute a script.
- PowerShell ISE creates a connection to PL Beta.
- You register PL 24.01.
- PowerShell ISE will still be using PL Beta.

So you have to quit PowerShell ISE before registering PL 24.01. Before changing the registration, make sure that no PhotoLine is running in the background (by using the Task Manager).

Martin

Fixed !
Powershell ISE was running when I did the re-install/registering ...

Thanks

Philippe