Replace objects in Room Editor

[davidkarbo97]

Is your feature request related to a problem?

It's frustrating to have to replace a bunch of objects without the need.

Describe the solution you'd like

I'd like the quick ability to either combine two objects in the IDE, or mass-replace objects with another object in the room editor - for example, I have a blue tree and a green tree, I've placed them all around two rooms, and now I'm realizing I'd just like them all to be blue in room 1 and green in room 2. Instead of manually replacing all objects, it'd be nice to be able to combine and choose the color via code.

Describe alternatives you've considered

I could just run identical code in each of the existing objects but that seems like a waste of space

Additional context

No response

[stuckie]

We will look into a Replace operation, but Merging is not something we are planning.

[Alphish]

One thing worth taking into account is handling of assigned Object Variables. Two approaches that make most sense to me:

• Object Variables belonging to the common ancestor are kept, other variables from the old object are discarded
• Object Variables with the same name keep their values, any variables not matched by the new object are discarded; it also covers common ancestor variables, since they'll have the same name

Personally, I'm inclined towards the latter. When same variable names are used between non-related objects, I imagine people will want to carry over the variables more often than reset them upon replacement.

[davidkarbo97]

Thanks! In my mind it'd look similar to when you click an object in the room editor and then replace it in the inspector with another object (but maintain the position in the room). The difference would be, you could highlight multiple objects on an instance layer and perform the same operation.

On Wed, Jan 24, 2024 at 2:26 AM Alice Jankowska @.***> wrote:

One thing worth taking into account is handling of assigned Object Variables. Two approaches that make most sense to me:

• Object Variables belonging to the common ancestor are kept, other variables from the old object are discarded
• Object Variables with the same name keep their values, any variables not matched by the new object are discarded; it also covers common ancestor variables, since they'll have the same name

Personally, I'm inclined towards the latter. When same variable names are used between non-related objects, I imagine people will want to carry over the variables more often than reset them upon replacement.

— Reply to this email directly, view it on GitHub https://github.com/YoYoGames/GameMaker-Bugs/issues/4479#issuecomment-1907840644, or unsubscribe https://github.com/notifications/unsubscribe-auth/AX5OWB7SDWPAEEKFAZB4U53YQDOUVAVCNFSM6AAAAABCICFFGCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBXHA2DANRUGQ . You are receiving this because you authored the thread.Message ID: @.***>