This gives what is to me smoother and more predictable snapping motion with
respect to the current mouse position.

For example-- imagine the grid cell size is 10 and the selected object under
the mouse already has its top left corner aligned with vertical grid line #2.

If I begin dragging that object to the left, within a single pixel of motion
it will snap to vertical grid line #1 which is 9 pixels away from the
object's current position.

With this commit, the user must drag the object cellsize / 2 pixels before it
snaps to a new position.

To me this seems smoother as it rounds to the nearest grid line rather than
to the grid line with the smallest coordinate value.

We also keep a partially transparent version of a grid for editmode. This
allows us to keep editmode visually distinct from runmode, even if snap-to-grid
isn't turned on.

If needed it's pretty easy to make the following changes:

* set the "big" cell size to something that isn't 100 (but I'm not sure how
  much control over the grid we actually want to give users-- e.g., setting
  the big cell to something for which the small cell isn't a factor
* allow snap-to-grid to be set independently for each canvas. (But again,
  what would be the use case for this?

Sam Thursfield authored 4 years ago and Albert Gräf committed 4 years ago

This causes tar_em_up.sh to download an older version of nw.js suitable
for OSX 10.8.

It was accidentally removed by me in 4bffb36f.

Disable zexy/lpt on Windows for now, it doesn't work there at present and causes a segfault in the regression tests.

This adds support for the SMMF MIDI message format,
cf. https://bitbucket.org/agraef/pd-smmf.

It also adds canvas/path search for soundfont files, so that these can
be found more easily without having to use absolute pathnames, as well
as a few cosmetic changes to help and error messages.

In default "legacy" mode, the object is 100% backwards-compatible
(except for the soundfont file search), so that existing patches will
continue to work without any changes.

In SMMF mode, which is invoked with the new -smmf option (used either as
a creation argument, or with the "init" message), the SMMF message
format can be used to denote MIDI messages. Legacy messages still
continue to work in SMMF mode as well, except the "note" and "bend"
messages which are used in both formats with the same argument count but
different argument order. However, the corresponding shortcuts "n" and
"b" of the legacy format still work even in SMMF mode.

Rationale: SMMF offers the following advantages over the legacy message
interface that fluid~ currently uses:

- It covers all MIDI voice messages, as well as system exclusive
  messages. (Note that sysex support is particularly interesting in the
  context of fluidsynth because it allows to pass tuning data using
  sysex messages following the MIDI Tuning Standard (MTS), which
  fluidsynth readily supports.)

- It enforces a close 1-1 correspondence between the Pd MIDI objects and
  the message format (it uses the same basenames as message selectors,
  and has the arguments in the right order to easily interface with the
  Pd MIDI objects).

- It is is readily supported by some helper abstractions (midi-input.pd
  and midi-output.pd, available at https://bitbucket.org/agraef/pd-smmf).

- Last but not least, it is compatible with pd-faust and pd-faustgen2
  which makes it very easy to integrate Faust- and soundfont-based
  synthesis in Pd.