logo hyperPad Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Login

    Feature Request: Accessible State of Duration Behaviours

    Scheduled Pinned Locked Moved
    Comments & Feedback
    1
    1
    59
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      Deeeds
      last edited by Deeeds

      WHAT?
      The ability to query a Behaviour about its current state.

      WHY?
      Because duration based behaviours have state, and this is important to animation sequencing and all other event based activity.

      States of Duration Behaviours are:

      • Active (running)
      • Passive (behaviour is set to ON but not currently running)
      • OFF (Behaviour is Set to OFF)

      HOW?
      Make it possible to query the current state of an Action "behaviour". Inside a conditional block/behaviour, permit the subject to be a behaviour, and the query to be about its state(s).

      eg.

                                            //
      if MoveBy() is Passive, run MoveBy()
      //
      

      inherently means that if MoveBy() is either Active or OFF, then do nothing.


      BENEFIT

      for users...
      Perhaps the biggest is providing simple, easy calling of actions without jamming them or accidentally restarting them, and without the need to make flags and handling mechanisms to prevent jams, restarts and other undesirable behaviour.

      for @Hamed :
      Puts off the immediate need to create a complex animation and blocking system for sequencing of actions, as users can use the state knowledge to make complex animations themselves, relatively easily, giving you the time to consider and make a full blown animation and action editor for hyperPad.


      Captain Obvious Tip: Minor version permits querying all other behaviours (those without duration) about their state (on or off) by asking. e.g.....

                                            //
       if myBehaviour ≠ OFF, do SomeStuff()
       //
      
      1 Reply Last reply Reply Quote 0
      • First post
        Last post