[confirm] Bugs with <border*>? (1 Viewer)

n4orcer

MP Donator
  • Premium Supporter
  • May 5, 2008
    116
    26
    Sweden
    Home Country
    Sweden Sweden
    MediaPortal Version: 1.0.1.0
    MediaPortal Skin: Maya
    Windows Version: Windows 7 x64
    CPU Type: AMD 4850e
    HDD: Segate 320GB
    Memory: Crosair 4GB XMS PC6400
    Motherboard: Gigabyte GA-MA78MG-S2H
    Video Card: ATI x3200
    Video Card Driver: 9.3
    Sound Card: Realtek HD-Audio
    Sound Card AC3: Optical out
    Sound Card Driver: v2.21
    1. TV Card:
    1. TV Card Type:
    1. TV Card Driver:
    2. TV Card:
    2. TV Card Type:
    2. TV Card Driver:
    3. TV Card:
    3. TV Card Type:
    3. TV Card Driver:
    4. TV Card:
    4. TV Card Type:
    4. TV Card Driver:
    MPEG2 Video Codec: FFDShow
    MPEG2 Audio Codec: FFDSho
    h.264 Video Codec: Cyberlink H.264/AVC Decoder
    Satelite/CableTV Provider:
    HTPC Case: Silverstone LC16-MR
    Cooling: 5x Noctuna 80mm 10db
    Power Supply: Acer 400W
    Remote: Logitech diNovo Edge, iMON PAD
    TV: LG 42LY95
    TV - HTPC Connection: HDMI trough Onkyo 876

    After redoing most of our graphics for our skin "Essence", we found out that there appears to be a bug with the "new" <border> control.

    It applies during animations and we have noticed it during fade animations. It looks like the border's do not fade in but is loaded directly when the animation starts.

    Edit: It works fine when using Slide instead of Fade.

    This is confirmed on two different computers using RC1.

    This is the code we use:
    Code:
    <texture>gui.common.border.gradient.background.png</texture>
    <border texture="gui.common.border.side.png" textureRepeat="yes" textureRotate="no" position="OutsideControl">1</border>

    The image "gui.common.border.side.png" is a 1pixel image filled with white at 50% opacity.

    Could this be the same kind of bug as with the <shadow*>?

    /n4orcer
     

    Users who are viewing this thread

    Top Bottom