Re: [orca-list] Possible to improve continuous read in VSCode?

[Nolan Darilek <nolan thewordnerd info>]

Nice, works beautifully. Thanks, VSCode is inching ever closer to being 
my goto text/development environment.


On 5/20/20 10:53 AM, Joanmarie Diggs wrote:
> Ok, I believe I've fixed the issue with SayAll by line repeating the 
> editor information. The sentence stuff will have to wait for later 
> versions of Electron.
>
> --joanie
>
>
> On 5/20/20 11:30, Joanmarie Diggs wrote:
> > Sentence boundaries used to be broken in Chromium. 
> > https://bugs.chromium.org/p/chromium/issues/detail?id=1000049
> >
> > I can reproduce the problem with the editor name being re-presented 
> > using Insiders, so I'll see about fixing that.
> >
> > Thanks!
> > --joanie
> >
> >
> > On 5/20/20 10:52, Nolan Darilek wrote:
> > > I know, old version of Electron, etc. Hard to know whether this has 
> > > since been fixed in Chromium and will be a non-issue in a few 
> > > months, or if it slipped beneath the radar.
> > >
> > >
> > > I like how VSCode restores previous sessions, along with positions 
> > > in files. I started experimenting with it as a way to read 
> > > text-based technical documents converted with pdftotext, since that 
> > > makes a mess of the formatting. The idea is that, if I want better 
> > > insight into a piece of code, I can copy it straight into another 
> > > tab and have it automatically formatted on paste. I can also run it 
> > > directly using extensions.
> > >
> > >
> > > I notice that continuous read in the editor doesn't quite work. It 
> > > works well enough once it starts, but it often jumps far up in the 
> > > text, then starts reading from that point. I have Orca set to read 
> > > by sentences, and it jumps further up than the previous sentence 
> > > boundary. It does continue reading normally, though.
> > >
> > >
> > > I've also set it to read by line. In this case it works better in 
> > > that it doesn't jump, but it speaks the name of the editor between 
> > > each line.
> > >
> > >
> > > To reproduce:
> > >
> > >
> > > 1. Open VSCode. (I've only tested with latest stable, not Insiders, 
> > > though I have no reason to think Insiders would behave differently.)
> > >
> > > 2. Open a long text document in the editor.
> > >
> > > 3. Focus on the editor and switch to Focus mode.
> > >
> > > 4. Arrow to a position lower down in the text and start 
> > > continuous-read.
> > >
> > > 5. For me, reading begins far above the cursor if Sentence mode is 
> > > used. It begins on the same line as the cursor when Line mode is 
> > > active, but the filename followed by "editor" is spoken between each 
> > > line.
> > >
> > >
> > > Thanks a bunch.
> > >
> > > _______________________________________________
> > > orca-list mailing list
> > > orca-list gnome org
> > > https://mail.gnome.org/mailman/listinfo/orca-list
> > > Orca wiki: https://wiki.gnome.org/Projects/Orca
> > > Orca documentation: https://help.gnome.org/users/orca/stable/
> > > GNOME Universal Access guide: 
> > > https://help.gnome.org/users/gnome-help/stable/a11y.html
> >
> > _______________________________________________
> > orca-list mailing list
> > orca-list gnome org
> > https://mail.gnome.org/mailman/listinfo/orca-list
> > Orca wiki: https://wiki.gnome.org/Projects/Orca
> > Orca documentation: https://help.gnome.org/users/orca/stable/
> > GNOME Universal Access guide: 
> > https://help.gnome.org/users/gnome-help/stable/a11y.html