I have now tested the modified XML file on MP 1.16f. In all cases, the recording that triggered the conflict panel was on a MUX different from all of the existing scheduled recordings. I did these tests:Could you pls test this xml with DWHD and possibly post a screenshot so I can see whether it is OK or needs some more finetuning
(1) One tuner enabled, one recording already scheduled.
(2) One tuner enabled, six recordings on the same MUX already scheduled.
(3) Six tuners enabled, six recordings each on a different MUX already scheduled.
For (3) I have shown the screenshot after scrolling the list of scheduled recordings.
I note that there is no indication that there may be one or more scheduled recordings off the bottom of the list, but I also note that "DefaultWideHD" eschews spin controls, so I suppose that the panel design is consistent with other panels in DWHD.
When I was modifying the panel layout for my "ClassicWide" skin, I actually tried the alternative actions. They work fine for the case of only one tuner, but do not really address the case of two or more tuners. However, I think that it is a functional deficiency in the MP Client and TV Server, and not a skin problem. I will open a thread in "Improvement Suggestions" to log the need for some improvement in this area.
-- from CyberSimian in the UK