Blue Vision (7 Viewers)

[ge2301]

That's why I would put the button only into master_menu.xaml, because only there the hidden menu is defined. Only thing we need to find out is, how to place button the best way into the intended position.

I would see two options: LayoutTransform to move the button up (not so good), or we define a placeholder in master_bare.xaml and only define a DynamicResource inside master_menu_bare.xaml (better )

I started following up the open points for BV skin. Somehow I stucked at the point you described above long time before.
It's clear for me, that the button should be defined in master:menu.xaml. As far as I remember I put it there and never could see it. I'd also like to try method 2, but not sure what you mean or how to do you. could you explain it? For me it's unclear why the the resource should come to a new master_menu_bar.xaml? Why the button would appear not in home screen then?

 

[morpheus_xx]

To the proposed way over dynamic resources:

First there are already examples for this way: there is a placeholder for alternative footer content: https://github.com/MediaPortal/Medi...BlueVision/screens/master_bare.xaml#L214-L218.
This resource of this placeholder can be defined in screens that base on master_bare (in fact all): https://github.com/MediaPortal/Medi...polloOne/screens/SimpleShowItems.xaml#L54-L56.

For the button this means:
1) Add a new placeholder into master_bare:
<Control x:Name="MenuButtonPlaceholder" HorizontalAlignment="Stretch" Template="{DynamicResource ResourceKey=Menu_Button_Placeholder}"> </Control>
2) In master_menu then define this resource:
<ControlTemplate x:Key="Menu_Button_Placeholder"> <!-- put button here--> </ControlTemplate>
3) In home you won't see a button, because it uses master_homemenu

 

[ge2301]

Thanks, now I got the logic!

I added to master_homemenu.xaml and master_configuration_menu.xaml

    <ControlTemplate x:Key="Menu_Button_Dummy_____">
      <Button x:Name="MenuButton" Style="{ThemeResource MenuButtonStyle}" Grid.Row="0" Grid.Column="0" Margin="48,-6,2,-32"
              HorizontalAlignment="Center" VerticalAlignment="Center"
              IsEnabled="False">
      </Button>
    </ControlTemplate>

and to master_menu.xaml

<Model x:Key="MenuModel" Id="A6C6D5DA-55FE-4b5f-AE83-B03E8BBFA177"/>  
<ControlTemplate x:Key="Menu_Button_Placeholder">
      <Button x:Name="MenuButton" Style="{ThemeResource MenuButtonStyle}" Grid.Row="0" Grid.Column="0" Margin="48,-6,2,-32"
              HorizontalAlignment="Center" VerticalAlignment="Center"
              IsEnabled="{Binding Source={StaticResource MenuModel},Path=!IsMenuOpen}"
              Command="{Command Source={StaticResource MenuModel}, Path=ToggleMenu}">
        <Button.Triggers>
          <Trigger Property="HasFocus" Value="True">
            <Trigger.Setters>
              <Setter Property="Opacity" Value="1"/>
            </Trigger.Setters>
          </Trigger>
        </Button.Triggers>
      </Button>
    </ControlTemplate>

Now I can apply to 3 controls in the master_bare.xaml

      <Control x:Name="MenuButtonDummy" HorizontalAlignment="Stretch" Template="{DynamicResource ResourceKey=Menu_Button_Dummy}"> </Control>
<Control x:Name="MenuButtonDummyConfig" HorizontalAlignment="Stretch" Template="{DynamicResource ResourceKey=Menu_Button_DummyConfig}"> </Control>
      <Control x:Name="MenuButtonPlaceholder" HorizontalAlignment="Stretch" Template="{DynamicResource ResourceKey=Menu_Button_Placeholder}"> </Control>

Benefit is, that the menu button is always visible, much better from design point of view, but only working when not in home view.
Thanks for the explanation, I'm sure it will help me also for other issues

 

[morpheus_xx]

@ge2301 do you think that you can push the "menu button" related changes in next days? I really like to have the menu button included in the U1 build.

I also plan to create a "big font" and "tiny font" theme. The bigger I need myself and other users request smaller fonts for desktop usage (especially TV guide)

 

[ge2301]

@ge2301 do you think that you can push the "menu button" related changes in next days? I really like to have the menu button included in the U1 build.

I also plan to create a "big font" and "tiny font" theme. The bigger I need myself and other users request smaller fonts for desktop usage (especially TV guide)

Hi,
all changes were pushed on 26.08. to BV-v6 branch
https://github.com/MediaPortal/MediaPortal-2/commit/fd8a836ed09b5c369f6bc5c808c58d151c1b4fda

 

[ge2301]

@morpheus_xx
I have also a question. I had a longer conversation with Lehmden about the usability and he gave some helpful feedbacks. that I was not aware of.
For example is it not possible to navigate to the new MP2 button with keyboard or remote control (of course only in screens, where it is activated).
From my understanding the navigation refers to the position of each button. E.g. one presses the "up-button", the focus will go to the closest button in upper side (closest inclused x - and y position). Or is the logic different? Every button should be accessable with remote and keyboard.

 

[Brownard]

Hi @ge2301,
I did a bit of work on the focus handling. You are basically right about how focus selection works although it is not strictly the closest element.
The control that is the most 'in line' with the direction of movement is selected, if more than 1 control is in line then the closest of those controls is chosen.
e.g. When pressing up, the control that is closest to being directly above, regardless of how far above it is, will be chosen.

 

[ge2301]

Hi @ge2301,
I did a bit of work on the focus handling. You are basically right about how focus selection works although it is not strictly the closest element.
The control that is the most 'in line' with the direction of movement is selected, if more than 1 control is in line then the closest of those controls is chosen.
e.g. When pressing up, the control that is closest to being directly above, regardless of how far above it is, will be chosen.

Thanks. I could meanwhile achive, that the new MP2 button is accessable. But one thing is still strange. When I move left from the group menu to the MP2 button, it works.
But if I navigate then back to the right, it does not jump back to the group menu, but the item view in the center.

I'll try some minor adjustments with "margin" settings. Perhaps it's just an position issue about a few pixel.

Do you also have knowleadge about the remote key assignment?
I'm dreaming of an option, that allows the user to self define the remote keys for actions Well, I have many dreams and it's not high in the prio list, but I want to share it at least

 

[morpheus_xx]

@ge2301 I just have pushed a new "default-large" theme for BV. It mainly changes some font sizes. Please check the media related screens, if the layout still fits (cover, list view...). Probably small adjustments are required due to larger fonts. Can you take care for modifactions, if needed? It will affect MediaConsts.xaml.

 

[ge2301]

@ge2301 I just have pushed a new "default-large" theme for BV. It mainly changes some font sizes. Please check the media related screens, if the layout still fits (cover, list view...). Probably small adjustments are required due to larger fonts. Can you take care for modifactions, if needed? It will affect MediaConsts.xaml.

Ok, I'll have a look, most pobably on Thursday. Regarding the TV-guide a screenshot would be nice, so I can see what to adjust. As I still have no TV-Tuner in my working PC, I can not test it
When do you plan to release the SRU1? Most probably on Thursday I can also finish a working beta of the Win10 theme. Basically all views are working (improved further compared to last screenshots). Some details and effects can be also added later.