[r158.2] timer behavior async

Bugs will be moved here once resolved.

Post » Tue Jan 21, 2014 7:53 pm

Link to .capx file https://dl.dropboxusercontent.com/u/666516/r158timerbehaviorasync.capx:
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   
Image ImageImage
B
171
S
50
G
179
Posts: 8,392
Reputation: 113,478

Post » Tue Jan 21, 2014 8:01 pm

I mean is the timer started at the beginning, or end of the value entered?
Image ImageImage
B
171
S
50
G
179
Posts: 8,392
Reputation: 113,478

Post » Fri Jan 24, 2014 5:38 pm

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.
Scirra Founder
B
399
S
236
G
89
Posts: 24,535
Reputation: 195,412

Post » Fri Jan 24, 2014 9:40 pm

Ok.
Could swear it worked before, but perhaps that was for multiple instances with the behavior.
Image ImageImage
B
171
S
50
G
179
Posts: 8,392
Reputation: 113,478


Return to Closed bugs

Who is online

Users browsing this forum: No registered users and 4 guests