But it can be done with CIQ apps or widgets. For example, in my weather widgets, I have 2-3 screens of data, and with a timer, the user can set it to change which screen is displayed every X seconds with no interaction by the user.
With widgets/device apps, chances are you already have a timer to call requestUpdate() to keep the current screen up to date, so it's just a bit of logic to say, "every X seconds switch to a different screen before the requestUpdate call.
For data screens in a native activity, on some devices (I won't say all), you can turn on auto scrolling.
On a 965 for example, if you start the run activity, then go to run settings, and move down the list you see, there is auto scroll, with off/slow/medium/fast as choices. Nothing you need to do in your data field....
Things like having a DF switch Data Screens would be a mess. Imagine you had multiple DF that all wanted to do the same thing and they all wanted to switch data screens.
