Bugs with idle loop

[GoogleCodeExporter]

There are some bugs with the current idle loop that make it hard to test it 
further.

1. Currently, the idle speech is read and displayed when EZ Access is on. This 
makes it practically impossible to use EZ Access because it keeps getting 
interrupted. Instead, the idle speech should only occur when EZ Access is off.

2. A pop-up displays the idle speech. I don't want this to interrupt 
touchscreen users, so in this case, there should be NO alert box. Typically, 
what we have done in our demos is just always display this speech on the screen 
as part of the splash screen (so it is available both visually and auditorily).

3. The idle loop, if the delay is set short, will interrupt itself. Ideally, 
this delay would happen after the speech output is done reading something. For 
example, "This is the speech loop." + 5000ms delay ... "This is the speech 
loop." etc.

Original issue reported on code.google.com by jbjor...@gmail.com on 9 Sep 2013 at 3:13

[GoogleCodeExporter]

Just for clarification: the idle speech is to help solve the novice EZ Access 
user problem. Somebody who does not know how to use EZ Access will hear the 
idle speech loop through headphones, which will tell them to press the Help 
button for more instructions. They only need to hear this on the first screen 
when they aren't already using EZ Access. We can also use non-looping idle 
speech through headphones to remind people that they can use the EZ Down button 
on subsequent screens.

The term "idle speech" may be a little bit of a misnomer in that it is not for 
someone who is idle in the application. (Idle speech is for when the 
application is idle, not when the user is idle or has just left.) That is a 
timeout, which would need to be implemented in JavaScript on each page. We may 
need to have some kind of hook for that behavior in EZ Access.

Original comment by jbjor...@gmail.com on 10 Sep 2013 at 2:56

[GoogleCodeExporter]

This is mostly fixed with the latest revision (r320). However, the timer needs 
to start from when the speech ended, which is on the todo for this and other 
issues.

Original comment by aeharding on 10 Sep 2013 at 8:07

[GoogleCodeExporter]

Fixed by r323

Original comment by aeharding on 11 Sep 2013 at 9:11

[GoogleCodeExporter]

Original comment by aeharding on 11 Sep 2013 at 9:11

• Changed state: Fixed