Auto-Expanding Adjustments Clipboard
Every time I copy adjustments the list in the Adjustments Clipboard expands fully - with the effect that half the list is off-screen and I have to either scroll down or re-collapse the adjustment groups in order to see what I'm doing.
This makes absolutely no sense to me: It would make much more sense if the list would just stay as it is - the groups which I don't touch should stay collapsed so I can easily see what I'm doing.
I have been raising this since Capture One 7 in the forum and in support cases, with the response that it will be addressed, which does not seem to happen. I will keep doing so until solved as it does not make any sense and it drives me crazy. Hope this will finally be addressed. PLEASE change this soon!
Apart from this I'm happy with C1 10 as far as I can say. It's fast, stable. Keep going!
Best regards,
Ariel
This makes absolutely no sense to me: It would make much more sense if the list would just stay as it is - the groups which I don't touch should stay collapsed so I can easily see what I'm doing.
I have been raising this since Capture One 7 in the forum and in support cases, with the response that it will be addressed, which does not seem to happen. I will keep doing so until solved as it does not make any sense and it drives me crazy. Hope this will finally be addressed. PLEASE change this soon!
Apart from this I'm happy with C1 10 as far as I can say. It's fast, stable. Keep going!
Best regards,
Ariel
0
-
Yes... I've been running into this issue as well on the Windows version.
Is there way to have it at least collapsed all the time verses auto expanding?0 -
[quote="AKXLPhotos" wrote:
Yes... I've been running into this issue as well on the Windows version.
Is there way to have it at least collapsed all the time verses auto expanding?
No, not in the Mac version at least. No matter what, all groups spring open every time i copy adjustments and and some crucial settings like "local adjustments" are off-screen. It drives me nuts and I don't understand why this can't be fixed.
It has been acknowledged as a bug since version 7 but nothing has been done about it.0
Post is closed for comments.
Comments
2 comments