Okay, I’ve been butting my head against this issue for too long now. I continually want to make rollovers that trigger images to appear (like icons triggering larger photos to appear) but I would cannot figure out how to make it so that the 1st image is “initially: visible” and yet still behaves the same as the others in the group.
It seems that setting something to be initially visible means that scrolling over its corresponding icon will make it invisible. I want it to remain visible when it’s icon is scrolled over, and disappear when other icons are scrolled over. I know it’s confusing, and maybe I’m not explaining it correctly, but are there any out there who are experiencing this?
I got around the issue once using “Source Code Snooper” action on the following page to make the “Mouseover icons to see images” text disappear no matter what icon you scroll over. http://www.stoutphotos.com/print.html
But I would like that page to load displaying one of those images, and NOT disappear when the user scrolls over it’s corresponding icon, and DO disappear when the user scrolls over another icon.
Just an added thought, I got around this issue with the “Source Code Snooper” action by assigning multiple target #'s to that text. Can you make that option available in the “Target Show/Hide Layer” action? If I could assign multiple target #'s, then you could place a duplicate html box of whatever you want to be “initially: visible” to turn off no matter which icon the user mouses over.
The usual procedure for this is to have all the images stacked one on top of the other so that subsequent triggers obscure the original by being displayed over the top of it.
If by “stacking” you mean placing them on top of each other, yes I do. When I’m trying to do this effect, I always try to do it as unlayered (turning CSS off) images, then selecting each item to appear during differing states. In the FW5 Action “Target Image” (renamed from FW4’s “Slave Image”, as far as I can tell it’s the same) it looks like little check marks you select for each: Normal, Image 1, Image 2, etc. That’s fine. I can work with that.
The problem is when it comes to CSS layered items. The layout I’m working on right now has a lot of layered stuff going on and I can’t always use unlayered images. Most of the time I want to do this with CSS layered text html boxes. (like to correspond as a description to a particular image) I need there to be that “Normal” state like in the “Target Image” action.
Also, thanks for the heads up on the typo. FW need grammar check! : )
Sometime around 13/5/08 (at 08:25 -0400) Aaron said:
The problem is when it comes to CSS layered items. The layout I’m
working on right now has a lot of layered stuff going on and I can’t
always use unlayered images.
You can group the items for a rollover together. Make the group, the
parent item, a layer and you’ll be able to set up your rollover AND
have the overall structure as a div/CSS-positioned/layered item.
Yes, this works for images, thanks. But I’m still having the problem with layered HTML text boxes. When I “group” several stacked and layered CSS HTML text boxes together, the only Action available (for doing this slave triggering) is “Target Show/Hide Layer”, which only gives me one option for “Initially: Visible/Hidden”.
Aha. I think that the Rollover Action does not support HTML elements.
That would be a nice addition!
Walter
On May 13, 2008, at 9:57 AM, Aaron wrote:
You can group the items for a rollover together.
Yes, this works for images, thanks. But I’m still having the
problem with layered HTML text boxes. When I “group” several
stacked and layered CSS HTML text boxes together, the only Action
available (for doing this slave triggering) is “Target Show/Hide
Layer”, which only gives me one option for “Initially: Visible/
Hidden”.
Here’s a link to the exact page I’m building. The HTML boxes in question are the guitar color descriptions on the right-side of the guitar pictures. Right now I got around the issue by layering 6 boxes. (an extra one for the 1st one you see) All of them have a background image that exactly corresponds to the underlaying blue fade, so they don’t overlap text. But essentially the first text description you see always stays there. The others just go over it. I’d like to do this better though, like in the “Target Image” Action applied to the guitar pics. (using the “Group” method you described, Keith)