Acknowledged

No "imageFormats" in compiler.json for instinct3amoled50mm and instinct3amoled45mm

There is no "imageFormats" in compiler.json for instinct3amoled50mm and instinct3amoled45mm, and as a result a call to drawBitmap2 causes an exception on the CIQ simulator:

Error: Unhandled Exception

Exception: Source must be native color format

When I copy the section:

"imageFormats": [
"yuv",
"jpg",
"png"
],

from another device's compiler.json, the exception does not occur and the bitmaps get displayed (although not perfect: png shows with transparent pixels rendered black, jpg shows with transparency as png should, and yuv crashes the simulator).

So I would like to ask - is the missing "imageFormats" in compiler.json a deliberate omission or will it be added later?

Parents
  • I heard back from the Instinct team and the omission of these image formats in the device configuration is intentional. Adding them wouldn't necessary cause any actual problems, but it would mean that the simulator is likely to behave in a way that doesn't reflect the behavior of the actual device.

Comment
  • I heard back from the Instinct team and the omission of these image formats in the device configuration is intentional. Adding them wouldn't necessary cause any actual problems, but it would mean that the simulator is likely to behave in a way that doesn't reflect the behavior of the actual device.

Children
  • Thank you for your reply.

    OK, so I have released a watch face which calls drawBitmap2 with Instinct 3 AMOLED devices included in the manifest. And I can see in ERA that it doesn't work. A call to drawBitmap2 causes a System Error on Instinct® 3 AMOLED 45mm: 6.28.

    So it seems to me like there is a problem:

    Either drawBitmap2 should not be available on these devices, i.e. (Toybox.Graphics.Dc has :drawBitmap2) evaluates to false, or it should work and not cause a System Error.