Ticket Created
over 4 years ago

ACROPOLIS-2993

Unable to dynamically update Menu2 title - works in sim, not on device

I modded the SDK's Menu2Sample to fire a timer every second which calls both setTitle() and updateItem(), followed by WatchUi.requestUpdate(), to cycle through 3 values for the title and an item sublabel. In the sim, both the title and the item sublabel are updated. For a real 935, only the item sublabel is updated.

The presence of the title as an option in the Menu2 constructor, as well as the availability of a separate setTitle() method, seems to imply that setTitle() should be able to work dynamically. (Otherwise what's the purpose of setTitle()?) Not to mention the fact that it does work dynamically in the sim.

If it's intentional that the title can't be updated dynamically, it would be nice to:

1) Update the docs to make this clear

2) Update the behavior in the sim

It would also be nice if the docs explicitly called out the fact that Menu2.onUpdate can't be overridden due to the fact that it's a native view. (Same with any other views which may have this restriction, such as ProgressBar.)

Sim:

https://ibb.co/qp7vX7Y

FR935:

https://ibb.co/4gkYkJH

Environment:

- Windows 10

- VS Code 1.54.1

- Monkey C extension 0.1.9

- CIQ SDK 3.2.5

- FR935 firmware 21.00

flowstate
Parents
  • over 4 years ago

    Thanks for some sensible comment of this finally  , appreciate that!

    But you see, that is one of the main problems why I am often so negative here. Before your team (CIQ) finally take full responsibility for the CIQ platform, there will always be similar mess. YOUR TEAM must know how the platform should behave on devices, write documentation accordingly and be able to verify this with product teams. Period. There is no excuse to this uncertainty between yours and product teams which bubbles out to the public. In properly working environment if this issue occur and lets say Brad gets such response from product team, he should immediately review this topic internally and not write similar responses to public. And lets not mention how old this functionality already is. 

    How do you think my clients, who want to have their own CIQ apps, can rely on WearSoft when I can't rely on your platform? Ask other B2B devs if you have any... This is not about bug, this is again about your abilities to handle it... 




Comment
  • over 4 years ago

    Thanks for some sensible comment of this finally  , appreciate that!

    But you see, that is one of the main problems why I am often so negative here. Before your team (CIQ) finally take full responsibility for the CIQ platform, there will always be similar mess. YOUR TEAM must know how the platform should behave on devices, write documentation accordingly and be able to verify this with product teams. Period. There is no excuse to this uncertainty between yours and product teams which bubbles out to the public. In properly working environment if this issue occur and lets say Brad gets such response from product team, he should immediately review this topic internally and not write similar responses to public. And lets not mention how old this functionality already is. 

    How do you think my clients, who want to have their own CIQ apps, can rely on WearSoft when I can't rely on your platform? Ask other B2B devs if you have any... This is not about bug, this is again about your abilities to handle it... 




Children
No Data