Re: help on design

2005-08-18 Thread J. Landman Gay
Charles Hartman wrote: Thanks (as always!). But I put those four handlers in my substack's stack script (and saved and closed the whole thing and removed it from memory, then reopened it and navigated in the main stack and opened the substack and navigated within it), and both the "go back"

Re: help on design

2005-08-18 Thread Charles Hartman
Thanks (as always!). But I put those four handlers in my substack's stack script (and saved and closed the whole thing and removed it from memory, then reopened it and navigated in the main stack and opened the substack and navigated within it), and both the "go back" and "go forth" buttons

Re: help on design

2005-08-18 Thread J. Landman Gay
Charles Hartman wrote: > 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? If managed correctly, then right, "no". In the substack: on openstack -- first time opened s

Re: help on design

2005-08-18 Thread Charles Hartman
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 u

Re: help on design

2005-08-18 Thread J. Landman Gay
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 t

Re: help on design

2005-08-18 Thread J. Landman Gay
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

Re: help on design

2005-08-18 Thread Charles Hartman
Hmm. The recentCards property mixes (long names of) cards from all stacks -- I guess that's what the "go recent" command consults. The recentNames property lists (short names of) cards from the current stack (or a named stack, as in "put the recentNames of stack myStack"), which is what I w

Re: help on design

2005-08-18 Thread Charles Hartman
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. So I'm looking at ways to parse the recentCards property. (Messy, but easier than building my own specialize

Re: help on design

2005-08-17 Thread J. Landman Gay
Charles Hartman wrote: The tutorial app that I hope I'm finishing up includes a "reference" substack that the user is likely to keep onscreen beside the main stack. It would be useful to have "forward" and (especially) "back" buttons for navigation within that substack. Here's how I thought

help on design

2005-08-17 Thread Charles Hartman
The tutorial app that I hope I'm finishing up includes a "reference" substack that the user is likely to keep onscreen beside the main stack. It would be useful to have "forward" and (especially) "back" buttons for navigation within that substack. Here's how I thought of doing it: In the