Date   

Re: More flexible line length in browsing mode

Gene
 

Its an interesting question and one I haven't thought about.  I find it a good idea to allow the maximum line length to be changed but is there a technical reason it is better to set a maximum length in the browse mode buffer than have the length determined by the screen width, as is the case in the presentation of the underlying HTML page?


Gene

On 11/24/2021 3:36 AM, Steve Nutt wrote:

I don't quite get why we need a line length mode anyway.

It would be good if NVDA could honour the lines on the screen, even in the virtual buffer.

I like the screen layout support, where links appear where they should, so why not make this work for formatting as well?

All the best

Steve

--
To subscribe to our News and Special Offers list, go to https://www.comproom.co.uk/subscribe

Computer Room Services
77 Exeter Close
Stevenage
Hertfordshire
SG1 4PW
T: +44(0)1438-742286
M: +44(0)7956-334938
F: +44(0)1438-759589
E: steve@...
W: https://www.comproom.co.uk

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Martin J. Dürst
Sent: 24 November 2021 08:25
To: nvda@nvda.groups.io
Subject: Re: [nvda] More flexible line length in browsing mode

Hello Gene,

Many thanks for your mail. We want to try and find out whether there is a difference between various ways of reading text (fixed one-hundred characters or somewhat more flexible). Of course, if there's a link, and NVDA is set to read that separately, I guess we will read that separately.

Regards, Martin.

On 2021-11-21 11:20, Gene via groups.io wrote:
In browse mode, you can set the line length. The default is one-hundred carachters. I suppose it would be possible to have a read by sentence option but I don’t know if there is any .demand for that. And it would conflict with sentences in which there are links and you have NVDA set to read every link on its own line.

Gene
-----Original Message-----
From: Tony Malykh
Sent: Saturday, November 20, 2021 7:43 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] More flexible line length in browsing mode

I believe in browse mode lines are defined visually, I don't recall
NVDA setting that would define line length.

If you would like to read by sentences, you can install my SentenceNav
add-on.

HTH

--Tony

On 11/18/2021 11:07 PM, Martin J. Dürst wrote:
Hello everybody,

I have been using NVDA on and off for a few weeks. It's really a
great help. I'm new to this mailing list, so please forgive me if I'm
asking something old.

When reading text from a Web page, the text is read in "lines", and
the user presses arrow-down for each line. NVDA has a setting for
line length, which is at 100 characters originally. So well, so good.

What I find somewhat confusing, and possibly a place for improvement,
is that often a "line" ends a word or two before the end of a
sentence, or includes a word or two of a new sentence. I suspect that
quit a bit of thought must have gone into this, but I haven't found
any details yet.

I would really appreciate if somebody could explain why "lines" end
at arbitrary positions in sentences, and are not done a bit more
flexibly so that they more often end at the end of a sentence.

If this has been discussed already, I would appreciate pointers. Also
if there's some scientific paper about the issue.

I have tried to think about why things are as described above, and
have come up with various possible reasons. If any of these reasons
applies, please just tell me.

- There is already a setting/add-on for this, just use it.

- Having more variable line lengths would make it more difficult to read
Web pages (e.g. because the intervals between the presses of the down
arrow would be more irregular). If that's the case, then I haven't yet
had enough practice to notice it.

- Finding better positions to split text into lines is a much harder
problem than it looks. It is difficult to find actual sentence
boundaries in text (not all periods are sentence endings), and
long sentences without punctuation are also difficult to split.

- Finding better positions to split is possible, but good algorithms
are too slow. Text-to-speech conversion already uses quite a bit
of processing power.

- Finding sentence boundaries is quit language dependent, and therefore
difficult to implement in a general way.

- The overall architecture of NVDA (and other screen readers) makes
it too difficult to implement such a feature.

- Some other screen readers already do a better job at this, but we
at NVDA just have not had time to get around to do something here.
Help is appreciated. (I might want to help.)

