6 Commits

• Refactor ShearedButton to allow easier relative sizing (#36802)

  This commit rearranges the contents of `ShearedButtons` to be more
  independent of each other in regards to sizing. Thanks to that, the
  custom logic related to enabling autosizing is no longer necessary.
  Witdh and height are no longer set via the constructor, and can be
  freely configured using the initializer syntax.
  
  Additionally, this allows the button to use relative sizing without
  having to resort to any hackery with `Size` (this will come in handy for
  me when implementing the new footer on multiplayer screens).
  
  Given that most of the `ShearedButton`s currently in use set their width
  explicitly, I did not set `AutoSizeAxes = Axes.X` like it would be by
  default previously. Instead it is set on the only two such buttons (show
  converts/selected mods on ssv2). I suppose it might be a good idea to
  have it set that by default if no `Width` is specified, as right now
  it'll just not show anything.
  
  Also I've set the margin on the text field by default in all cases
  instead of only when autosizing like how it was previously, since
  otherwise it would be a pain to set that on each button instance when
  needed. I've checked all affected components and could not find any text
  overflowing issues that this could cause.
  
  ---------
  
  Co-authored-by: Dean Herbert <pe@ppy.sh>

  Krzysztof Gutkowski · 2026-03-06 02:09:05 +09:00
  b76a7e1bb6
• Fix weird alignment code in wizard overlay footer content
  Salman Alshamrani · 2025-04-29 05:34:10 +03:00
  d1c4c65e6d
• Add padding around footer content to avoid sheared overflow
  Dean Herbert · 2025-04-22 17:19:16 +09:00
  066b036466
• Add completion flag to WizardOverlay
  Bartłomiej Dach · 2025-02-05 14:01:37 +01:00
  b6731ff773
• Implement visual appearance of beatmap submission wizard
  Bartłomiej Dach · 2025-02-04 09:06:33 +01:00
  4dd4e52e6d
• Abstract out WizardOverlay for multi-step wizard type screens

  To be used in the editor, for the beatmap submission wizard.
  
  I've recently been on record for hating "abstract" as a rationale to do
  anything, but seeing this commit ~3 months after I originally made it,
  it still feels okay to do for me in this particular case. I think the
  abstraction is loose enough, makes sense from a code reuse and UX
  consistency standpoint, and doesn't seem to leak any particular
  implementation details. That said, it is both a huge diffstat and also
  potentially controversial, which is why I'm PRing first separately.

  Bartłomiej Dach · 2025-01-30 09:39:08 +01:00
  31c4461fbb