[r158.2] timer behavior async

Link to .capx file dl.dropboxusercontent.com/u/666516/r158timerbehaviorasync.capx:[/b]

http://

Steps to reproduce:

1. Run capx

2. press blue sprite

3. Note sprite moves at end of cycle

4. enable the wait

5. run again

Observed result:

Timer behavior can not run asynchronous calls with a different amount of time

Expected result:

Should not need the wait

Possible bug on when the timer is started?

Browsers affected:

Chrome: yes/no

Firefox: yes/no

Internet Explorer: yes/no

Operating system & service pack:

7 64

Construct 2 version:

158.2

I mean is the timer started at the beginning, or end of the value entered?

Closing as not a bug. One timer name corresponds to one timer, so if you start a new timer with the same name, it replaces the old one.

Ok.

Could swear it worked before, but perhaps that was for multiple instances with the behavior.