There seems to be a conflict with using Scripty Lightbox and Link Text Style on the same item. When I click on the link it opens to a standard html window. When I delete the Link Text Style from the item, it works.
I have an html text box with html text links. These links then open to an html page.
Can you post an example somewhere? My guess would be that the Text
Link Style is doing something heavy-handed with the links, and that is
removing the links from Freeway’s document model before the
ScriptyLightbox Action can decorate those links with the lightwindow
classname. That’s all the SL does in this context – it doesn’t
rewrite anything else while publishing. Have you tried using Freeway’s
native link styling controls for this instead of the Action? Click
once on the HTML box containing the links, and then in the Inspector,
move to the Style tab (paintbrush). The links segment is at the bottom
of the Inspector. Open it up, and you’ll have a whole world of control
over colors, link styles, etc.
Walter
On Mar 30, 2010, at 9:32 AM, Robert B wrote:
There seems to be a conflict with using Scripty Lightbox and Link
Text Style on the same item. When I click on the link it opens to a
standard html window. When I delete the Link Text Style from the
item, it works.
I have an html text box with html text links. These links then open
to an html page.
Make a new style in your Styles palette. Give it a descriptive name
like dashedUnderline. Click the Extended button and the New button. In
the sub-sub-dialog, enter border-bottom in the Name field and 1px
dashed #333 in the Value field. Apply this style to some text on your
page to see if it looks the way you want it to. When you have made it
the color and thickness you like, you can remove the test text from
your page. Back in the Links segment of the Inspector, click on the
More button below the basic settings. There you will be able to choose
this new dashed underline style and apply it to the four states of a
link (so you could make more versions of this style, with different
effects for each of the states).
Walter
On Mar 30, 2010, at 10:09 AM, Robert B wrote:
Walt, it works fine using the styles in the tab. Thanks for that!
I always think of that as a page-wide style, so I never go there
first.
Slightly OT: How can I make a dashed underscore for links?
This is true. I didn’t write the Link Styles Action, so you’ll have to
contact its author and see if they can make it less destructive.
(Please note, that’s a working hypothesis on my part, not anything I
have tested or proven. All I can say definitively is that SL is non-
destructive – it doesn’t rewrite the tags as text when it does its
thing.)
Walter
On Mar 30, 2010, at 10:52 AM, Robert B wrote:
Only when the html box is a CSS layer does it seem to have Links
show up.
Yes, you cannot get the FW Internal Link Style to work on a non-
layered element, because Freeway doesn’t allow this for some reason.
And I was wrong about the order of operations using the More button.
You don’t need to create a named style first, you need to define your
link style within the dialog presented by the More button.
What you’ll need to do first is remove the normal browser underline
from the link. This is done by clicking once on the U button next to
the Normal Visited Hover Active pickers in the Links segment.
Then press the More button and build up your style there by clicking
the Extended button and adding the name/value pair I gave you
previously. You will need to do this for the link and the hover,
active, and visited states as well.
Walter
On Mar 30, 2010, at 11:56 AM, Robert B wrote:
Actually, I was talking about your instructions for the dashed
underline.
I can’t seem to get it to work. It just doesn’t show up.
And the FW internal Link style is what I was refering to as not
showing up on an html box, only on a CSS layer.