ha, good catch. the reason is that when you save a cloned abstraction, the clone object is 'updated' by simply cutting and pasting it. as a consequence, the copy buffer is filled with the clone object. I already have a working fix (https://github.com/pure-data/pure-data/pull/310) but I have to rewrite it to make it prettier :-) I'll do this with a couple of other bug fixes/improvements for [clone] when I finally find some time... the code was actually for a different issue (cloned abstractions are closed on saving) but it would also fix your issue (because the [clone] object isn't cut anymore).
Christof Gesendet: Samstag, 20. April 2019 um 07:38 Uhr Von: "Matt Davey" <[email protected]> An: "PD List" <[email protected]> Betreff: [PD] cut and paste bug with [clone] object Have noticed this bug a few times now: 1) Go inside a [clone] patch, and copy one of its objects. 2) Save the clone patch. 3) Paste the clipboard to a new patch somewhere. - The parent clone patch will be pasted, not the object which was originally copied. _______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list _______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
