Get keypresses from SVGForm with only label components.

Question

I have a Screen class, extending SVGFORM, with only labels in it.No buttons or spinners and the like.
The SVGForm is displayed and on clock ticks, I change the label strings (telling time). So no input facilities.
The SVGForm has commands, Exit and pause.
The SVGForm is on its own thread, being Runnable.
all works nicely, but:
I need to act on the user pressing the "FIRE" button of the handset.
How can I get at the key code ?
keyPressed() does not catch it, somehow...
one more:
I put the SVGForm on its own thread. The program starts with a splash screen, then an input form to get some variables and then the clock screen starts and keeps running, that being the sole purpose of the program. When the clock is stopped , the program may exit. Is a separate thread for it necessary/a good idea ? or shouldn't I be bothered with threads at all ?

Answer 1

Thanks for the reply
I have ended up with something that seems to be working finally.. it's very inspired by robotlegs probably.. I found the SQLite robot-legs-addressbook example extremely helpful and borrowed large swaths of code from it; it was really tricky for me to figure exactly what was doing what (especially because I wasn't aware yet of some of the finer points of debug mode and that thing where you cmd+click and it goes right to the function definition)..  I got it working by adding handlers as arguments to the add/update/modify functions..
in the model:
private var _doneAddHandler:Function;
public function add(doneAddHandler:Function):void {
var stmt:String = new String();
_doneAddHandler = doneAddHandler;
//etc
private function add_result(results:Vector.<SQLResult>):void
_doneAddHandler();
then in the component:
public function loadExercise():void {
_exercise.loadExercise(currentUser, DateTime, doneLoadExercise);
That is allowing me to grab the info I need from the database and dump it into the component and back and forth. Probably a little less decoupled than robotlegs.. which I was looking at a bit based on its use in SQLRunner and addressbook, and was quite tempted, but I was on a tight timeline and it seemed very daunting up front; I didn't find a strong enough handhold on it, even though on paper it seemed like exactly the solution to my problems.
I will have to write model classes for some specific views to get the basic information out, but now that communication's going on everything seems a lot more attainable.