- That's how screen readers always have done it, and everybody is
used to it, and so changing it isn't a good idea.

If there are any other actual or potential reasons, please tell me.

Many thanks in advance for your help.

With kind regards, Martin.











--
Prof. Dr.sc. Martin J. Dürst
Department of Intelligent Information Technology College of Science and Engineering Aoyama Gakuin University Fuchinobe 5-1-10, Chuo-ku, Sagamihara
252-5258 Japan











Re: More flexible line length in browsing mode

Steve Nutt
 

I don't quite get why we need a line length mode anyway.

It would be good if NVDA could honour the lines on the screen, even in the virtual buffer.

I like the screen layout support, where links appear where they should, so why not make this work for formatting as well?

All the best

Steve

--
To subscribe to our News and Special Offers list, go to https://www.comproom.co.uk/subscribe

Computer Room Services
77 Exeter Close
Stevenage
Hertfordshire
SG1 4PW
T: +44(0)1438-742286
M: +44(0)7956-334938
F: +44(0)1438-759589
E: steve@...
W: https://www.comproom.co.uk

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Martin J. Dürst
Sent: 24 November 2021 08:25
To: nvda@nvda.groups.io
Subject: Re: [nvda] More flexible line length in browsing mode

Hello Gene,

Many thanks for your mail. We want to try and find out whether there is a difference between various ways of reading text (fixed one-hundred characters or somewhat more flexible). Of course, if there's a link, and NVDA is set to read that separately, I guess we will read that separately.

Regards, Martin.

On 2021-11-21 11:20, Gene via groups.io wrote:
In browse mode, you can set the line length. The default is one-hundred carachters. I suppose it would be possible to have a read by sentence option but I don’t know if there is any .demand for that. And it would conflict with sentences in which there are links and you have NVDA set to read every link on its own line.

Gene
-----Original Message-----
From: Tony Malykh
Sent: Saturday, November 20, 2021 7:43 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] More flexible line length in browsing mode

I believe in browse mode lines are defined visually, I don't recall
NVDA setting that would define line length.

If you would like to read by sentences, you can install my SentenceNav
add-on.

HTH

--Tony

On 11/18/2021 11:07 PM, Martin J. Dürst wrote:
Hello everybody,

I have been using NVDA on and off for a few weeks. It's really a
great help. I'm new to this mailing list, so please forgive me if I'm
asking something old.

When reading text from a Web page, the text is read in "lines", and
the user presses arrow-down for each line. NVDA has a setting for
line length, which is at 100 characters originally. So well, so good.

What I find somewhat confusing, and possibly a place for improvement,
is that often a "line" ends a word or two before the end of a
sentence, or includes a word or two of a new sentence. I suspect that
quit a bit of thought must have gone into this, but I haven't found
any details yet.

I would really appreciate if somebody could explain why "lines" end
at arbitrary positions in sentences, and are not done a bit more
flexibly so that they more often end at the end of a sentence.

If this has been discussed already, I would appreciate pointers. Also
if there's some scientific paper about the issue.

I have tried to think about why things are as described above, and
have come up with various possible reasons. If any of these reasons
applies, please just tell me.

- There is already a setting/add-on for this, just use it.

- Having more variable line lengths would make it more difficult to read
Web pages (e.g. because the intervals between the presses of the down
arrow would be more irregular). If that's the case, then I haven't yet
had enough practice to notice it.

- Finding better positions to split text into lines is a much harder
problem than it looks. It is difficult to find actual sentence
boundaries in text (not all periods are sentence endings), and
long sentences without punctuation are also difficult to split.

- Finding better positions to split is possible, but good algorithms
are too slow. Text-to-speech conversion already uses quite a bit
of processing power.

- Finding sentence boundaries is quit language dependent, and therefore
difficult to implement in a general way.

- The overall architecture of NVDA (and other screen readers) makes
it too difficult to implement such a feature.

