Edit: I see a static font replacement list in Draw/FontCR.cpp. Is it how U++ does this?

If so, can we have a way to modify and let apps manage the list?

Generally, it would probably be more simple to just keep the list updated...

void AddFallbackFont()
void RemoveFallbackFont()
void InsertFallbackFont()
void ResetFallbackFonts() // Always resets the list to U++ defaults.
const Vector<>& GetFallbackFonts() // Not sure about this one, but may be used to fill font lists in UI, if needed;

Hello Mirek,

Quote:

Generally, it would probably be more simple to just keep the list updated...

What I have in my mind can be summarized as follows:

1) Make the same list dynamic (using a vector maybe?)
2) Accordinly, add global functions to manipulate or query the list on demand.
3) Keep the existing code as intact as possible.

Basically, it is a global list management.

For example (just to give an idea)

void AddFallbackFont()
void RemoveFallbackFont()
void InsertFallbackFont()
void ResetFallbackFonts() // Always resets the list to U++ defaults.
const Vector<>& GetFallbackFonts() // Not sure about this one, but may be used to fill font lists in UI, if needed;

Frankly I don't really care about emojis or icons. The "modern terminal emulation scene" is a very interesting and weird habitat, but what I really need is some special fallback fonts when a terminal connection requires font adjusting depending on the environment over a remote (SSH) connection, for example.

Besides U++ apps in general can benefit from this.

My main concern would be performance (though the impact of using a dynamic list should be negligable) and the potential concurrency problems these functions may bring in.

What do you think?

Best regards,
Oblivion

I think that whatever fonts you might add by AddFallbackFont, you can have in the list already... Smile

I mean, how are you going to use this?