preparing for ktmidi 0.6 and breaking API changes #49
atsushieno
started this conversation in
General
Replies: 2 comments
-
v0.6 changes are pushed at https://github.com/atsushieno/ktmidi/tree/v0.6-branch |
Beta Was this translation helpful? Give feedback.
0 replies
-
v0.6-branch is merged into main today, but I noticed that there will be a few more breaking API changes. Most of them could be still remain (with @ Deprecated), but there were still some immediate breakages. They are hopefully not too much (I assume there were not a lot of use in apps) - the changes this time are similar to the breaking changes mentioned earlier.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We just have released ktmidi 0.5 in June, but I'm thinking to bring in some breaking API changes around
MidiMusic
and thus bump the version to 0.6. Most notably...MidiMessage
and the one without the delta time was namedMidiEvent
. They becameMidi1Event
(with timestamp) andMidi1Message
(without it), respectively i.e. their names are now flipped.Midi1Music
class, withMidi1Track
class.Midi1Message
above actually becomes an interface. There will beMidi1SimpleMessage
data class andMidi1CompoundMessage
(non-data class) for SysEx and meta event messages.The old API still remains, with
@Deprecated
annotation, but there are some exceptional immediately-broken API that was inevitable:Midi1TrackSplitter
already contained1
in the name and now deals with the newMidi1Music
and co. starting v0.6 immediately. Hopefully no one used it.Midi1Player.addOnMessageListener()
and.removeOnMessageListener()
-Midi1Player
similarly contains1
in the name already and the members had to immediately switch to the new types.These are the breaking changes as far as I could verify from Metalava API diff reports. (Those reported as
RemovedDeprecatedMethod
are not counted as breaking changes here.)Beta Was this translation helpful? Give feedback.
All reactions