positioning is wrong on some devices

Issue was also discussed here with no solution (https://forums.garmin.com/developer/connect-iq/f/discussion/7057/font_system_number_thai_hot-wrong-positioning-on-fenix-5)

Apparently different fonts are used on FR935 and FR245 so basically the numbers for the time don't end up in the boxes in my layout.

I tried doing this:

Sys.getDeviceSettings().partNumber

and then comparing to 006-B3076-00 and 006-B3077-00 for the FR245 and FR 245 Music and using different labels in the layout.xml. It looks great in the simulator but a user has reported that the numbers are still offset. I tried to show the labels here but these code block things are weird, it isn't showing it:

<label id="HourLabel" x="78" y="50" font="Gfx.FONT_SYSTEM_NUMBER_HOT" ...
<label id="Hour245Label" x="77" y="33" font="Gfx.FONT_SYSTEM_NUMBER_HOT" ...

How do I fix things so the numbers go in the right places in the layout?

Top Replies

jim_m_58 over 4 years ago +1 verified

You don't want to use partNumber. There can be different part numbers for World Wide vs APAC devices. Look at using jungle or resource overrides.

You can also skip using layouts and just use dc calls…

All Replies

+1 jim_m_58 over 4 years ago

You don't want to use partNumber. There can be different part numbers for World Wide vs APAC devices. Look at using jungle or resource overrides.

You can also skip using layouts and just use dc calls.

0 mfyyra0eiA over 4 years ago in reply to jim_m_58

I appreciate the response but can you please be more specific? I still don't understand what I need to do, especially if I shouldn't use partNumber. How do I tell it where to put the numbers depending on which 240x240 watch they have? Thanks!

0 jim_m_58 over 4 years ago in reply to mfyyra0eiA

See this: https://developer.garmin.com/connect-iq/core-topics/build-configuration/

Like I said, you don't want to use part numbers at all. It could be a bit of a mess if your app gets auto migrated to a new device.

0 mfyyra0eiA over 4 years ago in reply to jim_m_58

resources-round-240x240 won't work because both are 240x240. So something like resources-fr245 and resources-fr245music? How do I determine what actual device resource qualifier is valid there?

0 jim_m_58 over 4 years ago in reply to mfyyra0eiA

See <sdkroot>/bin/default.jungle

0 jim_m_58 over 4 years ago in reply to jim_m_58

Are you sure you're not dealing with APAC vs WW? What languages are the actual devices set for?

0 jim_m_58 over 4 years ago in reply to jim_m_58

When you are comparing partNumber, are you using == or equal()? As they are strings you want to use equal()

0 mfyyra0eiA over 4 years ago in reply to jim_m_58

if ("006-B3076-00".equals(_cached_device_model) || "006-B3077-00".equals(_cached_device_model)) {

That seemed to fix the offset text in the fr245 emulator. But I am going to get rid of that code and try it with the resources-fr245 and resources-fr245m as you suggested. Thank you.

0 mfyyra0eiA over 4 years ago in reply to mfyyra0eiA

Just wanted to describe what I did in case anyone else comes across this.

I removed the partNumber code and made new directories next to the resources dir, resources-fr245 and resources-245m. I copied all the resources into those dirs and modified the x and y coordinates for the hour and minute labels for the appropriate values for those devices. (I also tested with obviously bad coordinates to make sure the new resources were being used). The proper resources are now being picked up depending on what device is being used, in the emulator anyway. I hope it looks right now on the real device. I will release it and notify the user and I will post back here if there are still issues. Thanks jim_m_58!