Dave Mielke writes:
> [quoted lines by Aura Kelloniemi on 2015/11/13 at 11:26 +0200]
>>BRLTTY nowadays displays colour names incorrectly with the Describe Character
>>command.
> Could you please test this with the latest code to see if it's been resolved?
It seems to work now. I wrote a small
Aura Kelloniemi, on Tue 17 Nov 2015 10:23:33 +0200, wrote:
> I could not get the blink attribute working on Linux console. Traditionally it
> changed the background colour to be bright, as the bold attribute does for the
> foreground colour.
The background color can not be made bright, only the fo
[quoted lines by Aura Kelloniemi on 2015/11/17 at 10:23 +0200]
>I could not get the blink attribute working on Linux console. Traditionally it
>changed the background colour to be bright, as the bold attribute does for the
>foreground colour.
I know what you mean, but your wording may be a bit co
Samuel Thibault, on Tue 17 Nov 2015 10:07:37 +0100, wrote:
> Aura Kelloniemi, on Tue 17 Nov 2015 10:23:33 +0200, wrote:
> > I could not get the blink attribute working on Linux console. Traditionally
> > it
> > changed the background colour to be bright, as the bold attribute does for
> > the
> >
Samuel Thibault writes:
> Samuel Thibault, on Tue 17 Nov 2015 10:07:37 +0100, wrote:
>> Aura Kelloniemi, on Tue 17 Nov 2015 10:23:33 +0200, wrote:
>> > I could not get the blink attribute working on Linux console.
>> > Traditionally it
>> > changed the background colour to be bright, as the bold
Aura Kelloniemi, on Tue 17 Nov 2015 14:58:22 +0200, wrote:
> Samuel Thibault writes:
> > Samuel Thibault, on Tue 17 Nov 2015 10:07:37 +0100, wrote:
> >> Aura Kelloniemi, on Tue 17 Nov 2015 10:23:33 +0200, wrote:
> >> > I could not get the blink attribute working on Linux console.
> >> > Traditio
Samuel Thibault (2015/11/17 14:06 +0100):
> The problem is that these userland-driven terminals don't provide the
> screen output. Ideally we'd manage to gather the people implementing
> them, and get to define a common interface to access the screen
> output.
Isn't AT-SPI good enough for that? Or
Shérab, on Tue 17 Nov 2015 15:04:54 +0100, wrote:
> Samuel Thibault (2015/11/17 14:06 +0100):
> > The problem is that these userland-driven terminals don't provide the
> > screen output. Ideally we'd manage to gather the people implementing
> > them, and get to define a common interface to access t
Samuel Thibault (2015/11/17 15:15 +0100):
> It is heavy for performance (at *best* thousands of requests
> per second), and it is really not suited to getting terminal
> information. The AccessibleTerminal interface has never been actually
> implemented.
>
> Generally speaking, the way AT-SPI work
Shérab, on Tue 17 Nov 2015 15:26:25 +0100, wrote:
> I was just wondering whether it wouldn't e
> possible to improve r enrich AT-SPI to make it more suitable for
> terminals, my concern being to avoid having too many standards and APIs
> around. But if you think it's best to just have another API b
Samuel Thibault writes:
> Shérab, on Tue 17 Nov 2015 15:04:54 +0100, wrote:
>> Samuel Thibault (2015/11/17 14:06 +0100):
>> > The problem is that these userland-driven terminals don't provide the
>> > screen output. Ideally we'd manage to gather the people implementing
>> > them, and get to defin
[quoted lines by Mario Lang on 2015/11/17 at 22:11 +0100]
>This is a very old open problem. I remember we agreed long ago on doing
>it similar to how Screen already does it (via the patch), but in a
>"standardized" way, such that the *same* sort of SHM layout could be
>used for several different
Hi. I have discovered since the update to the Humanware brailliant bi
40, I am getting no keyboard response with brltty -- I can use the four
keys on the front, but the keyboard is dead. So I tried to do a git
pull to see if that would help, but when I ran configure it said error
cannot find Prog
Hi,
You should probably run
./autogen
before running ./configure.
Shérab.
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@mielke.cc
For general information, go to: http://mielke.cc/mailman/listinfo/brl
Hi,
Recent firmware versions have the ability to turn the braille keyboard
off. Please check in the Brailliant settings (double press power button)
if it is enabled.
Bram
On 17-11-2015 21:58, cov...@ccs.covici.com wrote:
> Hi. I have discovered since the update to the Humanware brailliant bi
> 4
hmmm, strange but there is one, since there was a ./configure I never
thought to run autogen, but I will try that.
Seems to have worked -- thanks.
But I still have no keyboard at all.
Shérab wrote:
> Hi,
>
> You should probably run
> ./autogen
> before running ./configure.
>
> Shérab.
> _
[quoted lines by cov...@ccs.covici.com on 2015/11/17 at 15:58 -0500]
>I tried to do a git pull to see if that would help, but when I ran configure
>it said error cannot find Programs/brltty.h in . or .. and indeed there is no
>file brltty.h in the Programs directory.
You need to run ./autogen b
Yep, it was off -- whoever would have thought that they would have that
as the default -- thanks much.
Bram Duvigneau wrote:
> Hi,
>
> Recent firmware versions have the ability to turn the braille keyboard
> off. Please check in the Brailliant settings (double press power button)
> if it is ena
OK, so now I have the keyboard working in my virtual consoles, but orca
is not seeing brltty at all. There is a brlapi.key in /etc and this did
work with the older verwsion I was using, but now no joy.
Bram Duvigneau wrote:
> Hi,
>
> Recent firmware versions have the ability to turn the braill
Mario Lang, on Tue 17 Nov 2015 22:11:15 +0100, wrote:
> When we originally planned to do it via SHM, D-Bus was not around.
> Is SHM still the best option?
It's *way* faster than any IPC.
> However, D-Bus has access control, and maybe we could make use of that
> to minimize potential security risk
Dave Mielke, on Tue 17 Nov 2015 16:19:13 -0500, wrote:
> [quoted lines by Mario Lang on 2015/11/17 at 22:11 +0100]
> >This is a very old open problem. I remember we agreed long ago on doing
> >it similar to how Screen already does it (via the patch), but in a
> >"standardized" way, such that the *
Hi.
I have still issues with my Braille voyager 70. I have now purchased an
Convert box wich Optelec provide. The price was more or less robb. but
ok. 70 cells display is 70 cells display. So now it,s works very well
with both Jaws 17 and window eyes and other screenreaders running
windows 10
Samuel Thibault writes:
> Mario Lang, on Tue 17 Nov 2015 22:11:15 +0100, wrote:
>> When we originally planned to do it via SHM, D-Bus was not around.
>> Is SHM still the best option?
[--]
>> The libraries are a convenience, but it is perfectly
>> possible to code a standalone AT-SPI client just
23 matches
Mail list logo
