Dynamically creating notes that lay "on top" of cards

Silver, Jason jsilver at qualcomm.com
Thu Feb 10 16:33:00 EST 2005


Being such a bottom-up thinker, I'm having some trouble taking a step
back and looking at the overall structure for this design.  On our
"unstable yet maturing" mobile phone simulation, there are times when
dialogs (from here on in, I'll call them notes) must be displayed on top
of whatever is already on the screen.  For example, you may have written
a text message and pressed the "End" key; you'll be asked if you want to
save what you've written.  What happens is as follows:

1) The user does something which causes the note to be displayed
2) The existing screen is dimmed, and the note is displayed on top.
3) The softkeys are changed so that they relate to the note (e.g. "Yes"
and "No")
4) The user decides on a relevant action.

Okay, now the Revolution side of things.  To dim the screen, I've
created a solid white image that uses a blend so that the screen appears
faded.  Creating a note is simple - it would just consist of two fields
grouped: the "Title" of the note and the "Body" of the note.  Softkey
changes can be done with a function, passing two parameters (name of
left softkey, name of right softkey).  But here I am thinking bottom-up
again...

The "Big picture" questions concern how these new notes interact with
the existing card.  Since there can be several different notes that can
overlay on the card (albeit one at a time), it seems silly to have all
these notes pre-created and invisible.  So, the big question is, can we
just have a note, then simply feed it the title and body when it is
displayed?

Also, since the softkeys change, the behavior has to change for those
buttons.  The "ButtonPress" message which I previously created was
handled at the card  (specifically leftSoftkey and rightSoftkey).  Since
that one card can either not be displaying a note, or have one of any
number of notes on top of it, does it seem sensible to create yet
another switch statement?  The condition would have to check if a note
is visible.  But the behavior can be different depending on which
note...maybe I should create the notes, have the behavior encapsulated
in that note (i.e. the field), and pass the ButtonPress message to the
note if there's one up?

There are so many ways to do things in Transcript, and moreover, in
Revolution, that I don't know what to try first.  Any advice on which
direction to go would be helpful.  Thank you!

Best regards,
Jason 


More information about the Use-livecode mailing list