6d4f94756e
The general idea here is that we need the masks to handle mouse down events, as they need to handle the drag (mousedown -> drag immediately). I've rewritten the editor selections to use events, as there are some 3 different components that handle/trigger selections in different ways. 1. All selections/deselections now propagate through `HitObjectMask.Select()`/`HitObjectMask.Deselect()`. 2. Components that react to changes in the selection bind to the masks' `Selected`/`Deselected` events, and track them/change their states locally. 3. Masks provide a `SingleSelectionRequested` event which is invoked on the mouse-down event. Various components bind to this event to perform state changes locally in this scenario. 4. `DragBox` now handles all drag input locally. It triggers `Select`/`Deselect` on the masks it needs to. 5. `SelectionBox` handles the display of itself locally. 6. `SelectionBox` handles movement of groups of masks locally. 7. `HitObjectMasks` handles movement of itself locally. |
||
|---|---|---|
| .vscode | ||
| osu-framework@f60cd46471 | ||
| osu-resources@c3848d8b1c | ||
| osu.Desktop | ||
| osu.Desktop.Deploy | ||
| osu.Game | ||
| osu.Game.Rulesets.Catch | ||
| osu.Game.Rulesets.Catch.Tests | ||
| osu.Game.Rulesets.Mania | ||
| osu.Game.Rulesets.Mania.Tests | ||
| osu.Game.Rulesets.Osu | ||
| osu.Game.Rulesets.Osu.Tests | ||
| osu.Game.Rulesets.Taiko | ||
| osu.Game.Rulesets.Taiko.Tests | ||
| osu.Game.Tests | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| .travis.yml | ||
| appveyor.yml | ||
| COMPILING.md | ||
| ISSUE_TEMPLATE.md | ||
| LICENCE | ||
| osu.Game.props | ||
| osu.licenseheader | ||
| osu.sln | ||
| osu.sln.DotSettings | ||
| osu.TestProject.props | ||
| README.md | ||
osu! 
Rhythm is just a click away. The future of osu! and the beginning of an open era!
Status
This is still heavily under development and is not intended for end-user use. This repository is intended for developer collaboration. You're welcome to try and use it but please do not submit bug reports without a patch. Please do not ask for help building or using this software.
Requirements
- A desktop platform that can compile .NET 4.6.1. We recommend using Visual Studio Community Edition (Windows), Visual Studio for Mac (macOS) or MonoDevelop (Linux), all of which are free. Visual Studio Code may also be used but requires further setup steps which are not covered here.
Getting Started
- Clone the repository including submodules (
git clone --recurse-submodules https://github.com/ppy/osu) - Build in your IDE of choice (recommended IDEs automatically restore nuget packages; if you are using an alternative make sure to
nuget restore)
Contributing
We welcome all contributions, but keep in mind that we already have a lot of the UI designed. If you wish to work on something with the intention on having it included in the official distribution, please open an issue for discussion and we will give you what you need from a design perspective to proceed. If you want to make changes to the design, we recommend you open an issue with your intentions before spending too much time, to ensure no effort is wasted.
Please make sure you are familiar with the development and testing procedure we have set up. New component development, and where possible, bug fixing and debugging existing components should always be done under VisualTests.
Contributions can be made via pull requests to this repository. We hope to credit and reward larger contributions via a bounty system. If you're unsure of what you can help with, check out the list of open issues.
Note that while we already have certain standards in place, nothing is set in stone. If you have an issue with the way code is structured; with any libraries we are using; with any processes involved with contributing, please bring it up. I welcome all feedback so we can make contributing to this project as pain-free as possible.
Licence
The osu! client code and framework are licensed under the MIT licence. Please see the licence file for more information. tl;dr you can do whatever you want as long as you include the original copyright and license notice in any copy of the software/source.
Please note that this does not cover the usage of the "osu!" or "ppy" branding in any software, resources, advertising or promotion, as this is protected by trademark law.
Please also note that game resources are covered by a separate licence. Please see the ppy/osu-resources repository for clarifications.