It's now possible to say that a given process type will have a default height when added in the timeline.
We should investigate relevant default heights for most processes.

See
https://github.com/ossia/score/blob/master/src/plugins/score-plugin-fx/Fx/LFO.hpp#L102

and

https://github.com/ossia/score/blob/master/src/plugins/score-addon-gfx/Gfx/Video/Presenter.hpp#L32

Describe the feature
A simple text box in the button editor to be used to write and store notes for future button editing. This would be especially helpful for buttons with more extensive action sequences. Possibly even an option for notes on each individual action?

Is this platform dependent (windows, mac, ..)?
nope

**If documentation is required to implement, do you know where to

It seems like the only reasonable way to get a command-line/terminal program in a usable state onto people's Macs is with Homebrew. I don't really know how Homebrew works internally, though the tool build script I made for orca will check to see if ncurses and portmidi have been installed via Homebrew.

It would be nice if someone could help create a Homebrew thingy (formula? cask? uhh) so tha

I'm working with SLIPSerial and after I have decoded the packet I can't quickly parse it into an osc message, though all the methods are there to do it easily.

Would make this handy library even handier!

In order to make OSCMessage an immutable object (all fields final), while still having a comfortable way to create messages, we could simply use the builder pattern, like in OSCPortInBuilder.java

This is related to the concurrency issue #4.