I'll try this. But it looks like (am I wrong? always a good
possibility!), as long as the substack is open, cards from other
stacks will get added to the "recent" list. No?
(In the anticipated use, the substack will get opened sometime early
in the session, and will be left open while the user navigates
through the main stack, occasionally opening new cards in the substack.)
Charles
On Aug 18, 2005, at 12:20 PM, J. Landman Gay wrote:
J. Landman Gay wrote:
Charles Hartman wrote:
> Thanks. Unfortunately that doesn't behave quite the way I need
-- it
> goes back through cards no matter what stack they're in. I need
the
> buttons to navigate just within the substack.
That's perfect for this technique, then. On openstack, in the
substack, you set the lockrecent to false. When the substack
closes, you set it back to true. The result is that only the cards
in the substack get added to the recent list. Then use "go back"
and "go forth" to traverse the recentcards.
I should add one more thing to this. If the substack stays open,
then you'd want to use "suspendstack" and "resumestack" instead
when setting the property.
--
Jacqueline Landman Gay | [EMAIL PROTECTED]
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
