PhotoFlow 0.2.7 released

I have prepared a testing package from the current stable branch: https://filebin.net/am1v89iszewyj11g

It should:

  • fix the annoying crashes when deleting layers
  • provide a better behaviour of the “file export” dialog wit respect to file types and file extensions (you will maybe tell me if it is more intuitive or not)

Concerning the widgets layout, would you find more user-friendly a configuration with the layer list on the left of the preview, and the histogram and tool controls on the right of the preview?

I prefer to give you straightaway a quick & dirty feedback as I have some bodies to burry

EXPORT
Now name of origin file + extension’s there (.jpg) - that’s nice =)
but when I change to export the file as tif, extension remains .jpg
Why is there a All supported formats in the type the drop menu?

:cactus: Sugestion: is minimal but IF IT’S POSSIBLE where the drop menu is - ideally on top, near file name’s box - you can place a couple (as right now there’s only jpg and tif options) buttons with the type file. So when you export name of origin file is there by default and when you select type, extension is added to whatever name you’ve chosen.

BTW - on the tips export image to raster image format is too… detailed, what about export image? Same with others, save photoflow project and save as photoflow project or save a copy of photoflow project, if radicalizing you could even take out photoflow; save, save as, export

Remember the bug with post normalize in the GMIC film emulators :wink:

 
DELETE/CRASH

Regarding deleting several selected layers, no crash, CHECKED

But PF crashed several times when changing the file in raw uploader
 

Positioning wise I find it good as it is :golf:

Hi !

For Windows 10, is there an equivalent path ?
NB: it seems that PF does not show the hidden folders, then this may be not possible …
Thank you
Philippe

The default.pfp file is not yet supported under windows, but I can add this feature rather easily… I’ll prepare a test installer in a couple of days, if you want to give it a try.

Great ! I’m not as expert as other contributors here but I would be happy to help.


 
 

 
 

NOTES on possible PF’s cosmetics

• When clicking show/hide checkbox layer doesn’t get selected, ONLY clicking over layer’s name selects layer

• Histogram from Rawtherapee, personally don’t like the grid but the view options are great

• Free positioning of viewer at any zoom %

• Save and export options could be darker and get lighter when you hover over them

• When selecting working file (top) the active one goes lighter and slighty downwards

• When selecting Layers / Masks / ??? tab goes slightly upwards and lighter, obviously previously selected opposite luminosity and desplacement

• Pin (solo mode) turns green when activated

LIVE mode

One click layer and settings show, click layer again and they hide; ideally floating window if not aligned by center.
Possibility of pinning the window

Just for fun, In live mode Gioconda’s button turns green, if pushing further she closes her eyes when not in live mode, slighty desaturated too :stuck_out_tongue:


The name of the botton is just a breeze thought, in any case I’ll most def put your name next to open source *)=

1 Like

Hi!

Thanks for the suggestions, I really appreciate!

I’ve also been doing some UI tests over the weekend, also following what @assaft suggested in the other thread… here is a possible simplified layout:

Smaller sliders, and controls below the layers list. It is a bit tight on a 800px high screen, but should be OK at 1200px or more.

3 Likes

Nice, less clutter :seedling:

By simply moving open, save, etc buttons to the right you’ll gain a bit of precious extra vertical space… I doubt anybody would be opening more than 4 or 5 files in a single session. Just my 2c

So where did basic adj, curves and the others go?

I’ve put the buttons array back on the left of the layers list. The top open/save/etc… buttons will eventually be replaced by menu entries with shortcuts…

Here is how it looks like on a 1920x1200 panel:

It seems I still have to take a look into this… will do it this evening.

Thanks!

@phweyland I found the problem with your preset: it is the presence of the “&” character in the layer names that breaks the parsing of the preset file. I have to find a fix for this…

A bit old now… Is the default.pfp feature available for windows now ? How to use it ?

Is there something new about default.pfp ? If yes where should we store it ?

Not yet, but I am currently working on the windows package and I will look into that in the next days. Currently my main goal is to prepare a reliable 64-bits win version (the old ones are 32-bits), which might also fix the problem you reported here.

That sounds great !! :slight_smile: Thank you Carmelo

Just tried the today ppa photoflow-git:
20170716 Photoflow stable.txt (44.4 KB)
My last working install has been done on 30/05/2017.
Before installing a new version, I save the entire VM. Is there an quicker way to revert back to the previous PF install ?

Not to my knowledge… maybe @Dariusz_Duma knows a way to revert to an older package version from his PPA?

@phweyland the crash you are reporting looks very much like the same issue I have under windows… and seems to have been introduced by the last update of the RawSpeed library from Darktable.

Could you maybe give the AppImage package a try? You can get the latest one from here (grab the package with the most recent date, 20170702 at the time of writing). I do not have a good internet connection at the moment, so I cannot do any debugging before a couple of weeks…

@Dariusz_Duma would it be possible for you to provide a debugging version of the photoflow-git package in your PPA? The cmake build configuration provides a standard RelWithDebInfo target for this purpose. That would greatly help to debug this kind of issues.

@phweyland if the debug package becomes available, then a GDB backtrace would be really helpful.

With the today appimage : 20170716 Photoflow.Appimage.txt (60.8 KB)
About GDB, is that the same syntax as under windows ?

Looks like the same problem as the PPA version… which Linux version and CPU do you have?

The gbd syntax should be the same under windows and Linux.

Ubuntu 16.10 (as VM / Windows 10 host) & i5 760