Ticket Created
over 5 years ago

WERETECH-8406

DC content is not persistent between onUpdate on real VA4 but it is persistent in simulator

In simulator (VA4) is DC content persistent between onUpdate calls and it is possible to draw only changes. On real VA4 is DC content cleared before every onUpdate and it is necessary to draw whole display content.

VA4: 3.80, SDK: 3.1.6

jha2
Parents
  • over 5 years ago in reply to TomasSlavicek

    The vivoactive4 family of devices use a newer page management system that is very different from the system used by older devices. That is the source of the issues you're seeing.

    It looks like the first of those three tickets (expecting the view to not be cleared between onUpdate calls) was closed as By Design. According to the discussion there, it is expected that the ConnectIQ developer will completely redraw the screen when onUpdate is called. The only time you should be drawing a clipped area is in onPartialUpdate (which is only available for watch faces).

    The second issue (page transitions showing garbage) has a comment indicating that it was transferred to the vivoactive4 team, but I can't find any evidence that it actually was. It appears that this problem also affected the fr935, so it isn't actually related to the page management system. It looks like the issue filed against the fr935 was expected to be fixed when they pulled up the the ConnectIQ 3.1 VM which implies that this was a bug in ConnectIQ and not the device firmware.

    The third issue still Open, but it is really a duplicate of the first. I'm not sure if it will be closed as such or if the device team will relent and just stop clearing the view before calling to the application.

Comment
  • over 5 years ago in reply to TomasSlavicek

    The vivoactive4 family of devices use a newer page management system that is very different from the system used by older devices. That is the source of the issues you're seeing.

    It looks like the first of those three tickets (expecting the view to not be cleared between onUpdate calls) was closed as By Design. According to the discussion there, it is expected that the ConnectIQ developer will completely redraw the screen when onUpdate is called. The only time you should be drawing a clipped area is in onPartialUpdate (which is only available for watch faces).

    The second issue (page transitions showing garbage) has a comment indicating that it was transferred to the vivoactive4 team, but I can't find any evidence that it actually was. It appears that this problem also affected the fr935, so it isn't actually related to the page management system. It looks like the issue filed against the fr935 was expected to be fixed when they pulled up the the ConnectIQ 3.1 VM which implies that this was a bug in ConnectIQ and not the device firmware.

    The third issue still Open, but it is really a duplicate of the first. I'm not sure if it will be closed as such or if the device team will relent and just stop clearing the view before calling to the application.

Children