Rick- Vorlon wannabe
Registered: Apr 2002
Location: Ann Arbor, Michigan, USA
Originally posted by TiVoPony
Say, hypothetically, that it was done in the background. Say hypothetically, that moving it to a background task lengthens the amount of time it takes to sort everything out and makes the duration of the task indeterminate.
How do you explain to the average customer that although they changed the priorities earlier today, that tonight it's still recording according to the old schedule. That's an expensive phone call.
We're well aware of the situation. But the solution isn't always as simple as you might think.
Yeah, that's true (and as a onetime software developer I actually made that point as a reply in another thread long ago - nothing's as easy as it looks). That's why I was suggesting a status message about that. I see that in another case you do give the customer a warning something like "changes to this may not be immediately reflected in the To Do List." You could even give the customer the option, letting them know the above. In fact, that strikes me as not bad -- wordsmithing aside, but conceptually, "leaving this screen will cause the sorting to take much longer. Do you want to leave anyway?"
Does just letting the customer at, say, Watch Live TV and the Now Playing List, and maybe not letting them at anything else cause the priority to drop so low that it would go from "up to 40 minutes" to "up to all night"? I really have no idea how much CPU playback takes away. Is it dynamic, i.e. if backgrounded and just sitting at a menu, would it run significantly faster than if the user is watching a show? Or does the mere fact you background something make it take much longer?
"Well, I'd *go* with Betty, ... but I'd be thinkin' o' Wilma" (Dave Lister)
POST #13 | Report this post to a moderator
| IP: Logged