Blue Vision (5 Viewers)

morpheus_xx

Retired Team Member
  • Team MediaPortal
  • March 24, 2007
    12,073
    7,459
    Home Country
    Germany Germany
    What do you think about a sliding effects for the screens, when changing them?
    https://social.msdn.microsoft.com/F...f087e2906e5f/grid-sliding-animation?forum=wpf
    Just the code is not working yet: System.ArgumentException: Das Objekt mit dem Typ "System.Collections.Generic.List`1[System.Object]" kann nicht in den Typ "MediaPortal.UI.SkinEngine.Controls.Animations.Storyboard" konvertiert werden.
    Good idea, I'd like to see more animations in skin. I can check the cause, probably some syntax error. Can you post the current version? Can look at it this evening.
     

    ge2301

    Lead Design MP2
  • Team MediaPortal
  • January 11, 2014
    8,741
    3,501
    Stuttgart
    Home Country
    Germany Germany
    Is it possible to add an IsMainMenu property? You added a IsHome property and I like it. this would solve the issues with the MP2 button a few posts above. also I would like to have some features only and some not in MainMenu (the one with the big tiles) screen
    The home screen has an own .xaml file, so what you put there is only valid in this screen.

    What you put into master_bare (or others) is then valid in all screen which includes them.
    I have pushed the changes with MP2 button. Problem is, that I want the button to be visible always, so it's as the power button in master_bare.
    But it needs to be disabled only, if MainMenus are shown. If it's not disabled and pressed all other menus are deactivated. By adding IsEnabled="{Binding Source={StaticResource MenuModel},Path=!IsMainMenu}" this could be achieved, I have no other idea at the moment.
     

    ge2301

    Lead Design MP2
  • Team MediaPortal
  • January 11, 2014
    8,741
    3,501
    Stuttgart
    Home Country
    Germany Germany
    Good idea, I'd like to see more animations in skin. I can check the cause, probably some syntax error. Can you post the current version? Can look at it this evening.
    Here the modified master_homemenu.xaml and the resulting error logs.
     

    Attachments

    • screens.7z
      3.6 KB

    morpheus_xx

    Retired Team Member
  • Team MediaPortal
  • March 24, 2007
    12,073
    7,459
    Home Country
    Germany Germany
    I have pushed the changes with MP2 button. Problem is, that I want the button to be visible always, so it's as the power button in master_bare.
    But it needs to be disabled only, if MainMenus are shown. If it's not disabled and pressed all other menus are deactivated. By adding IsEnabled="{Binding Source={StaticResource MenuModel},Path=!IsMainMenu}" this could be achieved, I have no other idea at the moment.
    I will check this. There may be other ways in doing this.

    Here the modified master_homemenu.xaml and the resulting error logs.
    Please check this for example: https://github.com/MediaPortal/Medi...in/Skin/default/screens/test-opacitymask.xaml. Define the StoryBoards are resource and then use {StaticResource}.

    Just tried the Default skin. I don't see any effect during navigation.
    I was afraid of this. I'm quite sure it worked before, screens where scaled down on leave and scale up to full size on show. Have to check this as well.
     

    ge2301

    Lead Design MP2
  • Team MediaPortal
  • January 11, 2014
    8,741
    3,501
    Stuttgart
    Home Country
    Germany Germany
    Please check this for example: https://github.com/MediaPortal/Medi...in/Skin/default/screens/test-opacitymask.xaml. Define the StoryBoards are resource and then use {StaticResource}.
    Oursourcing the storyboard as resource does not give errors any more! But the effect is not as intended. I'll try a bit around and post the latest version

    Buttons.xaml:
    HTML:
          <Storyboard x:Key="Enter" BeginTime="00:00:00" >
                    <DoubleAnimation Storyboard.TargetName="ControlsGrid"
                                Storyboard.TargetProperty="(Canvas.Left)"
                                From="-820" To="0" Duration="0:0:0.9" />
          </Storyboard>
    
            <Storyboard x:Key="Leave" BeginTime="00:00:00" >
                    <DoubleAnimation Storyboard.TargetName="ControlsGrid"
                                Storyboard.TargetProperty="(Canvas.Left)"
                                From="0" To="{Binding ElementName=canvas, Path=ActualWidth}" Duration="0:0:0.9" />
          </Storyboard>
     

    Attachments

    • screens.7z
      2.1 KB
    Last edited:

    morpheus_xx

    Retired Team Member
  • Team MediaPortal
  • March 24, 2007
    12,073
    7,459
    Home Country
    Germany Germany
    I think I know the reason for difference:
    WPF:
    XML:
      <BeginStoryboard>
      <Storyboard>
      <DoubleAnimation Storyboard.TargetName="ControlsGrid"
      Storyboard.TargetProperty="(Canvas.Left)"
      From="-520" To="0" Duration="0:0:0.5" />
      </Storyboard>
      </BeginStoryboard>
    So "StoryBoard" object is added to default collection/property of BeginStoryBoard. MPF probably does not have defined this.
    In theory this should work then:
    XML:
      <BeginStoryboard>
     <BeginStoryboard.Storyboard>
      <Storyboard>
      <DoubleAnimation Storyboard.TargetName="ControlsGrid"
      Storyboard.TargetProperty="(Canvas.Left)"
      From="-520" To="0" Duration="0:0:0.5" />
      </Storyboard>
     </BeginStoryboard.Storyboard>
      </BeginStoryboard>

    Note the difference: <BeginStoryboard.Storyboard> defines the property to set.

    Another point I'll have to check :)
     

    ge2301

    Lead Design MP2
  • Team MediaPortal
  • January 11, 2014
    8,741
    3,501
    Stuttgart
    Home Country
    Germany Germany
    In theory this should work then:
    XML:
      <BeginStoryboard>
    <BeginStoryboard.Storyboard>
      <Storyboard>
      <DoubleAnimation Storyboard.TargetName="ControlsGrid"
      Storyboard.TargetProperty="(Canvas.Left)"
      From="-520" To="0" Duration="0:0:0.5" />
      </Storyboard>
    </BeginStoryboard.Storyboard>
      </BeginStoryboard>
    Note the difference: <BeginStoryboard.Storyboard> defines the property to set.
    Brings errors again:
    MediaPortal.UI.SkinEngine.Xaml.Exceptions.XamlLoadException: XAML loader: Error parsing file 'C:\Program Files (x86)\Team MediaPortal\MP2-Client\Plugins\BlueVision\Skin\BlueVision\screens\master_homemenu.xaml' ---> System.InvalidOperationException: Attached property 'BeginStoryboard.Storyboard' is not available on new target object 'MediaPortal.UI.SkinEngine.Controls.Visuals.Triggers.EventTrigger'
     

    Users who are viewing this thread

    Top Bottom