Sometime around 11/7/09 (at 09:49 -0400) SkipII said:
Process #2 worked, but I have had other times when it did not work,
but those times I was modifying an existing button group. There must
be some stray code os something that interferes.
Your Freeway document contains no code whatsoever (not counting
markup code you add yourself, of course), so you never have to worry
about ‘stray code’.
Freeway layouts are far more sophisticated than HTML can manage, in
just the same way that InDesign and QuarkXPress layouts are far more
sophisticated than PostScript (their output) can manage. The
software’s job is to produce the optimum code from your layout, from
scratch, each time you preview, publish or upload. Freeway does no
editing of existing code, so it completely avoids all the cruftiness
that can go with that. Everything is fresh, new and re-optimised
So don’t worry, it is simply not possible for Freeway to ‘have stray
code’ left in its page from earlier stages of your layout efforts.
Not possible at all.
I suspect the times it didn’t work were times when you had created
the group with items that were not, for whatever reason, layered.
Like I said, this is what causes the Rollover action to not be able
to see inside the group - which is precisely the problem you’ve had.
i do want to mention that, no, when I drew the first graphic for the
button group, it did not automatically have layer checked, even
though CSS Layers was active.
I suspect that either you initially drew it ‘inside’ an existing item
(as a child item) or it actually wasn’t active when you drew it. I
could be mistaken, but at this moment I know of no other way at all
for an item to begin life on a page in an unlayered state.
As long as no other issues are brought into play,
Process #2 will always work, and
Process #1 will (in today’s Freeway) never work.
The trick to keeping all this repeatable is to ensure that the items
you’re about to group are layered and are not children of other
freewaytalk mailing list
Update your subscriptions at: