In article <Km1ye.7894$vE5.5274@trndny07>, I'm (AT) Witz (DOT) end says...
Quote:
Same as in previous versions: Other than to select the layout from the
drop-down in the Status Area, there's nothing in terms of a menu item or
permanent button, if that's what you're looking for.
You would define your own button to Go To Layout [Layout Name, Number, by
calculation, etc], or you can incorporate that same step into a script.
Matt |
And...
Like previous version if this was a feature you wanted, you could
implement it easily enough* yourself.
Basically you need to have all your navigation scripted so that users
push buttons with scripts attached to them to move from layout to layout
(screen to screen), and then you have code in those scripts that update
a global list (implemented, for example, as simple list in a global text
field). When you click a button to navigate it pops a new entry at the
front of the list (and if the list is longer than the history length,
removes the entry at the back).
Adding a 'back' button can be as simple as going to the layout indicted
in the first entry, and then removing that entry.
Adding a 'forward' button is a touch more complicated, but essentially,
it involves implementing a list cursor (simply a counter), and then the
back/forward buttons display the layout indicated by the entry at the
cursor (without modifying the history list at all)... and of course,
when you add new entries, it clears everything ahead of the cursor
before adding an entry.
* By easily, I mean its quite easy to do if you design the navigation
system from the ground up to support this, and then build the rest of
the solution on top of it using it. If you have to retro-fit it onto an
existing system it tends to be a pile more work, with lots of bugs to
root out (e.g. misbehaving scripts that bypass the history recording
mechanism you just built)