So here is the situation:
1. I maintain a number of different FIT fields in my data field
2. The specific FIT fields I use are dependent on settings
3. I have changed my data fields and underlying app to make sure that onSettingsChanged() in the app is propagated to the view
Obviously, this causes a problem with my fit fields - if they have already been built, then they will be incorrect. I initially got round this by having a "run once" logic check so that I only built the FIT fields when the activity actually started (info.timerState == Activity.TIMER_STATE_ON). EG: I don't build the fields until they are going to be used the first time.
But this is not ideal for a number of reasons. For example, if somebody changes the fields or resets the activity, there are several roads to hell.
So...
Is there a way to tear down FIT fields once they've been built? What is the life cycle and when is it safe to assume they are gone? Are they part of the session, so that they will be reset onTimerReset, for example?
