________________________________
>From: Alexandre Torres Porres <[email protected]>
>To: Mario Mey <[email protected]>
>Cc: pd-list <[email protected]>
>Sent: Monday, September 23, 2013 12:13 PM
>Subject: Re: [PD] [change] bug?
>that's the way it works alright.
Yes. It's helpful to know that in Pure Data, an object that takes an optional
float argument
typically sets the value to zero if the user doesn't provide an argument.
It's not a requirement: an external author can set the default value to
anything they want.
It's just that doing that requires extra work (i.e., manually checking the
arguments), whereas
defaulting to zero happens automatically.
Anyway, I think the OP might want [change] to default to NULL-- that is, let
the next incoming
value pass no matter what because there isn't a previous value yet. That could
be handy.
You can make your own version of that by first sending a copy of the incoming
value through a
spigot:
[spigot 1]
|
[* -1]
|
[set $1(
|
[change]
Then set the right inlet of [spigot] to zero and send the incoming value to
your [change]
object, and it will be guaranteed to pass.
-Jonathan
>If your first value sent to it is zero, just initialize it with some other
>value as the argument
>cheers
>>2013/9/23 Mario Mey <[email protected]>
>>If i create [change] and send it a [0(, it outputs nothing. It seems like it
>>has already the 0 value initiated.
>>
>>I think [change] should not work like this...
>>
>>_______________________________________________
>>[email protected] mailing list
>>UNSUBSCRIBE and account-management ->
>>http://lists.puredata.info/listinfo/pd-list
>>
_______________________________________________
[email protected] mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
_______________________________________________
[email protected] mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
