But what I would like is for the cursor to do that each line or
window. Then I would never have to press an extra keystroke when at
the bottom of the page, because it would scroll and I could just keep
reading.
Some people like that; I don't. I want to know when I get to the bottom of
the
[quoted lines by Rob on 2018/03/06 at 17:32 -0600]
>The other change I made was removing the regular USB keyboard from the system.
>Do you think that might have something to do with it?
No, that shouldn't matter. Unless, of course, as does happen to me, you have a
cat who likes to sit, walk,
Dave Mielke wrote:
>The control and alt keys produce odd results.
> Yes, please do. We'll try to get this all figured out.
Hum, this is interesting.
I killed Brltty, turned off the braillesense, and then restarted the unit in
its terminal mode. Then restarted Brltty.
This time,
Dear Aura,
> Thanks. There have been some API changes in Python's regex module which I have
> to update my program for. I also need to do some checking, and make the key
> bindings somehow customizable - probably by editing a bunch of constants in a
> Python script, but that's better than no
[quoted lines by Rob on 2018/03/07 at 09:53 -0600]
>The control and alt keys produce odd results.
>Superscripts and circumflexes and accented letters. I can provide yet another
>debug log if necessary.
Yes, please do. We'll try to get this all figured out.
--
I believe the Bible to be the
Hi Shérab,
Shérab writes:
> Or perhaps you read books only through speech synthesis?
Yes! HTML files in Firefox. It lets me to read contituously without any
interaction. I can listen to a book and do other things for instance.
Regards,
--
Raphaël
The control and alt keys produce odd results.
Superscripts and circumflexes and accented letters. I can provide yet another
debug log if necessary.
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to:
[quoted lines by Dave Mielke on 2018/03/06 at 06:50 -0500]
>I agree with you that retrying every few seconds isn't nice, but I haven't yet
>come up with a better way to do it. There's no obvious way for brltty to know
>that a new Bluetooth device has been turned on, come within range, etc.
[quoted lines by Robert Pösel on 2018/03/06 at 10:15 +0100]
>while reading Android documentation I come to this recommendation:
>
>"Note: You should always call cancelDiscovery() to ensure that the
>device isn't performing device discovery before you call connect().
>If discovery is in progress,
Hi,
while reading Android documentation I come to this recommendation:
"Note: You should always call cancelDiscovery() to ensure that the
device isn't performing device discovery before you call connect(). If
discovery is in progress, then the connection attempt is significantly
slowed, and
10 matches
Mail list logo