Bugzilla – Bug 11737
Option to disable touch (or IR) input
Last modified: 2011-11-06 23:23:35 UTC
I'd like a way to temporarily lock the screen so I can wipe it down without powering off.
The cleaning cloth that comes with Fab4 will be a little thin, but if you use something thicker, like two layers of t-shirt fabric, the screen won't sense your fingers behind it. I'm going to leave this open and see if we get other complaints, or if it's just a documentation/FAQ issue...
Thanks for the tip! if I fold the included cloth into quarters, it doesn't detect the wiping as a touch. Others have requested a screen lock for keeping kids from messing with the touch screen, so it might be good to keep the enhancement open.
This enhancement needn't only be used for cleaning the screen. Testers in the beta forum have mentioned that it would be desirable to have the ability to disable the touch interface and only permit control through the IR remote. For instance, to keep children from messing with the player.
Tom, you were going to look at this.
*** Bug 11143 has been marked as a duplicate of this bug. ***
Reset priority before triage.
Matt, strings/design need for this. My thought is new choice items: Settings->Screen->Input Control which is a Choice item with the following choices (with Both as the default): "Both (Touch and Remote)" "Touch Only" "Remote Only" I could also put in a speculative string for both disabled, but that would require a factory reset to recover from, so I'm not sure we'd want to offer that. Also, I'm not sure what the offical verbage for "Remote" is.
Tom, love your suggestion, let's do it
strings added in r6795. non-string work still incomplete.
With regard to implementing this, are there any implications for the visibility of buttons on screen? I don't think it matters much, but there could be an argument that all buttons should be removed when touch is disabled.
Tom is no longer available to us
> Tom, love your suggestion, let's do it Yes, do it. Any chance this option could be targeted for 7.6 and added to an upcoming beta firmware? This doesn't necessarily need to be added to web UI settings - a localized setting within the SqueezePlay menus would be sufficient.
Unassigned bugs cannot have a priority.