I found this in else/mono.pd, what's up with the semicolon? Is "tables" just a comment?
-
semicolon in subpatch name?
-
@jameslo My guess it was just a simple way to get the full name to fit in the space at the left of window, easier to hit a semicolon to get a newline than it is to resize with the mouse or move objects.
-
The subpatch name is only used as title for the subpatch window. You can type whatever you want and even tweak the pd file to show $0 value.
In this context the string following the semicolon is just ignored.Work in progress : FCPD a FreeCAD PureData connexion
-
Seems like an undocumented feature. The kind that they teach you in school to never exploit.
Edit: only half serious about the finger-wagging
-
@jameslo It is documented, in the standard pd way, in other objects like [expr], or [text]. The semicolon is pds newline character and it inserts a newline after any unescaped semicolon it sees. I believe the only time a semicolon has a different behavior is in [msg( objects but even there it causes a newline and we can see how the send is sort of tacked onto the the primary function of being a newline.
-
@oid ...then I wonder if you would regard the tempo message to be documented for [makenote]? https://forum.pdpatchrepo.info/topic/13062/makenote-duration-can-use-tempo
-
@jameslo I was not suggesting that pd is consistent everywhere or even tries to be, was just hopping on board with the half serious finger waving because of all the time I have wasted over the years due to undocumented features and bugs so old that they should be considered features and be in the docs, but the explanation I tacked on probably confused that aspect.
This probably does fall into the category of things they teach you to never exploit, its really a quirk of the interface that could change and break your patches, which would really hurt me since I have one abstraction which relies on this quirk and I put a lot of time into it.
-
@oid Aw crap, I missed the fact that your tongue was half planted in your cheek. I'll do better next time. In the meantime, for your sake, I hope they never assign semantics to the text following the semicolon (in a subpatch identifier)!