Jump to content

bahmet

Members+
  • Posts

    321
  • Joined

  • Last visited

Posts posted by bahmet

  1. 4 часа назад, TCSSkin сказал:

    This is how i'd do it personally, 

    image.png.b6e18de603900e32db93101206551100.png

      Скрыть контент
    	<!-- CHANGE THE MIDDLE ALIGNMENT TO TOP IF YOU WANT IT AT THE TOP OF THE PANEL, BOTTOM ETC -->
    	<attachment_group class="vertical_arrange" vertical_alignment="middle"/>
    
    	<!-- STADIUM NAME -->
    	<widget class="stadium_button" id="namV" style="bold" size="large" auto_size="vertical" alignment="centre" icon_enabled="false">
    		<!--CALLS THE STADIUM NAME LABEL FROM STADIUM PROPERTIES.XML, WHICH CAN BE FOUND IN PROPERTIES.FMF -->
    		<record id="object_property" get_property="stad"/>
    	</widget>
    	
    	<!-- CONTAINER HOLDING CITY AND CAPACITY -->
    	<container>
    		<!-- LAYOUT IS SPLIT INTO TWO. IT ARRANGES THE PANEL HORIZONTALLY, USING A FILL ALIGNMENT. IT THEN MAKES USE OF A VERTICAL AUTOSIZE SO WE DON'T HAVE TO DEFINE HEIGHTS -->
    		<!-- CONTAINERS USED MUST BE AUTOSIZE CONTAINERS, AND TEXT WIDGETS MUST HAVE AUTO_SIZE VERTICAL TO WORK -->
    		<attachment_group class="horizontal_arrange_vertical_autosize" horizontal_alignment="fill"/>
    
    		<!-- CITY -->
    		<container>
    			<!-- AS MENTIONED PREVIOUSLY, THIS CONTAINER REQUIRES A AUTOSIZE -->
    			<!-- YOU CAN ADJUST THE SPACING BETWEEN THE TWO PANELS BY EDITING THE GAP VALUE. MINUS VALUES WILL BRING IT CLOSER, WHILE POSITIVE VALUES PUSHES IT APART -->
    			<attachment_group class="vertical_arrange_autosize" vertical_gap="0"/>
    			
    			<!-- DEFAULT PROPERTIES USED SO WE DON'T HAVE TO DEFINE THE SAME ATTRIBUTES AGAIN -->
    			<record id="default_properties" auto_size="vertical" alignment="centre"/>
    
    			<!-- LABEL -->
    			<widget class="label" font="label" colour="faded text">
    				<!-- THE LABEL CALLS THE ID FOR THE CITY FROM STADIUM PROPERTIES, THEN THE NAME="TRUE" ATTRIBUTE MAKES IT LOAD THE VALUE THAT IS DEFINED AS NAME -->
    				<record id="object_property" get_property="SctI" name="true"/>
    			</widget>
    
    			<!-- CITY -->
    			<widget class="city_label">
    				<record id="object_property" get_property="SctI"/>
    			</widget>
    		</container>
    		
    		<!-- CAPACITY -->
    		<container>
    			<!-- AS MENTIONED PREVIOUSLY, THIS CONTAINER REQUIRES A AUTOSIZE -->
    			<!-- YOU CAN ADJUST THE SPACING BETWEEN THE TWO PANELS BY EDITING THE GAP VALUE. MINUS VALUES WILL BRING IT CLOSER, WHILE POSITIVE VALUES PUSHES IT APART -->
    			<attachment_group class="vertical_arrange_autosize" vertical_gap="0"/>
    			
    			<!-- DEFAULT PROPERTIES USED SO WE DON'T HAVE TO DEFINE THE SAME ATTRIBUTES AGAIN -->
    			<record id="default_properties" auto_size="vertical" alignment="centre"/>
    
    			<!-- LABEL -->
    			<widget class="label" font="label" colour="faded text">
    				<!-- THE LABEL CALLS THE ID FOR THE CAPACITY FROM STADIUM PROPERTIES, THEN THE NAME="TRUE" ATTRIBUTE MAKES IT LOAD THE VALUE THAT IS DEFINED AS NAME -->
    				<record id="object_property" get_property="Scpy" name="true"/>
    			</widget>
    
    			<!-- CAPACITY -->
    			<widget class="dashed_number_label">
    				<record id="object_property" get_property="Scpy"/>
    			</widget>
    		</container>
    
    	</container>

     

     

    I'll try.

    Here I want to apply it.

    image.png.59f58aae615e2146c0dce03aaaa1fbe4.png

  2. How to make such a structure? Am I doing the right thing?

    image.png.66dc641b10066c9d4ec24e80ac18c522.pngimage.png.fc5f821ecd3665ba2e562b6fa90b3d40.png

    Спойлер
    <container class="main_transparent_box_no_margin" width="180" >
    	<layout class="arrange_vertical_attachment" layout="-1,-1" offset="0" gap="10" />	
    	<layout class="stick_to_sides_attachment" alignment="all" apply_to_children="true" inset="10" />
    	
    			<widget class="stadium_button" id="stad" auto_size="all"  navigation_focus_target="false" size="9" font="title" alignment="left,can_scale" offset="-5">
    					<layout class="centre_in_parent_attachment" alignment="all" />
    					<translation id="no_object_text" translation_id="227505" type="use" value="Unknown Stadium"/>
    					<string id="format" value="[%stadium#1-short]" />
    					<record id="object_property" get_property="stad" />
    			</widget>
    	
    	<container>	
    		<layout class="arrange_horizontal_attachment" layout="-1,-1" offset="0" gap="10" />
    			<widget class="city_label" id="namL" alignment="left,can_scale" style="bold" colour="white" size="8" font="title">
    				<record id="object_property">
    					<integer id="get_property" value="SctI" />
    				</record>
    			</widget> 
    		
    		<!--attendance-->
    		<container>
    			<attachment_group class="horizontal_arrange_vertical_autosize" horizontal_alignment="middle" />
    			<widget class="label" auto_size="all">
    				<translation id="text" translation_id="247242" type="use" value="Attendance" />
    			</widget>
    			<widget class="number_label" auto_size="all">
    				<record id="object_property" get_property="FxEA" dont_set_hint="true" />
    			</widget>
    		</container>
    		
    	</container>	
    </container> 

     

     

  3. 6 часов назад, ryandormer сказал:

    Я думал, что это так, поскольку уверен, что где-то несколько лет назад читал, что это всего лишь ярлык. Я сомневался только в том, что изменение "текучести команды" по-прежнему влияет на привычку вашей команды к свободе творчества. Кажется странным, что ваша команда стала бы менее знакомой с требуемой от них творческой свободой, если бы "текучесть команды" вообще не влияла на творческую свободу.

    This is an interface bug.

×
×
  • Create New...