scrollHorz does what you want
noahT wrote:
This it perfect for me but it brings up another issue: I am using a
left-right scroller and as far as I can tell, the fx option only
allows for one type of transition animation (in my case, I am using
fx: 'scrollLeft', so even when I hit the prev
This it perfect for me but it brings up another issue: I am using a
left-right scroller and as far as I can tell, the fx option only allows for
one type of transition animation (in my case, I am using fx: 'scrollLeft',
so even when I hit the prev button, it scrolls to the right when it should
scr
This it perfect for me but it brings up another issue: I am using a
left-right scroller and as far as I can tell, the fx option only
allows for one type of transition animation (in my case, I am using
fx: 'scrollLeft', so even when I hit the prev button, it scrolls to
the right when it should scro
Yes, i think that's the way to go, i'm just not talented enough with the js
to write that indexing code. that's why i'm posting here. this thread was
started by someone who had done the same thing, and with some help, got it
to work. i couldn't get his code to work, so i'm hoping someone might h
sorry, didn't realize you were running 12 slideshows. You could change
to classes on all your selectors and index them to shorten code to
one constructor. Not sure that performance wouldn't be a hinderance
though
Ed F. wrote:
Hi Charlie,
I'm sorry i don't think i'm making myself clear
Hi Charlie,
I'm sorry i don't think i'm making myself clear enough. here is the init.js
file that i'm using, you can see the repeated code for each instance of the
slideshow: http://tinyurl.com/mrhkym
as you can see, lots of duplicated code to deal with each unique instance of
the slideshow.
constructor you are showing is only about 10 lines. If the onAfter is
identical events for both you should be able to re use the same
function
after: onAfter1 for both
Ed F. wrote:
Hi Charlie, thanks for the reply, i appreciate it.
That's what I'm doing: repeating the constructor and ch
Hi Charlie, thanks for the reply, i appreciate it.
That's what I'm doing: repeating the constructor and changing the IDs. this
adds 200 extra lines of code to the js file though. Previously in this
thread, someone else figured out a way to not have to add unique IDs to the
html code. so that the
sorry , your next and prev ID's will need to be unique, change them
iin new constructor
Ed F. wrote:
I figured out a way to make the "current slide number" work for multiple
slideshows on the same page, but i have to repeat the function declarations
for each instance of a slideshow, lik
As long as you keep the ID's unique for the separate slideshows *and
pagers* you should be able to call same functions onAfter
duplicate your constructor with the other ID you want to have cylcle
on and change your pager ID accordingly
Ed F. wrote:
I figured out a way to make the "cu
I figured out a way to make the "current slide number" work for multiple
slideshows on the same page, but i have to repeat the function declarations
for each instance of a slideshow, like so:
// init for the cycle js
$(document).ready(function(){
$('#s1').cycle({
fx:'fade',
hi Mike,
thank you for replying. your plugin is awesome.
On thing, in your example, you only have one slideshow on the page, I have
multiple slideshows on the page with the updating count. and I can get the
updated count to work for the firat instance of the slideshow but it breaks
for the res
> Hi, I'm working on the same issue with Cycle. I have multiple slideshows on
> a page, each with current/total slide counter, example: "2 of 5 images"
> (oddly, there are no examples of this particular implementation on Mike
> Alsup's otherwise ridiculously varied and helpful cycle demo pages).
Hi, I'm working on the same issue with Cycle. I have multiple slideshows on
a page, each with current/total slide counter, example: "2 of 5 images"
(oddly, there are no examples of this particular implementation on Mike
Alsup's otherwise ridiculously varied and helpful cycle demo pages). and so
That worked perfectly. Thank for your help, I was completely stumped.
On Sep 24, 11:51 am, dlimpid <[EMAIL PROTECTED]> wrote:
> try this:
>
> $(function() {
> $('*').filter(function() { return this.id.match(/^s\d+$/); })
> .each(function(n) {
> $(this).cycle({
> timeout: 0,
>
If my first message was not an "e-mail to an author" and it is
moderated before revealed public, my second message was a real
mistake. If so, please just delete my second message and this. I'm
sorry again for my many mistakes. I'll learn how to use this group
properly.
On Sep 24, 6:54 am, Phillip
try this:
$(function() {
$('*').filter(function() { return this.id.match(/^s\d+$/); })
.each(function(n) {
$(this).cycle({
timeout: 0,
speed: 500,
fx: 'fade',
prev: '#s' + (n + 1) + '_prev',
next: '#s' + (n + 1) + '_next',
after: functio
Oops, I'm sorry. I think I sent a mail instead of posting the
messages.
I'm not a good hand at this site, so I made a mistake. Please don't
get me wrong.
Sorry.
On Sep 24, 6:54 am, Phillip <[EMAIL PROTECTED]> wrote:
> Thanks for the reply. I gave it shot, but still no dice. The good news
> is opt
Thanks for the reply. I gave it shot, but still no dice. The good news
is opts.slideCount is working. But opts.nextSlide doesn't seem to
update when you click ahead. Any ideas on what to try next?
> $(function(){
> $(slideShow).cycle({
> timeout: 0,
> speed: 500,
> fx: 'fade',
> prev: slideShow + '_prev',
> next: slideShow + '_next',
> before: function() {
>
20 matches
Mail list logo
