it works with pd~

Fix bug in which stdout didn't catch on that it should send to parent pd~
in binary; this was caused by different startup order when pd~ was started
with or without GUI (it failed when non-GUI, binary mode).

This patch makes it possible to have multiple running instances of Purr Data,
and to leverage that interface from Pd-l2ork to get [pd~] working on all
platforms

Some difficulties required revisions to [pd~] in Pd Vanilla's code
* use quoted path args for Windows when starting the [pd~] subprocess
* replace sys_havegui() from Pd Vanilla's recent "threadening" with sys_nogui

The "-unique" flag requires the OSX app bundle to be able to start by calling
the binary in Pd-l2ork.app/Contents/Resources/app.nw/bin/pd-l2ork. This should
also make it possible to run Purr Data on OSX both by using an app bundle
(where the GUI starts the Pd process) and by installing and running from the
command line (where the Pd process starts the GUI)

The "--user-data-dir" flag sets the directory for various nw.js state used
by a running instance. To prevent races nw.js requires that each running
instance have its own directory that is not shared with any other instances.

Setting the value for this flag has two important potential side-effects:

1. If you have a running instance and try to start an additional instance
   that has the same data directory, nw.js will just send an "open" event
   the first running instance and exit the 2nd instance gracefully. This is
   the default nw.js behavior and the default Pd-l2ork behavior as well.
2. If you have a running instance and try to start an additional instance
   with a different data directory than the first, you'll get a fully
   functional 2nd instance of nw.js running. This is the behavior we desire
   when the user runs pd-l2ork with the "-unique" flag.

In each case we set the data dir explicitly in order to get consistent
positional command line arguments in the GUI.

In normal mode Purr Data will use the default data dir as specified in the
nw.js docs for the particular platorm. Since the same default dir is used
each time Purr Data is run, there will be only one data dir that gets created.

When run with the "-unique" flag, Purr Data will append "-$portno" to the
default data directory, where $portno is the port Pd chose to communicate
with the GUI. That ensures that each separate instance of Purr Data can
get a unique data dir.

A side effect is that users may end up generating multiple data dirs that
don't get deleted on exit. But Pd starts searching for available ports in the
same range each time, and unless the user tries to run hundreds of instances
at once this directory spam shouldn't be too big of a problem.

Albert Gräf authored 8 years ago and Jonathan Wilkes committed 8 years ago

Replace the Pd-extended output~ abstraction with Alexandre Porres' improved version, with a small revision by Jonathan Wilkes to generate the array data at load time

another kludge-- bring back the code in makefile.mingw to compile everything in extra, and remove the expr~ external files

port f92dc617867c18216bf4a0e32ece6122b70abc5b from Pd-l2ork: updated bonk~, added bob~, updated makefile to properly build bob~

*forgot to update sched_tick due to a backport

*used better output~ abstraction

*fixed pd~ regression where instantiation within another instance of pd~ failed to start due to expectation of the new -unique flag without which all patches are opened within the existing instance.

*fixed segfault (affects all flavors) where creating an expr object with more than MAX_VARS variables (currently set to 9) crashed pd when freeing the object. Example: create [expr 1;2;3;4;5;6;7;8;9;10] as opposed to [expr 1;2;3;4;5;6;7;8;9]. Former crashes when being freed (destroyed), while latter doesn't.

*updated latest additions by Jonathan--still need following fixes:
1) enter-leave demos don't work at all (any demo involving enter-leave)
2) crasher in easing is still valid
3) spin-spin-spin crashes pd-l2ork when trying to close the patch while the image is spinning and being animated
4) curve-bbox is still having accuracy issues (tkpath issue)
5) polar clock still exhibits issues of warping curve (tkpath issue)
6) On the 15.events.pd change call is never issued--is this another side-effect of me not applying everything?
7) Is there a 14. patch for ds-tutorials? I didn't find one.
8) in ds-tutorials is gmon.out necessary or is this a stale file?