Simulator Weirdness in Multiple Field DFs

In my data field, I test for DF size and display "Invalid Field Size" if the size doesn't meet the requirements, and set "doNotRun = true". In compute() I just return if that flag is set, to not burn CPU if in an invalid field.

Strangely, that causes even the good fields to not run compute(). Is that a bug, or expected behavior?

In the image below... it runs fine in a 1 field layout, but when I switch to a 3 field layout, even the middle field (the good one) stops running compute().

Top Replies

jim_m_58 over 6 years ago +1

You want to set this flag in onLayout() or onUpdate() instead of compute(). compute() only runs once a second even if you are displaying the DF multiple times in the same activity or in the sim with something…

All Replies

jim_m_58 over 6 years ago

You want to set this flag in onLayout() or onUpdate() instead of compute(). compute() only runs once a second even if you are displaying the DF multiple times in the same activity or in the sim with something other than a 1 field layout. onLayout()/onUpdate() are called for every visible field.

There's a bug in the 3.1.6 SDK where onLayout isn't called correctly in the sim.

DaveBrillhart over 6 years ago in reply to jim_m_58

Ah. Ok. I do set the flag in onLayout()... But then use it in compute() to decide to run compute logic or not. But the 3.1.6 bug is what is getting me. Since it doesn't run for each DF instance. THANKS!

subra over 6 years ago

@DaveBrillhart

Just now I came across of this new feature

forums.garmin.com/.../using-relative-layouts-and-textarea

Maybe it's interesting for layout of your DF.

DaveBrillhart over 6 years ago in reply to subra

Thank you! Ironically I built my own methods that are similar. One provides the usable boundaries for any data field on any device (obscured etc). And the other picks the best font given the message and the height and width in which you want to fit that text.