Acknowledged

Bug: Boundary on Epix2 fields is off

In addition to this graphics defect: https://forums.garmin.com/developer/connect-iq/i/bug-reports/bug-graphics-text-on-epix2-difference-in-real-life-vs-simulator

it also seem field boundaries are sometimes wrong or off ... I'll add a picture with a clear example of this. I fill the field with a color - which show the problem in the the center divider line is not in center. Plese fix these problems with Epix2 !! 

Parents
  • TL;DR I found that in the first 2 screenshots:

    - the red fields are 1 pixel too tall (compared to the device reference)

    - the horizontal and vertical dividing lines are actually moving around (probably to prevent AMOLED burn-in). This explains why the lines either overlap the fields or are too far away from them

    To clarify / add additional summary, in the first 2 screenshots

    - the red fields are also placed 1 pixel too high (compared to the device reference)

    - the horizontal position of the red fields is actually perfect (according to spec). It's just that the motion of the center dividing lines makes the field position *look* wrong

Comment
  • TL;DR I found that in the first 2 screenshots:

    - the red fields are 1 pixel too tall (compared to the device reference)

    - the horizontal and vertical dividing lines are actually moving around (probably to prevent AMOLED burn-in). This explains why the lines either overlap the fields or are too far away from them

    To clarify / add additional summary, in the first 2 screenshots

    - the red fields are also placed 1 pixel too high (compared to the device reference)

    - the horizontal position of the red fields is actually perfect (according to spec). It's just that the motion of the center dividing lines makes the field position *look* wrong

Children
No Data