...and it would be lovely to have the text appear in a tooltip when mousing over the inlet/outlet in the parent patch! The drawback mentioned by Phil could be pretty annoying though. Question 1.: What's up with tooltips in pd right now? I couldn't find it out from the list archives. Question 2.: What if the parser would explicitly stop parsing elements when it finds ";#" and would use the remaining part as a comment/tooltip/whatever? Could this change break anything in real life?
András On Tue, Jun 19, 2012 at 10:22 PM, Phil Stone <[email protected]> wrote: > One potentially nasty drawback to this practice (I found) was that if you > change the pseudo-argument in any way, you lose whatever connections were > made to that inlet or outlet in the outer patch. I agree with you that > comments are a pain in the neck, but at least they don't exhibit this often > hard-to-find side effect. > > > Phil > www.pkstonemusic.com > > > > > On 6/19/12 12:41 PM, Jörn Nettingsmeier wrote: > >> quick question: is it legal to (ab)use creation parameters to inlets and >> outlets for documentation, or does that lead to unwanted side effects? >> >> i'd like to do something like this: >> >> [inlet Set level in dB] >> [inlet Set Fader position in mm] >> >> [outlet Current level in dB] >> [outlet Current Fader position in mm] >> [outlet~ Gain coefficient] >> >> of course i could use comments, but i don't like the way they don't >> line-wrap in a controlled way, plus their association to what they are >> annotating is a bit weak for my taste... >> >> best, >> >> >> jörn >> >> > > > ______________________________**_________________ > [email protected] mailing list > UNSUBSCRIBE and account-management -> http://lists.puredata.info/** > listinfo/pd-list <http://lists.puredata.info/listinfo/pd-list> >
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
