The first step to export in a higher resolution is to change the resolution,
which changes the width/heigh. For instance, an object with a width of 10cm
becomes 1cm when the resolution is increased by 10x. But this dependency is not
clear from the UI.
Second problem, deleting the number separator (dot or comma) for a high
resolution starts an internal calculation of the expected output size that
takes very long and fails silently in the end (0kb).
--- Comment #1 from Heiko Tietze <[hidden email]> ---
The user expects to define the width of the output sometimes in cm but most
often as pixel. As a second step he or she wants to fine-tune the resolution
(dpi). But changing the pixels per inch when the width is defined in inches
makes not much sense resp. would change the image width.
Proposed solution: We add a third input and show width, number of pixels, and
resolution with the option to manipulate every value resulting in an update of
the depending fields. The three options get radio buttons that define what of
the three options is fix as we have it for RGB/CMYK/HSV in the color picker.
Alternatively, we add a 4. control like a dropdown that defines what of the
three controls is sticky. The resulting workflow in both cases is that I change
on field resulting in an update of the second while the third is "sticky".