In custom mode, the resolution (l x w) is displayed in an input field. Intuitively, the length and width should be entered separately and connected with an “x”, but in reality, the input box only accepts one input value and automatically generate the second. This setting method goes against intuition. The UI should be improved or you can add some explanations.
3 Likes
This is an interesting idea. I agree that there are a lot of workflows where you’re thinking about creating a specific output resolution. Specifying it here will obviously also change the width and height of the render extent, but I think that is OK.
1 Like
It may be that my expression is not clear enough. I mean: the input field looks like it needs to enter two parameters. In fact, it only needs to enter one 
2 Likes
Not necessarily! You could make it that the extent’s dimensions determine the ratio. Then, you’d have two fields for resolution. When you enter a value in field A, field B is updated accordingly with the ratio, and vice versa. This has the added benefit that the user can easily aim for a minimum (or maximum) resolution for either width or height of the extent, and have the other resolution solved for automatically!
However…
You must make this behaviour, very, very clear. I am sadly not at my machine atm, but I could make some mock GUI, to see if it is nice behaviour.
1 Like