@chroma_ghost Thanks for your feedback, very much appreciated!
Now coming to the individual points:
- I agree fir the visual % scale, I will add this
- you can already toggle between 100% and zoom-to-fit with Ctrl-double-click on the preview area.
- zooming with the mouse wheel is not possible at the moment, for a simple technical reason: the widget used for the preview area reserves the mouse wheel for adjusting the vertical scrolling of the image, and I have not yet found a way to intercept and customise this behaviour...
- PhotoFlow has no SSE optimisations yet, it is pure C++ code that runs in multi-threaded mode. So there is certainly some margin for improving the speed in future. So far I preferred to focus on stability, and I'll start doing optimisations on tools that are already rock-solid.
- Some tools are intrinsically slow, so there is some limit to the achievable improvements... could you check the speed when using only "simple tools" like curves, basic adjustments, gradients, uniform fill?
This is actually what the code already does: only the visible portion of the preview is re-computed when some parameter is changed.
Some slow tools automatically perform caching of their output image (for example the RAW developer, or the local contrast when bilateral blurring is selected). The cached image is computed in the background, and automatically re-computed whenever needed.
I totally agree, and it is in my todo list
No, this is not existing.
Did you try this with RAW or Jpeg images?
What do you mean? The top layer is at the top of the stack, like in gimp...
That's a very nice suggestion, and should be easy enough to implement
There are two possibilities already available:
- the gradient tool has a "radial" option
- the "path mask tool"
Anyhow, I indeed plan to include some additional basic shapes for selections, like rectangles, ellipses, etc...
This is actually not possible, because the output of a given layer is always computed on-the-fly, except when it is cached
It is a NULL operation that can be used to "mark" a certain point in the layer stack. In next version, I will add the possibility to enable the caching of a buffer layer, so that one can pre-compute the image at a certain point of the edit for speeding up the computations...
I hope this clarifies most of your questions...