Sometime around 22/6/09 (at 05:11 -0400) wurliuchi said:
Thank you for the explanation. I don’t understand why moving an item
to the front puts it on the bottom of the item stack.
The list of items there is shown in ‘first/second/third’ order, just
as if you were writing items down in a list on paper. The first item
you write in your list is at the top of the page. The next item comes
below that, then the third item you add comes below the previous two,
Now look at the page rather than the list. When you add a new item to
your layout, it is always top-most in the stacking order. This is how
all DTP apps work, and how virtually every other kind of app (that
creates objects in a page-style space) works too.
Combine these two things and you get Freeway’s UI behaviour: the list
reflects the stacking order, which reflects the creation order. If
you shuffle things around in the page then the logical result is
things shuffled around in the list as well. (And you can use the list
order to rearrange the stacking order of items in the layout without
having to dig through piles of items in the page layout; just grab
and drag items up or down the list.)
Without this background info it can be a tad confusing. It could be
argued that the list should show new (top of the stack) items at the
top of the list. But there are arguments BOTH ways - and really, the
important thing is to understand the underlying logic of how things
It would be nice to have an “Always Keep In Front” check box in the
CSS Menu Action.
This is true. Of course, there is the issue of splitting the logic of
‘stacking order = output order’; if you JUST want it to be at the
top, bring it to the front. What you really want (if I’m
understanding things correctly) is for it to be at the front in
layout stacking terms but not in front of content divs in code
ordering terms, for accessibility reasons.
Perhaps just a minor terminology amendment might help? “Always Show
In Front” (Show rather than Keep)?
Anyway, this is purely idle conjecture as this feature doesn’t actually exist!
Also, it might be more useful in the short term as a free-standing
action that sets or alters the z-order of any chosen layered item
(div) rather than just the CSS Menus object. Certainly, I would have
thought it would be easier for some actions writer to put together!
freewaytalk mailing list
Update your subscriptions at: