`ProxySpace` support clarification

[keiviv]

Your beautiful Quark is godsend — I was literally torturing Google for days trying to find this cool functionality. It is conceptually perfect — high level, laconic, quite flexible, and amazingly powerful, judging by your two useful videos.

Can you be kind enough to clarify in the readme if it supports ProxySpace for the people. If it doesn't, maybe adding a note on planned or not planned support.

❤️

[grirgz]

Hello, sorry i was locked out of github due to 2FA, I see your message only now. Thank you for your kind words.

Param class doesn't support ProxySpace because it doesn't support NodeProxy. The problem with NodeProxy is there is no way that i know to find the name given the object, contrary to Pdef and Ndef. However I just added support for NodeProxy in the last commit so it does work now, i use the bus index as a name

here is my test code:

p = ProxySpace.new;
p.push;

~osc1 = { arg freq=100; SinOsc.ar(freq) * 0.1 ! 2  };
~osc1.play;

Param(~osc1, \freq).edit;
~osc1.asParamGroup.edit;

~osc1 = { arg freq=100; SinOsc.ar(freq * ( SinOsc.ar(freq * \fmr.kr(1)) * \fmamp.kr(0.5) + 1 )) * 0.1 ! 2  };

PlayerWrapper(~osc1).edit;

Of course this is not well tested, feel free to report any problem or ask questions, i would love some feedback on my work ^^

Also Param quark is much more than Param class, let me know if it break elsewhere with ProxySpace