Jump to content

Vakzin_QPR

Members+
  • Posts

    78
  • Joined

  • Last visited

Posts posted by Vakzin_QPR

  1. 2 hours ago, abbespl said:

    No, no, it's not about "add condition", it's those additional options "exclude" in right bottom corner of "edit search". As I remember from all previous editions of FM it was always an option "players not suitable for national team" or something similar.

    Here's the screenshot with only two options to exclude, nothing about National Team tho:

    Thank you for your information, screenshot and video!

    My conclusion is that the cause of this is not the skin.

    In Fm Full version, click_event="scdi" distinguish Nations from Clubs and open the corresponding dialog which is controlled by either one of the following two.
      If Clubs, "dialogs/person search dialog.xml" controls the panel.
      If Nations, it's "dialogs/person search dialog nation.xml".

    This doesn't work in FM Touch, I suppose.

    In Nations, three buttons(clear, exclude & OK) lean to the right.
    In Clubs, three buttons(settings, clear & exclude) lean to the left.
    As far as I see your screenshot, three lean to the left.
    (Is it right it's nation manager's?)
    If so, this means "dialogs/person search dialog nation.xml" doesn't work.

    In terms of this skin,
    I've editted "person/person search list.xml", but the code about "New Search" button is the same as the default skin.
    And I've not edited the following four.
     "dialogs/person search dialog.xml",
     "dialogs/person search dialog nation.xml",
     "filter_panels/person search filter popup.xml" and 
     "filter_panels/filter table small.xml".

    In short, I can't fix this problem.

    P.S.
    It's  very difficult for me too to pronounce "Grzegorz Brzęczyszczykiewicz"!
    I know only that ę is not e, but en(?). Like Wojciech Szczęsny.

  2. 1 hour ago, abbespl said:

    as far as I know that option needs to be unlocked by playing the game, sort of achievement reward. Eventually can be bought from Store inside the game. Then it shows like this while starting new game:

    Thank you for your information.
    I'm not going to pay more money, so I checked the problem in FM full version.

    However...
    I'm not sure what is the cause of them.

    1) General info view changes to default look when managing both National Team and Club.

    It also occurs in FM full version.
    I can't fix it by changing the codes of general view for fantasy draft and general view for create a club
      and by changing the ID "geni" to another.

    2) while searching for players I don't have options to search only for players who can play in my National team, that option is completely gone.

    About this, I couldn't understand what is the problem.
    If it is about the contents of "Add condition", we can't edit it.

    If not, could you attach the screenshots in which the language is changed to English and point the problem out?
       I'm sorry but what I know about Polish is only the pronunciation of Paweł Wszołek.

     

      FM Full                                                                                                                                FM Touch

    974414858_conditionF.thumb.jpg.89b98aacba1ea8fd6bf6d572e166fd32.jpg199507229_conditionT.thumb.jpg.e35337bfe0c2dbf4eb23c754a51a0f33.jpg

  3. 12 hours ago, abbespl said:

    General info view changes to default look when managing both National Team and Club. Also, while searching for players I don't have options to search only for players who can play in my National team, that option is completely gone.

    Thank you for letting me know.
    I'll check it.

    Added
    > when managing both National Team and Club
    When start a new game, I could only select Club Manager or Unemployed in FM Touch.

    Could you please let me know how to choose managing both National Team and Club in FM Touch?

    Thanks in advance.

  4. 55 minutes ago, abbespl said:

    how the heck I can move this panels a bit down, to stop text to covering itself.

    You could add class="inner_box" to the 2nd line (probably) of "player overview popup selector panel".
        <container id="SUBP" class="inner_box">

  5.     <container>
          <attachment_group class="horizontal_arrange" horizontal_alignment="fill" horizontal_offset="4" horizontal_gap="8" vertical_inset="0"/>
          <record id="default_properties">
            <list id="attachments">
              <record class="vertical_arrange" vertical_alignment="fill" vertical_offset="0" vertical_gap="0" horizontal_inset="0"/>
            </list>
            <record id="default_properties">
              <list id="attachments">
                <record class="vertical_arrange" vertical_alignment="fill" vertical_offset="0" vertical_gap="1" horizontal_inset="0"/>
              </list>
              <record id="default_properties" auto_size=""/>
            </record>
          </record>

            <container>
                <container>
                    <widget class="label" alignment="left,bottom" font="label">
                      <translation id="text" translation_id="458477" type="use" alignment="left" value="D.O.B.[COMMENT: player profile, personal details; Abbreviation for 'Date of Birth']"/>
                    </widget>
                    <container>
                      <attachment_group class="horizontal_arrange_vertical_autosize" horizontal_alignment="fill" horizontal_offset="0" horizontal_gap="4" vertical_alignment="top" vertical_inset="0"/>
                        <widget class="formatted_label" id="age " auto_size="vertical" font="value">
                          <translation id="format" translation_id="242551" type="use" value="[%number#1] years old"/>
                          <record id="object_property" get_property="Page" dont_set_hint="true"/>
                        </widget>
                        <widget class="dob_label" id="dobl" display_format="0" auto_size="vertical" font="value" colour="faded text">
                          <record id="object_property" get_property="Pdob"/>
                        </widget>
                    </container>
                </container>

                <container>
                    <widget class="label" alignment="left,bottom" font="label">
                      <translation id="text" translation_id="257347" type="use" value="Contract[COMMENT - transfer status filter text; offers at contract stage]"/>
                    </widget>
                    <container>
                      <attachment_group class="horizontal_arrange_vertical_autosize" horizontal_alignment="fill" horizontal_offset="0" horizontal_gap="4" vertical_alignment="top" vertical_inset="0"/>
                        <widget class="wage_label" id="Pcww" alignment="left,can_scale" auto_size="vertical" font="value">
                          <record id="object_property" get_property="Pcww"/>
                        </widget>
                        <widget class="contract_expiry_button" id="Pcex" alignment="left" auto_size="vertical" font="value" colour="faded text">
                          <record id="object_property" get_property="Pced"/>
                        </widget>
                    </container>
                </container>

                <container>
                    <widget class="label" alignment="left,bottom" font="label">
                      <translation id="text" translation_id="292633" type="use" value="Estimated Value[COMMENT: player profile; value label]"/>
                    </widget>
                    <widget class="value_label" id="valu" alignment="left,top" font="value">
                      <record id="object_property" get_property="Pdva" dont_set_hint="true"/>
                    </widget>
                </container>
            </container>

            <container>
                <container>
                    <container>
                      <attachment_group class="vertical_arrange" vertical_alignment="bottom"/>
                        <widget class="person_nationality_button" auto_size="vertical" font="value">
                          <record id="object_property" get_property="objt" set_property="objt"/>
                        </widget>
                    </container>
                    <widget class="international_appearances_label" alignment="left,top,can_scale" size="normal" style="light_bold">
                      <record id="object_property" get_property="Pist"/>
                    </widget>
                </container>

                <container>
                    <widget class="height_label" alignment="left,bottom" font="value">
                      <record id="object_property" get_property="Phei"/>
                    </widget>
                    <widget class="weight_label" alignment="left,top" size="10.5" style="light_bold">
                      <record id="object_property" get_property="Pwei"/>
                    </widget>
                </container>

                <container>
                    <widget class="label" alignment="left,bottom" font="label">
                      <record id="object_property" get_property="Pfot" name="true"/>
                    </widget>
                    <widget class="foot_label" alignment="left,top" font="value">
                      <record id="object_property" get_property="Pfot" dont_set_hint="true"/>
                    </widget>
                </container>
            </container>
        </container>

  6.     <container class="player_scout_reports_panel" file="none">
          <record id="object_property" get_property="objt" set_property="objt"/>
          <attachment_group class="vertical_arrange_autosize" vertical_offset="1" vertical_gap="1" horizontal_inset="2"/>
          <record id="default_properties">
            <list id="attachments">
              <record class="horizontal_arrange_vertical_autosize_centre" horizontal_alignment="right,extend" horizontal_offset="0" horizontal_gap="4" vertical_offset="0"/>
            </list>
            <record id="default_properties" auto_size="all"/>
          </record>

            <container>
                <widget class="label" font="label">
                  <translation id="text" translation_id="314426" type="use" value="Ability[COMMENT: player popup info panel - scout current ability rating]"/>
                </widget>
                <widget class="scout_stars_label" id="CAIC" click_event="ltms"/>
            </container>

            <container>
                <widget class="label" font="label">
                  <translation id="text" translation_id="314427" type="use" value="Potential[COMMENT: player popup info panel - scout potential ability rating]"/>
                </widget>
                <widget class="scout_stars_label" id="PAic" click_event="ltms"/>
            </container>
        </container>

  7. Thanks for your reply.

    1) Is there 
       "Documents/Sports Interactive/Football Manager 2020 touch/graphics" folder?
       or are there
       "Sports Interactive" or "Football Manager 2020 touch" folders in "Android files>Data>.comsega"?

    2) You can make fmf-files by using Resource Archiver.
       2-0) I'm not sure you can use Resource Archiver on Tablet.
            But you can use Resource Archiver on your laptop, I think.
       2-1) prepare the folders named "faces", "kits", "logos" and so on.
       2-2) put pictures and "config.xml" in those folders.
       2-3) press "Create Archive" in Resource Archiver.
       2-4) choose the folder you prepared.
       2-5) choose the "graphics" folder to save the fmf-file, or choose anywhere to save and move the fmf-files to the "graphics" folder after that.

    3) I made a sample, and will send you by Direct Message.
       Could you try that?

       Please put the "pictures" folder and "logos.fmf" into your graphics folder.
       And you need clear cache and reload skin.
       There are the logos of Premier League and the clubs in Premier League
       and the picture of The Kiyan Prince Foundation Stadium (QPR's).

  8. 49 minutes ago, mr_legalize said:

    There is no graphics folder that I can find on the tablet but I created one and it still doesnt seem to work. 

    Could you tell me the followings?
    1) Where did you make a folder named "graphics"?
    2) What are there in the "graphics" folder you made?
    3) What is the name of the fmf-file(s) you made?
    4) What are there in the new fmf-file(s)?
    5) Is there "config.xml" in the new fmf-file(s)?

  9. Because I don't have FM Touch for Tablet, I can't check if it works.
    But the followings might help you.

    1) Create fmf-files by using Resource Archiver.
           I hear that fmf-files more than 2GB don't work.
    2) Put them in graphic folder.
           I'm not sure where the "folder" is. 

    The site linked bellow may also help you.
    https://sortitoutsi.net/forums/topic/38013/how-to-add-kit-logo-and-face-packs-to-fm2018-touch-on-ios-on-ipad  

  10. 2 hours ago, JR866Gunner said:

    Quick question, what should I be doing with these two lines?

    1009th   <flags id="colour" value="negative" />
    932nd    <flags id="colour" value="positive" />

    Change to
        <flags id="colour" value="white" />
    or delete the two lines.

  11. On 01/04/2020 at 18:01, JR866Gunner said:

    How do I remove the club logos on the match preview screen please?

    the lines 91 to 121 of "YACS2020 Base/panels/match/match preview lineups panel.xml".

    On 02/04/2020 at 23:56, JR866Gunner said:

    How do I either make that alone white or maybe even the Wins white as well?

    on the line 1009 and 932 of "YACS2020 Base/properties/league stage properties.xml".

    9 hours ago, gibbo11 said:

    Where can I find the code to amend the Competition Screen like the one in the screenshot above?

    on the line 99 and 201 of "YACS2020 Base/panels/team/team competitions overview competition panel.xml".

  12. 41 minutes ago, yd1882 said:

    Do you know which coding in the 'player additional stats small' panel makes the competition logos appear?

    In FM Touch, the xml-file which controls Season Stats is not "player additional stats small.xml" but "player season stats table panel.xml". (I've not edited this file.)
    And you can't display the logos by editing that file. (I confirmed it.)

    Instead, you could change the code of "player overview panel.xml" to use "player additional stats small.xml".
    In detail, as follows.

    1) The following is the code on the lines 39 to 43 of "player overview panel.xml" in this skin.
            <!--Playing stats-->
            <widget class="player_season_stats_table_panel" id="ssts">
              <translation id="title" translation_id="247412" type="use" value="Stats"/>
              <record id="object_property" get_property="objt" set_property="objt"/>
            </widget>

    2) You could change it to the following.
            <container id="ssts" navigation_container="true" >
                <translation id="title" translation_id="247412" type="use" value="Stats"/>
                <layout class="stick_to_sides_attachment" alignment="all" apply_to_children="true" inset="0" />

                <widget class="player_additional_stats_panel" id="pcsp" file="player/player additional stats small">
                    <record id="object_property">
                        <list id="get_properties">
                            <!-- Hide this panel if player is in inactive league-->
                            <record id="object_property" get_property="objt" set_property="objt"/>
                            <record id="object_property" get_property="Pila" set_property="hidn"/>
                        </list>
                    </record>
                </widget>

                <widget class="player_stats_panel" id="pssp" file="player/player stats small">
                    <record id="object_property">
                        <list id="get_properties">
                            <!-- Show this panel if player is in inactive league-->
                            <record id="object_property" get_property="Pila" set_property="Shwn"/>
                            <record id="object_property" get_property="objt" set_property="objt"/>
                        </list>
                    </record>
                </widget>
            </container>

    3) Then, Season Stats will become like the screenshots. (the two are the players in active & inactive league.)

    stats 1.jpg

    stats 2.jpg

  13. 23 minutes ago, niiicoAFDFCH said:

    Is there a way to get the normal match review screen in this skin? As i need it for a FM league.

    The match review panel becomes like the first screenshot by deleting the following file in this skin.

            panels/match/match in between highlights panel review.xml

    However, because the selector panel is common with "match in between highlights", the background color of those boxes become darker than the default skin.
    (The way to change the color of those boxes is somewhat complicated, so please let me know If you need.)

    And some contents of the selector on the center-bottom will be different from the default state.
    (Overview, Match Stats, Action Zones, Focus of Attacks and Formations will be the same as the default.)

    In terms of the left & right side, only "Formation" will be changed from the default to like the second screenshot.
    If you would like to make those back to the default, you could delete the following two files.
    In this case, Formations in "match in between highlights" will also be changed to the default ones.

            panels/match/match formation panel review.xml
            panels/tactics/tactics icon info panel review.xml

    ibhR 1.jpg

    ibhR 2.jpg

  14. 1 hour ago, abbespl said:

    also if it would be possible to put attributes analyser above the position on the pitch on the left bottom? just between the player personal details and position on the pitch.

    Please try this.
    You could change the values of "minimum_height" & "default_height" of the analyser & the pitch on the line 347 & 357
    and change the spaces above & below of the analyser by changing the values of "inset" on the line 348 to fit your settings.

              <layout class="stick_to_sides_attachment" alignment="all" inset="12,0,4,0" apply_to_children="true"/>
    Four values mean top, left, bottom and right in order.

    1968478880_Angel1.thumb.jpg.693b2cabf417e0954e3ccd44f6c95246.jpg

    PPDP analyser.zip

  15. I wonder if SI coding team read this post, but I have a question(suspicion) about the 201st line of "skins/fmc/panels/team/team match chalkboard panel.xml".
            <container class="inner_box_no_margin" id="cEfP" file="filter_panels/player chalkboard event filter panel" />

    Is it really "player chalkboard event filter panel"?

    team match analysis 2.jpg

  16. 10 hours ago, abbespl said:

    You're the boss here Sir, I just did what I did with my limited set of coding skills, simply copy files to make transparency be gone and backgrounds working :).

    Including client object browser, not even being sure if we need it or not, to have a desired change.

    First of all, I don't mean to hurt your feeling. Please don't get me wrong.
    Thank you in advance.

    Your skin works well on PC.
    But at this rate, there are two problems, I think.

    1) It likely has some troubles when it works on tablet.

    2) You have a box over the background picture in your skin.
       The color of this box is "ui_background" which is the same as the general background color ("bg").
       And, the color of "bg" is dark blue (what is called SAMURAI blue) in my skin. 

    918559242_overbg.thumb.jpg.0059ee737b4a019098af21ec68361118.jpg

       For your information, you can change the color of the overlay box by changing the value on the line 13 of "graphics/boxes/custom/background/paper.xml" to "black" for example.
            <colour id="red_replacement" name="ui_background"/>


    What I had meant to tell you in my last post is the followings.
    If what you'd like to do is only to have a box over the background picture (this is the same meaning as to reduce transparency),
    you can get it by deleting only two lines from the code of "panels/client_object/client object browser.xml" in my skin.
    And what you can adjust the transparency seems to be useful for you, I think.

    The overlay boxes of following screenshots are none, 20, 30, 40, 60 and 80 in order.

    1309440421_over0.thumb.jpg.3432ffc57b67c245909c1b26ffbb158d.jpg639304875_over20.thumb.jpg.9315831f1c7b7a7fc0cd153fb5ca9cdf.jpg

    299872657_over30.thumb.jpg.7dfd087d72065cbda49c2e63c456fdf8.jpg1315920023_over40.thumb.jpg.0a45f70c275fedbf83003076e097a7be.jpg

    1412893843_over60.thumb.jpg.15e8e52628fac4dee4864b507adaf9b6.jpg2140652591_over80.thumb.jpg.b27e8611eb726cad8714f1fa4615b79a.jpg

     

    The differences of "panels/client_object/client object browser.xml" between yours and mine (for PC) are the followings as far as I know.
    1) the width of the sidebar
    2) the horizontal_gap of buttons on the match tab bar
    3) the insets of main content area
    4) the height of the match footer panel

    I too am not sure if these are needed.


    I hope this helps you and someone.

    P.S.
    The panel of screenshots is not included in version 1.0.

  17. Hi,

    First of all, it's OK to change something in this skin and to make/release a new one without my permission.
    And it's OK to change not only "name", but also "author", "description" and "skin_name".

    Hence, you need not delete your post.
    Thank you for your kindness. 


    I've checked the differences between the two.
    The code of "panels/client_object/client object browser.xml" is very different,
    but the major difference is only whether the overlay of the background is or not.
    Is it alright?

    If so, you can also have an overlay by removing the lines 19 (<!--) and 29 (-->) of that file in my skin.
    In this case, you can change the transparency of overlay/background by changing the value 20 on the 20th line of that file.
            <widget class="picture" file="hako/overlay/20" scale_picture="true" keep_aspect_ratio="false">

    You can select the value from 10, 20, 30, 40, 50, 60, 70 or 80.
    The bigger the value is, the darker the background will be.

    Hope this helps.

×
×
  • Create New...