Bandaid for curve box issue
I would like to know if anyone has figured out a workaround for the curve box issue. My laptop is 1280x800 wide-screen and I need to use the curves function for minor tweaking.
Adobe has released a wonderful option of collapsable boxes in LR. Will this option be part of the v4 upgrade?
Thanks, P.
Adobe has released a wonderful option of collapsable boxes in LR. Will this option be part of the v4 upgrade?
Thanks, P.
0
-
well...i just hide the windows taskbar and I get just enough space to manage... 😉 0 -
[quote="sorinat" wrote:
well...i just hide the windows taskbar and I get just enough space to manage... 😉
I'm on a 19" Trinitron, running 1024x768, so my problem is even worse.
I agree with the above poster, by auto-hiding the taskbar. Another bandaid
is to hide the toolbar, which gives me full view of the curves box.
I *could* run higher resolution, but I like my monitor setup the way it is.
Rob0 -
Briliiant. Thanks, those tips should be in the C4 manual! [quote="Robert Hoffman" wrote:
[quote="sorinat" wrote:
well...i just hide the windows taskbar and I get just enough space to manage... 😉
I'm on a 19" Trinitron, running 1024x768, so my problem is even worse.
I agree with the above poster, by auto-hiding the taskbar. Another bandaid
is to hide the toolbar, which gives me full view of the curves box.
I *could* run higher resolution, but I like my monitor setup the way it is.
Rob0 -
So this is a known issue? It was in the beta version and I gave up on it in about 10 minutes---what good is it w/o a curves tool. Now maybe I can play around with my computer in order to get some---shall we politely say---unusually designed software to work.
Edited to add: Oops. Allow me to correct myself. Hiding the toolbar is not sufficient on my PC as the bottom 1/3 is still hidden. Changing resolution is a non-starter.
I have no words to describe my amazement that this issue went into the release version. Absolutely stunning.0 -
I have no words to describe my amazement that this issue went into the release version. Absolutely stunning.
Have to agree, here. This is one thing, for sure, that should have been
resolved for the final release. There were MANY excellent suggestions
from beta-testers, which gave PO a golden opportunity to come up with
a great raw converter. But, they decided not to listen and deliver a product
almost identical to the beta.
Rob0 -
Rob
Development takes time and you do not revamp a software during beta stage.
We are listening and we have a good long list of feature requests which we are prioritizing and will implement.0 -
[quote="UlfLiljegren" wrote:
Rob
Development takes time and you do not revamp a software during beta stage.
We are listening and we have a good long list of feature requests which we are prioritizing and will implement.
This is encouraging. Implementation of just a few key features would
make a lot of us very happy campers. 😄
Rob0 -
[quote="UlfLiljegren" wrote:
Development takes time and you do not revamp a software during beta stage.
Granted, and I agree that a beta is not the time to be re-writing slabs of code, only bits, and only when necessary. But long before the beta is built, an application goes through a design phase. Why, at that point, was 800 pixels chosen as the minimum resolution? Yes it suits many laptops these days (like mine), but a more "standard" resolution would've made much more sense (ie: 1024x768 ; 1280x1024 is the next step up but may be too steep for some). 800 pixels will force many people to 1280x1024 anyway, and I am surprised this slipped through the peer reviews which I would've hoped your design had to pass through before the application was being built in earnest. Just sounds like a strange choice to me (unless it was originally 768 but somewhere the developers begged for another 32 pixels).0
投稿コメントは受け付けていません。
コメント
8件のコメント