[quoted lines by Leonard de Ruijter on 2023/10/09 at 19:50 +0200]
>Unfortunately, I can't get the thing to load on Python 3.11-32.
>
>I'm getting the error: `ImportError: DLL load failed while importing brlapi:
>The specified module could not be found.`
I'm not a Windows person so, really, can't
[quoted lines by Leonard de Ruijter on 2023/09/28 at 21:50 +0200]
>Unfortunately, I can't get brltty to build on my Windows system. Here is wat
>I do:
>
>
>1. With mingw-get, install msys1 and mingw
>
>2. Start msys1
>
>3. Run the winsetup script
>
>4. Run autogen
>
>5. Run mkwin ..
Looks right.
[quoted lines by Rob Hudson on 2023/10/12 at 20:58 -0500]
>/usr/lib/systemd/system/brltty.path
>/usr/lib/systemd/system/brltty@.path
But you said you used the unit name brltty@path.service. That name doesn't make
sense. Check README.Systemd for the details.
Are you using /etc/brltty.conf? If
[quoted lines by Lars Bjørndal on 2023/10/11 at 08:28 +0200]
>When I run brltty, I get BRLTTY.exe: Cannot open //etc/brltty.conf.
>
>Isn't the path wrong here, starting with two slashes?
No, because brltty for Windows is built using MinGW which recognizes the
slashes.
--
I believe the Bible
[quoted lines by Aura Kelloniemi on 2023/08/18 at 19:22 +0300]
>Does anybody know about the details of the bluetooth protocol used by Focus
>Blue 5th gen? Dave? Is it possible that different hosts should connect to a
>different bluetooth channel?
I'm sorry for answering so late. Been away (in
[quoted lines by Lars Bjørndal on 2023/10/13 at 20:38 +0200]
>I've recently upgraded my Windows box from Win 10 to Win 11.
I only have Windows 10 here. I'd appreciate it very much if those with Windows
11 could please try to figure out which problems it introduces and ways to deal
with them.
[Dave]
> [quoted lines by Lars Bjørndal on 2023/10/11 at 08:28 +0200]
>
> >When I run brltty, I get BRLTTY.exe: Cannot open //etc/brltty.conf.
> >
> >Isn't the path wrong here, starting with two slashes?
>
> No, because brltty for Windows is built using MinGW which recognizes the
> slashes.
Hi,
> >Does anybody know about the details of the bluetooth protocol used by Focus
> >Blue 5th gen? Dave? Is it possible that different hosts should connect to a
> >different bluetooth channel?
> I'm sorry for answering so late. Been away (in the hospital, actually) for
> a while.
Oh,
[quoted lines by Aura Kelloniemi on 2023/10/13 at 21:52 +0300]
>Oh, that sounds tough. I wish you feel better now.
Yes, but there's a way to go.
>This seems to fix the issue. Now I'm able to connect to Focus Blue with two
>devices simultaneously. Thank you!
Thanks. The change has now been
On 2023-10-13 at 16:06 -0400, Dave Mielke wrote:
> [quoted lines by Aura Kelloniemi on 2023/10/13 at 21:52 +0300]
> >This seems to fix the issue. Now I'm able to connect to Focus Blue with two
> >devices simultaneously. Thank you!
> Thanks. The change has now been committed and will be in
Yeah, brltty.path did it.
- Original Message -
From: Dave Mielke
To: "Informal discussion between users and developers of BRLTTY."
Date: Fri, 13 Oct 2023 05:27:23 -0400
Subject: Re: [BRLTTY] Restarting brltty via .path service
> [quoted lines by Rob Hudson on 2023/10/12 at 20:58
Hi Dave and Mario: This journey seems to get a bit stranger as I dig
into the problem. I did as both of you suggested and in the end used
both the inpkts and brlkeys arguments to the -l flag. I'm afraid I
couldn't make much sense out of the inpkts data because I don't
understand the format. In
[quoted lines by Kirk Reiser on 2023/10/13 at 10:05 -0400]
Do you happen to know (perhaps from the manual) if the keyboard emulates a PC
HID keyboard? If so, it mightn't be sending data that brltty can see.
>Here is the combined log from my last experimentation if you folks
>might be kind
[quoted lines by Aura Kelloniemi on 2023/10/14 at 00:13 +0300]
>Would you mind explaining what the issue was? As I Said, I'm not very familiar
>with bluetooth, and would like to understand this issue in case I encounter
>something similar in the future.
The layer of Bluetooth that we're using is
14 matches
Mail list logo