In a previous post we mentioned the ability to handle states
in buttons and how that fits well with icon fonts.

A question in the post raised the issue of commands which support such states but the API isn’t there.

To solve this we added a version of setMaterialIcon to FontImage
that accepts a Command as
its argument. This effectively makes commands work with such icon fonts.

To support that further we also added to Toolbar
the methods: addMaterialCommandToSideMenu, addMaterialCommandToRightBar, addMaterialCommandToLeftBar &
addMaterialCommandToOverflowMenu.

These accept one of the MATERIAL_* char constants from the FontImage class to create the icon for a command
relatively easily.

By default strings in Codename One are implicitly localized which is unique. Most frameworks require some
level of intervention to implement localization but since Codename One was developed by people whose
native language isn’t English we felt compelled to fix that…​

Localization should be the default and Codename One does the right thing here, however sometimes you want to
turn it off e.g. if you have a user submitted string that might be identical to an application resource bundle value.

In Label we have the
setShouldLocalize
method which works great for disabling the implicit localization. However, as
issue 1744 pointed out this needs to be done for
other components too…​

So we added the same method to SpanLabel, SpanButton & MultiButton. You can now control localization
specifically in all of those components.

Image locking is an esoteric performance implementation detail that most of you can and should be unaware of.

If you don’t care about the nitty gritty skip this section, for those of you who care and don’t know what I’m talking
about you can
read this section and sidebar in the developer guide.

In the coming update we fixed issue #1746 to
also lock other button states (this was very visible with things like toggle buttons). But the main change was
also changing the locking behavior to act more like a smartpointer and less as a boolean flag which should reduce
the cases of memory thrashing when using the same encoded image, over and over…​