[L2Ork-dev] atomic multi-step undo and pd vanilla

Alexandre Torres Porres porres at gmail.com
Fri Jun 19 16:23:52 EDT 2020


Em sex., 19 de jun. de 2020 às 17:05, Ivica Bukvic <ico at vt.edu> escreveu:

> IIRC Iemguis in 1.x used to long time ago not clip the values
>

yup, until 0.45, this changed n 0.46, but they missed doing that for nbx :(

This is another example of compatibility flags for Pd Vanilla, you can get
old behaviour with compatibility set to 0.45!


> BTW, now that the development pace is picking up significantly, we could
> use additional helping hands, so if you would like to help with merging
> these, your contributions will be more than welcome.
>

As I'm no real programmer, I'd need some help on how to do that. I'm only
being able to help some for Pd Vanilla cause I can use Github Desktop...
and even so I usually screw up and. It's kind of embarrassing, I know :)
moreover, I'm quite busy managing two quite big external libraries and also
helping out with Vanilla as I can.


> As for the values passing unchanged by the object limits, that is not
> something I believe is a good idea.
>

I hear you, not because I have an opinion about this, but because I usually
think many things aren't a good idea :) but please note that this already
happens for number atom boxes, so I guess the idea might have been to make
this more consistent. Anyway, now if you want to clip you have to use a
clip object.

And still about being a good idea or not, I guess it's more about being
compatible or not to vanilla patches and being able to run such patches as
intended and worry free.

I guess the decision is up to you and I don't mean to demand/impose
anything, I just have an opinion it'd be important to provide 100%
compatibility to patches written in Pd Vanilla.

cheers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://disis.music.vt.edu/pipermail/l2ork-dev/attachments/20200619/9a3e0331/attachment.html>


More information about the L2Ork-dev mailing list