Display Vivoactive 3

Former Member over 5 years ago

Hey,

I'm programming a watchface, also (or mostly) for the Vivoactive 3.

I recognized that everything is displayed with a 10 pixel offset on the y-achsis (downwards): for example something that should be displayed at (30/30) gets displayed at (30/40).

This also happens on the music version etc. and it makes no difference if you run it in the simulation or on a real watch.

Do you know any useful solution for this (or the reason, I'm interested why this happens^^)?

0 jim_m_58 over 5 years ago

This shouldn't happen. x=30, y=30 should use that. Post your code. While Gfx.TEXT_JUSTIFY_* options are you using?

What you see in the sim should be as you see on the watch.

0 Nikeow over 5 years ago

The Pixel offset you're talking about could be due to the padding on the fonts. try textheight or some calls like that in the api.

0 jim_m_58 over 5 years ago in reply to Nikeow

Also, in the sim, as you move the mouse around, the x/y is shown on the bottom line.

0 Former Member over 5 years ago in reply to jim_m_58

heyy, soi forgot to add that this only happens with the Vivoactive 3 with its different versions and not other watches.

But whatsoever, here's my code for one example:

<label id="TimeDisplay x="30" y="50" font="Graphics.FONT_NUMBER_THAI_HOT" justification="Graphics.TEXT_JUSTIFY_LEFT" color="FFFFFF" />

Based on this it should be placed on (30/50)

as you can see it works on the d2 Delta(or every other similar watch)

but on the Vivoactive 3 it is moved down by even 20 pixels (with the same code, only other device in the simulator) and both have a 240x240 pixel display (also the font looks different?)

for the coordinates on the bottom line I had my mouse on the nearly same position at the top left corner of the first 2

0 jim_m_58 over 5 years ago in reply to Former Member

The actual fonts vary by device, and on some, especially with number fonts, the font can have white space above and below the digits. The height of the fonts also varies by device as well as the font face. Check the Appendix of the UX Guide in the SDK for some of this info.