Re: [PD-dev] treating $1 as an argument in A_GIMME

2021-09-18 Thread Alexandre Torres Porres
that's also a good point! it's just that cyclone follows this max logic and we actually did change some of that from the older versions. Some objects in MAX have obligatory arguments and don't create if you don't give it any arguments. In Max that's fine cause you can still call the help file, in

Re: [PD-dev] treating $1 as an argument in A_GIMME

2021-09-18 Thread Christof Ressi
The thing is that when you're designing the abstraction, before it exists, when you're bringing it to life, in its creation process, you might be working on it under the top level, I see! and it's annoying to have the object not created. IMO, there is no reason why an object should refuse

Re: [PD-dev] treating $1 as an argument in A_GIMME

2021-09-17 Thread Alexandre Torres Porres
oh, by the wayt, in the end [play~ float] was not illegal in MAX, so I just made it create the object in Pd as well :) Em sex., 17 de set. de 2021 às 23:37, Alexandre Torres Porres < por...@gmail.com> escreveu: > > > Em sex., 17 de set. de 2021 às 17:18, Christof Ressi < >

Re: [PD-dev] treating $1 as an argument in A_GIMME

2021-09-17 Thread Alexandre Torres Porres
Em sex., 17 de set. de 2021 às 17:18, Christof Ressi escreveu: > It doesn't make sense to use $1 in the context of a top-level canvas > I know, that's not the case. > I guess you have an abstraction that should also work as a standalone > patch. > not really. The thing is that when you're

Re: [PD-dev] treating $1 as an argument in A_GIMME

2021-09-17 Thread Christof Ressi
Yes, that's the problem. I should have said it all works fine if this is an abstraction loaded with actual arguments. But I still wonder if there's anything I can do. There is: just don't do it :-) It doesn't make sense to use $1 in the context of a top-level canvas (until we get

Re: [PD-dev] treating $1 as an argument in A_GIMME

2021-09-17 Thread Alexandre Torres Porres
Em sex., 17 de set. de 2021 às 13:00, Christof Ressi escreveu: > I guess what happens is that you instantiate [cyclone/play~] on a top > level canvas (which doesn't have creation arguments), so the value of > "$1" is always "0". A_DEFSYM converts non-symbols to an empty symbol. > Yes, that's

Re: [PD-dev] treating $1 as an argument in A_GIMME

2021-09-17 Thread Christof Ressi
Hi, when using A_GIMME I can test if the type is A_FLOAT or A_SYMBOL, but if I give it a "$1", for instance, it's treated as a float. Well, it depends on the actual value of "$1". In the case of [cyclone/play~ $1], the "$1" is replaced by its actual value before being passed to the object.

[PD-dev] treating $1 as an argument in A_GIMME

2021-09-17 Thread Alexandre Torres Porres
Hi, when using A_GIMME I can test if the type is A_FLOAT or A_SYMBOL, but if I give it a "$1", for instance, it's treated as a float. Now, if I have 'A_DEFSYM' instead of 'A_GIMME', then '$1' is considered as a symbol. The problem is that I have to check if the first argument of cyclone/play~ is