*Added global connectme flag that allows for irregular/unusual objects to be properly positioned when being autopatched. This also deals with objects that do not have their top-left corner aligned with the (0,0) coords.

This adds an option to make bendin use the vanilla range of 0..16383 for
compatibility. As was observed a long time ago, this is at odds with the
bendout range of -8192..8191, and was thus fixed in pd-l2ork at some
point. But Miller Puckette has decided that this bug won't *ever* be fixed in
vanilla, and this is even documented in vanilla's midi-help.pd patch.

This discrepancy breaks a lot of patches involving MIDI, so a compatibility
option is needed. It's been possible to use -legacy to get vanilla's bendin,
but it's better not to conflate legacy iemgui positioning issues with the
bendin implementation. The former won't usually break interoperability, but
the latter does.

So, as suggested by Ico Bukvic, we add a flag as an optional second argument
to bendin instead. If present, this option explicitly denotes the target
range: zero means the default (pd-l2ork, signed) output range, nonzero the
vanilla-compatible unsigned range. In addition, there's a new -legacy-bendin
command line option which makes unsigned output the default for bendin objects
which don't specify the range explicitly. You'll want to put this into your
startup flags in the preferences if you need out-of-the-box vanilla
compatibility.

Jean-Michaël Celerier authored 4 years ago and Albert Gräf committed 4 years ago

Else this does not seem to build with MSVC 2019

comment the line that defines an extra inlet for the 'inlet~' object

show error message in the case its a inlet(~) object but argument 'fwd' is not specified. Third approach

fix for case fwd message is not properly built, pd could crash

add zcheckgetfn method. given a selector and a list of param types, checks if the object has that method and if the params coincide

switch to mess3 method for calling fwd callback and add proper argument verification,  pack conditions to call inlet_fwd inside it, selector 'fwd' can be sent again through inlet objects

create wrappers of symbol and blob for inlet_fwd

create wrappers of pointer for inlet_fwd

We're not yet saving the hex colors as that will break in older patches.
But we do print out warning messages in this interim period and will
save the hex colors at a later date. Once that change is made, all the
interim versions will be able to read the new format

Vanilla commit 94d59de44ea23aa084596d1ba2050d3883511ec3

vanilla commit 853967de05253eaba8bf153450d573e8b6067576

Vanilla commit ab4750bd39964efd5c9a32fdaf9fb300d0d2f5d7

If a user added a device on the commandline, it's likely that they want
this device to be the default.

This allows Purr Data to work nicely inside a Flatpak sandbox, as we
can use `-alsaadd pulse` to enable audio output to PulseAudio by
default, with direct hardware access still an option.

This could lead to an assert failure inside ALSA if the output device
wasn't open and we tried to configure it anyway.

As the comment above the alsa_checkiosync() function suggests, there's
no sync to be done if we only have an input or an output.

The (input) and (output) markers were missing in some cases, and
incorrect in others.

make frontend paramenter passing more clear, add two arguments sel_start and sel_end that define the arbitrary selection

* b_sym field to t_textbuf
* 2nd inlet and "send" method for text define
* text insert class
* improve a stray evalfile error
* show the [text] name (if it exists) in the title for the window
* updates help doc accordingly