hi all -
A counter-proposal; I want to get 0.52 out this summer. Perhaps we should
prioritize which PRs to include in it and I'll just merge them into master.
Since it would be early int he cycle there would be plenty of time to work
out the kinks before finalizing the release.
I think these
Hi all,
Here's another thought.
What about setting "log" to "6", which would enable sending anything that is
posted on the pd console to the current "pd" symbol, so that you place a [r pd]
in your patch and route the console messages and errors?
Best!
Fede
Just 2 innocent ideas to add to brainstorm,
1.) what about a special subpatch? like pd-try, or just try, it could work
as a normal subpatch, but with a mandatory outlet that would catch errors
for the objects that live inside it
just like we can open a [pd] object or a [clone] object, [pd-try
On 6/15/21 2:42 PM, José de Abreu wrote:
typos.. of course i meant [try soundfiler]...
sidenote: there's already a [try] object in iemguts.
it does something else (fallbacks for an object)
ghmkdtf
IOhannes
OpenPGP_signature
Description: OpenPGP digital signature
typos.. of course i meant [try soundfiler]...
but adding something
the second idea would be interesting because it would be fast to change a
patch, if you highlight the object that is throwing errors from the pd
console (or using find last error), if you want to catch these errors you
can just
Slightly off-topic:
IOhannes, et al should we consider making a develop-testing style branch for
integrating a number of PRs and the current develop branch for extended
testing? I'd also like to have my sound file update branch get more use and it
would then be an easier sell for Pd 0.52
* Christof Ressi [2021-06-14 22:35]:
> that's an excellent idea!
>
> ---
>
> I think it could work like this:
>
> [catch] has one inlet and two outlets. If you send a message to the inlet,
Sounds good, but please don't call it [catch] for the reasons given earlier
(confusion with catch~).
On 6/15/21 9:28 AM, João Pais wrote:
Hi,
in parallel to the error discussion going on: the already existing "find
last error" function can be quite helpful, but it doesn't always work. I
didn't find any documentation for it (maybe I didn't search long
enough), is it marked somewhere in which
Hi,
in parallel to the error discussion going on: the already existing "find
last error" function can be quite helpful, but it doesn't always work. I
didn't find any documentation for it (maybe I didn't search long
enough), is it marked somewhere in which situations it works, and in
which
