We have about 20 examples of getting settings in the callback.  I agree it blocks the event system and should take very little time but I don't consider this to violate it.  

Especially since the entire task above where I would do it is _also_ in a periodic callback from the event system and previously called this every occurrence this is a solid improvement since it makes those calls more quick and granular.  Tasks like this should _probably_ be replaced with the FreeRTOS software timers http://www.freertos.org/RTOS-software-timer.html but that does require another task thread to manage them all.

If we want to remove all these instances we should create a separate issue and try and do it in an appropriate way.  This would be an example of a reasonable use of Corvus's delay callback routine.  Ideally that could be integrated into the software timers framework so only one task were required for both mechanisms.

So for now I'm not going to change this behavior since it's an improvement on the previous code and doing it the "right" way wouldn't make it better (just another callback).