Hi all,
As the title says, can I quickly generate composites from a prototype?
Thanks!
Hi all,
As the title says, can I quickly generate composites from a prototype?
Thanks!
Turn the question around: ācan I make a composite into a prototype?ā The answer is no. āCan the composited notes have the same or different prototypes?ā Yes.
So, you can generate a composite āApple Pieā whose two notes have prototypes āFruitā and āCrustā, individually. Then you can make a new instance of the āApple Pieā composite and one of that instanceās two notes will have the āFruitā prototype and the other the āCrustā prototype.
So, ācan I quickly generate composites from a prototypeā. No. But you can quickly add a composite from a previously defined composite. (The āApple Pieā composite needs to be located in /Composites
, as you know.)
Composites and prototypes are two separate concepts.
The preceding is absolutely correct. There is a possible solution (just tested) if you are happy that the composite is a child of the note using a prototype. This occurs because when a note is given a prototype the note also inherits, by default**, the prototypeās children and these can include composites.
My test used the built-in ālistā composite as a child of my test prototype. When a note was then set to use that prototype the note gained a list composite, the compositeās items being children of the note. This method canāt be used to make a composite that is a sibling of the note.
** see more on prototypes ābequeathingā their children.
Well, yes and no. Yes, because the note you to which you assign the prototype (with its composited children) does indeed itself gain a child ācompositeā. But this doesnāt work like ānormalā compositing. Letās say you have made the āApple Pieā composite I mentioned above. And you make that āApple Pieā composite into a child of a note āDesertā, and finally make āDesertā into a prototype. You can, as suggested, assign the āDesertā prototype to another note. But in this case, the composited child it gains that way is no longer an āApple Pieā composite. It looks like it is, but doesnāt inherit the āApple Pieā name and a few other attributes.
[ā¦ after re-learning how to bequeath prototyped childrenā¦]
So:
File is here: Protocomposite1.tbx (76.3 KB)
Iām not sure if this does exactly what the OP wants, but I think itās as close as we can get. Iāve reported the non-naming of bequeather composites, I suspect that issue isnāt intentional and will likely get fixed.
Ah, silly me ā somehow I totally missed how named composites can be created (by putting them under /Composites container), but thatās exactly what I needed. I just wanted a quick way to create a group of notes with different shapes and colors while maintaining their relative positions. For some reason, I thought I had to go the prototype routeā¦
Thanks for your help and effort!
Four years later, but thanks !
I definitely had this confusion about differentiating Composites and Prototypes, and I feel others would too, your post helped clear things up!