Post by crashfu on Feb 6, 2015 6:19:17 GMT
Suggesting a new parameter for just about any part that does something: delayed activation.
IE if I set a cannon with a delay of 1.0, it will fire one second AFTER I've pushed the button it is assigned to. That way I could set up rows of cannons and, from a single button press, have them fire in a drawn out barrage instead of blasting a simultaneous wall of cannonballs.
Additionally, for actions where the button can / would be held down, there would be a "duration" parameter, to be used with or without delay. Duration will make a function continue for a specified amount of time from a single button tap. These two parameters could work as follows:
Delay = 0, Duration = 0: Function performs as it currently does, activating immediately and for as long as button is held.
Delay = 0, Duration > 0: If button is tapped, function will activate immediately and continue for the duration stated. Holding button down will override that duration, as if Duration had been left to 0.0
Delay > 0, Duration = 0: Button press will be ignored for period of delay, then activate as long as held. If button is tapped, it will wait the delay and then activate for minimal amount of time.
Delay > 0, Duration > 0: On button tap, delay will be waited and then function will proceed for duration. If holding button down, will function as above.
P.S. I should note that this suggestion is different in function but accomplishes a similar end result to Arlekin's macro suggestion, found here: besiege.freeforums.net/thread/341/macros-complicated-procedures If the moderator wishes, I could copy-paste this suggestion in his thread and delete this, to avoid any clutter or confusion.
IE if I set a cannon with a delay of 1.0, it will fire one second AFTER I've pushed the button it is assigned to. That way I could set up rows of cannons and, from a single button press, have them fire in a drawn out barrage instead of blasting a simultaneous wall of cannonballs.
Additionally, for actions where the button can / would be held down, there would be a "duration" parameter, to be used with or without delay. Duration will make a function continue for a specified amount of time from a single button tap. These two parameters could work as follows:
Delay = 0, Duration = 0: Function performs as it currently does, activating immediately and for as long as button is held.
Delay = 0, Duration > 0: If button is tapped, function will activate immediately and continue for the duration stated. Holding button down will override that duration, as if Duration had been left to 0.0
Delay > 0, Duration = 0: Button press will be ignored for period of delay, then activate as long as held. If button is tapped, it will wait the delay and then activate for minimal amount of time.
Delay > 0, Duration > 0: On button tap, delay will be waited and then function will proceed for duration. If holding button down, will function as above.
P.S. I should note that this suggestion is different in function but accomplishes a similar end result to Arlekin's macro suggestion, found here: besiege.freeforums.net/thread/341/macros-complicated-procedures If the moderator wishes, I could copy-paste this suggestion in his thread and delete this, to avoid any clutter or confusion.
