One thing worth mentioning is that the [line], [line~] and [vline~]
objects clear the values send to the cold inlets after sending a message
to the hot inlet. This makes sure you can do:

[1, 0 1000(

If this wasn't the case, then the [1( message would take the last ramp
value, instead of setting the state immediately.

This is a bit off an oddity, because usually objects keep values stored
in cold inlets.

Everything IOhannes and I said is actually clearly documented in the
help patch for [line], but missing in the help patches for [line~] and
[vline~]. Maybe they should refer to [line] more explicitly...

Christof

On 18.03.2020 10:30, IOhannes m zmölnig wrote:
> On 3/18/20 10:03 AM, Peter P. wrote:
>> Hi list,
>>
>> what is the function of the second inlet of line~ and the second and
>> third inlet of vline~? The help patches don't mention it and the list
> both [line~] and [vline~] only have *float* inlets.
>
> however, you will mostly send "list" messages to those objects, so how
> does this work?
>
> if you send a message [0 100( to [line~], you are really sending a "100"
> to the second inlet, and then a "0" to the first inlet.
> similarily, if you send [1 100 50( to [vline~], you are really sending
> "50" to the 3rd inlet, then "100" to the 2nd inlet and finally "1" to
> the 1st inlet.
>
> see also doc/2.control.examples/04.messages.pd
>
> gfmdsar
> IOhannes
>
>
> _______________________________________________
> Pd-list@lists.iem.at mailing list
> UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list



_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list