UX Guide updates for Fenix6 range

When will Garmin update the UX Guide to include Fenix6 specs?

The fonts are different and I really don't want to spend the time experimenting to get them right for my app:

Fenix 5:Fenix 6

Or are they the same and it's a problem with the Sim? I can't afford to buy each new model just to check my app ;-(

The fenix6 device fonts are not the same as the fenix5 device fonts. The simulator properly emulates this. You will need to adjust your layouts.

Given the positioning of the arrows in the screenshot above, it looks like you'll need to adjust them anyways (to compensate for the different device resolutions)

Alan.raceQs over 5 years ago in reply to Travis.ConnectIQ

Yes, I know I have to do some fiddly, time-consuming and unrewarding work to fit the new screen sizes, which is why I was asking about the availability of some technical documentation before I start.

Should I wait for the UX Guide update or try to work it out with trial and error?

Travis.ConnectIQ over 5 years ago in reply to Alan.raceQs

The UX guide is currently maintained by hand. It has not been updated in a while and I would not expect it to be updated soon.

What technical specifications are you wanting?

Alan.raceQs over 5 years ago in reply to Travis.ConnectIQ

Where else do I go for the screen layout specs of the devices that were provided in the UX Guide?

peterdedecker over 5 years ago in reply to Alan.raceQs

a lot of that info can be retrieved from devices.xml in the bin folder

Travis.ConnectIQ over 5 years ago in reply to Alan.raceQs

As pointed out above by peterdedecker, this information is from devices.xml.

The information that you see in the User Experience Guide appendices is derived from the values in devices.xml. The screen shots are generated using the simulator which also uses the devices.xml file to determine how to display the data fields.

ekutter-dnu over 5 years ago

The layout problems you are having above might be due to the fonts themselves. On many of the older devices, the number fonts didn't have space above the actual glyphs in the ascent values. The number fonts now more closely match the full fonts and include this spacing. What that does is effectively shift the number font's downwards if you are aligning at the top.