[Xerte] default button

Julian Tenney Julian.Tenney at nottingham.ac.uk
Tue Oct 28 12:49:34 GMT 2008


You don't see the yellow rectangle for custom buttons? They do work for
custom button here.

 

From: xerte-bounces at lists.nottingham.ac.uk
[mailto:xerte-bounces at lists.nottingham.ac.uk] On Behalf Of Elly Langewis
Sent: Tuesday, October 28, 2008 10:21 AM
To: Xerte discussion list
Subject: Re: [Xerte] default button

 

Hi Julian,

 

Well, there is no urgency. It seems to work for TextEntry interactions,
and in the model you use setFocus in exactly the same way. Enough other
things to figure out to keep me busy, and this is just a minor problem.

Is there btw something I should do (or not do) to make the yellow boxes
appear when the user presses the Tab? I take it they should work for
custom buttons as well?

 

Elly

On Mon, Oct 27, 2008 at 10:11 PM, Julian Tenney
<Julian.Tenney at nottingham.ac.uk> wrote:

I can look into it. I wonder whether this is the right way to do things
- the selection is usually set by the user, and I'd expect the user in
Xerte to move the focus around using the tab key.

 

________________________________

From: xerte-bounces at lists.nottingham.ac.uk on behalf of Elly Langewis
Sent: Mon 27/10/2008 16:54 


To: Xerte discussion list
Subject: Re: [Xerte] default button

 

Ok now I do not understand it anymore.

 

1. For a TextEntry I can only set the focus in a script icon that is at
the same level as the TextEntry (hanging off the interaction icon). When
I don't set the focus, the user has to click at the TextEntry box first.
When I do set the focus, the user can type the answer right away. When I
put the script icon on any other place, this does not work.

If I track the focus with selection.getFocus() it is undefined, before
and after I set the focus. But it works.

 

2. If I try to do the same for a button response, the focus is not
changed. (no focus, or if another button had the focus, it still has)

 

3. The perpetual menu button has the focus, even if there is an
interaction with a number of other buttons (the menu intself), and I
press one of these (for paragraph 1). After that, the menu button still
has the focus.

 

Can anybody shed a light on this? It feels like I am doing several
things wrong, but how should I do it then?

 

Thanks in advance,

 

Elly

On Mon, Oct 27, 2008 at 12:42 PM, Elly Langewis <e.a.langewis at gmail.com>
wrote:

Hi,

 

I got it to work with the rs property without quotes, for a text
response. I do not succeed to set the focus to another perpetual button.
Strange.

 

Elly

On Mon, Oct 27, 2008 at 12:22 PM, Elly Langewis <e.a.langewis at gmail.com>
wrote:

Hi Julian,

 

Whatever I type as myButtonID - ID, rs, name, or
'_level0.engine.IFC.FW_ENT.Int_MC7.but9' - the focus does not change
(debug(Selection.getFocus()). Any ideas what I could be doing wrong? As
the get does work, I think the set should work too.

 

Elly

 




 

On Fri, Oct 24, 2008 at 4:53 PM, Julian Tenney
<Julian.Tenney at nottingham.ac.uk> wrote:

Selection.setFocus(myButtonID) I think.

 

You can listen for rootIcon.onKeyDown to listen for keypresses, so you
can have an event responses for y and n and the yes / no buttons as
well. Being able to define the action key would be useful - I'll look at
that next week.

 

 

 

From: xerte-bounces at lists.nottingham.ac.uk
[mailto:xerte-bounces at lists.nottingham.ac.uk] On Behalf Of Elly Langewis
Sent: Friday, October 24, 2008 4:48 PM
To: Xerte discussion list
Subject: Re: [Xerte] default button

 

Thanks Julian, that explains. 

Is it possible to set the focus to a certain button? And is it possible
to make a button react to a certain key pressed, like when I have two
buttons, yes and no, and want the user to be able to press Y or N
(besides making a third response to catch that)?

 

Elly

On Fri, Oct 24, 2008 at 5:03 PM, Julian Tenney
<Julian.Tenney at nottingham.ac.uk> wrote:

It's built in accessibility. It will only respond to keys whilst it has
the focus. When you click elsewhere, the focus moves away from the
button and it doesn't respond to keypresses. All the interaction
responses can be controlled with the keyboard.

 

From: xerte-bounces at lists.nottingham.ac.uk
[mailto:xerte-bounces at lists.nottingham.ac.uk] On Behalf Of Elly Langewis
Sent: Friday, October 24, 2008 3:41 PM
To: Xerte discussion list
Subject: [Xerte] default button

 

Hi,

 

I've got a perpetual button ('Menu') in my Entry Frame. For some reason,
when I have used the button (just once), this button will also get
pressed when I hit the space bar. As I have not found yet how to let a
button react to key responses I was quite surprised...

Does anyone know what caused this behaviour? It disappeats after using a
text entry response, but after hitting the button again it reacts to the
space bar again.

 

TIA

 

Elly

 


_______________________________________________
Xerte mailing list
Xerte at lists.nottingham.ac.uk
http://lists.nottingham.ac.uk/mailman/listinfo/xerte




-- 
Elly Langewis
courseware developer
Department of Biology
Utrecht University


_______________________________________________
Xerte mailing list
Xerte at lists.nottingham.ac.uk
http://lists.nottingham.ac.uk/mailman/listinfo/xerte




-- 
Elly Langewis
courseware developer
Department of Biology
Utrecht University




-- 
Elly Langewis
courseware developer
Department of Biology
Utrecht University




-- 
Elly Langewis
courseware developer
Department of Biology
Utrecht University


_______________________________________________
Xerte mailing list
Xerte at lists.nottingham.ac.uk
http://lists.nottingham.ac.uk/mailman/listinfo/xerte




-- 
Elly Langewis
courseware developer
Department of Biology
Utrecht University

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.nottingham.ac.uk/pipermail/xerte/attachments/20081028/c23a8419/attachment.html


More information about the Xerte mailing list