Ack, it doesn't look like moving the enable state onto GroupFeatureState will work without extensive refactoring. The enable state needs to persist across each engine callback, but a new GroupFeatureState is constructed for each engine callback.
Ack, it doesn't look like moving the enable state onto GroupFeatureState will work without extensive refactoring. The enable state needs to persist across each engine callback, but a new GroupFeatureState is constructed for each engine callback.