513 Messages
•
11.1K Points
Sat, Apr 2, 2011 2:06 PM
2
Lightroom: Ability to hide icons for crop & spot removal tools to give more space in other panels in Develop module
It would be nice if one could hide the toolbar containing the icons for the crop tool, spot removal tool etc. The vertical space saved would become available for the development panels.
Sometimes having more than one panel in view is handy as a change in one panel may necessitate a change in another and vice versa. To support this every little bit of further space would help. I imagine many only use the keyboard shortcuts for the tools after a while and don't really need the toolbar anymore.
Sometimes having more than one panel in view is handy as a change in one panel may necessitate a change in another and vice versa. To support this every little bit of further space would help. I imagine many only use the keyboard shortcuts for the tools after a while and don't really need the toolbar anymore.
Ideas
•
Updated
10 years ago
4
10
2
Helpful Widget
How can we improve?
Tags
develop module
toolbar
saving screen estate
Responses
Ian_Lyons
Champion
•
28 Messages
•
532 Points
10 years ago
Actually, I've found the opposite to be the case. On each and every occasion I've asked user groups whether they use icons or keyboard shortcuts the majority indicate icons.
Also, deliberately hiding such an important aspect of the toolset from users would be the work of a fool.
If you're going to make a feature request then I suggest that you ensure that it isn't going to be at the detriment of other users.
1
0
tk_images
513 Messages
•
11.1K Points
10 years ago
The toolbar will neither be hidden from users nor will users be forced to use the option.
Note that you can already use the "T" key to hide the image toolbar. While this can be confusing to some who may hide the image toolbar and then don't remember how to bring it back, obviously someone (smart) thought it would still be a good idea to make the image toolbar hidable.
I'm simply asking for the same option to be available for the toolbar.
I appreciate your sampling of user behaviour but you will still acknowledge that there are many users who predominantly use keyboard shortcuts, right?
Could you please explain to me why my idea would be "to the detriment of other users"?
0
0
john_beardsworth
1.3K Messages
•
22.5K Points
10 years ago
0
0
tk_images
513 Messages
•
11.1K Points
10 years ago
Things like that don't really cost much "development time". Where would you like the development time to be invested?
0
0
john_beardsworth
1.3K Messages
•
22.5K Points
10 years ago
If vertical space is really a problem, IMHO the better solution is smaller fonts, less space above and below text, smaller panel headers.
2
0
john_beardsworth
1.3K Messages
•
22.5K Points
10 years ago
As for "what list?" I was following directly on from your "Where would you like the development time to be invested?"
1
0
tk_images
513 Messages
•
11.1K Points
10 years ago
I feel that is an unfair way of championing ideas one personally feels are in the critical development path. I suggest that people should "like" the ideas they want to promote and "dislike" ideas that they feel would get in their way, but a feature which is completely neutral to anyone not using it shouldn't be voted down on the grounds of "stealing development time".
I argue that ideas should be judged on their merit and it is then up to the product manager / developers to decide whether the idea is worth spending development time on.
Voting against on the grounds of "stealing development time" is numerically indistinguishable from genuine criticism and could be used to achieve a double promotion of the ideas one believes to be worthy of development.
1
0
rob_cole_2221866
4.5K Messages
•
76.3K Points
10 years ago
PS - I really think it best to steer away from opposing ideas based on opportunity cost - let Adobe have that job...
4
0
rob_cole_2221866
4.5K Messages
•
76.3K Points
10 years ago
0
0
john_beardsworth
1.3K Messages
•
22.5K Points
10 years ago
But it isn't implemented, and the criticism is primarily of the FR itself. You can't then discount that disagreement by hiding behind "it would only be an option".
0
0