Disable nwworkingdir workaround in gui_canvas_saveas for nw.js 0.46+, fixes the first bug reported in #669.

Additional optimizations to avoid unnecessary runtime string comparisons for the purpose of OS detection.

Fixed inconsistent window sizes across Linux and OSX (this was a bug), and Linux/OSX and Windows (this is an nw.js inconsistency linked to innerHeight and innerWidth misreporting their size for some reason on Win10).

Fixed the window resizing bug when saving a patch with optimal zoom, closing it, and then reopening it (see http://disis.music.vt.edu/pipermail/l2ork-dev/2020-August/002901.html). Please note that this will need to be reverted once we migrate to nw.js 0.46+ (as per provided comment inside the canvas_check_geometry. Also improved the patch scrollbars to be flush against the window edges.

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

Addressed the issue where optimal zoom did not update the scrollable area and reenabled the zoom of the scrollbars when zooming (this scrollbar zoom size may require further reflection to decide the best path forward).

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