- Some other screen readers already do a better job at this, but we
at NVDA just have not had time to get around to do something here.
Help is appreciated. (I might want to help.)

- That's how screen readers always have done it, and everybody is
used to it, and so changing it isn't a good idea.

If there are any other actual or potential reasons, please tell me.

Many thanks in advance for your help.

With kind regards, Martin.












--
Prof. Dr.sc. Martin J. Dürst
Department of Intelligent Information Technology College of Science and Engineering Aoyama Gakuin University Fuchinobe 5-1-10, Chuo-ku, Sagamihara
252-5258 Japan


Re: More flexible line length in browsing mode

Martin J. Dürst <duerst@...>
 

Hello Quentin,

Many thanks for your reply. Creating an issue is a good idea, but we first want to try to implement and test it ourselves. We will look at Tony's SentenceNav add-on for some ideas on implementation.

Also, if you can give us a pointer on where the code for breaking text into lines of equal length is, that would be fine. If there is another list for such questions, please just tell us.

Regards, Martin.

On 2021-11-22 15:38, Quentin Christensen via groups.io wrote:
As Gene noted, the line length in NVDA is a simple number - and it doesn't
look to see if it can "just add the last word of a sentence". I can see
that it might be advantageous though, I would suggest the best thing to do
is create an issue on our tracker at:
https://github.com/nvaccess/nvda/issues requesting the feature.
Kind regards
Quentin.
On Sun, Nov 21, 2021 at 1:20 PM Gene <gsasner@...> wrote:

In browse mode, you can set the line length. The default is one-hundred
carachters. I suppose it would be possible to have a read by sentence
option but I don’t know if there is any .demand for that. And it would
conflict with sentences in which there are links and you have NVDA set to
read every link on its own line.

Gene
-----Original Message-----
*From:* Tony Malykh <anton.malykh@...>
*Sent:* Saturday, November 20, 2021 7:43 PM
*To:* nvda@nvda.groups.io
*Subject:* Re: [nvda] More flexible line length in browsing mode

I believe in browse mode lines are defined visually, I don't recall NVDA
setting that would define line length.

If you would like to read by sentences, you can install my SentenceNav
add-on.

HTH

--Tony

On 11/18/2021 11:07 PM, Martin J. Dürst wrote:
Hello everybody,

I have been using NVDA on and off for a few weeks. It's really a great
help. I'm new to this mailing list, so please forgive me if I'm asking
something old.

When reading text from a Web page, the text is read in "lines", and
the user presses arrow-down for each line. NVDA has a setting for line
length, which is at 100 characters originally. So well, so good.

What I find somewhat confusing, and possibly a place for improvement,
is that often a "line" ends a word or two before the end of a
sentence, or includes a word or two of a new sentence. I suspect that
quit a bit of thought must have gone into this, but I haven't found
any details yet.

I would really appreciate if somebody could explain why "lines" end at
arbitrary positions in sentences, and are not done a bit more flexibly
so that they more often end at the end of a sentence.

If this has been discussed already, I would appreciate pointers. Also
if there's some scientific paper about the issue.

I have tried to think about why things are as described above, and
have come up with various possible reasons. If any of these reasons
applies, please just tell me.

- There is already a setting/add-on for this, just use it.

- Having more variable line lengths would make it more difficult to read
Web pages (e.g. because the intervals between the presses of the down
arrow would be more irregular). If that's the case, then I haven't yet
had enough practice to notice it.

- Finding better positions to split text into lines is a much harder
problem than it looks. It is difficult to find actual sentence
boundaries in text (not all periods are sentence endings), and
long sentences without punctuation are also difficult to split.

- Finding better positions to split is possible, but good algorithms
are too slow. Text-to-speech conversion already uses quite a bit
of processing power.

- Finding sentence boundaries is quit language dependent, and therefore
difficult to implement in a general way.

- The overall architecture of NVDA (and other screen readers) makes
it too difficult to implement such a feature.

