FONT_PATTERN discussion and understanding

[olivierflying747-8]

@profezzorn

Just try to play a wav file falling back on talkie or beeps. (name of wav depends on the error.)
If the wav doesn’t doesn’t exist or can’t be found, just fall back on what we already have.

That is exactly what I want.

@profezzorn

However, make sense as a way to save memory without having to rely on beep codes.

No without having to rely on talkie codes as they take a lot of memory. beep codes are retained as a fall back because they only take very little memory, however beep codes can be hard to differentiate.

@profezzorn

error messages really shouldn’t occur once you have finished your saber

I agree for “error_in_blade_array”, once the saber is finished, that error shouldn’t occur. My saber will never be finished though because I’ll keep changing the fonts so all the other errors can and will occur. And I would rather have Vader telling me what that error is than the talkies telling me what’s wrong.

@Fett263

Not really following what’s being asked. If a change to my prop is helpful to users and doesn’t impact existing functionality, I’m fine with it, but I’m not really sure what this is about or if it’s actually needed.

When FONT_PATH was introduced in the Gearing up for OS8 thread, you had asked:

@Fett263

This is the default for my prop, so would I need to do anything to enable it or is it already in prop_base?

But you never got an answer on how to make your edit mode compatible with that define.
And the answer is:

@profezzorn

basically, it would need to remove line 2985 and 2986 and do this instead:

current_preset_.font = format_pattern(FONT_PATTERN, font);

I always thought that having to name my common folder as “common” to be compatible with your prop (instead of “_common” or “voicepack”, or what ever the user preference is) was a limitation in your prop.

With FONT_PATTERN, that limitation disappears if you choose to make your edit mode compatible with FONT_PATTERN. And it will be transparent to the user because FONT_PATTERN will default to “*;common” if not defined in the config.