I mean, for pixel position, sizes, etc. It’s not like I’ll be making a rectangle that’s 100 and a half pixels high. These might as well be integers.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I mean, for pixel position, sizes, etc. It’s not like I’ll be making a rectangle that’s 100 and a half pixels high. These might as well be integers.
If you draw anti-aliased geometry, you need fractional coordinates.
If your geometry might be rescaled by the underlying API to display on a variety of screens you need fractional coordinates.
If you want to be able to tell the API to rotate, scale or shear your geometry you need fractional coordinates.
If you want to be able to break a line from A to C into a piece from A to B and a piece from B to C, and have them join up to look just like the original line, then you need fractional coordinates.
If you want to have a high precision internal representation of your geometry that’s independent of the low precision details of the underlying display hardware, you need fractional coordinates.
If your API doesn’t do these things now, but you need it to support these things in the next version without breaking compatibility, then you need fractional coordinates.