Side navigation
#4127 closed bug (wontfix)
Opened February 11, 2009 07:07PM UTC
Closed February 14, 2009 05:30PM UTC
Last modified March 14, 2012 12:14PM UTC
1st function in queue won't run unless type is "fx"
Reported by: | MoonScript | Owned by: | flesler |
---|---|---|---|
Priority: | minor | Milestone: | 1.3.2 |
Component: | data | Version: | 1.3.1 |
Keywords: | queue | Cc: | |
Blocked by: | Blocking: |
Description
Bug in v1.3:
The 1st function in the queue will not get called if the type is not "fx". So any queues under a different namespace will not kick off the function!
Code in v1.2.6:
if ( queue(this, type).length == 1 )
fn.call(this);
Code in v1.3:
if( type == "fx" && queue.length == 1 )
queue[0].call(this);
Attachments (0)
Change History (4)
Changed February 12, 2009 04:07AM UTC by comment:1
component: | data → fx |
---|---|
owner: | → flesler |
Changed February 12, 2009 04:07AM UTC by comment:2
component: | fx → data |
---|
Changed February 14, 2009 05:30PM UTC by comment:3
resolution: | → wontfix |
---|---|
status: | new → closed |
version: | 1.3 → 1.3.1 |
That's correct - and an intended change. Since the execution of the function was really only something that was ever needed for 'fx' we made it exclusive to that.
Changed February 17, 2009 03:46PM UTC by comment:4
john, can you please elaborate on that? I am using the "queue" feature to handle an AJAX queue. So a user could click a bunch of things as fast as they can, and I will queue those actions up and process them in order. I understand that you originally intended the queue for animations, but when I first found this queue function, I saw it as a generic job-handler, where I could queue up a bunch of functions, and run them in order. Why not leave it generic, for the use that I am describing (such as for AJAX)?