-
Notifications
You must be signed in to change notification settings - Fork 62
Flags: Do not hardcode one Flag field per class #492
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This was hardcoded to one Flag per struct. The generator is now smarter and you can specify multiple flags which are resolved by their flag name.
…ify which enum names are considered to be "scoped" ('class' enums in C++)
… determine if an event has been created by EasyRPGs new "CloneMapEvent" command
|
@florianessl this should be okay now? |
…preter related SaveState structures (SaveEventExecState, SaveEventExecFrame & SaveMapEventBase) Co-Authored-By: florianessl <github@iessl.at>
|
This wasn't an old bug but just something I missed when refactoring: The code was only executed when the flag field had the name STRUCT_FLAGS. |
…than the struct oversight from the refactor Thanks @florianessl
Use only "Flags" when struct = flagname as we originally did.
|
Fixed. Actually we do not guarantee a stable structure for the XML file across versions. But I have to admit that this looks really ugly with the |

This is an alternative approach for #491
Instead of a single variable it uses our Flag feature to provide bool variables. This reduces the need for bitmasking.
Problem was that our code always hardcoded
StructName_Flagsfor Flags. This restriction is now lifted and multiple Structs can have the same flags and a struct can have multiple flags.Don't merge, Player build failure because classes are renamed