2009-10-08, 11:09
I was reviewing my debug log for a Library related issue this morning,and noticed the following entry;
When I went poking about in the source, I noticed that trunk/skin/PM3.HD/720p/DialogVideoScan.xml sets defaultcontrol to "402", although control 402 is not guaranteed to be visible; either 402 or 405 will show;
Does this really matter at all? Is it normal to (and acceptable to have this error), or should the file be patched so that there's no default control at all (or should something like the seemingly blank label 401 be set as the deault)?
Interested in any feedback. Minor and inconsequential as it is, I'd take some satisfaction from identifying or submiting a patch that fixes someething, even if it is only a one-liner that is invisible to all bar those that trawl through debug logs!
Cheers,
Fergus.
Code:
ERROR: Control 402 in window 10133 has been asked to focus, but it can'tWhen I went poking about in the source, I noticed that trunk/skin/PM3.HD/720p/DialogVideoScan.xml sets defaultcontrol to "402", although control 402 is not guaranteed to be visible; either 402 or 405 will show;
Code:
<control type="label" id="402">
<visible>Skin.HasSetting(No_Media_Titles_In_Scanner</visible>
</control>
<control type="label" id="405">
<visible>!Skin.HasSetting(No_Media_Titles_In_Scanner)</visible>
</control>Does this really matter at all? Is it normal to (and acceptable to have this error), or should the file be patched so that there's no default control at all (or should something like the seemingly blank label 401 be set as the deault)?
Interested in any feedback. Minor and inconsequential as it is, I'd take some satisfaction from identifying or submiting a patch that fixes someething, even if it is only a one-liner that is invisible to all bar those that trawl through debug logs!
Cheers,
Fergus.
