Attribute data from previous versions of libmapper

[dandrewstewart]

Does the current version of libmapper require all of the same data – the same attribute data – generated by previous versions? For example, are all of these necessary and/or used: @id 4 @mode expression @expression y=x*(1)+(23) @srcMin 1 @srcmax 85 @destmin 24 @Destmax 108 @boundMin none @boundMax none @mute 0 @srcType i @destType i @srcLength 1 @destLength 1 @sendAsInstance 0

[malloch]

To be clear for others reading this – this is a question regarding attributes of mapping connections ("maps") if they are created by sending messages to the oscmulticast object rather than using a GUI such as webmapper – most users are expected to use a GUI to design/modify/load mapping connections. The issue identified is the lack of good documentation, so I will leave the issue open until this has been addressed.

Answer:
– the attributes @mode and @expression are unchanged, however there are now only 2 viable values for mode: "linear" and "expression"
– the attribute @mute has been renamed to @muted
– the @id, @type and @length attributes are automatically generated by libmapper and should not be sent
– the attribute @sendAsInstance has changed to @use_instances. You can omit this attribute unless you are using multi-instance signals
– the @min and @max attributes have changed format to e.g. @src@min, @src@max, @dst@min, @dst@max
– the bound attributes have changed format to @dst@bound_min, @dst@bound_max

Another change not addressed here concerns the format of the messages used to act on maps, which now explicitly separates and identifies the source(s) and destination of the map using an arrow "->":

old format: "/connect" "srcDevName/sigName" "srcDevName/sigName" ...
new format: "/map" "srcDevName/sigName" "->" "srcDevName/sigName" ...