User Tag List

Results 1 to 2 of 2

Thread: path movement node unscoped?

  1. #1
    Clicker Fusion 2.5 DeveloperAndroid Export ModuleHTML5 Export ModuleiOS Export Module
    Fusion 2.5 (Steam)
    schrodinger's Avatar
    Join Date
    Nov 2014
    Posts
    3,156
    Mentioned
    28 Post(s)
    Tagged
    1 Thread(s)

    path movement node unscoped?

    I've multiple drop-down menus all belonging to the same qualifier group.
    Each one has its path movement that starts when clicking over the object and reverses when clicking again.

    But... I want some actions to be performed when the menu opens ---> reaches the end of its path.
    And the problem comes here: I've noticed that path movement seems not to be "object-selective",
    when the menu reaches the end of the path, ALL of the objects belonging to the same qualifiers are selected for the performing actions.

    It can be easily tested with 2 or more actives all belonging to the same qualifier,
    applying a simple linear path movement, with different length for each object,
    and the event:

    (qualifier) reaches the end of its path ----> (qualifier): destroy

    destroys ALL of the actives when just the first of them reaches the end of the path
    (while in my interpretation would have destroyed one by one only the single actives reaching the end of their own path)

    This is not the same behaviour I get when for example i set the "mouse click over (qualifier)" ----> (qualifier): destroy
    in this situation the object is correctly scoped, hence only the clicked object gets destroyed.

    Is the action "object reaches the end of its path" a non-selective event,
    and is this meant to be like this for reasons I currently don't get, or am I misunderstanding something?
    Or is this to be considered an uncorrect behaviour?
    (don't want to say that bad word ...bug )


    **************
    EDIT: just to clarify,
    I know it can be tackled adding a foreach event,
    but I can't still get the differences between actions that are actually "self-scoping"
    and actions that are not, I would have presumed this was one of them...
    how can I tell one from the other? Only by experience-test or is there a behind-logic I don't get?

  2. #2
    Clicker Fusion 2.5HTML5 Export ModuleiOS Export Module

    Join Date
    May 2014
    Posts
    1
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    This is still the case. I wanted to be able to create a new object (with path movement) every second and have it destroy itself when it reached the end of its path, but as described above ALL instances of that object are destroyed when the first one reaches the end of its path. The same holds true if trying to destroy the object when it reaches a named node. Is there a reference that describes which conditions select objects and which do not?

Similar Threads

  1. path movement : goto node name
    By arthurh in forum Multimedia Fusion 2 - Technical Support
    Replies: 5
    Last Post: 24th October 2013, 10:05 AM
  2. Problem: Advanced Path Movement - Selecting the closest node?
    By GreenOnion in forum Multimedia Fusion 2 - Technical Support
    Replies: 4
    Last Post: 7th March 2013, 02:16 PM
  3. Advanced path movement Node Problem
    By StingRay in forum Multimedia Fusion 2 - Technical Support
    Replies: 2
    Last Post: 28th July 2010, 05:41 PM
  4. Path node name?
    By Bruto in forum Multimedia Fusion 2 - Technical Support
    Replies: 4
    Last Post: 1st September 2006, 01:30 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •