Reply to thread

Message

<blockquote data-quote="CyberSimian" data-source="post: 1232788" data-attributes="member: 141969">I have found the problem with my &quot;ClassicWide&quot; skin; your problem may or may not be the same.The xml definition of the side menu starts with a control tag that has a type of actiongroup.&nbsp; There is a nested control tag, but preceding that I had these:[code]&lt;dimColor&gt;ffffffff&lt;/dimColor&gt;&lt;visible&gt;!Control.HasFocus(50)&lt;/visible&gt;[/code]DWHD is different; it has the following dimcolor tag:[code]&lt;dimColor&gt;00ffffff&lt;/dimColor&gt;[/code]In addition, the visible tag in DWHD is moved from the control with a type of actiongroup to the subsequent control with a type of group.&nbsp; Making these changes to &quot;ClassicWide&quot; fixes the problem for me.&nbsp; I have not yet tested this enough to know whether there are any unwanted side effects of these changes.-- from CyberSimian in the UK</blockquote>

[QUOTE="CyberSimian, post: 1232788, member: 141969"] I have found the problem with my "ClassicWide" skin; your problem may or may not be the same. The xml definition of the side menu starts with a [b]control[/b] tag that has a [b]type[/b] of [b]actiongroup[/b]. There is a nested [b]control[/b] tag, but preceding that I had these: [code]<dimColor>ffffffff</dimColor> <visible>!Control.HasFocus(50)</visible>[/code] DWHD is different; it has the following [b]dimcolor[/b] tag: [code]<dimColor>00ffffff</dimColor>[/code] In addition, the [b]visible[/b] tag in DWHD is moved from the control with a type of [B]actiongroup[/B] to the subsequent control with a type of [B]group[/B]. Making these changes to "ClassicWide" fixes the problem for me. I have not yet tested this enough to know whether there are any unwanted side effects of these changes. -- from CyberSimian in the UK [/QUOTE]

Verification