- Some other screen readers already do a better job at this, but we
at NVDA just have not had time to get around to do something here.
Help is appreciated. (I might want to help.)

- That's how screen readers always have done it, and everybody is
used to it, and so changing it isn't a good idea.

If there are any other actual or potential reasons, please tell me.

Many thanks in advance for your help.

With kind regards, Martin.









--
Prof. Dr.sc. Martin J. Dürst
Department of Intelligent Information Technology
College of Science and Engineering
Aoyama Gakuin University
Fuchinobe 5-1-10, Chuo-ku, Sagamihara
252-5258 Japan


Re: More flexible line length in browsing mode

Martin J. Dürst <duerst@...>
 

Hello Gene,

Many thanks for your mail. We want to try and find out whether there is a difference between various ways of reading text (fixed one-hundred characters or somewhat more flexible). Of course, if there's a link, and NVDA is set to read that separately, I guess we will read that separately.

Regards, Martin.

On 2021-11-21 11:20, Gene via groups.io wrote:
In browse mode, you can set the line length. The default is one-hundred carachters. I suppose it would be possible to have a read by sentence option but I don’t know if there is any .demand for that. And it would conflict with sentences in which there are links and you have NVDA set to read every link on its own line.
Gene
-----Original Message-----
From: Tony Malykh
Sent: Saturday, November 20, 2021 7:43 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] More flexible line length in browsing mode
I believe in browse mode lines are defined visually, I don't recall NVDA
setting that would define line length.
If you would like to read by sentences, you can install my SentenceNav
add-on.
HTH
--Tony
On 11/18/2021 11:07 PM, Martin J. Dürst wrote:
Hello everybody,

I have been using NVDA on and off for a few weeks. It's really a great
help. I'm new to this mailing list, so please forgive me if I'm asking
something old.

When reading text from a Web page, the text is read in "lines", and
the user presses arrow-down for each line. NVDA has a setting for line
length, which is at 100 characters originally. So well, so good.

What I find somewhat confusing, and possibly a place for improvement,
is that often a "line" ends a word or two before the end of a
sentence, or includes a word or two of a new sentence. I suspect that
quit a bit of thought must have gone into this, but I haven't found
any details yet.

I would really appreciate if somebody could explain why "lines" end at
arbitrary positions in sentences, and are not done a bit more flexibly
so that they more often end at the end of a sentence.

If this has been discussed already, I would appreciate pointers. Also
if there's some scientific paper about the issue.

I have tried to think about why things are as described above, and
have come up with various possible reasons. If any of these reasons
applies, please just tell me.

- There is already a setting/add-on for this, just use it.

- Having more variable line lengths would make it more difficult to read
Web pages (e.g. because the intervals between the presses of the down
arrow would be more irregular). If that's the case, then I haven't yet
had enough practice to notice it.

- Finding better positions to split text into lines is a much harder
problem than it looks. It is difficult to find actual sentence
boundaries in text (not all periods are sentence endings), and
long sentences without punctuation are also difficult to split.

- Finding better positions to split is possible, but good algorithms
are too slow. Text-to-speech conversion already uses quite a bit
of processing power.

- Finding sentence boundaries is quit language dependent, and therefore
difficult to implement in a general way.

- The overall architecture of NVDA (and other screen readers) makes
it too difficult to implement such a feature.

- Some other screen readers already do a better job at this, but we
at NVDA just have not had time to get around to do something here.
Help is appreciated. (I might want to help.)

- That's how screen readers always have done it, and everybody is
used to it, and so changing it isn't a good idea.

If there are any other actual or potential reasons, please tell me.

Many thanks in advance for your help.

With kind regards, Martin.




--
Prof. Dr.sc. Martin J. Dürst
Department of Intelligent Information Technology
College of Science and Engineering
Aoyama Gakuin University
Fuchinobe 5-1-10, Chuo-ku, Sagamihara
252-5258 Japan


