Hello Jason,
Could you just make the purple area a button. Turn off showName,autoHilite,sharedHilite, showFocusBorder. And turn off traversalOn - so that it doesn't take focus off the field if it is clicked..
You can use property inspector (size & position/layer) to 'send to the back' alter you create the button.
Regards Pat [EMAIL PROTECTED]
----- Original Message ----- From: "Silver, Jason" <[EMAIL PROTECTED]>
To: <use-revolution@lists.runrev.com>
Sent: Wednesday, February 09, 2005 8:54 AM
Subject: mouseDown/Up - no actions when not on buttons
Hello (again) :) After some very useful advice from Jacqueline Landman Gay at Hyperactive, I've changed the structure of my mobile phone sim tool. Now, instead of the buttons being on a palette, they're grouped and behave like a background, showing up on every card. When buttons are pressed, they send a custom ButtonPress message with the name of the button being pressed to the card. The card then has a switch statement, and does some action based on which button was pressed.
The current card I'm working on is a Login type screen, with two focusable/editable fields, User ID and Password. (Please see my shared stack in RevOnline's User Spaces; the username is jsilver). In the switch statements, I have this script when the user presses up (or down):
case navUp -- Determine which text field the user is currently in put the short name of the selectedField into activeField if activeField = "User ID" then focus on field "Password" else -- The user must be in the password field focus on field "User ID" end if break
This works all well and good, except when pressing on an area that's not a button (in my stack, the purpleish area). The cursor then disappears from either the User ID or Password fields, and then when pressing Up or Down, the following error occurs (because the focus is not in a field):
Type: Chunk: no target found Object: Login Screen Line: put the short name of the selectedField into activeField
Basically, I never want the focus to leave either the User ID or Password fields; this simulation is supposed to be controlled solely by the buttons placed in the "Buttons" group. Is there an easy way to block the mouseUp (or mouseDown?) handler from doing anything when not on those buttons? I've tried adding "exit mouseDown" type handlers in the card and stack, but this doesn't do anything. Any help is appreciated.
Thanks again!
Jason Silver
Human Factors Engineer, Sr.
QUALCOMM Inc.
(858) 845-3444
[EMAIL PROTECTED]
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
