[L2Ork-dev] feature request: subpatch encapsulation
Ivica Ico Bukvic
ico at vt.edu
Fri Jan 30 17:36:32 UTC 2015
I think this is a great suggestion. It is also one that will take some
time and effort. For this reason, I am thinking about opening a bounty
system and soliciting donations for features like these as they are not
directly related to the most pressing issues, but if there is a
finanical incentive that would allow us to block off time and/or hire
part-time help, then we could elevate things like these to the top of
Speaking of which, how would community feel about something like bounty
system if that would move us forward faster in terms of development?
Alternately, how about a kickstarter or an indiegogo project?
On 1/29/2015 7:48 PM, Gilberto Agostinho wrote:
> Hello all,
> I would like to ask you if you'd consider implementing a feature
> similar to Max MSP's encapsulation. Basically, if you select some
> objects in a patch and then use the encapsulation shortcut (if memory
> serves me right, in Max it used to be Ctrl+Shift+E), then they will be
> replaced by a single subpatch. To explain better, here is a video that
> I edited showing the desired feature in Pd-l2Ork:
> This can be a very handy feature: usually when patching people starts
> with something very simple and if (or rather /when/) things start to
> get complicated, they have to use a lot of copy and paste to create
> subpatches manually, memorize where the connections where, create
> inlets and outlets manually, etc. This feature would become very handy
> in these situations.
> Would you consider this to be feasible in Pd-l2Ork?
> Thanks a lot and take care,
> L2Ork-dev mailing list
> L2Ork-dev at disis.music.vt.edu
Ivica Ico Bukvic, D.M.A.
ICAT Senior Fellow
School of Performing Arts – 0141
Blacksburg, VA 24061
ico at vt.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the L2Ork-dev