Re: More flexible line length in browsing mode

Martin J. Dürst <duerst@...>
 

Hello Tony,

Sorry to be late with my answer. We will definitely look at your SentenceNav add-on.

Regards, Martin.

On 2021-11-21 10:43, Tony Malykh via groups.io wrote:
I believe in browse mode lines are defined visually, I don't recall NVDA setting that would define line length.
If you would like to read by sentences, you can install my SentenceNav add-on.
HTH
--Tony
On 11/18/2021 11:07 PM, Martin J. Dürst wrote:
Hello everybody,

I have been using NVDA on and off for a few weeks. It's really a great help. I'm new to this mailing list, so please forgive me if I'm asking something old.

When reading text from a Web page, the text is read in "lines", and the user presses arrow-down for each line. NVDA has a setting for line length, which is at 100 characters originally. So well, so good.

What I find somewhat confusing, and possibly a place for improvement, is that often a "line" ends a word or two before the end of a sentence, or includes a word or two of a new sentence. I suspect that quit a bit of thought must have gone into this, but I haven't found any details yet.

I would really appreciate if somebody could explain why "lines" end at arbitrary positions in sentences, and are not done a bit more flexibly so that they more often end at the end of a sentence.

If this has been discussed already, I would appreciate pointers. Also if there's some scientific paper about the issue.

I have tried to think about why things are as described above, and have come up with various possible reasons. If any of these reasons applies, please just tell me.

- There is already a setting/add-on for this, just use it.

- Having more variable line lengths would make it more difficult to read
  Web pages (e.g. because the intervals between the presses of the down
  arrow would be more irregular). If that's the case, then I haven't yet
  had enough practice to notice it.

- Finding better positions to split text into lines is a much harder
  problem than it looks. It is difficult to find actual sentence
  boundaries in text (not all periods are sentence endings), and
  long sentences without punctuation are also difficult to split.

- Finding better positions to split is possible, but good algorithms
  are too slow. Text-to-speech conversion already uses quite a bit
  of processing power.

- Finding sentence boundaries is quit language dependent, and therefore
  difficult to implement in a general way.

- The overall architecture of NVDA (and other screen readers) makes
  it too difficult to implement such a feature.

- Some other screen readers already do a better job at this, but we
  at NVDA just have not had time to get around to do something here.
  Help is appreciated. (I might want to help.)

- That's how screen readers always have done it, and everybody is
  used to it, and so changing it isn't a good idea.

If there are any other actual or potential reasons, please tell me.

Many thanks in advance for your help.

With kind regards,   Martin.




.
--
Prof. Dr.sc. Martin J. Dürst
Department of Intelligent Information Technology
College of Science and Engineering
Aoyama Gakuin University
Fuchinobe 5-1-10, Chuo-ku, Sagamihara
252-5258 Japan


Re: anyone noticed this

 

Hmmm yeahh it worked after another restart.

Sometimes after updating some sounds and stuff don't work till I reboot a second time.



On 24/11/2021 4:40 pm, Quentin Christensen wrote:
I just had a look on mine - Windows 10 (64-bit) Version: 21H2 (2009), Build: 19044.1348 and collapsing items on the start menu leaves the focus on the collapsed item, as expected.

With the symbol grouping - could it be your punctuation level?  Mine is called "#" and that does read as "Number grouping" at some, most and all, but if you have your punctuation level set to "none" it just reads "Grouping".

Quentin.

On Tue, Nov 23, 2021 at 5:29 PM Shaun Everiss <sm.everiss@...> wrote:

This is windows 10 I thought I put 10 in the message somewhere.



On 23/11/2021 7:22 pm, Arlene wrote:

Hi, Is this windows ten or 11?

 

Sent from Mail for Windows

 

From: Shaun Everiss
Sent: November 22, 2021 9:43 PM
To: nvda@nvda.groups.io
Subject: [nvda] anyone noticed this

 

