Aha, 'spigot' is the object I've been searching for. The purpose of the "set set $1" was to prep the change object with the new value before reinitializing the receive, so that the value doesn't jump when unmuted, so the "set $1" is still necessary. The rest of the patch looks up a note name according to y, which I only want it to do when manually dragging notes. Thanks! Date: Sun, 28 Aug 2005 12:13:29 +0200 From: Frank Barknecht fbar@footils.org Subject: Re: [PD] A mute device To: pd-list@iem.at Message-ID: 20050828101329.GA11691@fliwatut.scifi Content-Type: text/plain; charset="us-ascii"
Hallo, Chuckk Hubbard hat gesagt: // Chuckk Hubbard wrote:
Hi. I came up with this as a way to mute a stream of numbers. Basically, I
...
Is it illegal to send a "receive whatever" message to a non-GUI receive?
It is not illegal, but personally I consider renaming receives in GUI objects a last resort, as this makes reading and understanding patches much, much harder and can lead to subtle logic errors. For example I had a rather hard time figuring out what your patch is supposed to do by looking at it, until I opened all GUI objects to find the one which has the "raty" or "nothing" receive.
In your patch it is not necessary to make things so complicated. Using a [spigot] makes everything much clearer, at least accoding to my taste.
Also your "set set $1" construct could be replaced by a simple [f] where you can use the cold right inlet to store a number without outputting until a bang arrives at the hot left inlet.
I illustrated this in the attached patch based on your previous mute.pd
Frank Barknecht _ ______footils.org__
Hallo, Chuckk Hubbard hat gesagt: // Chuckk Hubbard wrote:
set $1" was to prep the change object with the new value before reinitializing the receive, so that the value doesn't jump when unmuted, so the "set $1" is still necessary.
Ah, I understand. However you could still replace the [set set $1(---[( with the float object like:
[r radskip] | [r ratsy] | | [f ] | [set $1( | [change]
This way you don't need to change the message object's content at all and your patch will always look the same, regardless of when it was saved.
Frank Barknecht _ ______footils.org__
_ __latest track: "plak" @ http://footils.org/cms/show/44
All those sends are unnecessary then. Here's my new version. Thanks again. -Chuckk
On 8/28/05, Chuckk Hubbard badmuthahubbard@gmail.com wrote:
Aha, 'spigot' is the object I've been searching for. The purpose of the "set set $1" was to prep the change object with the new value before reinitializing the receive, so that the value doesn't jump when unmuted, so the "set $1" is still necessary. The rest of the patch looks up a note name according to y, which I only want it to do when manually dragging notes. Thanks! Date: Sun, 28 Aug 2005 12:13:29 +0200 From: Frank Barknecht fbar@footils.org Subject: Re: [PD] A mute device To: pd-list@iem.at Message-ID: < 20050828101329.GA11691@fliwatut.scifi> Content-Type: text/plain; charset="us-ascii"
Hallo, Chuckk Hubbard hat gesagt: // Chuckk Hubbard wrote:
Hi. I came up with this as a way to mute a stream of numbers. Basically,
I ...
Is it illegal to send a "receive whatever" message to a non-GUI receive?
It is not illegal, but personally I consider renaming receives in GUI objects a last resort, as this makes reading and understanding patches much, much harder and can lead to subtle logic errors. For example I had a rather hard time figuring out what your patch is supposed to do by looking at it, until I opened all GUI objects to find the one which has the "raty" or "nothing" receive.
In your patch it is not necessary to make things so complicated. Using a [spigot] makes everything much clearer, at least accoding to my taste.
Also your "set set $1" construct could be replaced by a simple [f] where you can use the cold right inlet to store a number without outputting until a bang arrives at the hot left inlet.
I illustrated this in the attached patch based on your previous mute.pd
Ciao
Frank Barknecht _ ______footils.org__