Skip to content

Conversation

@minetoblend
Copy link
Contributor

@minetoblend minetoblend commented Nov 14, 2025

Supersedes #35695
Prerequisite for #35704

Attempt number two... I tried to keep the changeset as small as possible this time, managed to cut it down to a third the original size.

The PR attempts to split the BeatmapSelectPanel class into two subclasses based on panel type, to make it easier to implement custom animations/designs for each panel type in follow-up work (see #35704).

The PR also moves the responsibility for fetching the APIBeatmaps into the matchmaking subscreen, which loads them in bulk and then hands everything to the BeatmapSelectGrid all at once. Came up on discord, and it made passing the data to the panels a lot easier.

@minetoblend minetoblend force-pushed the feature/quickplay-beatmap-bulk-fetch branch from a1668d1 to 7d7ff4b Compare November 14, 2025 10:20
Copy link
Contributor

@smoogipoo smoogipoo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems probably okay. I'm starting to feel a little concerned about loading every beatmap before displaying anything, but perhaps we'll cross that point when we get to it by querying every beatmap in the background on room join or something.

I've done some simple merge conflict resolution expecting the followup PR to remove it or move it elsewhere appropriate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants