2017-11-04 11:25 GMT-02:00 Alexandre Torres Porres <por...@gmail.com>:
> So I had a [togedge~] and [trigger~] object but was designing a third one > named [past~], which ended up encompassing functionalities found in both of > these other two objects, and I also hated the names of the former two > objects > the thing about names, [trigger~] was actually a threshold detector, but I couldn't use [threshold~] cause Pd uses it. I could also go for an abbreviation, such [thresh~], but cyclone has one object named like that. Since I don't want name conflicts with cyclone (cause I maintain it too). Not only that, but as far as name precautions goes, I'm not taking any name that belongs to any external from good old Pd Extended, that makes it hard. So, [togedge~] was also a name that related to [togedge] from Max, but it was a bad name and a bad relationship (cause max also has [edge~]). So yeah, I couldn't use [edge~] either... Anyway the only solution I found after struggling a lot was to have an object with a name that I also hate called past~, that sends an impulse when you go past over a threshold and another when it falls below it. cheers
_______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
