Jump to content

BuzzR

Members+
  • Posts

    379
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by BuzzR

  1. 3 minutes ago, EnigMattic1 said:

    Being a total novice, I honestly don't even know where to start. I have the 2 xml files mentioned above, but the actual code is pretty much alien to me at the moment.

    Don't worry. I was lost a couple of weeks ago, too. I am not an expert - far from it, but I've grinded through the info found on the forums, so things are getting clearer- at least a little :) .

    1. So first of all, you need the base skin. Check this topic by @michaeltmurrayuk Base Skins 2021 . All the basics are there, including how to install one of them.

         After you've got one of the basic skin in place, you can modify it without worries of messing with the default one.

    2. Go to the skin folder you've just installed.

        In the "\panels" folder create another folder called "club". 

    3. Copy in this "club" folder the file "club overview stadium panel.xml" from the previous posts.

    4. In game clear cache & reload the skin. ( See instructions on the Base Skins 2021 topic )

    Obs. There is no need of "club overview panel.xml" if you do not modify the default one.

    Obs. You can edit the files ( ex: change the size of the widget - see previous posts ) with your game running. Edit the file, save it, reload the skin in-game. Remember to clear cache if you have it checked. 

     

  2. 10 hours ago, McClane29 said:

    Thanks for all the effort you've made in assisting, @BuzzR

    Unfortunately though, I can't locate the code you have stated above. I am only using the 'Club Overview Panel' which I have attached.

    Should I have a "club overview stadium panel.xml" too? If so, could you share such file.

    Don't mention it. Glad to be helpful. 

    I've seen your "club overview panel.xml"  now. It looks like you have added the stadium picture widget directly in this panel.

    What I've seen others do - more skilled and experienced with fm skinning - they do keep things separately as the devs intended ( separation of concerns and all that :) ).

    So, there is a default file witch is named "club overview stadium panel.xml" that does this - encapsulates the stadium info to be used by "club overview panel.xml".

    In this file we've added the stadium picture widget, so if we want to see the stadium info and the picture we will only reference this file/panel and not edit other files/panels every time.

    As @wkdsoul kindly mentioned, use the "club overview stadium panel.xml" I have provided (  copy this file next to your "club overview panel.xml" ).  It already has the picture widget.

    Delete the stadium picture widget from your "club overview panel.xml".

    If there are size issues with the picture, edit the "club overview stadium panel.xml" as we talk previously.

    Good luck.

  3. 8 hours ago, McClane29 said:

    Any other suggestions to reduce the size of the stadium image? Could there be something missing from the config which isn't making it recognise the changes to the default height?

    The stadium picture widget is nested inside a container, along with stadium name widget and city name widget, assuming you are using the club overview stadium panel.xml that is similar to the one I have.

    <container class="bordered_box" appearance="" >
    			<layout class="arrange_vertical_attachment" alignment="top,extend" layout="-1,-1,400" offset="0"/>
    			<layout class="stick_to_sides_attachment" alignment="horizontal" inset="0" apply_to_children="true"/>
    			
    			<!--stadium name-->
    			<widget class="client_object_label" size="13" style="bold" id="bbbb" alignment="centre_x,top">
    				<record id="object_property">
    					<integer id="get_property" value="objt" />
    				</record>
    			</widget>
    
    			<!--stadium city-->
    			<widget class="city_label" size="10" colour="white" id="nnnn" alignment="centre_x,top" show_nation="true">
    				<record id="object_property">
    					<integer id="get_property" value="SctI" />
    				</record>
    			</widget>	
    			
    			<!--Stadium picture-->
    			<widget class="stadium_picture" id="STAp" priority="1" image_alignment="centre_x, centre_y" keep_aspect_ratio="true" default_height="400">
    				<record id="object_property">
    					<integer id="get_property" value="objt" />
    					<integer id="set_property" value="objt" />
    				</record>
    			</widget>				
    		</container> 		

    There is a line that defines how this widgets are sharing the height of the container, with a property  layout="-1,-1,400" .

    I think you should use the same value here ( for the third value ) as the default_height you are going for. 

    So for example: default_height="200", then change layout="-1,-1,200" for the container.

    Maybe there is no need for default_height for the widget if you use the layout parameter for the nesting container. You should try and see.

    I am also doing a lot of trial and error with all this skining.

    Good luck.

     

    Edit: spelling. 

  4. Glad it worked.

    8 hours ago, McClane29 said:

    However, it needs tweaking slightly as it is very close to the text above and below. Any suggestions to make the image smaller etc? 

    I suggest you lower the value of default_height property from the stadium picture widget. Play a little with some values, see what works for you. 

    Good luck.

     

  5. There are some UI choices that feel strange, imho.

    1. Team Talk screen :

    User's eyes are all over the place in this screen.. players and their reactions are left , top , right. One has to go over every individual player widget to see reactions / rating. 

    A list was perfect for this as you can assess immediately what has changed. Even a list of widgets, but they should be all in the same place.

    Individual Team talk, again moving from bottom left to top right of the screen to check boxes.

    2. Match screen

    Play / Pause button is on one side of the screen , Skip replay button is on the other side under the score ( why? ) .

    Again user's eyes are all over the screen in between highlights: 

      a. text commentary down middle screen,

      b. own players health and morale icons bottom right vs opposition players middle screen right,

      c. stats left screen vs stats right screen.

      d. assistant manager feedback - center screen.

      e. Scores on other stadiums , bottom left popup.

      f. There are 3 panels with 3 different sizes and/or alignments between highlights. Top left anchor, center small one, center (?!) right big one... why ?!

     

     

     

     

  6. These are 2 screens I have modified on the base dark skin using inspiration from various skins -  rensie, newton, royal - and some posts from around here.

    I cannot say I will release this, as there isn't much to release :) and some panels are scaled for my resolution ( I think ) - as I am kind of old and my sight is not so good :).

    Anyway , I would love to add some stuff from here and there, mod other screens maybe.. but there is such a tedious job to try, test, retry in order to identify xmls, widgets etc.

    20201203221450_1.jpg

    20201203221720_1.jpg

  7. Hi..

    If you didn't solve it, here is my suggestion.

    I think you need to edit "club overview stadium panel. xml" and add the picture widget 

    <!--Stadium picture-->
    			<widget class="stadium_picture" id="STAp" priority="1" image_alignment="centre_x, centre_y" keep_aspect_ratio="true" default_height="400">
    				<record id="object_property">
    					<integer id="get_property" value="objt" />
    					<integer id="set_property" value="objt" />
    				</record>
    			</widget>			

    I have tested your "club overview panel.xml" and it works with my own edited " club overview stadium panel.xml". ( see file attached ).

    Good luck.

    club overview stadium panel.xml

×
×
  • Create New...