-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use a real life unit for spacing #27
Comments
Here’s just a random thought:
|
Yeah having a good description would help but I always worry about adding long descriptions because people just dont read them or get confused about what they mean no matter how you word it. After writing the issue my final thought really was to do the live preview then assess if we still need todo this. My suspicion is it wont be needed once we have the live preview |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: