Page 1 of 2 12 LastLast
Results 1 to 20 of 30

Thread: [CODING] XML Skinning system buglist

  1. #1

    Join Date
    Feb 2004
    Posts
    1,037

    [CODING] XML Skinning system buglist

    Hey all,
    I am working to get the hang of the new skinning system of Xfire by translating my old skin to the new code.
    I found a few problems i ran into while coding. Post in this topic the problems and bugs you find and I edit the first post for the developers. I know the system is still in test-phase, but this is to help the developers to find problems and fix them in the final release.

    Text in red are replies by the developers I got.

    Only post bugs and problems you found in the code, if you want help with the XML system, please use THIS topic.

    Wiki
    There has been a Wiki set up to help with everything related to Xfire. There is also a section for coding skins in the new XML-format. It is far from being finished, but we are working on it. Visit it here.

    [Buglist v1.58]
    - The tooltip colors are not inplemented yet (Fixed in v1.59)
    - ResizeX and ResizeY are for the main windows needed in the "components.xml", not in the "mainwindow.xml". ResizeX and ResizeY are stored for all the other components in the "mainwindow.xml" (Placing them in both but it is not needed or used. Think it is a bug that for the main window this must be placed in the "components.xml") (Partly fixed in v1.59)
    - Components placed in a TabControl do not disappear when switching tabs. Instead components in the active tab overwrite them. So if there is not the same amount of buttons in one TabControl, the old buttons are still shown.
    (This is used to be this way. If you want to overwrite buttons with a bigger button you must use a higher Z-index, and replace the empty buttons with transparent tiles.)(Still in progress)
    - Scrollbars are not working (Scrollbars do work, see third post)
    - Font settings of text with a "State" (like "WritingMessage") doesn't work properly. (Not fixed, see v1.59)
    - Background "Header buddyview" not definable in themes.xml
    (Works, use
    Code:
    <Images HeaderColor="HeaderColor">
    instead of
    Code:
    <Images Color="HeaderColor">
    - WindowFocus="True" is not working in ChatEdit class. (Fixed in v1.59)


    [Buglist v1.59]
    - Although almost all ResizeX and ResizeY tags are moved away from the components.xml to the window xml files, is the ResizeX and ResizeY for the popups still in the components.xml needed.
    - Font settings of text with a "State" (like "WritingMessage") doesn't work properly. (Temporary bugfix: place all font definitions in State="Normal" instead of State="Disabled")

  2. #2

    Join Date
    Apr 2004
    Posts
    1,990
    Great idea to have a post like this. You have mentioned several of the issues/bugs i have discovered so far. If i find anything not listed yet i'll be sure to post here.

  3. #3

    Join Date
    Dec 2003
    Posts
    31
    - The tooltip colors are not inplemented yet (planned for next update)
    This was caught late in QA and was not able to make it in the release. It's been fixed and will be out next release.

    - ResizeX and ResizeY are for the main windows needed in the "components.xml", not in the "mainwindow.xml". ResizeX and ResizeY are stored for all the other components in the "mainwindow.xml" (Placing them in both but it is not needed or used. Think it is a bug that for the main window this must be placed in the "components.xml")
    This is because of the strange compatibility that we have w/ the old ini skins. We're looking into putting special code to move this into the layout instead of the components section.

    EDIT: We just fixed this so that it's now in the mainwindow.xml section instead of the components section.

    - Components placed in a TabControl do not disappear when switching tabs. Instead components in the active tab overwrite them. So if there is not the same amount of buttons in one TabControl, the old buttons are still shown.
    We believe this is the same behavior as the old skins. We can fix this in the future.

    - Scrollbars are not working (???)
    Specifying a scrollbar looks like the following in the components section.

    Code:
    	<Component Name="DefaultScrollbar"
    		Class="Scrollbar"
    		>
    		<Images State="Normal" Color="ScrollbarColor" ColorBG="ScrollbarColorBG">
    			<Image Type="ScrollLeft">SCROLLLEFTNORM</Image>
    			<Image Type="ScrollRight">SCROLLRIGHTNORM</Image>
    			
    			<Image Type="ScrollUp">SCROLLUPNORM</Image>
    			<Image Type="ScrollDown">SCROLLDOWNNORM</Image>
    			
    			<Image Type="ScrollHorzGripperLeft">SCROLLGRIPPERHORZLEFT</Image>
    			<Image Type="ScrollHorzGripperMiddle">SCROLLGRIPPERHORZMIDDLE</Image>
    			<Image Type="ScrollHorzGripperOverlay">SCROLLGRIPPERGRIPSHORZ</Image>
    			<Image Type="ScrollHorzGripperRight">SCROLLGRIPPERHORZRIGHT</Image>
    			
    			<Image Type="ScrollVertGripperTop">SCROLLGRIPPERVERTTOP</Image>
    			<Image Type="ScrollVertGripperMiddle">SCROLLGRIPPERVERTMIDDLE</Image>
    			<Image Type="ScrollVertGripperOverlay">SCROLLGRIPPERGRIPSVERT</Image>
    			<Image Type="ScrollVertGripperBottom">SCROLLGRIPPERVERTBOTTOM</Image>
    			
    			<Image Type="ScrollHorzGutterLeft">SCROLLBACKGROUNDHORZLEFT</Image>
    			<Image Type="ScrollHorzGutterMiddle">SCROLLBACKGROUNDHORZMIDDLE</Image>
    			<Image Type="ScrollHorzGutterRight">SCROLLBACKGROUNDHORZRIGHT</Image>
    			
    			<Image Type="ScrollVertGutterTop">SCROLLBACKGROUNDVERTTOP</Image>
    			<Image Type="ScrollVertGutterMiddle">SCROLLBACKGROUNDVERTMIDDLE</Image>
    			<Image Type="ScrollVertGutterBottom">SCROLLBACKGROUNDVERTBOTTOM</Image>
    		</Images>
    		<Images State="Hover" Color="ScrollbarColor" ColorBG="ScrollbarColorBG">
    			<Image Type="ScrollLeft">SCROLLLEFTHOVER</Image>
    			<Image Type="ScrollRight">SCROLLRIGHTHOVER</Image>
    			
    			<Image Type="ScrollUp">SCROLLUPHOVER</Image>
    			<Image Type="ScrollDown">SCROLLDOWNHOVER</Image>
    			
    			<Image Type="ScrollHorzGripperLeft">SCROLLGRIPPERHORZLEFTHOVER</Image>
    			<Image Type="ScrollHorzGripperMiddle">SCROLLGRIPPERHORZMIDDLEHOVER</Image>
    			<Image Type="ScrollHorzGripperRight">SCROLLGRIPPERHORZRIGHTHOVER</Image>
    			
    			<Image Type="ScrollVertGripperTop">SCROLLGRIPPERVERTTOPHOVER</Image>
    			<Image Type="ScrollVertGripperMiddle">SCROLLGRIPPERVERTMIDDLEHOVER</Image>
    			<Image Type="ScrollVertGripperBottom">SCROLLGRIPPERVERTBOTTOMHOVER</Image>
    		</Images>
    		<Images State="Down" Color="ScrollbarColor" ColorBG="ScrollbarColorBG">
    			<Image Type="ScrollLeft">SCROLLLEFTDOWN</Image>
    			<Image Type="ScrollRight">SCROLLRIGHTDOWN</Image>
    			
    			<Image Type="ScrollUp">SCROLLUPDOWN</Image>
    			<Image Type="ScrollDown">SCROLLDOWNDOWN</Image>
    			
    			<Image Type="ScrollHorzGripperLeft">SCROLLGRIPPERHORZLEFTDOWN</Image>
    			<Image Type="ScrollHorzGripperMiddle">SCROLLGRIPPERHORZMIDDLEDOWN</Image>
    			<Image Type="ScrollHorzGripperRight">SCROLLGRIPPERHORZRIGHTDOWN</Image>
    			
    			<Image Type="ScrollVertGripperTop">SCROLLGRIPPERVERTTOPDOWN</Image>
    			<Image Type="ScrollVertGripperMiddle">SCROLLGRIPPERVERTMIDDLEDOWN</Image>
    			<Image Type="ScrollVertGripperBottom">SCROLLGRIPPERVERTBOTTOMDOWN</Image>
    		</Images>
    		<Images State="Disabled" Color="ScrollbarColor" ColorBG="ScrollbarColorBG">
    			<Image Type="ScrollLeft">SCROLLLEFTDISABLED</Image>
    			<Image Type="ScrollRight">SCROLLRIGHTDISABLED</Image>
    			
    			<Image Type="ScrollUp">SCROLLUPDISABLED</Image>
    			<Image Type="ScrollDown">SCROLLDOWNDISABLED</Image>
    		</Images>
    	</Component>
    Then in the places where scrollbars are used, you do this.

    Code:
    	<Component Name="BuddyView"
    		Class="BuddyListView"
    		WindowFocus="true"
    		Color="BuddyViewBG"
    		Scrollbar="DefaultScrollbar"
    		>...</Component>
    - Font settings of text with a "State" (like "WritingMessage") doesn't work properly.
    This is a bug which should be fixed next release.

    - Background "Header buddyview" not definable in themes.xml (???)
    This should be working. You specify the header information like this.

    Code:
    <Component Name="BuddyView" ...>
    		<Images HeaderColor="HeaderColor">
    			<Image Type="HeaderLeft">LISTVIEWHEADERLEFT</Image>
    			<Image Type="HeaderMiddle">LISTVIEWHEADERMIDDLE</Image>
    			<Image Type="HeaderRight">LISTVIEWHEADERRIGHT</Image>
    			<Image Type="HeaderArrowUp">LISTVIEWHEADERARROWUP</Image>
    			<Image Type="HeaderArrowDown">LISTVIEWHEADERARROWDOWN</Image>
    			<Image Type="Collapsed">ARROWRIGHT</Image>
    			<Image Type="Expanded">ARROWDOWN</Image>
    		</Images>
    </BuddyView>

  4. #4

    Join Date
    Apr 2004
    Posts
    1,990
    @ Yulius

    Thanks for the information. Greatly appreciated.

  5. #5

    Join Date
    Dec 2003
    Posts
    31
    starting up xml xfire skin development wiki site.

    This URL has been changed
    http://wiki.xfire.com/

    I'll try to put more information.

    EDIT. Changed url from skinwiki.xfire.com to wiki.xfire.com

  6. #6

    Join Date
    Feb 2005
    Posts
    1,913
    Great! Love you :-*

  7. #7

    Join Date
    Mar 2004
    Posts
    692
    Quote Originally Posted by yulius
    starting up xml xfire skin development wiki site.

    http://skinwiki.xfire.com/

    I'll try to put more information.
    Very cool. That's exactly what we needed for this new way of coding.

    Of course now I need to find one on what this XML thing is all together. :shock:

  8. #8

    coding

    Coding? I didn't know u could use coding, you mean on your profile? Can someone show me where to paste it?

  9. #9

    Join Date
    Apr 2004
    Posts
    1,990
    The coding/scripting being talked about is for the Xfire client skinning systems. The user interface that you see when you open your Xfire.

  10. #10

    Join Date
    Apr 2004
    Posts
    1,990
    I've found a reproducible bug.

    This is with the call button for the chat skins. When you are recieving a voice call with just one chat window open after just starting the "xfire" skin the animated gif for ringing will play as it should, but if there are two or more chat windows open the animations stop working and wont start again until the skin is reloaded.

  11. #11
    Xfire Loyalist
    Join Date
    Feb 2004
    Posts
    1,575
    can you add this stuff to the wiki

    Most Questions answered here - http://www.xfire.com/faq/

  12. #12
    Nice Tut

  13. #13
    Wiki site link is dead.

  14. #14

    Join Date
    Feb 2007
    Posts
    5
    Please missing skining function on contex menu and dialog. Please add this functions. Thx

    PS: Sry, I don't speak english ;-)

  15. #15
    nice :lol:

  16. #16

  17. #17

    RE: [CODING] XML Skinning system buglist

    I found that I cant edit the layout of XIG2BAR.xml to a significant degree.

    If I place any of the buttons except for "XFire" "Edit" and "Game" before the alert status container, it causes any and all games to crash when attempting to bring up the in-game overlay.

    on a further note, even commenting out the alert status container causes such a crash, but commenting out everything after it, does not.

  18. #18
    Xfire Loyalist
    Join Date
    Feb 2008
    Posts
    341

    RE: [CODING] XML Skinning system buglist

    Quote Originally Posted by yuukiminoru
    I found that I cant edit the layout of XIG2BAR.xml to a significant degree.

    If I place any of the buttons except for "XFire" "Edit" and "Game" before the alert status container, it causes any and all games to crash when attempting to bring up the in-game overlay.

    on a further note, even commenting out the alert status container causes such a crash, but commenting out everything after it, does not.
    The XIG Bar is limited to what you can do to it. As you found out if you try to remove any of the default components or include any news ones it will not work. You also can't really position those tiles (except for the clock and fps but even then you can only move them up and down), but you can position the space between them and some other minor things.

    So basically, make buttons for the elements, a background for the bar, and colors for the text that is on it and that's all you can do to the bar.
    Looking for Xfire skins? http://www.harrisj.net/

  19. #19

    Join Date
    Dec 2009
    Posts
    116

    RE: [CODING] XML Skinning system buglist

    just saw we have a bug list thread =)

    "my" bug is here: http://www.xfire.com/forums/182629/topic/2261836/

    the colorshift dont work. =/

  20. #20

    Join Date
    Dec 2009
    Posts
    116

    RE: [CODING] XML Skinning system buglist

    Main InfoView bug:

    when you maximize the main window with open infoview,
    then (double click on title bar) back to normal size
    the background from the infoview dont show up anymore.

    But only when u set:

    Y="ShadowInfoTop.BOTTOM"
    X="ShadowInfoLeft.right"
    Indentright="Right.width"
    IndentBottom="ShadowInfoBottom.HEIGHT"







    <Tile Name="ShadowMainInfoViewPopup"
    JustX="LEFT" JustY="TOP" x="right.right" Y="49" Z="5" IndentBottom="2"
    Component="MainInfoViewPopup">



    <Tile Name="Middle"
    Z="1"
    Y="ShadowInfoTop.BOTTOM"
    X="ShadowInfoLeft.right"
    Indentright="Right.width"
    IndentBottom="ShadowInfoBottom.HEIGHT"
    ResizeX="100"
    ResizeY="100"
    Component="InfoMiddle">
    </Tile>


    <Tile Name="ShadowInfoTop"
    ResizeX="100"
    IndentLeft="1"
    Component="InfoTop"
    >
    </Tile>
    <Tile Name="ShadowInfoBottom"
    JustY="BOTTOM"
    ResizeX="100"
    IndentLeft="1"
    Component="InfoBottom"
    >
    </Tile>
    <Tile Name="ShadowInfoLeft"
    JustX="LEFT"
    x="1"
    ResizeY="100"
    Component="InfoLeft"
    >
    </Tile>
    <Tile Name="ShadowInfoRight"
    JustX="Right"
    x="0"
    ResizeY="100"
    Component="InfoRight"
    >
    </Tile>

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •