Auto-save and Auto-load of pts

[GoogleCodeExporter]

Hello,
It's about a week I'm using Photivo, it's a great sw! I used A****S**t, and 
it's a good program, fast and easy to use, but after comparing some 
developments (expecially "hard" ones) I was so impressed than I decide to 
choice Photivo as RAW developer.
There is just a little point I prefer in previous software (but also in 
RawTherapee, Darktable, etc.): the possibility to auto-save and auto-load the 
setting file: during the work the pipe modifications are saved in 
PICTURE_NAME.pts, while when I open PICTURE_NAME.RAWfile, Photivo should verify 
and load PICTURE_NAME.pts, and it should be useful if it places a little mark 
to indicate in FileManager the file have already a pts setting file (just like 
AfterShot, RawTherapee). Of course if you want to save a different version,you 
could disable autosaving, or create a new pts.
As you can see, it's not an important thing, and I don't know if it ìs a 
simple or difficult modification (programming languages are for me as ancient 
egyptian language!), but in any case I give you my little suggestion...
Thanks again for your great work!
Andrea

Original issue reported on code.google.com by maino.an...@gmail.com on 4 Sep 2012 at 6:51

[GoogleCodeExporter]

I would strongly support this wish! Photivo is great software, but a 
raw-workflow without exporting every manipulated image to tif or jpeg is 
difficult as long as one has to load the previously made settings manually 
every time a photo is opened.

Matthias

Original comment by hicnun...@gmail.com on 11 Oct 2012 at 9:26

[GoogleCodeExporter]

I’ll mark this postponed for the moment. The whole preset handling stuff is 
the Next Big Thing I plan to work on but unfortunately time is limited and 
there are a couple of things that need to be finished first (say the local spot 
filter ...)

What I imagine for the “presets project” is a) a better way for presest 
management than the standard file dialogs we have now and b) attach specific 
presets to specific files; and that includes some kind of auto preset 
loading/saving as well. For (b) we already have a good part of the code to 
switch to XMP based presets from domlyons’ GSOC project that needs to be 
integrated into the “production ready” Photivo code anyway.

So in a nutshell: Don’t expect anything in the immediate future, but 
”Preset 2.0” ;) will happen. As an immediate workaround you can save your 
current pipe config at any time with a right click on the Save button. 

Original comment by brother.john.gm@googlemail.com on 12 Oct 2012 at 9:28

• Changed state: Postponed
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Thank you for the reply.

As a workaround one can use the following script in Windows that loads the 
settings file with the image:

@echo off

set IMAGE=%1
for %%i in (%IMAGE%) DO set PATH=%%~dpni.pts
if exist %PATH% (
"C:\Program Files\Photivo\photivo.exe" --pts %PATH% -i %IMAGE%
exit
)
"C:\Program Files\Photivo\photivo.exe" -i %IMAGE%
exit

Original comment by hicnun...@gmail.com on 14 Oct 2012 at 7:00