User Interface:
The list of layers moves up and down if you have a layer selected or not. Its annoying when editing a mask as the layer selection is empty after you switch to mask mode, and when you click the back button. I’ve also had problems with layers getting moved in the stack when I click on them because photoflow is mistaking the UI movement for a drag and drop operation.
Raw Developer:
The advanced settings (white level etc.) don’t seem to do anything. Mostly this isn’t an issue, but for some raw files (e.g. Morning mist in salted meadows (Arcachon)), the white clipping level is slightly wrong and the sun comes out magenta.
Scale and Rotate:
The ‘height’ scale doesn’t seem to do anything. Again, not a problem usually (different X and Y scales is unusual). I noticed it because I tried to load a Nikon D1X raw file from a recent Play Raw (can’t find the link, sorry) and it comes out stretched horizontally.
I am finding that you can’t edit the rotation points on the image once you have set them (unless you move the angle slider a bit - that seems to fix it).
Crashes:
I don’t have a reproducable test case, but I seem to be getting more crashes when turning layers off recently. It seems to be the histogram that fails (usually by accessing a nil pointer).
Crop:
The new UI seems nicer than the old one. It seems easier to see where the edges of the crop are than with the previous one. I don’t think you need to change the mouse cursor - having the handles on the crop area appear and disappear as you mouse over them is enough feedback for me.
Opening .pfi files saved on Windows (e.g. this one: Volterra, Italy) crashes the macOS version of Photoflow. Manually editing the path in the raw loader part of the .pfi fixes this.
Was wondering if it would be possible for a G’MIC update at this juncture, and as a bonus, provide the user a way to point to the system G’MIC so as to have the ability to update it him or herself. The related bug would be when I type something into the G’MIC Interpreter and press Enter, PF crashes.
A forward mouse roll causes a decrease in the value of the selected slider and a back roll causes an increase. It is the opposite in other applications like darktable and is counterintuitive (at least for me).
Hints : Is it too much work to add hints for (more) buttons&menus that will be shown when the mouse pointer is over them? As an example, when the pointer is on (selected) “RAW developer”, the hint may read “Double click to adjust”… (I know there are already some).
Highlight and shadow clipping warnings do not seem to work for “exposure” in the “RAW developer” while they do for the exposure in “basic adjustmen” menu (missing t is not mine : ) ) . Is this the expected behavior?
@bc_the-path#2 I have asked for documentation for a long time. Each module has an italic i button but the info window is almost always empty. Tool tips are the natural progression of the info window. Looks like what other popular apps do.
I wonder if there is a way for interested users to contribute to this. @Carmelo_DrRaw mentioned the possibility at one point.
@bc_the-path@afre
Yes, one can provide a brief help text for each tool. There are some examples here: PhotoFlow/help/en at stable · aferrero2707/PhotoFlow · GitHub.
The easiest way to contribute is to provide a text file for a given tool, I will then take care of giving it the right name and extension. The folder is structured in a way that should allow multi-language support, but for now english would be already enough.
Whether to put the help text into the info window or a tooltip (or both) is open for discussion and suggestions…
There is room for both: the info window providing an overview and the tool tip parameter notes.
I know something else you could add that won’t be too much effort (I think). Remember how I requested the ability to see more of the samplers module on my small screen? Well, could we have the same thing happen for the histogram: double click to undock into a window that I could enlarge? ATM, the histogram is rather small to see if any of it passes the clip range. Speaking of clip range, would it also be possible to have a line at the mid point (0.5)?
Do you have natural scrolling enabled on your system? What package version are you using? What GTK version? This commit seems to be related to what you observe… if that is the case, I am afraid it is a general GTK bug and not photoflow-specific.
No, it isn’t, unless you have checked the “clip overflow values” in the RAW developer. The screenshot below shows an example of settings that produce correct highlights warnings on my system:
I am gradually adding tooltips, starting from the various sliders of the RAW developer module. I will commit a first update later today…
So far I have not tested the GTK3 version very extensively… could you eventually try to grab the latest GTK2 appimage and see if you get the same behavior? Just download the package, make it executable, and run it…
I did try the GTK2 Appimage. Just the same behavior. The link you referenced above for a commit seems like describing a similar problem.
All sliders in my other applications run normally like those displayed by “gtk3-widget-factory”.
ADD: I have found the “Natural scrolling” adjustment. If I turn it ON, PhotoFlow sliders behave NORMALLY! But, darktable and GIMP start MISBEHAVING.