Hi.

 

Well

 

Just got the latest windows build

 

21.2 19.441387 build released today.

 

This had the windows installer fix.

 

I have however noticed a small issue which isn't an issue as such

because I can get round it easy enough.

 

Its just when I select the first item in the start menu ie hitting down

arrow from search I get all apps, then you get the programs starting

with punctuation like & or *, etc well that group does not read but the

items in it do and can be executed.

 

When colapsing a group it seems I get jumpped back to the top of the

list as well.

 

Again not a real big huge issue since I mostly search anyway but just

wandered if anyone has noticed.

 

I have not had any other issues in fact things seem a bit more stable,

but we will see what happens after I do some more shell work.

 

 

 

 

 

 

 

 



--
Quentin Christensen
Training and Support Manager


Re: anyone noticed this

Quentin Christensen
 

I just had a look on mine - Windows 10 (64-bit) Version: 21H2 (2009), Build: 19044.1348 and collapsing items on the start menu leaves the focus on the collapsed item, as expected.

With the symbol grouping - could it be your punctuation level?  Mine is called "#" and that does read as "Number grouping" at some, most and all, but if you have your punctuation level set to "none" it just reads "Grouping".

Quentin.

On Tue, Nov 23, 2021 at 5:29 PM Shaun Everiss <sm.everiss@...> wrote:

This is windows 10 I thought I put 10 in the message somewhere.



On 23/11/2021 7:22 pm, Arlene wrote:

Hi, Is this windows ten or 11?

 

Sent from Mail for Windows

 

From: Shaun Everiss
Sent: November 22, 2021 9:43 PM
To: nvda@nvda.groups.io
Subject: [nvda] anyone noticed this

 

Hi.

 

Well

 

Just got the latest windows build

 

21.2 19.441387 build released today.

 

This had the windows installer fix.

 

I have however noticed a small issue which isn't an issue as such

because I can get round it easy enough.

 

Its just when I select the first item in the start menu ie hitting down

arrow from search I get all apps, then you get the programs starting

with punctuation like & or *, etc well that group does not read but the

items in it do and can be executed.

 

When colapsing a group it seems I get jumpped back to the top of the

list as well.

 

Again not a real big huge issue since I mostly search anyway but just

wandered if anyone has noticed.

 

I have not had any other issues in fact things seem a bit more stable,

but we will see what happens after I do some more shell work.

 

 

 

 

 

 

 

 



--
Quentin Christensen
Training and Support Manager


Re: Rearrange Pinned Items

 

For rearranging pinned items on the taskbar I really recommend using the mouse with left click and drag even if you cannot see, after you've routed the mouse to the screen reader object.  Though things can be dragged in to the taskbar from the desktop to create a pinned item, the reverse is not true.  Pinned items in the taskbar can only be removed or moved left and right relative to each other.

Though you may have to give it a couple of tries to get a sense of how far your mouse moves in the taskbar relative to how far you've moved it left/right with the left mouse button held, you can safely practice moving these icons around, checking their order, and lather, rinse, repeat until you've got the order you want.

Though drag and drop with unconstrained 4-directional movement and movement in and out of windows with focus is an absolute nightmare for a blind user, bidirectional constrained movement within something like the taskbar is significantly easier and practice does make perfect, or something near to it.

This is one of those rare times when actually using the mouse fully as intended works because of exactly what you're trying to do and the inability to drag something out of the taskbar.  But it does take some playing around, as mouse movement speed and the like can vary from computer to computer.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 


Re: accessible way of moving playlists to folders in spotify?

Gene
 

I only played with the attachment a little bit but I’m not sure it does anything more than the method for dragging and dropping already available in NVDA. 
 
Gene

-----Original Message-----
Sent: Tuesday, November 23, 2021 2:18 PM
Subject: Re: [nvda] accessible way of moving playlists to folders in spotify?
 

Yeah seems to have a nightmare with object navigation. At times I get an object has no location when using the review cursor and navigator to find the correct playlist.

