Possible Bug in SDK Examples

FazliSapuan · May 2013

I noticed there is a "fonts_unload_custom_font" in the API yet in all the official examples that use a custom font (Simplicity and feature_custom_font), they are not unloaded using this function.

Is this function still necessary? Because if it is, then I think we've got some pretty broken examples over here. Many devs use the official examples as a reference of how things should be done.

Dirk Mika · May 2013

AFAIK, it had been discussed quite some times. You definitely have to unload custom fonts otherwise you will run out of resources sooner or later.

So, yes I would consider the examples as incomplete at least.

Dirk

FazliSapuan · May 2013

Well I'm more concerned that an "incomplete" watchface is in the official "store" right now. It's hard to trust other third-party watchfaces when the pebble guys can't even get it right.

Philip · May 2013

The fonts_unload_custom_font() function should only be needed if you want to load multiple custom fonts at runtime that can't all fit in memory at once.

Unlike image and other resources, memory allocated to custom font resources is automatically freed when you exit an app.

Thus, the example is correct and I haven't been leading anyone astray.

(But if someone has an app where this appears to not be happening I'd appreciate a pointer--as that would indicate something isn't working as it should be.)

FazliSapuan · May 2013

Thank you very much for this clarification! I was really surprised when somebody accused my code of leaking memory.

I guess there's some room for improvement in the API docs to explain things like these in greater detail.

Cheers!

Possible Bug in SDK Examples

Comments