[Proto-Scripty] Re: Prototype Form.serializeElements

2009-12-24 Thread Al C
How 'bout something like var paramsA = Form.serializeElements( $(frm).getInputs('checkbox', typeA),true); var paramsB = Form.serializeElements( $(frm).getInputs('checkbox', typeB),true); var paramsC = Form.serializeElements( $(frm).getInputs('checkbox', typeC),true); var params = paramsA

Re: [Proto-Scripty] Re: Pulse effect sometimes stopping on darkened version

2009-12-24 Thread Walter Lee Davis
You might find it easier to set up queues if you don't use inline code. Create an observer in the head of your page, and then you can keep all your code in one place and integrate the effects so they are aware of each other's existence and state. document.observe('dom:loaded', function(){

[Proto-Scripty] Re: Pulse effect sometimes stopping on darkened version

2009-12-24 Thread evilC
Thanks walter, though I am not sure I understand that code. if the identify command assigns and ID, it returns it, but the code throws it away then does a switch on the id on the next line. It also appears that maybe I missed something about how queue works if you are passing it the id of the

Re: [Proto-Scripty] Re: Pulse effect sometimes stopping on darkened version

2009-12-24 Thread Walter Lee Davis
Identify assigns an ID to the element if none exists, and that ID will persist until the page is done processing. Basically, it's a throw- away line to ensure that if the element that fired the event doesn't have an ID, the rest of your code doesn't go sproing. You could just as easily