Reply to thread

Message

<blockquote data-quote="Pat Clark" data-source="post: 1042096" data-attributes="member: 123421">No need for being sorry!&nbsp; After all you do, with such good humor and spirit, we're lucky to have you working for us!New download seems OK.&nbsp; I did a clean install.If it is true that the skin engine cannot handle false visibility conditions in the topbar or in a horizontal stack, do you suppose it can be fixed in 1.6 final?&nbsp; There are some cases in the &quot;normal&quot; topbar where the action of a button could be varied, depending on what's happening at the time.For example, the &quot;|&lt;==&quot; and &quot;==&gt;|&quot; buttons never seem to do anything on my system until I change their action from 14,15 to 20,21.&nbsp; Are 14,15 a holdover from before the addition of auto-skip?&nbsp; What are they supposed to do?It would be nice if they invoked skip steps for video, and &quot;skip to front or back&quot; for audio.</blockquote>

[QUOTE="Pat Clark, post: 1042096, member: 123421"] No need for being sorry! After all you do, with such good humor and spirit, we're lucky to have you working for us! New download seems OK. I did a clean install. If it is true that the skin engine cannot handle false visibility conditions in the topbar or in a horizontal stack, do you suppose it can be fixed in 1.6 final? There are some cases in the "normal" topbar where the action of a button could be varied, depending on what's happening at the time. For example, the "|<==" and "==>|" buttons never seem to do anything on my system until I change their action from 14,15 to 20,21. Are 14,15 a holdover from before the addition of auto-skip? What are they [B]supposed[/B] to do? It would be nice if they invoked skip steps for video, and "skip to front or back" for audio. [/QUOTE]

Verification