Thanks for your bug report. This is due to a change that affects the loading of the custom toolbar button bitmap set via the toolbar GUI. This issue has been fixed for the next version.
For now, the only way around this would be to create a script that uses the /toolbar command to load individual parts of the bitmap as separate buttons.
