Dragging behaviors onto one another

Welcome to our brand new Clickteam Community Hub! We hope you will enjoy using the new features, which we will be further expanding in the coming months.

A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.

Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!

Clickteam.
  • Hello!

    Is there a way to disable the feature of dragging another behavior onto another thus replacing it? This is definitely on the top list of worst features of anything ever, and I own East West Word Builder which was designed by someone who was using all substances at once. If this is not a thing, could we just remove it in the next version, or at least get a prompt if we want to actually do this? I just wrote 200 events in a behavior and since I just did it, didn't have a backup of the file, then I accidentally dragged another behavior onto this, and tried to find a weird looking bug for an hour, until I realized I had simply overwritten my entire code with this magnificent feature.

    Sorry about sounding sarcastic, but I try to find the funny in this. This feature suuuuuucks.

  • Undo doesn't usually affect anything you do in the properties window. You can't undo rearranging or renaming altVals, for example, so it likely wouldn't affect this. But I'm curious how MistaSub got behaviours to overwrite each other. I've had a go myself just for the sake of my own curiosity, but can't figure it out.

    Please login to see this link.
    My Fusion Tools: Please login to see this link. | Please login to see this link. | Please login to see this link.

  • Wow, you guys are right! I just assumed this was a thing for the longest time. But what the hell is overwriting my behaviors? The name is the same as before, but all of a sudden one behavior has been overwritten by another behavior from the same object. This happens while I am working on two different behaviors within an object so often, that I have started a habit of trying to not move the mouse while clicking the behavior edit tab. Another thing I do is use mouse 3 and 4 all the time when making my objects. I mean, to switch between behaviors in the project.

  • Wow, you guys are right! I just assumed this was a thing for the longest time. But what the hell is overwriting my behaviors? The name is the same as before, but all of a sudden one behavior has been overwritten by another behavior from the same object. This happens while I am working on two different behaviors within an object so often, that I have started a habit of trying to not move the mouse while clicking the behavior edit tab. Another thing I do is use mouse 3 and 4 all the time when making my objects. I mean, to switch between behaviors in the project.

    Hmm.. I don't know if it can help, but imagine this scenario:

    - you add an active object on the frame (say Active-1)
    - you write a behaviour for that active object
    - you clone the active object Active-1. Now you have, for instance, Active-1 and Active-2 on the frame. At this stage, both active objects have ( and I mean have and not share ) the same behaviour, being each of them a single independent active object - in fact they have different names.
    - you now edit the behaviour of Active-1 and add some other events.
    - if you now edit the behaviour of Active-2, you will see that it does not contain the changes you made on the behaviour of Active-1. This is so because you have made a clone of Active-1 and not a copy.

    If you instead make a copy of Active-1, the two active objects share the same behaviour, thus when you edit the behaviour of one active object, the changes reflect also the behaviour of the other (copyed) object. Is this that you perhaps mean with "overwriting the behaviour" ?

    I hope it helps in some way and adds more light to the "overwritten" topic, however I apologize if I wrote something obvious that you already knew.

    One thing more. I didn't understand what do you mean with
    "Another thing I do is use mouse 3 and 4 all the time when making my objects. I mean, to switch between behaviors in the project."
    What do you mean with mouse 3 and 4 ? Please explain.

    Best regards,
    Sergio

  • He means the 'forward/back' thumb buttons on the mouse (the OS usually considers them buttons #4 and #5, with #3 being the middle button). I believe they're mapped to "View>Back" and "View>Forward" by default.

    I could be wrong, of course, but my guess is that the problem might lie somewhere here. MistaSub, my advice is to try and pay extra attention when you use those buttons. Because maybe there's a Fusion bug that causes back/forward to trigger the wrong behaviour editor in some situation. Or maybe there's some situation where you're accidentally moving to a different editor than the one you think you're moving to.

    Please login to see this link.
    My Fusion Tools: Please login to see this link. | Please login to see this link. | Please login to see this link.

  • He means the 'forward/back' thumb buttons on the mouse (the OS usually considers them buttons #4 and #5, with #3 being the middle button). I believe they're mapped to "View>Back" and "View>Forward" by default.

    I could be wrong, of course, but my guess is that the problem might lie somewhere here. MistaSub, my advice is to try and pay extra attention when you use those buttons. Because maybe there's a Fusion bug that causes back/forward to trigger the wrong behaviour editor in some situation. Or maybe there's some situation where you're accidentally moving to a different editor than the one you think you're moving to.


    Yes, you are correct about what I meant. So, this has happened twice since I posted this. And it just happened the second time, and sort of on purpose. I deleted a behavior, thought of this thread, and switched back into it from another behavior with the mouse thing I talked about (switched back to it after I had deleted it). And lo and behold, one of the behaviors in the object overwritten by the deleted one. Unless, I screwed this up, there might be a bug there. Unfortunately I am not sure if the behavior that was overwritten was the one I switched to (the one I was backing into the deleted object from), but I feel like it was another one, because I tried to test it. I don't know, I hadn't really touched this object in 2 years, and it was one of the first ones I created, and all the behaviors look pretty similar to me now on the surface. Another detail, in case it matters is I deleted all events from the behavior, then deleted the behavior, this is something I end up doing when I am refactoring.

    Clarification: I mean I caused this to happen clearly, hadn't happened in a long time. At first I felt like it didn't work, because the behavior I switched from remained intact, but when I booted the game, a separate behavior in that object had indeed been overwritten. I don't know, to me that feels like either I am the biggest idiot on the planet, or there is a bug there. Both of which are completely possible.

  • I just had this bug, first time in a long while. I noticed it has nothing to do with overwriting the behavior. Rather some bug is causing one behavior to open another one. So clicking behavior 3 might open behavior 1. Also, this affects runtime, and does act as if the behavior is doubled. I know this, because at the top line where the path is displayed, I got the name of behavior 1 when opening behavior 3, after thinking I had overwritten behavior 3.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!