Providing notice of recording conflicts

[the-warriners]

I would certainly look forward to this feature. I look a the front screen daily but only check for conflicts about every other week when i remember or when something fails to record due to a conflict.

Having lots of scheduled recording that sometimes change time slots makes this a potentially very useful new feature.

[Torque]

Or where the next recording info shows up, have another "panel" that only displays conflicts. I'm at the point where I won't sit thru the rotation of next recordings because I can have up to 5-6 per day... I'll use the Recordings menu and pending because that's potentially about 30-45 seconds of watching/waiting. If conflicts were in there too, chances are I wouldn't see them.

A panel dedicated to showing conflicts would be ideal. If that panel is blank, there are no conflicts.

[Torque]

*Bump* for this request (I think Sub was on vacation when I posted this, so it quickly left the first page of topics).

A "panel" dedicated to just conflicts on the main menu would be ideal.

[Torque]

There is a skinning option in the next release that could be used to show the users something on the main menu in the event of a conflict.

I havnt actually added anything to show in the blue skin, because I could think of anything nice looking.

Crap, i completely missed you saying this. Is this in a .99x version (i don't remember when the last version was released) or in a 1.x version? Thanks.

[sub]

Crap, i completely missed you saying this. Is this in a .99x version (i don't remember when the last version was released) or in a 1.x version? Thanks.

Yes, its in v0.99.12. From memory, you can add something to the NextRecording.xml skin file, with the conditional visible="@hasConflict" attribute, and it'll be shown if there is a conflict or hidden if there isnt.

[Torque]

Sweet, i'm gonna give that a shot right now. Thanks!

[Torque]

Sub when you get time, could you post the actual syntax... I can't get this to work. Thanks.

[sub]

I just double checked, and strangely I used the conditional: visible="@HasRecording". Mustnt have had the brain engaged at the time. I'll change it to @HasConflict for the next release.