Connect IQ 1.2.4 SDK Available!

This is great. The new version of the SDK has managed to reduce the previous 1.2.3 SDK memory size/consumption.

However, compared to 1.2.1 it is still eating up an additional 0.5kb of memory.

Will test rendering issues on the 920 but the comment about hand made fonts leaves me wondering. By hand made do you mean made with BMPFONT?

Will test rendering issues on the 920 but the comment about hand made fonts leaves me wondering. By hand made do you mean made with BMPFONT?

It refers to fonts that are manually tweaked by hand after it was created with BMFont.
You have to be careful not to modify just anything exported by BMFont unless you understand what you are doing.

For instance, if you resize the png by cropping it, you have to make sure your values in the fnt file matches the new dimensions.
Other properties in fnt could have a relationship, so when changing something, there might be another property that has to be kept in sync.

There is a tighter relationship between some properties and their values.
The ConnectIQ compiler uses more of them than in the past.

I have already confirmed that the font rendering issue on the 920xt is solved by this release :)

Just to follow up additionally on the font issues, we're looking at ways to better address custom font management in the future. There are a few different ways we could approach it, so it's going to take some time to investigate and find what works best with the fewest compromises. We'll do our best to minimize font problems in the meantime, of course, but I'm optimistic that fonts management will function much better in future versions of the SDK.

When it is possible support Cycling dynamics and DI2 values for data fields

Hi,

I want to know when it is possible the SDK support Vector Cycling Dynamics data including power balance, touque efficiency, Pedding smooth, and Power Phase, Power Peak Phase, Center pedalling offset.

Also, the DI2 infomation such as Gears ratios, etc.


Additionally, when Garmin edge 1000 can use customized Layouts for data fields?
Recently the internal layouts set the 5 will be like this:
._________.
|_________|
|_________|
|_________|
|_________|
|_________|

Is that possible to use 5 layouts like:
._________.
|..............|
|..............|
|_________|
|____|____|
|____|____|

Just to follow up additionally on the font issues, we're looking at ways to better address custom font management in the future. There are a few different ways we could approach it, so it's going to take some time to investigate and find what works best with the fewest compromises. We'll do our best to minimize font problems in the meantime, of course, but I'm optimistic that fonts management will function much better in future versions of the SDK.

Do we still have to manually change the xadvance to match the width?

The way I see it is that the hard work of fixing your fonts should already have been done.

You've already fixed the fonts in order to compile with the previous SDK, so in theory it should not be an issue going forward.

If you want to make new fonts, just check with that font if you need to do the xadvance trick.
I suppose if it is still a problem, the folks here will take another look at it.

At the moment all my fonts are good for compilation. However, In future when creating new fonts, I will be very careful not to change too many things manually.

Obviously if a BMFont exported font, with no manual changes, won't play ball with the compiler, report it together with a zip of your *.fnt and *.png files.

I do need to do my fonts again as need to add Greek and Cyrilic chars.

Hi,

I want to know when it is possible the SDK support Vector Cycling Dynamics data including power balance, touque efficiency, Pedding smooth, and Power Phase, Power Peak Phase, Center pedalling offset.

Also, the DI2 infomation such as Gears ratios, etc.


Additionally, when Garmin edge 1000 can use customized Layouts for data fields?
Recently the internal layouts set the 5 will be like this:
._________.
|_________|
|_________|
|_________|
|_________|
|_________|

Is that possible to use 5 layouts like:
._________.
|..............|
|..............|
|_________|
|____|____|
|____|____|

We have tasks already on our list that will include adding cycling data to activity info, so that's planned. I don't know exactly when it will be available, but I think it's safe to say some of these items will be sometime this year.

Data field layouts are controlled by the product, so that's really a question the product team would need to answer. I don't know whether they have plans to allow more layout customization or not. However, you could design a Connect IQ data field that mimics two separate fields if you wanted, like in your lower example.

Any idea where the 0.5 kb has gone?