Re: [BRLTTY] Handytech Active Braille

Vincent LE GOFF writes: > I'm currently testing a Handytech Active Braille display and I'm now > trying to use BRLTTY with it.  Strangely enough, BRLTTY recognizes the > display at once and with no particular problem, Good. > but key mappings don't work at all as

Re: [BRLTTY] Music notation .bse???

Dave Mielke writes: > [quoted lines by Adrian van Bloois on 2017/11/17 at 22:48 +0100] > > You see a lot of Dot7s (which should be ignored or removed) because > strict BRF is being used. This is why we have the -6 option of brltty-trtxt. I usually clean up BRF Braille music by

Re: [BRLTTY] BrlAPI Raw key code mode?

Dave Mielke <d...@mielke.cc> writes: > [quoted lines by Mario Lang on 2017/07/28 at 10:14 +0200] > >>At least what I am seeing is, that no commands whatsoever arrive if I have >>selected "raw keycode" mode. Which makes sense, since you probably wouldn't >

Re: [BRLTTY] BrlAPI Raw key code mode?

Dave Mielke <d...@mielke.cc> writes: > [quoted lines by Mario Lang on 2017/07/28 at 09:03 +0200] > >>I would even go as far as dropping the exception for BRL_SWITCHVT and >>similar. >>After all, the client has just requested raw keycodes, they shou

Re: [BRLTTY] BrlAPI Raw key code mode?

Dave Mielke <d...@mielke.cc> writes: > [quoted lines by Mario Lang on 2017/07/27 at 21:17 +0200] > >>This did the trick: >> >> brlapi_range_t Ranges[1]; >> Ranges[0].first = 0; >> Ranges[0].last = 0X; >> brlapi__acceptKeyRanges

Re: [BRLTTY] BrlAPI Raw key code mode?

Shérab <sebastien.hinde...@ens-lyon.org> writes: > Mario Lang (2017/07/27 16:40 +0200): >> In fact, I know the core doesn't pass the keypresses on because some of >> the keys result in BRLTTY playing a sound, as if it were trying to read >> a screen.

Re: [BRLTTY] BrlAPI Raw key code mode?

Dave Mielke writes: >>Actually, it seems the HandyTech driver does not support delivering raw >>key codes yet. It should define the BRL_HAVE_KEY_CODES macro and >>implement the brl_readKey and brl_keyToCommand methods. > > That made sense way back in the days when bindings were

Re: [BRLTTY] BrlAPI Raw key code mode?

Shérab <sebastien.hinde...@ens-lyon.org> writes: > Mario Lang (2017/07/23 11:54 +0200): >> Oh!!! Thanks for reminding me. Indeed, now it dawns on me that there >> is this driver-specific translation mechanism... This sort of got lost >> in the noise (for me) si

Re: [BRLTTY] BrlAPI Raw key code mode?

Shérab <sebastien.hinde...@ens-lyon.org> writes: > Mario Lang (2017/07/23 00:12 +0200): >> Hi. >> >> Does anyone know if Raw keycode mode of BrlAPI does still work? Here, >> calling brlapi__readKey after brlapi__enterTtyMode with "HandyTech" as >>

[BRLTTY] BrlAPI Raw key code mode?

Hi. Does anyone know if Raw keycode mode of BrlAPI does still work? Here, calling brlapi__readKey after brlapi__enterTtyMode with "HandyTech" as the driver string seems to block forever, while "" as driver string gives me command keys as expected. I know the number of users of raw mode might be

Re: [BRLTTY] adding custom command to replace a braille window

Vikash Kesharwani writes: > Translation is not an issue. I am facing issue with cursor routing. It does > not work all the time. Can there be any particular reason for this. Is > cursor routing guaranteed to execute( I am using nano) or there is any >

Re: [BRLTTY] The launch of my crowd funding campaign on Patreon.

Luke Yelavich writes: > I am writing to let you all know of my newly launched crowd funding campaign > to continue to work full time on Linux accessibility development. Please > spread the word if you are able, it would be much appreciated. > >

Re: [BRLTTY] 5.5 will be released soon.

Dave Mielke writes: >>and are there some non translated strings in this future release? > > Mario should now be able to give you a good answer to this question since > he's > updated the German translations. The messages template is up-to-date. Please change to the Messages

Re: [BRLTTY] Testing on Windows

Samuel Thibault writes: > The source seems to be downloadable on > > https://3rdpartysource.microsoft.com/download/Redistributed%20OSS/5.4/brltty-5.4.zip > > It seems to correspond to git 8d46edbf16 + a cherry-pick of 738c1d8b76 > (which was submitted by microsoft

Re: [BRLTTY] Testing on Windows

. If anyone can figure out the URL of the actual download, that would be highly appreciated for analysis. > -Ursprüngliche Nachricht- > Von: BRLTTY [mailto:brltty-boun...@brltty.com] Im Auftrag von Mario Lang > Gesendet: Donnerstag, 6. April 2017 11:30 > An: 'Informal

Re: [BRLTTY] Testing on Windows

Felix Grützmacher - Help Tech Elektronik GmbH writes: > I just tested Easy Braille (ID 0x44) with the following result: > 2017-04-06@10:17:55.937 USB: testing device: vendor=1FE4 product=0044 > 2017-04-06@10:17:55.937 USB: setup packet: Typ:80 Req:06 Val:0300

Re: [BRLTTY] Testing on Windows

Felix Grützmacher - Handy Tech Elektronik GmbH writes: > Here is a log excerpt created from running as debug. Seems something went > wrong. Basically the exact same log was already submitted by you in July 2016. Dave analyzed it quite in detail in

Re: [BRLTTY] Testing on Windows

Felix Grützmacher - Help Tech Elektronik GmbH writes: > yes, this is an actual physical Active Braille it's talking to, with > standard firmware. I might be lying, but I believe Felix is the first person to test AB/AS models on Windows. At least I never did,

Re: [BRLTTY] braille star 40

Felix Grützmacher - Handy Tech Elektronik GmbH writes: > this might just be me stating the really obvious and making a fool of > myself, but since the FTDI chip emulates a serial connection through USB and > the FTDI driver takes care of that, wouldn't it make