1. Each time Sando Options are needed, even an access to single property from them, they are recreated from the dialog page. I think there's only one instance of sando options neccessary, that should be common for all classes. Maybe the implementation and
usage of this class should be adapted to Singleton model?
2. I think good practice would be to provide some manager for options that handles changes made in options dialog page. For example if I commit changes in options dialog page it should automatically update the sando options instance and perform some other
actions (ideally it should also inform about the changes the interested classes).
If the current approach has a good explanation or You have better suggestions to improving options section please comment here.
Appreciate Your thoughts and remarks ;)
Sorry for the delay... was offline for a few days. Anyway, I just took a real quick look at the code and it looks like you're right. If you are up for it please feel free to fix this behavior so that the options are just read once per session
(until they are updated).
In my opinion this would be a very good first contribution. The hijack Crtl+F task is actually a *really* big task and I would recommend against doing that one as your first bug. It would be really cool to see an 'options-manager'!
Please feel free to contact me if you want to discuss anything else... I'm here to help as you make your first contribution!
Merry Christmas and Happy New Year!