neoscore
neoscore copied to clipboard
A python library for notating music in a graphics-first paradigm
It's currently pretty awkward to work out the document-space position of a mouse event. We should support this out of the box.
In theory we should support any SMuFL-compliant music font, but we've only ever worked with and tested against Bravura. We should try out some other fonts and see what breaks.
Beam lengths look good in the `examples/beams.py` example, but it seems the [beams doc page examples](https://neoscore.org/western/beams.html) run into a case where the beams are too long. ```python staff = Staff(ORIGIN,...
We already support ties via the `Slur` class, but users do need to be careful to make sure that this tie stays horizontal. We can make this easier for users...
Rotation
This is a tracking issue for support gaps relating to object rotation. Most of this is likely out of scope for the current release plan, but they are outlined here...
If the string given to a `Text` starts or ends in whitespace, it is clipped on the opposite side by the whitespace width. This is a funny consequence of the...
`Chordrest` currently uses a very basic algorithm for laying out accidentals - it works through the accidentals from top to bottom, and if a bounding rect collision with the previous...
We don't have any built-in support for tuplets. Users can manually construct these using `MusicText` (for plain number/ratio annotations) and in combination with a `Path` (for brackets), but it's a...
Given a number of staves in a staff group in a flowable, if the staves have different key signatures that are not declared at the same point, the calculated flowable...
`PositionedObject._render_in_flowable` currently assumes that an object only needs to be drawn in flowable lines starting at its `pos`, but this doesn't account for objects with bounding rects left of the...