Hise 5 & Compilation Flags

DanH

So I have a compilation flag list as long as my arm and it's increasing!!

I'm not even sure if I need them all anymore either, some are 5 years old! I know some flags have to be set when compiling Hise but I'm not even sure which those are now!

So since Hise 5 is already introducing some breaking changes shall we break some more stuff? Or perhaps have a second page in the project settings which has checkboxes for all the available flags? A least then the process is not so opaque as it is now and people can see what's available... and a small explanation could also be available.

Or a mix of the two?!

Some examples:

HISE_SAMPLE_DIALOG_SHOW_INSTALL_BUTTON=1
HISE_SAMPLE_DIALOG_SHOW_LOCATE_BUTTON=0

This could and should be a checkbox in 2025! Does the original sample installer even still exist?!

HISE_USE_EXTENDED_TEMPO_VALUES

Surely time to break Hise with this one? Or even better be able to select how slow you want it to go as I think 16/1 would be good but currently not included even in this flag...

ENABLE_ALL_PEAK_METERS=1

Essential for loads of new plugins being made in Hise but I see this question a lot on the forum.

The new modulation ones too (Hardcoded Mods etc) would be better set in project settings that flags (see bottom of list below).

Some others I'm using, old and new (if anyone can tell me if I no longer need them that would be great!):

HISE_USE_OPENGL_FOR_PLUGIN=1
HISE_DEACTIVATE_OVERLAY=1
HISE_DEFAULT_OPENGL_VALUE=1
HISE_USE_SVF_FOR_CURVE_EQ
NUM_HARDCODED_FX_MODS=8
HISE_NUM_SCRIPTNODE_FX_MODS=4
HISE_NUM_POLYPHONIC_SCRIPTNODE_FX_MODS=4
HISE_NUM_SCRIPTNODE_SYNTH_MODS=4
NUM_HARDCODED_FX_MODS=4
NUM_HARDCODED_POLY_FX_MODS=4
NUM_HARDCODED_SYNTH_MODS=4

d.healey

@DanH Check Help >> About HISE

griffinboy

@d-healey

Ah it's nice that we can see that.

d.healey

@griffinboy I should add that these ones are dynamic, you can change them at run-time, and this doesn't include all possibilities, Christoph is adding to them. There is a recent thread about it somewhere.

DanH

@d-healey Cool, so basically this but for the flags you set in Settings and make them toggle

d.healey

@DanH what happens if you want to use different flags on different operating systems?

DanH

@d-healey perhaps it needs two columns then?

Christoph Hart

@DanH but why? Just dump them in the field, I would have to add a toggle button each time I add a preprocessor.

DanH

@Christoph-Hart for UX and ease of use basically. Especially helpful for less experienced devs I'm sure. Plus is there a list of available flags in the Docs we can refer to? (I know it's been posted to the forum at some point). Feels like it would be nice to have them all in one place and easy to toggle on / off.

ustk

@Christoph-Hart At least an exhaustive list of available flags with proper explanations would be so so useful.
I agree that some of them are constantly asked. And I myself wonder wether this thing I can't get working is because I forgot a flag or not (A flag that I don't recall the existence, and even less its name btw...)

So if not a dynamic setting in Hise (that I understand why it wouldn't be ideal), at least a real list of flags (in Hise or doc, whatever...)

d.healey

@Christoph-Hart I wonder if you add a comment next to each define in the source, if your doc generator could pick them up automatically and add them to the documentation?