i frequently use the read-aloud in android version. i look at the phone occasionally when a word is weird. about 1/6 of the time, the word i want to see is underneath the TTS playback control bar.
i would love for the control bar to not cover any of the words.
ideas:
1) have scroll-mode respect top/bottom margins (in TTS and otherwise). right now, in scroll-mode, top/bottom margin values are completely ignored. this is somewhat counter-intuitive, as left/right margins are respected. if bottom margin is respected, setting this value to 80 would solve the problem. (this option looks like it might require a minor redesign)
2) split the screen 90%/10% instead of using an overlay. (looks like too much ui devel work)
3) add an option to aggressively scroll, always putting the start of the current sentence on the first line. (this is how i planned on implementing it, until i realized android was a nightmare to compile anything whatsoever for). this option may be the best solution, since long sentences can apparently go off the page.
maybe 3 settings, normal (first word is on page), moderate (first word is on first half of page), aggressive (first word is on first line).
4) add a button to hide the controls, and clicking anywhere re-summons it (like how clicking anywhere closes TTS currently)
p.s.: didnt see any rules for feature requests, sorry for any issues. i run the android version on my SailfishOS device (Sony Xperia X Compact) through aliendalvik emulating android 4.4.4.
I have this problem too. This happens for me when a paragraph is big and there isn't a full stop. I think the threshold for when to scroll is not enough gor this case .
i frequently use the read-aloud in android version. i look at the phone occasionally when a word is weird. about 1/6 of the time, the word i want to see is underneath the TTS playback control bar.
i would love for the control bar to not cover any of the words.
ideas: 1) have scroll-mode respect top/bottom margins (in TTS and otherwise). right now, in scroll-mode, top/bottom margin values are completely ignored. this is somewhat counter-intuitive, as left/right margins are respected. if bottom margin is respected, setting this value to 80 would solve the problem. (this option looks like it might require a minor redesign)
2) split the screen 90%/10% instead of using an overlay. (looks like too much ui devel work)
3) add an option to aggressively scroll, always putting the start of the current sentence on the first line. (this is how i planned on implementing it, until i realized android was a nightmare to compile anything whatsoever for). this option may be the best solution, since long sentences can apparently go off the page. maybe 3 settings, normal (first word is on page), moderate (first word is on first half of page), aggressive (first word is on first line).
4) add a button to hide the controls, and clicking anywhere re-summons it (like how clicking anywhere closes TTS currently)
p.s.: didnt see any rules for feature requests, sorry for any issues. i run the android version on my SailfishOS device (Sony Xperia X Compact) through aliendalvik emulating android 4.4.4.