setAntiAlias on EDGE1030 - is it supposed to work on this device?

Is the "setAntiAlias" function supposed to be there on all CIQ3.2 devices?

I have an Edge1030 which is CIQ3.2.4 since firmware version 11 which was released in November 2020, but until now it was still CIQ3.1.6 in the compiler device definition.

After seeing the announcement for device definitions update (https://forums.garmin.com/developer/connect-iq/b/news-announcements) I was impatient to try some of the new CIQ3.2. features and the first thing I wanted to see was the anti-aliasing.

And it did not work...

The device definition correctly says "connectIQversion = 3.2.4" and the compiler is successfully executing a build for this target SDK version.

However checking for the existence of "setAntiAlias" function in the device context with the has keyword returns false.

Trying to call it directly for the dc in onUpdate() of course throws a "Symbol not found" exception.

0 NVelev over 4 years ago

The same code runs fine when target device is set to fenix6 for example and there is a visible difference in the screen output when anti alias is enabled or disabled.

0 Shent-Aurkhan (SHN) over 4 years ago in reply to NVelev

hi, see this tread:

https://forums.garmin.com/developer/connect-iq/f/discussion/250838/weather-temperature-datafield-sdk-3-2

I guess it is the same "issue"

0 NVelev over 4 years ago in reply to Shent-Aurkhan (SHN)

Could be.

Hopefully this behavior of the simulator will be fixed in the next SDK release.

PS: Unfortunately I can't check if it works on the real edge1030 device right now, as I've sent it over to Garmin due to the "blue halo" screen issue and I don't have it with me.

0 jim_m_58 over 4 years ago in reply to NVelev

I'm thinking the non music 245 or 645 also doesn't support this. When this feature first came out, I added code for it to all my watch faces that would benefit to use it if it's available.

In initialize, I set a class variable

if(Toybox.Graphics.Dc has :setAntiAlias) {hasAA=true;}

and then in onUpdate,

if(hasAA) {dc.setAntiAlias(true);}

0 Travis.ConnectIQ over 4 years ago

We know about this issue. This device should have antialiasing support in the simulator and on device. Unfortunately, we didn't fully enable it.

0 NVelev over 4 years ago in reply to Travis.ConnectIQ

Thank you for your reply.

Looking forward to the next SDK release :)

0 Travis.ConnectIQ over 4 years ago in reply to NVelev

Changes to device configurations no longer require an SDK release. We updated the device configurations today, so all you will need to do is update them in the SDK manager.

0 DaveBrillhart over 3 years ago in reply to jim_m_58

Awsome! This worked perfectly.