home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Quality Assurance
Default Skins Feedback
Support for new DefaultWideHD
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="CyberSimian" data-source="post: 1221858" data-attributes="member: 141969"><p>I have now tested the modified XML file on MP 1.16f. In all cases, <em>the recording that triggered the conflict panel was on a MUX different from all of the existing scheduled recordings</em>. I did these tests:</p><p></p><p>(1) One tuner enabled, one recording already scheduled.</p><p>(2) One tuner enabled, six recordings on the same MUX already scheduled.</p><p>(3) Six tuners enabled, six recordings each on a different MUX already scheduled.</p><p></p><p>For (3) I have shown the screenshot after scrolling the list of scheduled recordings.</p><p></p><p>[ATTACH]190134[/ATTACH] [ATTACH]190135[/ATTACH] [ATTACH]190136[/ATTACH]</p><p></p><p>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.</p><p></p><p>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.</p><p></p><p>-- from CyberSimian in the UK</p></blockquote><p></p>
[QUOTE="CyberSimian, post: 1221858, member: 141969"] I have now tested the modified XML file on MP 1.16f. In all cases, [I]the recording that triggered the conflict panel was on a MUX different from all of the existing scheduled recordings[/I]. I did these tests: (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. [ATTACH]190134[/ATTACH] [ATTACH]190135[/ATTACH] [ATTACH]190136[/ATTACH] 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 [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Quality Assurance
Default Skins Feedback
Support for new DefaultWideHD
Contact us
RSS
Top
Bottom