I've been repeatedly wishing for two features lately:
1) Provide send/receive functionality that has private scoping like pv. I'm picturing either the introduction of a "private" argument to send/receive, or an "immediate" argument to pv that allows pv to output immediately instead of waiting for a bang.
2) Allow pvar to reference objects outside of the current patch. I specifically want to use the parent:: syntax so pvar can be encapsulated.
In some ways this functionality is available via a pattr bound to parent::guiObjectName, but this disrupts the nicely structured pattr hierarchy I am trying to set up. I don't want to encapsulate my pattrs because I drop pattrforwards into my top level patcher to arbitrarily connect midi controllers to various parts of my patch, and I want to use intuitive naming conventions (delay::feedback instead of delay::guiControls::feedback). I could introduce additional pattrs just for controlling the gui objects, but then I have to deal with managing which pattrs are active and inactive, which isn't trivial in large patcher hierarchies where I'm dropping in bpatchers on the fly.
Those alternatives aside, I've found pvar is a great tool for separating gui from process logic. Gui logic is often a good candidate for encapsulation, so it's a shame I can't encapsulate an integral part of that logic (the pvar object).
If this feature is added it would be fantastic if encapsulating pvar automatically prepended parent:: to the pvar argument when applicable (when the pvar is encapsulated without the referenced gui object). I know I'm lazy, but the existence of autopattr seems to indicate that C74 occasionally tailors to laziness ;)
I know a lot of this been asked for before, so thanks for listening.