On 23/11/2021 20:00, Sarah k Alawami wrote:

Since it is electron I doubt it will work. I have not had any luck using this add on for dragging dropping  stuff, at all. Not to say it does not work, but for me it has worked maybe 1 time out of the 10 or so I’ve used it.

 

From: nvda@nvda.groups.io mailto:nvda@nvda.groups.io On Behalf Of Orhan Deniz via groups.io
Sent: Tuesday, November 23, 2021 11:46 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] accessible way of moving playlists to folders in spotify?

 

It seems that when I try to mark a playlist, then drop it into the relevant folder I get a can't drop here error. I am not sure if this add on will work with spotify playlists, but I will give it more of a road-test.

On 23/11/2021 19:39, Brian Vogel wrote:

Orhan,

Just FYI, this add-on is compatible with 2021.3 and, in addition, does have help/usage information packaged with it that you can access via gaining focus the add-on in Add-Ons Manager (NVDA + N, T, A, Enter) then activating the Add-On Help button.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043 

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 


Re: accessible way of moving playlists to folders in spotify?

Orhan Deniz
 

Yeah seems to have a nightmare with object navigation. At times I get an object has no location when using the review cursor and navigator to find the correct playlist.

On 23/11/2021 20:00, Sarah k Alawami wrote:

Since it is electron I doubt it will work. I have not had any luck using this add on for dragging dropping  stuff, at all. Not to say it does not work, but for me it has worked maybe 1 time out of the 10 or so I’ve used it.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Orhan Deniz via groups.io
Sent: Tuesday, November 23, 2021 11:46 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] accessible way of moving playlists to folders in spotify?

 

It seems that when I try to mark a playlist, then drop it into the relevant folder I get a can't drop here error. I am not sure if this add on will work with spotify playlists, but I will give it more of a road-test.

On 23/11/2021 19:39, Brian Vogel wrote:

Orhan,

Just FYI, this add-on is compatible with 2021.3 and, in addition, does have help/usage information packaged with it that you can access via gaining focus the add-on in Add-Ons Manager (NVDA + N, T, A, Enter) then activating the Add-On Help button.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 


Re: accessible way of moving playlists to folders in spotify?

Sarah k Alawami
 

Since it is electron I doubt it will work. I have not had any luck using this add on for dragging dropping  stuff, at all. Not to say it does not work, but for me it has worked maybe 1 time out of the 10 or so I’ve used it.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Orhan Deniz via groups.io
Sent: Tuesday, November 23, 2021 11:46 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] accessible way of moving playlists to folders in spotify?

 

It seems that when I try to mark a playlist, then drop it into the relevant folder I get a can't drop here error. I am not sure if this add on will work with spotify playlists, but I will give it more of a road-test.

On 23/11/2021 19:39, Brian Vogel wrote:

Orhan,

Just FYI, this add-on is compatible with 2021.3 and, in addition, does have help/usage information packaged with it that you can access via gaining focus the add-on in Add-Ons Manager (NVDA + N, T, A, Enter) then activating the Add-On Help button.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 


Re: Rearrange Pinned Items

Sarah k Alawami
 

The drag and drop add on actually does not help. Most of the time my curser is not above like it shows. I verify this with the keys that the add on gives.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Rowen Cary
Sent: Monday, November 22, 2021 5:55 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Rearrange Pinned Items

 

Hi, Drag and drop add-ons may also help.

Cheers


Re: accessible way of moving playlists to folders in spotify?

 

With any luck someone else who uses the add-on, Spotify, or both will chime in.  I've never touched Spotify, so I'm a dead end there.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 


Re: accessible way of moving playlists to folders in spotify?

Orhan Deniz
 

It seems that when I try to mark a playlist, then drop it into the relevant folder I get a can't drop here error. I am not sure if this add on will work with spotify playlists, but I will give it more of a road-test.

