None of the methods in this category has Data at the end, why this one has? and the ones who are not using the notify template method yet, have the adjust at the begging of the name, why this one hasn't?
I guess this is a double negative so it's confusing, but I try to keep the normal state first in these #if build switches. So this one is a #ifndef which is the normal path where accelerometer feature is enabled. And so the #else is the abnormal state where accelerometer is disabled.
Let's all agree to do it this way moving forward. I like the arrangement of files in their corresponding buckets, denali.pro looks much cleaner this way.
I amended comment to clarify these are all for development builds only - Bamboo will never see any of these. As for which dev build switches are commented out or not, this is just how they are used. You un-comment a switch to get that special test feature/behavior as needed. You comment it out to turn it off. So this isn't TODO situation. It's just a means to facilitate all of the various test build requests I get.
Please follow the code structure for consistency. The naming like all the other Model classes should be : typedef Model::<Class>::Data <Class>Data; The chosen name is not consistent and also is too short and doesn't show the content type. In this case, it should also have Adjust at the beginning as well, if I understood the class purpose correctly.
I didn't realize you were already working on the UI sound playback. Are you planning on leaving this class as or will continue to work on playing sound?
