Bartłomiej Dach 15feb17da8 Change difficulty cache storage type to nullable ... The recent changes related to adding support for working beatmap load cancellation exposed a flaw in the beatmap difficulty cache. With the way the difficulty computation logic was written, any error in the calculation process (including beatmap load timeout, or cancellation) would result in a 0.00 star rating being permanently cached in memory for the given beatmap. To resolve, change the difficulty cache's return type to nullable. In failure scenarios, `null` is returned, rather than `default(StarDifficulty)` as done previously.		2021-11-20 17:00:50 +01:00
..
Contracted
Expanded	Change difficulty cache storage type to nullable	2021-11-20 17:00:50 +01:00
Statistics	Fix HUD unstable rate counter not including judgements before load complete	2021-11-11 13:36:05 +01:00
AspectContainer.cs
PanelState.cs
ReplayDownloadButton.cs	Fix some oversights and test failures	2021-10-27 23:42:27 +09:00
ResultsScreen.cs	Fix score panels sometimes jumping when toggling statistics fast	2021-11-17 23:15:51 -08:00
RetryButton.cs
ScorePanel.cs
ScorePanelList.cs	Fix incorrect keyboard navigation order in score panel list	2021-09-07 21:14:38 +02:00
ScorePanelTrackingContainer.cs
SoloResultsScreen.cs	Rename BeatmapInfo.OnlineBeatmapID to OnlineID to match interface	2021-11-12 17:46:24 +09:00