Yes that makes sense. Basically, if you use "watch" on something in the future, instead of executing your "watch" command right away, it would delay the command.rondepping wrote:The ability to select a program and channel in the future and when clicking on the watch button ( or a different button ) schedule a channel change at that time.
That would be bad, if that's how MLPause works...rondepping wrote:I think the problem with using mlpause is that it will stop MLServer from doing anything else till that time. ( I may be wrong on that )
Time to take a look at those...... or the server automation rules would really be the way to go.
Let say you press watch for a tv show in the future, which would fill 2 variables:rondepping wrote:or the server automation rules would really be the way to go.
That was what I had in mind. Further down the road the ability to manage the events from the UI would be nice, but for now manually deleting the server rule andthe variables if you change your mind is ok.Fonceur wrote:Let say you press watch for a tv show in the future, which would fill 2 variables:rondepping wrote:or the server automation rules would really be the way to go.
tvlobby_time1 = "12/6/2007 9:00 PM"
tvlobby_event1 = YourWatchCommand1 (already starts by MLServeCmd.Macro).
Then you would create a series of automation rules that look something like:
whenever currentdate greater than tvlobby_timeN
You would have 5 or 10 automation rules like that. Of course tvlobby would try to add the new variables with the lowest N possible... Does it sound like that might work?
Users browsing this forum: No registered users and 1 guest