Improve Capture One
Request a new feature, or support for a camera/lens that you would like to use in Capture One.
Request a new feature, or support for a camera/lens that you would like to use in Capture One.
I often find myself fighting with the Layers and Masks panel, especially on a laptop. It would be helpful if there is more flexibility to how it can be sized.
Currently small is too small (shows only 2.5 rows), and Medium is often too big for my needs of about 5-6 layers except in rare cases, which results in a lot of wasted space and the scrollable area pushed down.
Auto size is incredibly stupid - it will create a huge Layer area even when there's only 1 layer!
What I want is to be able to arbitrarily resize it to my liking by dragging the bottom - just as you can do when the Layers panel is dragged into a floating window. Or an option to shrink to fit the number of layers I currently have by either expanding or contracting.There's so much other customization with the C1 interface it seems odd that this is still so primitive.
|
Current workaround
Toggle between small/medium, or create a floating panel. Both require extra steps, sometimes on a per-image basis. The floating panel is still visible when looking in full screen view, meaning it has to be moved out of the way, and then put back when leaving full screen, adding more inconvenience. |
The Capture One team have made a number of great improvements to the app in recent months. But the experience of using Capture One is being held back by the odd interface excise (like a tax on your attention) that is the panel sizing function. Instead of a field that updates dynamically based on the height of the contents, or via a grab handle at the bottom of the panel divider, we have to select among a series of height presets.
As the new masking features become more powerful and easy to use, the panel sizer's deficiencies become ever more pronounced. C1 combines incredible photo development power with awkard interface detailing and attention-sapping chrome. I'm sure there are reasons for this: backlogs, technical debt, throughput limits on a developer team that has a demanding user base, etc.
But now that we have tools like Claude Code, Codex, Codestral, etc, I can't quite see a reason why a low-hanging fruit like dynamic panel resizing can't be tackled quite quickly.
Hope there's space in the backlog to tackle this soon.
Oh, and thanks for (finally …) adding Sparkle for integrated updates. It's great to not have to log in, download, install just to get the update.
+1
In particular, it should be possible to rely on the 'auto' option to dynamically resize to the right size for the number of layers present - the same way it behaves when not docked to the top of the tool stack