[quoted lines by J. R. Westmoreland on 2012/03/19 at 18:12 -0600]
>I suspect that you could get jittering of the display. This might not happen
>on a newer, faster, display but a lot of the old stuff kicking around could be
>an issue.
>I see something like it under windows if the application doe
[quoted lines by Vladimir 'φ-coder/phcoder' Serbinenko on 2012/03/20 at 00:41
+0100]
Hi:
>What prevents from starting an update immediately or after few ms
>delay and aborting/restarting it if cursor changes again?
That's roughly the way it works. A cursor move operation is enqueued, and then
Dave will correct me if I'm off the mark here.
I suspect that you could get jittering of the display. This might not happen on
a newer, faster, display but a lot of the old stuff kicking around could be an
issue.
I see something like it under windows if the application does a lot of jumping
aro
On 19.03.2012 22:01, Dave Mielke wrote:
[quoted lines by Shérab on 2012/03/19 at 21:52 +0100]
What I've noticed e.g. when running brltty in the Iris is that one can
see the cursor moving on the display to its final position and the whole
process seems to me a bit slower than it was before.
Is
On Mon, 19 Mar 2012, Dave Mielke wrote:
> [quoted lines by Shérab on 2012/03/19 at 21:52 +0100]
>
> >Would it make sense tomodify the algorithm in the following way: for the
> >first few vertical/horizontal motions, wait a bit longer in case the
> >cursor moves temporaily. If that does not occur,
[quoted lines by Shérab on 2012/03/19 at 21:52 +0100]
>What I've noticed e.g. when running brltty in the Iris is that one can
>see the cursor moving on the display to its final position and the whole
>process seems to me a bit slower than it was before.
Is it too slow?
>Would it make sense tomod
Hi,
> The problem it resolves is the cursor being temporarily moved to an
> unexpected
> location, so that must be happening.
>
> To do this, brltty has to wait a little longer to ensure that the cursor has
> stopped moving around. I'm very interested, therefore, in as many users as
> possibl
[quoted lines by Shérab on 2012/03/19 at 21:36 +0100]
>> Please test the latest dvelopment code to see if the problem is still
>> occurring.
>
>It seems to fix the problem, indeed.*
The problem it resolves is the cursor being temporarily moved to an unexpected
location, so that must be happenin
Dave Mielke (2012/03/19 16:10 -0400):
> Please test the latest dvelopment code to see if the problem is still
> occurring.
It seems to fix the problem, indeed.*
Sherab.
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-
Please test the latest dvelopment code to see if the problem is still
occurring.
--
Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God.
Phone: 1-613-726-0014 | Ottawa, Ontario | 2011 May 21 is the End of Salvation.
EMail: d...@mielke.cc | Canada K2A 1H7 | http://M
> If it's the problem that I think it is, it has to do with status lines which
> contain things like the current cursor position. As the cursor moves, the
> status line is updated. Updating the status line requires temporarily moving
> the cursor to an unexpected place. If the timing is just wro
[quoted lines by Mario Lang on 2012/03/19 at 20:32 +0100]
>No, the problem can not be in Lynx since moving the cursor manually just
>works fine.
If it's the problem that I think it is, it has to do with status lines which
contain things like the current cursor position. As the cursor moves, the
Shérab writes:
> Mario Lang (2012/03/18 13:30 +0100):
>> Anyone seen similar behaviour?
>
> Yes. Even moving the cursorone character to the right or the left with
> routing keys fails most of the time here. Oh but this happens even with
> an older brltty so perhaps the problem is in lynx ?
No, t
Hello,
I think these lines are anough, if you want the complete log I can send it.
***
brltty.exe: checking braille device: serial:COM5
brltty.exe: checking for braille driver: sk
brltty.exe: initializing braille driver: sk -> serial:COM5
brltty.exe: device directory: //.
brltty.exe: CreateFile ->
[quoted lines by Mario Lang on 2012/03/18 at 13:30 +0100]
>I remember we changed something about the algorithm recently, was that past
>4.3 or prior to its release?
The change was after 4.3, so could you please retest with the latest
development code?
--
Dave Mielke | 2213 Fox Cresc
[quoted lines by Simone Dal Maso on 2012/03/19 at 10:37 +0100]
>But, today I discover that brltty is not able to recognize the seika80.
>The display remain completely empty, no beep, no error message or
>something like brltty started.
>is it possible to use brltty with seika 80?
Could you please
Hello,
I'm using brltty with the standard seika 40 brailledisplay with NVDA, on
Windows, and there are no problems.
But, today I discover that brltty is not able to recognize the seika80.
The display remain completely empty, no beep, no error message or
something like brltty started.
is it pos
17 matches
Mail list logo
