Currently we ask the user to change a number that represents spacing, but it doesnt mean anything to them.
The number translates to pixels, but even then its kinda fuzzy because pixels are not created equal.
Instead we want to convert it until a real distance unit, like centimetres.
However, this could also be confusing. If its in a CM and a user prints it at A5 size then the units will be wrong. So maybe we accept its wrong for these edge cases or we make it clear, the size is for A4 prints? Even then there will be some variability on how much border each printer produces.
Its a tough one. We could perhaps opt for a % based system? Although that could be more confusing.
Doing a preview (see #9) would mostly make this irrelevant.
Currently we ask the user to change a number that represents spacing, but it doesnt mean anything to them.
The number translates to pixels, but even then its kinda fuzzy because pixels are not created equal.
Instead we want to convert it until a real distance unit, like centimetres.
However, this could also be confusing. If its in a CM and a user prints it at A5 size then the units will be wrong. So maybe we accept its wrong for these edge cases or we make it clear, the size is for A4 prints? Even then there will be some variability on how much border each printer produces.
Its a tough one. We could perhaps opt for a % based system? Although that could be more confusing.
Doing a preview (see #9) would mostly make this irrelevant.