Carousel action: one button, multiple panes?

Question: Is there any way to have a carousel button (or tab) control two separate panes (one for graphics, one for text) on the same page?

If not, can a target image be triggered from a specific layer in the pane stack?

Any help would be appreciated. Thanks.

quote

On May 1, 2008, at 9:26 AM, BadGenius wrote:

Question: Is there any way to have a carousel button (or tab) control two separate panes (one for graphics, one for text) on the same page?

You could hard-code this, but it’s probably a lot of trouble to do. I actually had to spend quite a lot of effort getting Carousel to stop doing this when you had multiple carousels on a single page.

If not, can a target image be triggered from a specific layer in the pane stack?

Say a little more about this. I’m not sure I understand the question. Each pane of a carousel is like a little page unto itself. You can do anything you like within it that you might otherwise do on the page itself.

Walter

quote

Walter:

Apologies for my lack of terminology as I’m a Freeway Pro novice.

To clarify, let’s say I have 3 images in my pane stack (A,B,C) and when the middle image B is triggered (by button or tab), I want a separate image X on the page to become visible.

quote

Ooh. Cool idea. I just tried to make this go, and I can’t seem to find a way to trigger it. The basic idea is sound, and it should be possible to make it work, but there doesn’t seem to be an event fired when the Carousel slides the pane into view. From the JavaScript perspective, the pane is always “visible”, it’s just hidden by CSS. I was hoping you could simply try if($('yourpane').visible() ... but that never fires.

Walter

On May 1, 2008, at 9:43 AM, BadGenius wrote:

Walter:

Apologies for my lack of terminology as I’m a Freeway Pro novice.

To clarify, let’s say I have 3 images in my pane stack (A,B,C) and when the middle image B is triggered (by button or tab), I want a separate image X on the page to become visible.

quote

You could ofcourse do this simply by adding a rollover action to the button, activating a initially hidden layer … or am I thinking to simplistic?

quote

That wouldn’t cover the case where someone scrolls the pane in question into view using the previous/next buttons. It’s a good idea, though.

Walter

quote

I indeed didn’t think of that option … that is tricky; an event takes place, how to add another event to this one.

quote

It’s easy to add an event listener to an event, but the trouble is that in this case, no event (except for the ambiguous click on one of many controls) actually takes place. The scroll into view does not actually generate an event, since it’s just a change in a left or top offset parameter. I tried observing document#change, but that doesn’t fire either.

Walter

quote