Schedule
LinkDetails
Co-authored-by: Bartłomiej Dach <dach.bartlomiej@gmail.com>
Remove unused `IScrollingHitObject` interface
IScrollingHitObject
Multiple `ScrollingHitObjectContainer` logic simplification
LegacyBeatmapSkin
SkinProvidingContainer
FindProvider
LegacySkin
HitObjectContainer.OnAdd
OnRemove
Now, `OnAdd` is always invoked after the DHO is added to the container. This change is required by `ScrollingHitObjectContainer` to compute origin adjusted lifetime when origin position is relative to the parent drawable size.
Allow `LegacyDefaultSkin` to be constructed without extra resource store parameter
Fix usage of DI before it's ready in combo colour tests
TestCase
DefaultLegacySkin
Make `BeatmapSet.Files` non-nullable
Hide legacy HUD combo counters on osu!catch ruleset
IStorageResourceProvider
Fix bindable lease failure in editor beatmap creation tests
# Conflicts: # osu.Game/Rulesets/UI/Scrolling/ScrollingHitObjectContainer.cs
scrollLength
It was not clear when the field is updated.
The scheduling is no longer necessary because `OnAdd` is changed to not invoked immediately for non-pooled DHOs.
Only top-level hit objects are checked for layout computation caching. Also, lifetime of nested hit objects are not managed by the HitObjectContainer.
ContentVisible
HiddenByRulesetImplementation
Update hit object lifetime on `HitObject.DefaultsApplied`
Tidy up OsuGameBase
previous
GetWorkingBeatmap
This should not be required since the introduction of `workingCache`, which does the same thing in a more global way.