Jan 19, 2009 06:24
There's a problem with jumping to new Topics. I got confused, as
usual, and added Quip dialogue pairs to a Topic I was jumping to. Which --
I don't think it ever prints the dialogue pair if it jumps to a new branch
like that. So then I thought, ok, I'm supposed to just make a Topic object
a basically blank declaration whose purpose is to be the parent of some
new Quip options. Except when I did that, it then still didn't print the
dialogue, because now it's one menu removed.
When there's a JumpTo point, it should -- hmm. I guess it's supposed to do
a JumpTo after it's already printed some dialogue, which means you selected
a menu option. It prints the dialogue pair, and then if there's a JumpTo
this will print a new menu of choices next time from that new Topic. But
I was trying to do a special case (actually something I might want to do
fairly often), which was that a certain Topic (or Quip) was available early
in the menu tree, then disappeared when you followed a branch for a while,
then reappeared later (due to a JumpTo call). So it needed to be both a
Topic and a normal Quip at the same time, and I guess that just doesn't
make enough sense. Is there a way to sensibly handle all cases like this,
or do I have to add redundant identical copies of Quips if I want them to
show up twice in the menu?
Actually no, that's not a good solution, because I want the whole tree of
subclips from that Quip to be intact whether you choose it earlier or
choose it later. So I really need to think about how this will work.
notes,
writing,
process,
interactive fiction,
programming,
work-in-progress