Reply to thread

Message

Grouping the controls certainly seems to be the way to go. I successfully got the jump from left to right working, with a button in the middle to do action 18 which is only visible when video is playing. Use the videowindow as a preview only, slide it out of the way when not playing as per the above, and put the group of three buttons over the top of it, remembering NOT to collapse the middle button when not visible.

I've taken it a step further in the attached file with a grid layout, and a power off button appearing when video and audio are not playing. It's rough and ready at the moment. It works fine using direction keys. Mouse users would want to modify the button sizes or maybe overlay buttons to allow for mouse navigation.

Things I have learned from this process:
1. VideoWindow takes focus even when not visible
2. VideoWindow will always render the TV picture at the starting co-ordinates irrespective of animations but....
3. The VideoWindow can be slid off the screen or out of the way with an animation when not playing using "Hidden" as above
4. Unfortunately when a button is not visible, MP starts looking for the next alternative button in the direction of travel +/- 1 pixel rather than +/- 0 pixels which would have allowed for buttons to be stacked on top of each other.

Tomorrow I am going to try out the set focus idea.

RH

<blockquote data-quote="Rob Hexenmeister" data-source="post: 1270044" data-attributes="member: 113164">Grouping the controls certainly seems to be the way to go. I successfully got the jump from left to right working, with a button in the middle to do action 18 which is only visible when video is playing. Use the videowindow as a preview only, slide it out of the way when not playing as per the above, and put the group of three buttons over the top of it, remembering NOT to collapse the middle button when not visible.I've taken it a step further in the attached file with a grid layout, and a power off button appearing when video and audio are not playing. It's rough and ready at the moment. It works fine using direction keys. Mouse users would want to modify the button sizes or maybe overlay buttons to allow for mouse navigation.Things I have learned from this process:1. VideoWindow takes focus even when not visible2. VideoWindow will always render the TV picture at the starting co-ordinates irrespective of animations but....3. The VideoWindow can be slid off the screen or out of the way with an animation when not playing using &quot;Hidden&quot; as above4. Unfortunately when a button is not visible, MP starts looking for the next alternative button in the direction of travel +/- 1 pixel rather than +/- 0 pixels which would have allowed for buttons to be stacked on top of each other.Tomorrow I am going to try out the set focus idea.RH</blockquote>

[QUOTE="Rob Hexenmeister, post: 1270044, member: 113164"] Grouping the controls certainly seems to be the way to go. I successfully got the jump from left to right working, with a button in the middle to do action 18 which is only visible when video is playing. Use the videowindow as a preview only, slide it out of the way when not playing as per the above, and put the group of three buttons over the top of it, remembering NOT to collapse the middle button when not visible. I've taken it a step further in the attached file with a grid layout, and a power off button appearing when video and audio are not playing. It's rough and ready at the moment. It works fine using direction keys. Mouse users would want to modify the button sizes or maybe overlay buttons to allow for mouse navigation. Things I have learned from this process: 1. VideoWindow takes focus even when not visible 2. VideoWindow will always render the TV picture at the starting co-ordinates irrespective of animations but.... 3. The VideoWindow can be slid off the screen or out of the way with an animation when not playing using "Hidden" as above 4. Unfortunately when a button is not visible, MP starts looking for the next alternative button in the direction of travel +/- 1 pixel rather than +/- 0 pixels which would have allowed for buttons to be stacked on top of each other. Tomorrow I am going to try out the set focus idea. RH [/QUOTE]