I've written a bit about this a little while back: #43
As I wrote in there, In my opinion the two biggest improvements should be:

A buffer exchange END tag so that if I want a part to 'buffer' in multiple steps I don't have to constantly store and retrieve every step but I can just store it in step 4 and retrieve it in step 8 for example.
A feature that automatically ignores parts in the PLI within the buffer retrieve

Furthermore, another cool addition would be to be able to retrieve buffers within submodels from the parent (or even further up in the tree) models. A common example would be Technic models were you add those 'pins with bush' only halfway on a submodel, then put the submodel on the mainmodel and push the pins all the way to lock the models together (if that description makes sense ;) ). But this is a nice to have feature and I can imagine that it's more difficult to implement than the above things.

If you could implement the first feature I mentioned above within the next ~4 weeks I would be so incredible thankful. I have to use A LOT of buffer exchange soon (well, part of the reason that it's a lot of buffer exchange is the lack of that feature :P) and that alone would make my life so much better. Is there a donate button somewhere?

PS: I'll get back to you about the assembly positioning issue later today. Didn't had any time last couple of days.

@jacovandermolen Why it can have more letters is indeed a bit useless with the current implementation of buffer-exchange. But if it would be possible to carry a buffer over multiple steps, then having multiple letters (or names) would become much more useful I think.

Update the Buffer Exchange framework #115

Description

Subject

Environment

Solution

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions