help on design
charles.hartman at conncoll.edu
Thu Aug 18 08:39:22 CDT 2005
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 want. So the information is available.
But the only mechanism I can find for *navigating* with these lists
is "go recent" -- and I haven't found any way to restrict that to
cards of one (sub)stack. My best guess so far ("go recent card of
stack mySubStack") is accepted by the message box, but the stack
restriction in the command doesn't seem to have any effect -- I just
go back through the recentCards history list in all stacks, including
What am I missing this time??
On Aug 18, 2005, at 8:56 AM, 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. So I'm looking at
> ways to parse the recentCards property. (Messy, but easier than
> building my own specialized history list.) Thanks for the tip!
> On Aug 17, 2005, at 11:05 PM, J. Landman Gay wrote:
>>> Does this seem like the best approach? Or is there a better
>>> method -- or something built into Rev -- that I'm missing?
>> go back
>> go forth -- or the synonym "go forward"
>> If you want to exclude particular cards from the visited list, and
>> you know the user will be going to one of those cards, set the
>> lockrecent property to true ahead of time. When lockrecent is
>> true, cards are not added to the history trail.
>> See the "go" entry in the dictionary for lots of other options too.
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
More information about the use-livecode