Mark Oates

This has bumped up a bit in priority. I can see an upcoming scenario where this feature might be needed - rendering interpolator paths for automation controls comes to mind....

Additional ideas listed in https://github.com/allegroflare/allegro_flare/issues/228

Note that `DatatypeDefinition` class and dictionary instance `std::vector DatatypeDefinition::definitions;` is declared and defined entirely within the `Attributes` class source file. This design is embedding a global dictionary "`definitions`" within the...

After the previous comment above, I don't think this is a major issue, particularly for the `0.9`. There's no immediate need for this feature and approximately 100% of projects so...

A lot of changes have happened on the project since v0.8.9, with [proper `namespace` fixes](https://github.com/allegroflare/allegro_flare/issues/152) across the board, [including for the `Display` issue](https://github.com/allegroflare/allegro_flare/commit/2d1fdeb8dd786428264b48facae180fcba5c5ae3#diff-296f151788090bb7ab6e3867c1b6d9e9) you mentioned. I should create a more...

I've created an issue to address the build: https://github.com/allegroflare/allegro_flare/issues/176

Also consider renaming `ALLEGRO_AUDIO_VOICE`, `ALLEGRO_AUDIO_MIXER`, constants from audio to `ALLEGRO_AUDIO_VOICE`, and `ALLEGRO_AUDIO_MIXER`.

use `al_get_channel_count` to replace logic code in this example: https://github.com/liballeg/allegro5/blob/d25c4cff7621db614e5236a1646f5d76309ca73f/examples/ex_synth.cpp#L156-L166 ``` switch (al_get_mixer_channels(mixer)) { case ALLEGRO_CHANNEL_CONF_1: nch = 1; break; case ALLEGRO_CHANNEL_CONF_2: nch = 2; break; default: /* Not supported....

Consider adding a `FontKit` which would have predefined named font styles like "title", "header1", "paragraph", etc.

Another way to look at this is to consider in what kinds of scenarios you might need the different arrangements? For example, you might have a component that internally relies...