Tim, do you have an example posted anywhere? I don’t recall what this Action does.
Walter
On Feb 7, 2013, at 9:19 AM, Tim Plumb wrote:
Hi Kelly,
Not at the moment. Carousel 2 works in a different way to the original version and no longer uses background images for the tabs. Rewriting the Action to work with the latest version of the Carousel Action wouldn’t be hard although I suspect Walter may want to look at adding this functionality directly into the Carousel 2 Actions himself.
If you just want a rollover (rather than an active or mouse down image) then you can use the stock Softpress Rollover Actions.
Regards,
Tim.
On 7 Feb 2013, at 08:05, RavenManiac wrote:
Tim, do you have an updated Carousel Tab Button that works with FWP 6.0 and Carousel 2?
Tim, do you have an example posted anywhere? I don’t recall what this Action does.
Walter
Walter, here is a site I designed using Tim’s action. As you’ll see, the action is on the home page and it’s basically responsible for making the Carousel navigation buttons turn red as each pane changes.
Oh, okay. Carousel 2 also assigns the .active class to the current tab, so all you would need is a CSS style that matches. Come to think of it, nothing at all changed in this part of the Actions, the final construction is identical. The image is wrapped with a link to the pane’s ID, and depending on whether it is currently selected or not, the link gets the active class assigned to it.
If I were going to make this part of the Action, I would add an image picker to the Action interface, where you could choose the “active” image, and use the image that the Action is applied to as the normal image. Swap the normal image for the _clear.gif during the publish cycle, and set the normal image as the background-image, then write out CSS to make the .active state. But that’s going to mean a separate rule for each tab. Very messy and duplicative. I’ll give it some thought, but there’s a few more things in front of this on the Actions front.
Walter
On Feb 7, 2013, at 9:33 AM, RavenManiac wrote:
On 7 Feb 2013, 1:25 pm, waltd wrote:
Tim, do you have an example posted anywhere? I don’t recall what this Action does.
Walter
Walter, here is a site I designed using Tim’s action. As you’ll see, the action is on the home page and it’s basically responsible for making the Carousel navigation buttons turn red as each pane changes.
Hi Walter,
Yep that what the tab action does at the moment. I must be missing something as it falls over and dies when I try it with the new Action in FW6.
I’ll take a closer look at this later if I get a chance as it should function as before.
Thanks,
Tim.
On 7 Feb 2013, at 14:53, Walter Lee Davis wrote:
If I were going to make this part of the Action, I would add an image picker to the Action interface, where you could choose the “active” image, and use the image that the Action is applied to as the normal image. Swap the normal image for the _clear.gif during the publish cycle, and set the normal image as the background-image, then write out CSS to make the .active state. But that’s going to mean a separate rule for each tab. Very messy and duplicative. I’ll give it some thought, but there’s a few more things in front of this on the Actions front.
I think this still works with the updated Carousel1, so perhaps I’ll try that for the time being. Anxious to move one of my sites over to FWP 6 to check it out.
I’ve flagged the Action to look at tomorrow but then I’ve got a to-do list as long as my arm so don’t be surprised if it turns into Monday!
Regards,
Tim.
On 7 Feb 2013, at 21:52, RavenManiac wrote:
I’ll try that for the time being. Anxious to move one of my sites over to FWP 6 to check it out.
Hi Walter,
I’m looking at the Carousel Tab Button Action at the moment and it appears that the original carousel Action placed the active class on the tab image and the new one (Carousel2) places it on the enclosing link. This is causing the CSS targeting in the Carousel Tab Button Action to miss the targets.
If you get a second can you please confirm that the class has moved between versions?
At the moment I’ve a version of the Carousel Tab Button Action that works with Carousel1 and another that works with Carousel2 but I’d like to consolidate these into a unified version if I can.
Thanks,
Tim.
On 7 Feb 2013, at 14:53, Walter Lee Davis wrote:
Come to think of it, nothing at all changed in this part of the Actions, the final construction is identical.
Hi Tim & Walter, after much searching I have finally found out exactly what my issue is too. I too sorely need that “Carousel 2 Tab Button” action you guys are working on. If say I were to make a donation via PayPal to both you guys, enough for some beer & pizza, do you think that would help bump this to the top of your to-do lists? Cause if so just say the word & the donations will be on the way ASAP! Oh, say please! Please! Thanks you guys!a
The updated Action works with Walter’s original Carousel Action as well as with the new Carousel2.
The Action allows you to set separate graphics for each of the six tab states on the carousel; normal, hover, mouse down, selected, selected hover and selected mouse down.
Here’s an example of the Wood Slider Carousel 1 demo showing the tab states; http://www.freewayactions.com/test/wood-slider/
Regards,
Tim.
Hi Tim, sorry for the delay getting back to you. Yes, the class moved, in order to be consistent between the text and image versions of the Action. (One JavaScript to rule them all.)
Walter
On Feb 8, 2013, at 4:32 PM, Tim Plumb wrote:
Hi Walter,
I’m looking at the Carousel Tab Button Action at the moment and it appears that the original carousel Action placed the active class on the tab image and the new one (Carousel2) places it on the enclosing link. This is causing the CSS targeting in the Carousel Tab Button Action to miss the targets.
If you get a second can you please confirm that the class has moved between versions?
At the moment I’ve a version of the Carousel Tab Button Action that works with Carousel1 and another that works with Carousel2 but I’d like to consolidate these into a unified version if I can.
Thanks,
Tim.
On 7 Feb 2013, at 14:53, Walter Lee Davis wrote:
Come to think of it, nothing at all changed in this part of the Actions, the final construction is identical.