On 23/11/2021 19:39, Brian Vogel wrote:
Orhan,

Just FYI, this add-on is compatible with 2021.3 and, in addition, does have help/usage information packaged with it that you can access via gaining focus the add-on in Add-Ons Manager (NVDA + N, T, A, Enter) then activating the Add-On Help button.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 


Re: accessible way of moving playlists to folders in spotify?

 

Orhan,

Just FYI, this add-on is compatible with 2021.3 and, in addition, does have help/usage information packaged with it that you can access via gaining focus the add-on in Add-Ons Manager (NVDA + N, T, A, Enter) then activating the Add-On Help button.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 


Re: accessible way of moving playlists to folders in spotify?

Orhan Deniz
 

I shall try that then and report back.

On 23/11/2021 19:30, Brian Vogel wrote:
Orhan,

I mentioned the following just last night in a topic about Rearranging Task Bar Items, but since you weren't a member then, you would not have seen it.

Javi Dominguez has written an add-on for Drag and Drop, which others have said is very helpful.  And by that I mean helpful in achieving actual drag and drop regardless of the context.  It would be worth a try.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 


Re: accessible way of moving playlists to folders in spotify?

 

Orhan,

I mentioned the following just last night in a topic about Rearranging Task Bar Items, but since you weren't a member then, you would not have seen it.

Javi Dominguez has written an add-on for Drag and Drop, which others have said is very helpful.  And by that I mean helpful in achieving actual drag and drop regardless of the context.  It would be worth a try.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The ignorance of one voter in a democracy impairs the security of all.

         ~ John F. Kennedy

 


accessible way of moving playlists to folders in spotify?

Orhan Deniz
 

Hello there,

I'm aware that drag+drop in browse mode rarely works. Has anyone however found a way to move playlists to designated folders in spotify? As a bit of a dj its important for me to have stuff filed properly and currently what I have to do is create a new playlist in the folder, copy the old playlist, then delete it. Needless to say this is cumbersome when in theory I should be able to just move them. But of course, cut+paste commands only work within playlists, not to move playlists to folders.


Best,

Orhan.


Re: Is the Windows 10 (and, I'd presume, 11) Sandbox Feature Accessible?

 

Hi,

Regarding keyboard shortcuts, it will feel like logging onto a Remote Desktop session - you would press Control+Alt+Break (Pause) key to switch between host (the computer you are using) and guest (sandboxed environment). The way I run NVDA (or for that matter, any screen reader other than Narrator) inside Windows Sandbox is:

  1. On the host computer, prepare the screen reader files - NVDA installer or a portable copy of NVDA.
  2. Copy the screen reader file(s) to the clipboard.
  3. Go to Windows Sandbox and switch to the guest environment.
  4. Open a folder location (say, Documents). The easiest way is typing the name of the folder from Run dialog.
  5. When the desired folder opens in the guest environment, paste the just copied scren reader file(s).
  6. Because it will take time for files to be copied (especially if you are copying a folder containing portable NVDA files), switch out of sandboxed environment, then use Windows OCR (NVDA+R) to recognize what Windows Sandbox is displaying.
  7. Once the copy operation is complete, switch back to the sandboxed environment, locate NVDA executable and run it.

You can also do all these with Narrator on - just before opening the folder in the guest environment (just after performing step 3), press Control+Windows+Enter while switched to the guest environment to start Narrator inside the sandbox. When NVDA starts, close Narrator.

I belive Windows Sandbox was covered somewhat on WinAccess forum (may need to check the archive for that one).

Cheers,

Joseph


Re: Assistance with how to use NVDA remote

Fawaz Abdul rahman
 

hi,
What are you confused about?

On Tue, Nov 23, 2021 at 6:14 PM aidan gamble <aidan.touchstone@...> wrote:
Hello, please may anyone assist me with using NVDA remote function?  I have read the user guide and I am still confused. Thank you





6901 - 6920 of 96786