I've been thinking about this, and I realise that there are a few
things that might need to be modified in the Kwicker/KwickerChain
classes for your case. Actually, I have now modified the demo classes
to include these changes...
- Allow a custom duration to the normal mouse-over kwick as well as
the chained kwick
- Added 'activateOnCreation' option to Kwicker (and so also to
KwickerChain) (defaults to true). This means you can pass in
{activateOnCreation:false} as options to the constructor to make sure
that when the object is first created, mouseenter/leave does nothing
(As you might want to wait until the chained animation is complete
before allowing mouseenter effects).
- Added 'activateOnChainReveal' option to the KwickerChain class
(defaults to true). This means you can automatically add the
mouseenter/leave events once the chained-reveal of all elements is
complete (as this defaults to true, you can probably ignore this
option).
Michal.
On Jan 20, 9:50 am, Michal <[email protected]> wrote:
> > Wow. THose are all really great demos!! they gave me about a thousand
> > ideas to play with on my next site!
>
> Thanks!
>
> > Can you have the chain action on the second page be called via body onload?
>
> There should (hopefully) be no problem with that, you should just be
> able to call chainReveal() on the KwickerChain instance from an onload
> listener (instead of a click listener as it is in the demo)
>
> Michal.
