Construct 3 r389

You're viewing a single comment in a conversation. View all the comments
  • 8 Comments

  • Order by
  • The hierarchy changes are interesting. Though I wonder what happens with replicas that have an additional object in the hierarchy, time to find out :)

      • [-] [+]
      • 2
      • DiegoM's avatar
      • DiegoM
      • Construct Team Construct 3 Developer
      • 2 points
      • (0 children)

      Making changes that make a connection, remove a connection or outright delete an instance from a template's hierarchy will make all replica's match the template. I think we will add a new property to templates to decide whether or not to use this behaviour.

      I think in most cases this is the desired behaviour, after all the replicas are supposed to match the template... but I can see how in some cases someone might want to make sure a replica does not update automatically with the template or a template does not propagate hierarchy changes automatically.

      We figured it was better to wait for feedback on this one.

    • If it's a replica why would it be different than the original? :S

      • I just have an additional sprite attached to some replicas. Kinda like how the width/height etc of replicas can be overwitten and different from the template. Worst case I'll just make extra templates tho.

        • Okey, interesting, hope it doesn't bug for you then.

          • Seems fine for the most part. I did get it to crash with a few specific steps tho so I'll report that. I do think in general that this is a good change, although if we do autoupdating like that, it should also update when I move around the sprites (other than the parent) imo. So the additional options Diego mentioned would be great + also update when I move around the hierarchies.

              • [-] [+]
              • 1
              • DiegoM's avatar
              • DiegoM
              • Construct Team Construct 3 Developer
              • 1 points
              • (1 child)

              When you make changes to instances in a hierarchy where a template instance is the root, those changes should be applied on the corresponding instance on the replicas.

              That is, if the template and the replicas match up perfectly, if they don't the changes are not applied because there is no way to guarantee the instance in the template has a corresponding one in the replica.

              • Ah yeah I just noticed that. It works like that once a "replace whole" is performed. But I did find a slight inconsistency there that I'm also gonna report.