(There are, however, many cases where you would like the use the patch's $0 value inside a message box ... in which case, the $0 value of the parent is passed into the message box as $1 or $2...etc... Please see the example patch for a demonstration of this)
In Pd-l2ork/Purr Data you can just use
[$0(and it will expand to the value of "$0" for that canvas. This gets rid of the little clumps of
[f $0]every time you want it in a message box.
Do you have any plans to switch this site over to https any time soon? Browsers are already warning about sending password over an unencrypted connection.
EFF's LetsEncrypt program provides free certs. If you're on a modern Gnu/Linux distro they even have a tool to automate the process of generating and renewing the cert.
Just remembered-- here's a pattern Frank Barknecht posted to the user list some time ago:
Here we route based on the value of "x". The
[route]object chops off the 'x' value, which leaves us with "z" for the output. Then it's just a matter of adding the desired value to z.
This works well for two (or maybe three) variables-- that is, as long as it's easy to remember the position of "x" and "y" in the list output from "pack". For more complex conditions you can throw an
[expr]in between the "x" and the "route".
That turns out to be one of the most difficult questions to answer in Pd.
Technically you can use the
[value]object along with the
[expr]object to do this. But typically Pd users will just feed a copy of the "z" value further down the patch and store it in a [
float]to be output and added to the appropriate number (in this case either 10 or -10).
When there are many variables to keep track of users will sometimes use dollarsign arguments to handle the data. But this has its own readability problems because it typically (at least) doubles the amount of information you have to track in your head-- i.e., mapping simple variable names to variable positions.
It would be nice to be able to send objects through the wires which contain key/value pairs, but that would bring its own problems.
After using Purr Data for a couple of days now, I really appreciate it!
E.g. I don't want to miss scaling the surface anymore.
But I still have some questions:
- Is it possible to use pyext in a reliable manner?
I'm not familiar with pyext. Is it currently maintained and stable in Vanilla?
- What about [pd~]? I really need that. Will it work in future?
[pd~] should work fine in Purr Data.