Duplicate Objects behave differently than expected, Referencing Duplicate Objects

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.

    From my understanding Duplicate objects and all the instances are the same object in which actions and properties of one will affect all instances of the same duplicated object. (because there is only one object i can interact with in the interface)

    Test1
    Setup: Have an active object (Object1) and duplicate it a few times. Set it to be not visible at start.
    Event: click mouse button
    Action: Object1 Reappear
    Result: All Object1 instances reappear (working as expected)

    Test2
    Setup: Have an active object (Object1) and duplicate it a few times. Set it to be not visible at start.
    Event: click mouse button on object
    Action: Object1 Reappear
    Result: Only the clicked instance of Object1 reappear (instead of all of them)

    Is there a way to make all the objects reappear on object click as with Test1? ie. referencing all duplicates of the Object1 somehow. Don't know if this is a bug or not.

    not a bug, it's the way fusion works,

    in short:

    a generic condition not referenced to any specific object
    >>> actions affect all instances

    a condition that reference one or more specific objects (like clicking on it)
    >>> actions will affect only that/those instances

    to "escape" this situation,
    clicking on instance 1 and affect ALL instances,
    you have a number of solutions,
    simpler one imo could be:

    user clicks on "object"
    >>> start loop "reappear" 1 times

    on loop "reappear"
    >>> "object" reappear

    this because firing a fastloop "breaks" references,
    the fastloop will perform "unscoped",
    with no reference to the generating condition,
    and so affecting all instances of "object"

    a selection of my Fusion examples can be found Please login to see this link.

Participate now!

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

Register Yourself Login