Under Review
over 2 years ago

Venu 2 bug: 1st onUpdate call after an onShow event reports getObscurityFlags for the previous data screen - NOW MUCH WORSE

A while ago I report few data fields were wrong: https://forums.garmin.com/developer/connect-iq/i/bug-reports/bug-obscurity-flags-wrong-on-venu2-device


Just tested again with the new v10.22. And, it's now MUCH WORSE!!

Essentially almost ALL FIELDS are now reporting wrong getObscurityFlags() !!!

Even the full screen / single field layout reports getObscurityFlags()=12 - HUH???

My pacer App design is highly relying on this to work - or I get reports and crashes from field.

PLEASE FIX ASAP!!!!

Also, a Question: I only have a venu 2 device my self, I need to know which other devices this is wrong on now with the new update? I will need to redraw the App or something for those devices.

Hr. Mortensen
  • over 1 year ago in reply to Hr. Mortensen

    I have tested the latest firmware update 11.16. 

    The good news is that all data fields now report correct getObscurityFlags()!

    But, getWidth() when called in real device returns incorrect numbers for the left & right center fields in 4 fields layout vs the simulator and documentation. 199 pixels is return in real life device, the correct value is 207. 

    Also, in 4 fields layout, getWidth() for the bottom field returns 253 and not the correct 416. AND the bottom data field is still not (I guess due to the getWidth bug) fulle painted - like in picture above. 

    PLEASE FIX 

  • over 2 years ago 
    I have also a layout problem, on the Venu 2S with firmware v10.22.
    A user has reported "the data are not properly displayed anymore since the latest system update of my Venue 2S."
    He says the text is positioned in the wrong place. I haven't investigated yet but it could well be due to incorrect obscurity flags.
  • over 2 years ago

    To clarify: In the examples I have made, my App is only used once. So, NOT shown on one screen mulitple times. The other ones shown are Garmin native fields (Danish headings).

  • over 2 years ago

    Or maybe it's not supposed to be used more than once?
    Some DF-s have multiple copies in the store so people can have multiple instances of it. It is probably in order to be able to have different settings (like: Running vs Bike or even Running vs Trail running). But I don't think that the same DF is supposed to be displayed on 1 screen multiple times.

  • over 2 years ago

    Seem more is wrong than just the ObscurityFlags. My App fills the entire field with a color and draw a number on top. Here is how it looks with my data field inserted in two locations, top and then bottom. Clearly the field boundary or something is not right in the bottom one!