> In regards to the 9/9/9 release; it seems like the fxFn is set to null
> in the resetState function and not being set back. I am invoking the
> script with:
>
> $(document).ready( function() {jQuery
> ('#cf73b7c6341940210VgnVCM100000288ea8c0____').cycle({
> pagerEvent: 'mouseover',
> timeout: 4500,
> pager: '#pager',
> cleartype: 1,
> slideExpr: ".carouselElement",
> fxFn:'slideFade' });
>
> });


For custom transitions it's best to add your function to the
'transitions' object.  The 'fxFn' option is not well-supported for
external use - I should update the docs to reflect that.  So I would
recommend an approach like this:

// declare your transition fn
$.fn.cycle.transitions.slideFade = function($container, $slides, opts)
{
    // your transition logic goes here!
}

// and set the 'fx' option to the name of your transition
jQuery('#slideshow').cycle({
        fx: 'slideFade',
        pagerEvent: 'mouseover',
        timeout: 4500,
        pager: '#pager',
        cleartype: 1,
        slideExpr: ".carouselElement"
});


For example, this is how the 'scrollUp' effect is defined:

$.fn.cycle.transitions.scrollUp = function($cont, $slides, opts) {
        $cont.css('overflow','hidden');
        opts.before.push($.fn.cycle.commonReset);
        var h = $cont.height();
        opts.cssBefore ={ top: h, left: 0 };
        opts.cssFirst = { top: 0 };
        opts.animIn       = { top: 0 };
        opts.animOut  = { top: -h };
};



Reply via email to