Sorry, I haven’t had a chance to look at this. The previous version
had some other-Action-conflict problems, and Joe Billings kindly
refactored it to remove those, but in the process some of the
dimension-checking stuff got broken. I thought I caught all the
outliers before I released the last version, but apparently not. I
will probably get a chance to work on this at the weekend, not much
hope for a spare moment until then. If you’d like an easy work-around,
try making the carousel element without any padding, then draw a
second box over the top of that to hold your content. Make sure this
child box is an actual child element of the outer carousel or pane,
and you should be all set. (Click once on the carousel or pane, then
select the HTML box tool, and begin and end your drag-to-draw over the
top of that parent box.)
Walter
On May 20, 2010, at 8:45 AM, tobiaseichner wrote:
Sorry to be so persistent… is there an other solution than
removing the padding of each pane ?
As mentioned before, the previous version worked well there, so
maybe it’s a bug or maybe the new behaviour of the action is
intended that way. Not sure.
No matter, I appreciate your help with this regardless when you are able to look at it.
It was just important for me to get your confirmation that you are aware about the bug (and the confirmation that it is a bug and not an intended behaviour) and that it’s on your to-do list.
Someone cheered too soon… while the Carousel is working well on new pages, it doesn’t work anymore on existing pages.
I have tried to figure out the reason, but failed. There are two Carousels on some pages, where one doesn’t switch overall and the other switches, but without animation.
Even removing and reapplying the Carousel action elements to the page, moving the *.freeway_ folder, clearing the site folder - no luck.
On Safari, there is just one error message:
TypeError: Result of expression ‘Effect.SmoothScroll’ [undefined] is not a constructor. (file glider.js)
Do you have any hint for me where to look ? Maybe I’ve overseen something.
Update: There seems to be an incompatibility between carousel and (older) lightbox actions. Removing the lightbox action makes the carousels to work as intended.
I had the version 0.3.4 of the lightbox action installed. After updating it to the latest one, 0.3.5, all carousels are working. Well, at first glance. I say this with care, since it was just tested with one project I had.
That error sounds like you have a general Freeway bug at work. Actions that attach files can get very confused in certain cases, and end up attaching the wrong file, or no file, to the page. If you look at the top of your page’s HTML (view source in a browser) you should see at least three lines that look like this:
If you see something else, like maybe a script tag that points to a CSS file, or to an image (saw one to a _clear.gif last week) then you have hit this bug.
The only sure way around it is to clear out your local Site Folder, publish EVERYTHING again, and upload again. That usually fixes it, although there have been cases where it doesn’t. Removing all Actions, publishing, and then re-applying all Actions is an extreme, but helpful way out of this also.
As best I understand it, Freeway maintains an ordered internal list of Actions and the files they link to. Under some circumstances, that list can get out of order, and files go where they shouldn’t, or fall off the end of the list altogether.
Oh, and if you can reduce this problem to a repeatable set of steps, please do mail them to support(at)softpress.com, where they like to put them in the killing jar and then look at them under the microscope while wearing Tyvek isolation suits and bulky breathing apparatus.
hi walter, new to this and just read the whole thread and no-one has had the same issue as myself. using carousel 1.2.7 and following your new instructions on a test page I always get a fwShellCommand is not defined error? apologies if this is something simple! thanks
hi walter, new to this and just read the whole thread and no-one has
had the same issue as myself. using carousel 1.2.7 and following
your new instructions on a test page I always get a fwShellCommand
is not defined error? apologies if this is something simple! thanks
sorted! thanks. the only problem now is that even though I’ve installed all the carousel actions and they are ticked the buttons one isnt in the drop down? great work by the way. cheers
Carousel Button will only appear in the list when you have selected a
graphics box. Most Actions work this way, by the way, they only appear
when it’s possible to use them.
Walter
On Jul 13, 2010, at 3:21 PM, richie hume wrote:
sorted! thanks. the only problem now is that even though I’ve
installed all the carousel actions and they are ticked the buttons
one isnt in the drop down? great work by the way. cheers
Is it possible to ‘Loop’ the carousel? ie: when you click the ‘next’ button, if you’re on the final pane, the first pane appears without flying back through all the previous panes?
Not at this time, no. The underlying effect has the beginnings of that
option stubbed in, but the original developer never finished it. I
have looked at adding it from time to time, but it’s quite a big
undertaking. At some point I may be able to do this.
Walter
On Sep 13, 2010, at 11:55 AM, Sly wrote:
Is it possible to ‘Loop’ the carousel? ie: when you click the ‘next’
button, if you’re on the final pane, the first pane appears without
flying back through all the previous panes?
Sly and Carla, simply scroll back up this thread to the posts made by myself and Walter on April 2nd. (I wish I could post a link to jump you to specific posts, but this forum doesn’t seem to allow for such basic conveniences.)
Suffice it to say that although it is a “big undertaking” it is truly “a feature to die for” with regard to Carousel. It is one of those “should have been in there from the get-go” features.
I wouldn’t go that far. The original of this idea (as far as I know)
was the Coda home page: Coda is now Nova which did not have that
feature. The mental model enforced by the “whip back to the left”
rewind is one of a single strip of options, rather than a Möbius strip
or some other mind-bending construct. It tells you quite dramatically
when you have gone all the way to the right.
Don’t get me wrong, I still think it would be cool to be able to loop
back to the beginning, particularly for the sorts of passive elements
like news tickers or other control-less things for which the whipping
back is a distraction rather than a clever mnemonic. But as far as
capturing the complete essence of the original, I think this Action
does a great job, and I don’t feel it lacks for features or
configuration options.
Walter
On Sep 13, 2010, at 5:06 PM, JDW wrote:
It is one of those “should have been in there from the get-go”
features.
