> I guess the larger question is that I still don't understand the > difference between Activity and DevEvent. Is Activity going to get > phased out? Or Activity's sole purpose is 'statechange'.
Sorry, I should have answered this in the last email. Yes, Activity is going to get phased out (some day), since DevEvent can do everything it does and more. And, yes, Activity's sole purpose is (AFAIK) 'statechange'. In order to phase out Activity, we have to (a) make sure that every sensor that generates Activity also generates DevEvents, and (b) make sure that every analysis using Active Time gets it from DevEvents, not Activity. I think we're pretty close to having (a), but we haven't even started on (b). My estimate for when (b) might happen is maybe within the next two or three releases. So, the moral of the story is: for now, generate both Activity and DevEvents if you want to generate either. This ensures forward and backward compatibility. Then, when we get around to implementing (b), all you have to do is delete the Activity sensor data additions and you're done. Cheers, Philip
