mirror of
https://github.com/ppy/osu.git
synced 2025-01-18 20:13:21 +08:00
5c8ae6f851
As I look into re-implementing the ability to choose combo colour for an object (also known as "colourhax") from the editor UI, I stumble upon these wretched ternary items again and sigh a deep sigh of annoyance. The structure is overly rigid. `TernaryItem` does nothing that `DrawableTernaryItem` couldn't, except make it more annoying to add specific sub-variants of `DrawableTernaryItem` that could do more things. Yes you could sprinkle more levels of virtuals to `CreateDrawableButton()` or something, but after all, as Saint Exupéry says, "perfection is finally attained not when there is no longer anything to add, but when there is no longer anything to take away." So I'm leaning for taking one step towards perfection. |
||
|---|---|---|
| .. | ||
| Checks | ||
| Tools | ||
| BeatmapVerifier.cs | ||
| BeatmapVerifierContext.cs | ||
| ComposerDistanceSnapProvider.cs | ||
| DrawableEditorRulesetWrapper.cs | ||
| EditorTimestampParser.cs | ||
| EditorToolboxGroup.cs | ||
| ExpandableButton.cs | ||
| ExpandableSpriteText.cs | ||
| ExpandingToolboxContainer.cs | ||
| HitObjectComposer.cs | ||
| HitObjectCompositionToolButton.cs | ||
| HitObjectPlacementBlueprint.cs | ||
| HitObjectSelectionBlueprint.cs | ||
| IBeatmapVerifier.cs | ||
| IBeatSnapProvider.cs | ||
| IDistanceSnapProvider.cs | ||
| IPositionSnapProvider.cs | ||
| PlacementBlueprint.cs | ||
| ScrollingHitObjectComposer.cs | ||
| SelectionBlueprint.cs | ||
| SnapResult.cs | ||
| SnapType.cs | ||