By default static parameters are not saved by a GroIMP project. Their value is “loaded” during class initialization. Even if the value of the parameter change during runtime, when, the class is re-initialized, the static parameter is reset.

However, GroIMP project save as their current state. Thus, parameters whose value changed during runtime might be relevent to be saved.

The easiest way to includes static variables in the serialization process, is to declare them as global. The keyword global is implicitly including public and static. It additionally adds the persistent handles for parameters, which enables it to be saved and reloaded.

global int myInt = 3;

Note: Globals are slightly slower that normal static variables.

GroIMP will run hooks when the project is saved or loaded. It is possible to declare classes that will automatically by executed during each of these steps.

See here for an example.

Every classes that implements de.grogra.pf.ui.registry.RunAfterSave will execute the method public void save(RegistryContext ctx) when the project is saved.

Note: the method is called when the project is saved. Not when it is recompiled. (Saving at recompilation is optional). Saving a file in the project might not save the project, (it might only trigger the recompilation).

Every classes that implements de.grogra.pf.ui.registry.RunAfterLoad will execute the method public void load(RegistryContext ctx) when the project is loaded.

Note: there can be several classes that implements any of these two interfaces. They will be ALL executed.