Skip to content

FR: Page turns while touch input is disabled on ereaders lacking physical buttons #10273

Description

@jonnyl2

Does your feature request involve difficulty completing a task? Please describe.

Disabling touch input is very useful for reading while using a finger to track the text (e.g., for speed reading or for reading very tiny text so a lot of text can fit on one screen). However, it makes it impossible to turn pages on ereaders without physical buttons. Some ereaders have at least one physical button (e.g., back or home button), which can be defined as a page turn button, which solves this problem. On ereaders without any buttons (besides power) however, one needs to gesture to enable touch input again, turn page, then toggle touch input off again.

Describe the solution you'd like

Personally I'd like to be able to optionally exclude the 4 corner areas from the disable touch input feature. I've defined the corners as using just 3-5% of the screen length/width so accidental touches wouldn't be a problem. Using existing functionality, corner gestures can be set up to turn pages, call QuickMenus etc.

Describe alternatives you've considered

If all four corners are considered too much, to exclude just one or two corners (e.g., bottom right or bottom left and right) would also solve the main issue.

Alternatively, being able to define just two special gestures that only take effect when touch input is disabled. For example, two-finger swipe gestures to left and right. (A drawback would be that this could again be prone to accidental page turns; also, it could get confusing if the same gestures are already defined for a different function while touch input is enabled.)

Another option I was thinking of is that each user-defined gesture could have a tickbox allow while touch input is disabled so any gesture could optionally be excluded and used for page turns or to call a QuickMenu etc.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions