explore use of specialized types to detect DIP vs DDP bugs |
||||||
Issue descriptionIn the display management and ui code, pixel coordinates are sometimes in DIP or DDP units. Computations are done to convert between these and further, values must be rounded in various places so that float pixel coordinates end up being exact DDP when drawing or pointer positioning. Explore adding some kind of trait for classes such gfx::Size that require explicit conversion between DDP, DIP and rounded DDP and DIP to improve readability and make it easier to not introduce subtle rounding bugs (i.e. leaving 1 DDP thick artifacts.)
,
Jan 30 2017
,
Jan 31 2017
,
Feb 21 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 26 2018
Are we still thinking of doing this?
,
Feb 26 2018
The fact that we haven't done it keeps resulting in bugs that take developer time. But obviously this change would itself consume a lot of developer time. It's not obvious to me how to estimate and compare the two time costs. I'd welcome opinions on how to measure and compare the costs.
,
Aug 15
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by enne@chromium.org
, Jan 25 2017Labels: -Type-Bug Type-Feature