Gene New Zealand <hurrikennyandopo@...>
hi I guess it depends what you want to do. Some people have found the golden cursor pretty good and for the sighted to see what is been focused on by nvda the focus highlighter add on is good. For me i use also the vlc add on for the vlc media player. Do you know where to look to locate teh addons in nvda. When nvda is running use the nvda key + the letter N. When it comes up arrow down to tools, then a sub menu will come off it. You will then need to go to manage add ons, then press the enter key. Under that section is a button called get add ons i think it is called. Press the enter key on it then the browser will open to the nvda add on web page. If you are interested i do have a written and audio tutorial on how to install them remove them etc along with a list of add ons, so far found at http://accessibilitycentral.net/NVDA%20addons.htmlThe link to this page if off my Accessibility Central.net website and is separate to the nvda community add on website. You may find some other information you might be interested in off the pages connected to this one on NVDA and also other blindness related material. hope this helps. Gene nz
toggle quoted messageShow quoted text
On 24/11/2016 8:41 AM, Don H wrote: Once again just getting started with NVDA after being a long term user of Window Eyes. I have NVDA installed on a Win 10 system. Primary uses are web surfing and Email. Have IE, Google Chrome and Firefox installed and use Thunderbird as my Email client. So now to the question, are there some must have addon's for best performance and other addon's that are otherwise suggested? Thanks
|
|
Re: Python internals, code reviews and use of variables: RE: [nvda] help menu
Hi, No need for this, as NVDA will check the path it needs to look up when you run it the first time. Cheers, Joseph
toggle quoted messageShow quoted text
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Gene Sent: Wednesday, November 23, 2016 11:43 AM To: nvda@nvda.groups.io Subject: Re: Python internals, code reviews and use of variables: RE: [nvda] help menu I'm not sure of this but wouldn't some sort of variable be necessary to accommodate those running NVDA as a portable program? The path and drive could vary enormously depending on where the portable version is being run from. ----- Original Message ----- Sent: Wednesday, November 23, 2016 1:26 PM Subject: Python internals, code reviews and use of variables: RE: [nvda] help menu Hi, It’s two different ways of accomplishing the same thing. Some would say using a variable is best for readability purposes (after all, Python community values readability above others), while majority of us would just encode the constant. Modern compilers will actually detect this and just put in the constant (which is way beyond the scope of this discussion). I usually prefer the second approach myself, knowing that this generates less Python bytecode instructions (for add-on code reviews, I sometimes overlook this, but in NVDA Core code review, this is considered important, mostly when it comes to coding style). The following is mostly meant for resident add-on writers but it might be helpful for users to hear this as a side note (and yes, I’ll revisit this subject on the add-ons list later): you can in fact disassemble Python bytecode. If you want to do under the hood optimizations for your add-on code, it is crucial to know some internals of Python interpreter and how instructions are fetched and executed. This applies to any Python code that has a source code or not – yes, we can disassemble add-on code where there is no source code and reconstruct what you were trying to do. This should not be an excuse for you to bring an add-on with no source code to my office for review – I and other reviewers will ask you to present a copy of your source code before initiating add-on code reviews. In case of my reviews, I would quickly look at your code, provide some feedback and that’ll be all; if you do request a more detailed review, I’ll look at translatable strings, documentation, GUI routines, and do compatibility/integration check with NVDA Core and provide feedback as though I’m reviewing a module for NVDA screen reader itself. Hope this helps. Cheers, Joseph Why would you put the path to the file in a variable? That path never would change, would it? So, wouldn't you therefore want it in a constant? --- Christopher Gilland JAWS Certified, 2016. Training Instructor. ----- Original Message ----- Sent: Wednesday, November 23, 2016 1:24 PM Subject: Re: [nvda] help menu Hi all, In this case, Gene is correct: although you may have told a different browser to open files, whichever program is associated with HTML files will be used (see my technical notes below). For new users: those who were (or part of) BrailleNote users mailing list may recognize the below kind of note (I mention this as I see some familiar faces), only this time I can dive inside the lake instead of using crystal balls from old days (i.e. when in doubt, looking at NVDA source code is helpful sometimes). Technical: there is a function in Python that’ll let you open whichever file you like. Internally, this is the function used by NVDA to open various documents, namely user guide, commands quick reference and others. The below code lets you do this: import os # Either you can spell out the path directly or use a variable. os.startfile(path) # In case of the English user guide on 64-bit Windows, it’ll open the following path: os.startfile(“C:\\Program Files (x86)\\NVDA\\Documentation\\en\\userGuide.html”) The “os.startfile” function will invoke Windows API function that looks up file associations stored on the registry hive HKEY_CLASSES_ROOT (HKCR), which then runs the program associated with the given file extension or protocol. You can override this on an individual extension/protocol basis (either from Control Panel or from Settings if you are using older versions of Windows or Windows 10, respectively). In case of the NVDA user guide, the following steps are taken: 1. NVDA notices you want to open the user guide. 2. The “gui.getDocPath” function is called, which consults the current NVDA interface language and the name of the doc file you wish to open. If the documentation for your language isn’t there, it falls back to English. Surprisingly, this is the same step taken when opening add-on readme files. 3. An event handler function is run when you select “User guide” from NVDA’s help menu, which runs “os.startfile” and opens the path that the previous function returns. I guess the above notes could have been best served on the NVDA development list. But I wrote the above to show three things: 1. We do have reps from NV Access here (Quentin, the author of the highly acclaimed NVDA basics tutorial), as well as NVDA developers who are more than happy to explain NVDA internals (at least two devs are here, including I (the one who brought ability to disable individual add-ons) and Derek Riemer (the one who worked on ability to hear indentations via tones). 2. That NVDA ecosystem is vast – not just what you see, hear and read, but source code as well. 3. There are lots more involved than Python and dialogs when it comes to talking about NVDA and its internals (and no, you cannot port NVDA to other operating systems (easily), and if you do, good luck). A tip for those seeking to learn NVDA’s source code inside out: start by asking yourself, “how does NVDA commands work”. Perhaps you can start by reading global commands module where all you need to know about majority of NVDA commands are spelled out, including internals of title bar reading command, object navigation and others. As I stressed many times (including during a lecture series I led concerning writing your first ever NVDA app module this summer), grasping Python is a must. Cheers, Joseph I know. That was kind of the point that I was attempting to make. Joseph has said to open IE, then while open, try launching the quick commands help after first launching IE. What I was trying to say was, that didn't make sense, as I agree with what you're saying, Gene, that's not generally how file associations work. Alas, looks like Don got it resolved, so that's good to know. --- Christopher Gilland JAWS Certified, 2016. Training Instructor. ----- Original Message ----- Sent: Wednesday, November 23, 2016 12:50 PM Subject: Re: [nvda] help menu That isn't how file associations work. If a browser is opened and another browser is the default, the default browser will open when a file type is clicked on that the browser is supposed to open. ----- Original Message ----- Sent: Wednesday, November 23, 2016 11:40 AM Subject: Re: [nvda] help menu I was gonna say. Wouldn't that just launch whatever browser in a new window with that documentation? In this case, the user's guide? The behavior symptoms Don's describing don't surprise me. Is NVDA supposed to detect what browser is opened ahead of time, hince why you said, open IE first, then launch the guide? --- Christopher Gilland JAWS Certified, 2016. Training Instructor.
info@... Phone: (704) 256-8010. ----- Original Message ----- From: "Don H" <lmddh50@...> To: <nvda@nvda.groups.io> Sent: Wednesday, November 23, 2016 12:00 PM Subject: Re: [nvda] help menu
> Sorry if I follow your instructions and have IE open before opening the > NVDA menu then select the user guide from the help menu it opens in Edge > not IE. > > On 11/23/2016 10:42 AM, Joseph Lee wrote: >> Hi, >> The corrected instruction is to go to IE, then open NVDA menu/help, then >> select the item you want. >> Cheers, >> Joseph >> >> -----Original Message----- >> From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Don H >> Sent: Wednesday, November 23, 2016 8:35 AM >> To: nvda@nvda.groups.io >> Subject: Re: [nvda] help menu >> >> With IE open F1 brings up the IE help using IE. >> >> On 11/23/2016 10:14 AM, Gene wrote: >>> Open Internet Explorer and see what happens if you issue the command f1. >>> >>> Gene >>> ----- Original Message ----- >>> *From:* Don H <mailto:lmddh50@...> >>> *Sent:* Wednesday, November 23, 2016 10:05 AM >>> *To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> >>> *Subject:* Re: [nvda] help menu >>> >>> As I said following your steps I have IE set as my default browser. >>> Help documents still open in Edge. >>> >>> On 11/23/2016 9:58 AM, Andre Fisher wrote: >>>> 1. Press Windows key+I to go to the Settings app. >>>> 2. Depending on which version of Windows 10 you are using, you might >>>> need to Tab till you hear System. Press Enter on it. >>>> 3. Use the Down Arrow until you hear Default Apps. Press Enter 4. >>>> Press Tab continuously till you hear Web browser: Microsoft Edge or >>>> otherwise. >>>> 5. Press Enter and Tab to Internet Explorer. >>>> Press Enter and close the app. >>>> >>>> That's it! >>>> >>>> On 11/23/16, Don H <lmddh50@... <mailto:lmddh50@...>> >>> wrote: >>>>> Running Win 10 and have IE set as my default browser. When I select >>>>> help within the NVDA menu it opens the help documentation in MS Edge. >>>>> Is there a way to get it to open within IE or is there a way to get >>>>> this documentation in txt format? >>>>> Thanks >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> >>> >>> >>> >> >> >> >> >> >> > > >
|
|
Try contacting Microsoft with your question. Microsoft Disability Answer Desk 1-800-936-5900
toggle quoted messageShow quoted text
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sakina Sent: Wednesday, November 23, 2016 2:22 AM To: nvda@nvda.groups.io Subject: [nvda] Please help Dear All, I am visually impaired and at very infant stages of understanding all the technical terms of computers. Please can any one help as to how or if I can still upgrade to window 10 as I missed out the free upgrade. I have an old Vista laptop and using NVDA Microsoft word, office 2003 I will greatly appreciate and look forward to any help With kind regards Sakina
|
|
Since you're using Windows 10, the Windows 10 Apps Essentials add-on is definitely recommended. Joseph Lee and others made it, and I I personally use it.
toggle quoted messageShow quoted text
On 11/23/16, Don H <lmddh50@comcast.net> wrote: Once again just getting started with NVDA after being a long term user of Window Eyes. I have NVDA installed on a Win 10 system. Primary uses are web surfing and Email. Have IE, Google Chrome and Firefox installed and use Thunderbird as my Email client. So now to the question, are there some must have addon's for best performance and other addon's that are otherwise suggested? Thanks
|
|
Once again just getting started with NVDA after being a long term user of Window Eyes. I have NVDA installed on a Win 10 system. Primary uses are web surfing and Email. Have IE, Google Chrome and Firefox installed and use Thunderbird as my Email client. So now to the question, are there some must have addon's for best performance and other addon's that are otherwise suggested? Thanks
|
|
Re: Python internals, code reviews and use of variables: RE: [nvda] help menu
I'm not sure of this but wouldn't some sort of
variable be necessary to accommodate those running NVDA as a portable
program? The path and drive could vary enormously depending on where the
portable version is being run from.
Gene
toggle quoted messageShow quoted text
----- Original Message -----
Sent: Wednesday, November 23, 2016 1:26 PM
Subject: Python internals, code reviews and use of variables: RE:
[nvda] help menu
Hi,
It’s two different
ways of accomplishing the same thing. Some would say using a variable is best
for readability purposes (after all, Python community values readability above
others), while majority of us would just encode the constant. Modern compilers
will actually detect this and just put in the constant (which is way beyond the
scope of this discussion). I usually prefer the second approach myself, knowing
that this generates less Python bytecode instructions (for add-on code reviews,
I sometimes overlook this, but in NVDA Core code review, this is considered
important, mostly when it comes to coding style).
The following is
mostly meant for resident add-on writers but it might be helpful for users to
hear this as a side note (and yes, I’ll revisit this subject on the add-ons list
later): you can in fact disassemble Python bytecode. If you want to do under the
hood optimizations for your add-on code, it is crucial to know some internals of
Python interpreter and how instructions are fetched and executed. This applies
to any Python code that has a source code or not – yes, we can disassemble
add-on code where there is no source code and reconstruct what you were trying
to do. This should not be an excuse for you to bring an add-on with no source
code to my office for review – I and other reviewers will ask you to present a
copy of your source code before initiating add-on code reviews. In case of my
reviews, I would quickly look at your code, provide some feedback and that’ll be
all; if you do request a more detailed review, I’ll look at translatable
strings, documentation, GUI routines, and do compatibility/integration check
with NVDA Core and provide feedback as though I’m reviewing a module for NVDA
screen reader itself.
Hope this
helps.
Cheers,
Joseph
From: nvda@nvda.groups.io
[mailto:nvda@nvda.groups.io] On Behalf Of Christopher-Mark
Gilland Sent: Wednesday, November 23, 2016 10:50 AM To:
nvda@nvda.groups.io Subject: Re: [nvda] help
menu
Why would you put the
path to the file in a variable? That path never would change, would it? So,
wouldn't you therefore want it in a constant?
--- Christopher Gilland JAWS Certified,
2016. Training Instructor.
----- Original
Message -----
Sent: Wednesday, November
23, 2016 1:24 PM
Subject: Re: [nvda] help
menu
Hi
all,
In this case, Gene
is correct: although you may have told a different browser to open files,
whichever program is associated with HTML files will be used (see my technical
notes below).
For new users:
those who were (or part of) BrailleNote users mailing list may recognize the
below kind of note (I mention this as I see some familiar faces), only this
time I can dive inside the lake instead of using crystal balls from old days
(i.e. when in doubt, looking at NVDA source code is helpful
sometimes).
Technical: there is
a function in Python that’ll let you open whichever file you like. Internally,
this is the function used by NVDA to open various documents, namely user
guide, commands quick reference and others. The below code lets you do
this:
import
os
# Either you can
spell out the path directly or use a variable.
os.startfile(path)
# In case of the
English user guide on 64-bit Windows, it’ll open the following
path:
os.startfile(“C:\\Program
Files (x86)\\NVDA\\Documentation\\en\\userGuide.html”)
The “os.startfile”
function will invoke Windows API function that looks up file associations
stored on the registry hive HKEY_CLASSES_ROOT (HKCR), which then runs the
program associated with the given file extension or protocol. You can override
this on an individual extension/protocol basis (either from Control Panel or
from Settings if you are using older versions of Windows or Windows 10,
respectively).
In case of the NVDA
user guide, the following steps are taken:
1. NVDA notices you
want to open the user guide.
2. The
“gui.getDocPath” function is called, which consults the current NVDA interface
language and the name of the doc file you wish to open. If the documentation
for your language isn’t there, it falls back to English. Surprisingly, this is
the same step taken when opening add-on readme files.
3. An event handler
function is run when you select “User guide” from NVDA’s help menu, which runs
“os.startfile” and opens the path that the previous function
returns.
I guess the above
notes could have been best served on the NVDA development list. But I wrote
the above to show three things:
1. We do have reps
from NV Access here (Quentin, the author of the highly acclaimed NVDA basics
tutorial), as well as NVDA developers who are more than happy to explain NVDA
internals (at least two devs are here, including I (the one who brought
ability to disable individual add-ons) and Derek Riemer (the one who worked on
ability to hear indentations via tones).
2. That NVDA ecosystem
is vast – not just what you see, hear and read, but source code as
well.
3. There are lots more
involved than Python and dialogs when it comes to talking about NVDA and its
internals (and no, you cannot port NVDA to other operating systems (easily),
and if you do, good luck).
A tip for those
seeking to learn NVDA’s source code inside out: start by asking yourself, “how
does NVDA commands work”. Perhaps you can start by reading global commands
module where all you need to know about majority of NVDA commands are spelled
out, including internals of title bar reading command, object navigation and
others. As I stressed many times (including during a lecture series I led
concerning writing your first ever NVDA app module this summer), grasping
Python is a must.
Cheers,
Joseph
I know. That was kind
of the point that I was attempting to make. Joseph has said to open IE, then
while open, try launching the quick commands help after first launching IE.
What I was trying to say was, that didn't make sense, as I agree with what
you're saying, Gene, that's not generally how file associations work. Alas,
looks like Don got it resolved, so that's good to
know.
--- Christopher Gilland JAWS Certified,
2016. Training Instructor.
----- Original
Message -----
Sent: Wednesday,
November 23, 2016 12:50 PM
Subject: Re: [nvda] help
menu
That isn't how file
associations work. If a browser is opened and another browser is the
default, the default browser will open when a file type is clicked on that
the browser is supposed to open.
----- Original
Message -----
Sent: Wednesday,
November 23, 2016 11:40 AM
Subject: Re: [nvda] help
menu
I was gonna say. Wouldn't
that just launch whatever browser in a new window with that
documentation? In this case, the user's guide? The behavior symptoms
Don's describing don't surprise me. Is NVDA supposed to detect
what browser is opened ahead of time, hince why you said, open IE first,
then launch the guide? --- Christopher Gilland JAWS Certified,
2016. Training Instructor.
info@... Phone:
(704) 256-8010. ----- Original Message ----- From: "Don H" <lmddh50@...> To: <nvda@nvda.groups.io> Sent:
Wednesday, November 23, 2016 12:00 PM Subject: Re: [nvda] help
menu
> Sorry if I follow your instructions and have IE open
before opening the > NVDA menu then select the user guide from the
help menu it opens in Edge > not IE. > > On 11/23/2016
10:42 AM, Joseph Lee wrote: >> Hi, >> The corrected
instruction is to go to IE, then open NVDA menu/help, then >>
select the item you want. >> Cheers, >>
Joseph >> >> -----Original Message----- >> From:
nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf
Of Don H >> Sent: Wednesday, November 23, 2016 8:35 AM >>
To: nvda@nvda.groups.io >>
Subject: Re: [nvda] help menu >> >> With IE open F1 brings
up the IE help using IE. >> >> On 11/23/2016 10:14 AM,
Gene wrote: >>> Open Internet Explorer and see what happens if
you issue the command f1. >>> >>>
Gene >>> ----- Original Message ----- >>> *From:*
Don H <mailto:lmddh50@...> >>>
*Sent:* Wednesday, November 23, 2016 10:05 AM >>> *To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> >>>
*Subject:* Re: [nvda] help menu >>> >>> As I said
following your steps I have IE set as my default browser. >>>
Help documents still open in Edge. >>> >>> On
11/23/2016 9:58 AM, Andre Fisher wrote: >>>> 1. Press Windows
key+I to go to the Settings app. >>>> 2. Depending on which
version of Windows 10 you are using, you might >>>> need to
Tab till you hear System. Press Enter on it. >>>> 3. Use the
Down Arrow until you hear Default Apps. Press Enter 4. >>>>
Press Tab continuously till you hear Web browser: Microsoft Edge
or >>>> otherwise. >>>> 5. Press Enter and Tab
to Internet Explorer. >>>> Press Enter and close the
app. >>>> >>>> That's
it! >>>> >>>> On 11/23/16, Don H <lmddh50@... <mailto:lmddh50@...>> >>>
wrote: >>>>> Running Win 10 and have IE set as my default
browser. When I select >>>>> help within the NVDA
menu it opens the help documentation in MS Edge. >>>>> Is
there a way to get it to open within IE or is there a way to
get >>>>> this documentation in txt
format? >>>>>
Thanks >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> >>> >>> >>> >> >> >> >> >> >> > >
>
|
|
One of the things I do when I want to know what some of the Quick Navigation Keys do on a web page is to activate Keyboard Help, and that's done with NNVDA Key plus the Number 1 on the Number Row. Once activated you can press any key or key combination and NVDA will tell you what that key does.
Thx, Albert
|
|
Re: Python internals, code reviews and use of variables: RE: [nvda] help menu
Christopher-Mark Gilland <clgilland07@...>
It does help, yes. Enough said. I didn't intend for
the discussion to get really lengthy about this, I just didn't understand why
you were approaching it as you were saying, but that does make sense, now that
you explain.
--- Christopher Gilland JAWS Certified, 2016. Training
Instructor.
toggle quoted messageShow quoted text
----- Original Message -----
Sent: Wednesday, November 23, 2016 2:26
PM
Subject: Python internals, code reviews
and use of variables: RE: [nvda] help menu
Hi,
It’s two different
ways of accomplishing the same thing. Some would say using a variable is best
for readability purposes (after all, Python community values readability above
others), while majority of us would just encode the constant. Modern compilers
will actually detect this and just put in the constant (which is way beyond
the scope of this discussion). I usually prefer the second approach myself,
knowing that this generates less Python bytecode instructions (for add-on code
reviews, I sometimes overlook this, but in NVDA Core code review, this is
considered important, mostly when it comes to coding
style).
The following is
mostly meant for resident add-on writers but it might be helpful for users to
hear this as a side note (and yes, I’ll revisit this subject on the add-ons
list later): you can in fact disassemble Python bytecode. If you want to do
under the hood optimizations for your add-on code, it is crucial to know some
internals of Python interpreter and how instructions are fetched and executed.
This applies to any Python code that has a source code or not – yes, we can
disassemble add-on code where there is no source code and reconstruct what you
were trying to do. This should not be an excuse for you to bring an add-on
with no source code to my office for review – I and other reviewers will ask
you to present a copy of your source code before initiating add-on code
reviews. In case of my reviews, I would quickly look at your code, provide
some feedback and that’ll be all; if you do request a more detailed review,
I’ll look at translatable strings, documentation, GUI routines, and do
compatibility/integration check with NVDA Core and provide feedback as though
I’m reviewing a module for NVDA screen reader itself.
Hope this
helps.
Cheers,
Joseph
From:
nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of
Christopher-Mark Gilland Sent: Wednesday, November 23, 2016
10:50 AM To: nvda@nvda.groups.io Subject: Re: [nvda] help
menu
Why would you put the
path to the file in a variable? That path never would change, would it? So,
wouldn't you therefore want it in a constant?
--- Christopher Gilland JAWS Certified,
2016. Training Instructor.
----- Original
Message -----
Sent: Wednesday,
November 23, 2016 1:24 PM
Subject: Re: [nvda] help
menu
Hi
all,
In this case,
Gene is correct: although you may have told a different browser to open
files, whichever program is associated with HTML files will be used (see my
technical notes below).
For new users:
those who were (or part of) BrailleNote users mailing list may recognize the
below kind of note (I mention this as I see some familiar faces), only this
time I can dive inside the lake instead of using crystal balls from old days
(i.e. when in doubt, looking at NVDA source code is helpful
sometimes).
Technical: there
is a function in Python that’ll let you open whichever file you like.
Internally, this is the function used by NVDA to open various documents,
namely user guide, commands quick reference and others. The below code lets
you do this:
import
os
# Either you can
spell out the path directly or use a variable.
os.startfile(path)
# In case of the
English user guide on 64-bit Windows, it’ll open the following
path:
os.startfile(“C:\\Program
Files (x86)\\NVDA\\Documentation\\en\\userGuide.html”)
The
“os.startfile” function will invoke Windows API function that looks up file
associations stored on the registry hive HKEY_CLASSES_ROOT (HKCR), which
then runs the program associated with the given file extension or protocol.
You can override this on an individual extension/protocol basis (either from
Control Panel or from Settings if you are using older versions of Windows or
Windows 10, respectively).
In case of the
NVDA user guide, the following steps are taken:
1. NVDA notices you
want to open the user guide.
2. The
“gui.getDocPath” function is called, which consults the current NVDA
interface language and the name of the doc file you wish to open. If the
documentation for your language isn’t there, it falls back to English.
Surprisingly, this is the same step taken when opening add-on readme
files.
3. An event handler
function is run when you select “User guide” from NVDA’s help menu, which
runs “os.startfile” and opens the path that the previous function
returns.
I guess the above
notes could have been best served on the NVDA development list. But I wrote
the above to show three things:
1. We do have reps
from NV Access here (Quentin, the author of the highly acclaimed NVDA basics
tutorial), as well as NVDA developers who are more than happy to explain
NVDA internals (at least two devs are here, including I (the one who brought
ability to disable individual add-ons) and Derek Riemer (the one who worked
on ability to hear indentations via tones).
2. That NVDA
ecosystem is vast – not just what you see, hear and read, but source code as
well.
3. There are lots
more involved than Python and dialogs when it comes to talking about NVDA
and its internals (and no, you cannot port NVDA to other operating systems
(easily), and if you do, good luck).
A tip for those
seeking to learn NVDA’s source code inside out: start by asking yourself,
“how does NVDA commands work”. Perhaps you can start by reading global
commands module where all you need to know about majority of NVDA commands
are spelled out, including internals of title bar reading command, object
navigation and others. As I stressed many times (including during a lecture
series I led concerning writing your first ever NVDA app module this
summer), grasping Python is a must.
Cheers,
Joseph
I know. That was
kind of the point that I was attempting to make. Joseph has said to open IE,
then while open, try launching the quick commands help after first launching
IE. What I was trying to say was, that didn't make sense, as I agree with
what you're saying, Gene, that's not generally how file associations work.
Alas, looks like Don got it resolved, so that's good to
know.
--- Christopher Gilland JAWS Certified,
2016. Training Instructor.
----- Original
Message -----
Sent: Wednesday,
November 23, 2016 12:50 PM
Subject: Re: [nvda] help
menu
That isn't how
file associations work. If a browser is opened and another browser
is the default, the default browser will open when a file type is clicked
on that the browser is supposed to open.
----- Original
Message -----
Sent: Wednesday,
November 23, 2016 11:40 AM
Subject: Re: [nvda] help
menu
I was gonna say. Wouldn't
that just launch whatever browser in a new window with that
documentation? In this case, the user's guide? The behavior symptoms
Don's describing don't surprise me. Is NVDA supposed to detect
what browser is opened ahead of time, hince why you said, open IE
first, then launch the guide? --- Christopher Gilland JAWS
Certified, 2016. Training Instructor.
info@... Phone:
(704) 256-8010. ----- Original Message ----- From: "Don H" <lmddh50@...> To:
<nvda@nvda.groups.io> Sent:
Wednesday, November 23, 2016 12:00 PM Subject: Re: [nvda] help
menu
> Sorry if I follow your instructions and have IE open
before opening the > NVDA menu then select the user guide from the
help menu it opens in Edge > not IE. > > On 11/23/2016
10:42 AM, Joseph Lee wrote: >> Hi, >> The corrected
instruction is to go to IE, then open NVDA menu/help, then >>
select the item you want. >> Cheers, >>
Joseph >> >> -----Original Message----- >>
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On
Behalf Of Don H >> Sent: Wednesday, November 23, 2016 8:35
AM >> To: nvda@nvda.groups.io >>
Subject: Re: [nvda] help menu >> >> With IE open F1
brings up the IE help using IE. >> >> On 11/23/2016
10:14 AM, Gene wrote: >>> Open Internet Explorer and see what
happens if you issue the command f1. >>> >>>
Gene >>> ----- Original Message ----- >>> *From:*
Don H <mailto:lmddh50@...> >>>
*Sent:* Wednesday, November 23, 2016 10:05 AM >>> *To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> >>>
*Subject:* Re: [nvda] help menu >>> >>> As I said
following your steps I have IE set as my default browser. >>>
Help documents still open in Edge. >>> >>> On
11/23/2016 9:58 AM, Andre Fisher wrote: >>>> 1. Press
Windows key+I to go to the Settings app. >>>> 2. Depending
on which version of Windows 10 you are using, you
might >>>> need to Tab till you hear System. Press Enter on
it. >>>> 3. Use the Down Arrow until you hear Default Apps.
Press Enter 4. >>>> Press Tab continuously till you hear
Web browser: Microsoft Edge or >>>>
otherwise. >>>> 5. Press Enter and Tab to Internet
Explorer. >>>> Press Enter and close the
app. >>>> >>>> That's
it! >>>> >>>> On 11/23/16, Don H <lmddh50@... <mailto:lmddh50@...>> >>>
wrote: >>>>> Running Win 10 and have IE set as my
default browser. When I select >>>>> help within
the NVDA menu it opens the help documentation in MS
Edge. >>>>> Is there a way to get it to open within IE
or is there a way to get >>>>> this documentation in txt
format? >>>>>
Thanks >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> >>> >>> >>> >> >> >> >> >> >> > >
>
|
|
Python internals, code reviews and use of variables: RE: [nvda] help menu
Hi, It’s two different ways of accomplishing the same thing. Some would say using a variable is best for readability purposes (after all, Python community values readability above others), while majority of us would just encode the constant. Modern compilers will actually detect this and just put in the constant (which is way beyond the scope of this discussion). I usually prefer the second approach myself, knowing that this generates less Python bytecode instructions (for add-on code reviews, I sometimes overlook this, but in NVDA Core code review, this is considered important, mostly when it comes to coding style). The following is mostly meant for resident add-on writers but it might be helpful for users to hear this as a side note (and yes, I’ll revisit this subject on the add-ons list later): you can in fact disassemble Python bytecode. If you want to do under the hood optimizations for your add-on code, it is crucial to know some internals of Python interpreter and how instructions are fetched and executed. This applies to any Python code that has a source code or not – yes, we can disassemble add-on code where there is no source code and reconstruct what you were trying to do. This should not be an excuse for you to bring an add-on with no source code to my office for review – I and other reviewers will ask you to present a copy of your source code before initiating add-on code reviews. In case of my reviews, I would quickly look at your code, provide some feedback and that’ll be all; if you do request a more detailed review, I’ll look at translatable strings, documentation, GUI routines, and do compatibility/integration check with NVDA Core and provide feedback as though I’m reviewing a module for NVDA screen reader itself. Hope this helps. Cheers, Joseph
toggle quoted messageShow quoted text
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Christopher-Mark Gilland Sent: Wednesday, November 23, 2016 10:50 AM To: nvda@nvda.groups.io Subject: Re: [nvda] help menu Why would you put the path to the file in a variable? That path never would change, would it? So, wouldn't you therefore want it in a constant? --- Christopher Gilland JAWS Certified, 2016. Training Instructor. ----- Original Message ----- Sent: Wednesday, November 23, 2016 1:24 PM Subject: Re: [nvda] help menu Hi all, In this case, Gene is correct: although you may have told a different browser to open files, whichever program is associated with HTML files will be used (see my technical notes below). For new users: those who were (or part of) BrailleNote users mailing list may recognize the below kind of note (I mention this as I see some familiar faces), only this time I can dive inside the lake instead of using crystal balls from old days (i.e. when in doubt, looking at NVDA source code is helpful sometimes). Technical: there is a function in Python that’ll let you open whichever file you like. Internally, this is the function used by NVDA to open various documents, namely user guide, commands quick reference and others. The below code lets you do this: import os # Either you can spell out the path directly or use a variable. os.startfile(path) # In case of the English user guide on 64-bit Windows, it’ll open the following path: os.startfile(“C:\\Program Files (x86)\\NVDA\\Documentation\\en\\userGuide.html”) The “os.startfile” function will invoke Windows API function that looks up file associations stored on the registry hive HKEY_CLASSES_ROOT (HKCR), which then runs the program associated with the given file extension or protocol. You can override this on an individual extension/protocol basis (either from Control Panel or from Settings if you are using older versions of Windows or Windows 10, respectively). In case of the NVDA user guide, the following steps are taken: 1. NVDA notices you want to open the user guide. 2. The “gui.getDocPath” function is called, which consults the current NVDA interface language and the name of the doc file you wish to open. If the documentation for your language isn’t there, it falls back to English. Surprisingly, this is the same step taken when opening add-on readme files. 3. An event handler function is run when you select “User guide” from NVDA’s help menu, which runs “os.startfile” and opens the path that the previous function returns. I guess the above notes could have been best served on the NVDA development list. But I wrote the above to show three things: 1. We do have reps from NV Access here (Quentin, the author of the highly acclaimed NVDA basics tutorial), as well as NVDA developers who are more than happy to explain NVDA internals (at least two devs are here, including I (the one who brought ability to disable individual add-ons) and Derek Riemer (the one who worked on ability to hear indentations via tones). 2. That NVDA ecosystem is vast – not just what you see, hear and read, but source code as well. 3. There are lots more involved than Python and dialogs when it comes to talking about NVDA and its internals (and no, you cannot port NVDA to other operating systems (easily), and if you do, good luck). A tip for those seeking to learn NVDA’s source code inside out: start by asking yourself, “how does NVDA commands work”. Perhaps you can start by reading global commands module where all you need to know about majority of NVDA commands are spelled out, including internals of title bar reading command, object navigation and others. As I stressed many times (including during a lecture series I led concerning writing your first ever NVDA app module this summer), grasping Python is a must. Cheers, Joseph I know. That was kind of the point that I was attempting to make. Joseph has said to open IE, then while open, try launching the quick commands help after first launching IE. What I was trying to say was, that didn't make sense, as I agree with what you're saying, Gene, that's not generally how file associations work. Alas, looks like Don got it resolved, so that's good to know. --- Christopher Gilland JAWS Certified, 2016. Training Instructor. ----- Original Message ----- Sent: Wednesday, November 23, 2016 12:50 PM Subject: Re: [nvda] help menu That isn't how file associations work. If a browser is opened and another browser is the default, the default browser will open when a file type is clicked on that the browser is supposed to open. ----- Original Message ----- Sent: Wednesday, November 23, 2016 11:40 AM Subject: Re: [nvda] help menu I was gonna say. Wouldn't that just launch whatever browser in a new window with that documentation? In this case, the user's guide? The behavior symptoms Don's describing don't surprise me. Is NVDA supposed to detect what browser is opened ahead of time, hince why you said, open IE first, then launch the guide? --- Christopher Gilland JAWS Certified, 2016. Training Instructor.
info@... Phone: (704) 256-8010. ----- Original Message ----- From: "Don H" <lmddh50@...> To: <nvda@nvda.groups.io> Sent: Wednesday, November 23, 2016 12:00 PM Subject: Re: [nvda] help menu
> Sorry if I follow your instructions and have IE open before opening the > NVDA menu then select the user guide from the help menu it opens in Edge > not IE. > > On 11/23/2016 10:42 AM, Joseph Lee wrote: >> Hi, >> The corrected instruction is to go to IE, then open NVDA menu/help, then >> select the item you want. >> Cheers, >> Joseph >> >> -----Original Message----- >> From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Don H >> Sent: Wednesday, November 23, 2016 8:35 AM >> To: nvda@nvda.groups.io >> Subject: Re: [nvda] help menu >> >> With IE open F1 brings up the IE help using IE. >> >> On 11/23/2016 10:14 AM, Gene wrote: >>> Open Internet Explorer and see what happens if you issue the command f1. >>> >>> Gene >>> ----- Original Message ----- >>> *From:* Don H <mailto:lmddh50@...> >>> *Sent:* Wednesday, November 23, 2016 10:05 AM >>> *To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> >>> *Subject:* Re: [nvda] help menu >>> >>> As I said following your steps I have IE set as my default browser. >>> Help documents still open in Edge. >>> >>> On 11/23/2016 9:58 AM, Andre Fisher wrote: >>>> 1. Press Windows key+I to go to the Settings app. >>>> 2. Depending on which version of Windows 10 you are using, you might >>>> need to Tab till you hear System. Press Enter on it. >>>> 3. Use the Down Arrow until you hear Default Apps. Press Enter 4. >>>> Press Tab continuously till you hear Web browser: Microsoft Edge or >>>> otherwise. >>>> 5. Press Enter and Tab to Internet Explorer. >>>> Press Enter and close the app. >>>> >>>> That's it! >>>> >>>> On 11/23/16, Don H <lmddh50@... <mailto:lmddh50@...>> >>> wrote: >>>>> Running Win 10 and have IE set as my default browser. When I select >>>>> help within the NVDA menu it opens the help documentation in MS Edge. >>>>> Is there a way to get it to open within IE or is there a way to get >>>>> this documentation in txt format? >>>>> Thanks >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> >>> >>> >>> >> >> >> >> >> >> > > >
|
|
Try resetting your default browser, or manually setting the program that opens html files.
toggle quoted messageShow quoted text
On 11/23/2016 9:03 AM, Gene wrote: I'm not sure why that is but one solution might be that once it opens, copy the address from the address bar in Edge and then close Edge. Open Internet Explorer, paste the address into Internet Explorer and open the page there. Then make a favorite so you can open it directly in Internet Explorer.
Gene ----- Original Message ----- *From:* Don H <mailto:lmddh50@comcast.net> *Sent:* Wednesday, November 23, 2016 10:57 AM *To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> *Subject:* Re: [nvda] help menu
Maybe I didn't make myself clear regarding the problem. When I open the NVDA menu move down and expand the help menu and press enter on user guide the guide opens in Edge. I have IE set as my default browser.
On 11/23/2016 10:48 AM, Gene wrote:
Does that solve the problem? I believe you were specifically asking about how to get help for Internet Explorer in Internet Explorer. For other programs where this happens, you should be able to open at least the main help document from within the program. F1 often brings it up. If not, look in the menus. When getting to know an unfamiliar program, looking through the menus is often a good way to learn many things.
Gee
*From:* Don H <mailto:lmddh50@comcast.net> *Sent:* Wednesday, November 23, 2016 10:34 AM *To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> <mailto:nvda@nvda.groups.io>
*Subject:* Re: [nvda] help menu
With IE open F1 brings up the IE help using IE.
On 11/23/2016 10:14 AM, Gene wrote:
Open Internet Explorer and see what happens if you issue the command f1.
Gene ----- Original Message ----- *From:* Don H <mailto:lmddh50@comcast.net> *Sent:* Wednesday, November 23, 2016 10:05 AM *To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> <mailto:nvda@nvda.groups.io>
<mailto:nvda@nvda.groups.io>
*Subject:* Re: [nvda] help menu
As I said following your steps I have IE set as my default browser. Help documents still open in Edge.
On 11/23/2016 9:58 AM, Andre Fisher wrote:
1. Press Windows key+I to go to the Settings app. 2. Depending on which version of Windows 10 you are using, you might need to Tab till you hear System. Press Enter on it. 3. Use the Down Arrow until you hear Default Apps. Press Enter 4. Press Tab continuously till you hear Web browser: Microsoft Edge or otherwise. 5. Press Enter and Tab to Internet Explorer. Press Enter and close the app.
That's it!
On 11/23/16, Don H <lmddh50@comcast.net <mailto:lmddh50@comcast.net> <mailto:lmddh50@comcast.net>
<mailto:lmddh50@comcast.net>>
wrote:
Running Win 10 and have IE set as my default browser. When I select help within the NVDA menu it opens the help documentation in MS Edge. Is there a way to get it to open within IE or is there a way to get
this
documentation in txt format? Thanks
|
|
Well, I don't understand what's being said here because it's not what I see when I change default browsers. Any time I change my default browser all of my existing links to, or actual, HTML documents immediately get an icon change from whatever had been the default browser to what is now the default browser and open in that new default. Just switched from Firefox to Chrome to test and all of my NVDA documentation in the form of HTML files shows a Chrome icon and opens in Chrome. I have never had to change HTML file type handling separately from default browser since the default browser is what should be being used to open any HTML file. -- Brian Here is a test to find out whether your mission in life is complete. If you’re alive, it isn’t. ~ Lauren Bacall
|
|
Christopher-Mark Gilland <clgilland07@...>
Why would you put the path to the file in a
variable? That path never would change, would it? So, wouldn't you therefore
want it in a constant?
--- Christopher Gilland JAWS Certified, 2016. Training
Instructor.
toggle quoted messageShow quoted text
----- Original Message -----
Sent: Wednesday, November 23, 2016 1:24
PM
Subject: Re: [nvda] help menu
Hi
all,
In this case, Gene
is correct: although you may have told a different browser to open files,
whichever program is associated with HTML files will be used (see my technical
notes below).
For new users:
those who were (or part of) BrailleNote users mailing list may recognize the
below kind of note (I mention this as I see some familiar faces), only this
time I can dive inside the lake instead of using crystal balls from old days
(i.e. when in doubt, looking at NVDA source code is helpful
sometimes).
Technical: there is
a function in Python that’ll let you open whichever file you like. Internally,
this is the function used by NVDA to open various documents, namely user
guide, commands quick reference and others. The below code lets you do
this:
import
os
# Either you can
spell out the path directly or use a variable.
os.startfile(path)
# In case of the
English user guide on 64-bit Windows, it’ll open the following
path:
os.startfile(“C:\\Program
Files (x86)\\NVDA\\Documentation\\en\\userGuide.html”)
The “os.startfile”
function will invoke Windows API function that looks up file associations
stored on the registry hive HKEY_CLASSES_ROOT (HKCR), which then runs the
program associated with the given file extension or protocol. You can override
this on an individual extension/protocol basis (either from Control Panel or
from Settings if you are using older versions of Windows or Windows 10,
respectively).
In case of the NVDA
user guide, the following steps are taken:
1.
NVDA notices you
want to open the user guide.
2.
The
“gui.getDocPath” function is called, which consults the current NVDA interface
language and the name of the doc file you wish to open. If the documentation
for your language isn’t there, it falls back to English. Surprisingly, this is
the same step taken when opening add-on readme files.
3.
An event handler
function is run when you select “User guide” from NVDA’s help menu, which runs
“os.startfile” and opens the path that the previous function
returns.
I guess the above
notes could have been best served on the NVDA development list. But I wrote
the above to show three things:
1.
We do have reps
from NV Access here (Quentin, the author of the highly acclaimed NVDA basics
tutorial), as well as NVDA developers who are more than happy to explain NVDA
internals (at least two devs are here, including I (the one who brought
ability to disable individual add-ons) and Derek Riemer (the one who worked on
ability to hear indentations via tones).
2.
That NVDA ecosystem
is vast – not just what you see, hear and read, but source code as
well.
3.
There are lots more
involved than Python and dialogs when it comes to talking about NVDA and its
internals (and no, you cannot port NVDA to other operating systems (easily),
and if you do, good luck).
A tip for those
seeking to learn NVDA’s source code inside out: start by asking yourself, “how
does NVDA commands work”. Perhaps you can start by reading global commands
module where all you need to know about majority of NVDA commands are spelled
out, including internals of title bar reading command, object navigation and
others. As I stressed many times (including during a lecture series I led
concerning writing your first ever NVDA app module this summer), grasping
Python is a must.
Cheers,
Joseph
From:
nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of
Christopher-Mark Gilland Sent: Wednesday, November 23, 2016 9:54
AM To: nvda@nvda.groups.io Subject: Re: [nvda] help
menu
I know. That was kind
of the point that I was attempting to make. Joseph has said to open IE, then
while open, try launching the quick commands help after first launching IE.
What I was trying to say was, that didn't make sense, as I agree with what
you're saying, Gene, that's not generally how file associations work. Alas,
looks like Don got it resolved, so that's good to
know.
--- Christopher Gilland JAWS Certified,
2016. Training Instructor.
----- Original
Message -----
Sent: Wednesday,
November 23, 2016 12:50 PM
Subject: Re: [nvda] help
menu
That isn't how file
associations work. If a browser is opened and another browser is the
default, the default browser will open when a file type is clicked on that
the browser is supposed to open.
----- Original
Message -----
Sent: Wednesday,
November 23, 2016 11:40 AM
Subject: Re: [nvda] help
menu
I was gonna say. Wouldn't
that just launch whatever browser in a new window with that
documentation? In this case, the user's guide? The behavior symptoms
Don's describing don't surprise me. Is NVDA supposed to detect
what browser is opened ahead of time, hince why you said, open IE first,
then launch the guide? --- Christopher Gilland JAWS Certified,
2016. Training Instructor.
info@... Phone:
(704) 256-8010. ----- Original Message ----- From: "Don H" <lmddh50@...> To: <nvda@nvda.groups.io> Sent:
Wednesday, November 23, 2016 12:00 PM Subject: Re: [nvda] help
menu
> Sorry if I follow your instructions and have IE open
before opening the > NVDA menu then select the user guide from the
help menu it opens in Edge > not IE. > > On 11/23/2016
10:42 AM, Joseph Lee wrote: >> Hi, >> The corrected
instruction is to go to IE, then open NVDA menu/help, then >>
select the item you want. >> Cheers, >>
Joseph >> >> -----Original Message----- >> From:
nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf
Of Don H >> Sent: Wednesday, November 23, 2016 8:35 AM >>
To: nvda@nvda.groups.io >>
Subject: Re: [nvda] help menu >> >> With IE open F1 brings
up the IE help using IE. >> >> On 11/23/2016 10:14 AM,
Gene wrote: >>> Open Internet Explorer and see what happens if
you issue the command f1. >>> >>>
Gene >>> ----- Original Message ----- >>> *From:*
Don H <mailto:lmddh50@...> >>>
*Sent:* Wednesday, November 23, 2016 10:05 AM >>> *To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> >>>
*Subject:* Re: [nvda] help menu >>> >>> As I said
following your steps I have IE set as my default browser. >>>
Help documents still open in Edge. >>> >>> On
11/23/2016 9:58 AM, Andre Fisher wrote: >>>> 1. Press Windows
key+I to go to the Settings app. >>>> 2. Depending on which
version of Windows 10 you are using, you might >>>> need to
Tab till you hear System. Press Enter on it. >>>> 3. Use the
Down Arrow until you hear Default Apps. Press Enter 4. >>>>
Press Tab continuously till you hear Web browser: Microsoft Edge
or >>>> otherwise. >>>> 5. Press Enter and Tab
to Internet Explorer. >>>> Press Enter and close the
app. >>>> >>>> That's
it! >>>> >>>> On 11/23/16, Don H <lmddh50@... <mailto:lmddh50@...>> >>>
wrote: >>>>> Running Win 10 and have IE set as my default
browser. When I select >>>>> help within the NVDA
menu it opens the help documentation in MS Edge. >>>>> Is
there a way to get it to open within IE or is there a way to
get >>>>> this documentation in txt
format? >>>>>
Thanks >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> >>> >>> >>> >> >> >> >> >> >> > >
>
|
|
Joseph, I was not aware of that, but even with it being the case I often want to access this information when NVDA is not running. For someone who's an actual user of a screen reader to accomplish their daily routine on a computer the NVDA help menu is, of course, ideal. For me screen readers are a "fire it up to test out things X, Y, and Z" affair rather than a constant. -- Brian Here is a test to find out whether your mission in life is complete. If you’re alive, it isn’t. ~ Lauren Bacall
|
|
Hi all, In this case, Gene is correct: although you may have told a different browser to open files, whichever program is associated with HTML files will be used (see my technical notes below). For new users: those who were (or part of) BrailleNote users mailing list may recognize the below kind of note (I mention this as I see some familiar faces), only this time I can dive inside the lake instead of using crystal balls from old days (i.e. when in doubt, looking at NVDA source code is helpful sometimes). Technical: there is a function in Python that’ll let you open whichever file you like. Internally, this is the function used by NVDA to open various documents, namely user guide, commands quick reference and others. The below code lets you do this: import os # Either you can spell out the path directly or use a variable. os.startfile(path) # In case of the English user guide on 64-bit Windows, it’ll open the following path: os.startfile(“C:\\Program Files (x86)\\NVDA\\Documentation\\en\\userGuide.html”) The “os.startfile” function will invoke Windows API function that looks up file associations stored on the registry hive HKEY_CLASSES_ROOT (HKCR), which then runs the program associated with the given file extension or protocol. You can override this on an individual extension/protocol basis (either from Control Panel or from Settings if you are using older versions of Windows or Windows 10, respectively). In case of the NVDA user guide, the following steps are taken: 1. NVDA notices you want to open the user guide. 2. The “gui.getDocPath” function is called, which consults the current NVDA interface language and the name of the doc file you wish to open. If the documentation for your language isn’t there, it falls back to English. Surprisingly, this is the same step taken when opening add-on readme files. 3. An event handler function is run when you select “User guide” from NVDA’s help menu, which runs “os.startfile” and opens the path that the previous function returns. I guess the above notes could have been best served on the NVDA development list. But I wrote the above to show three things: 1. We do have reps from NV Access here (Quentin, the author of the highly acclaimed NVDA basics tutorial), as well as NVDA developers who are more than happy to explain NVDA internals (at least two devs are here, including I (the one who brought ability to disable individual add-ons) and Derek Riemer (the one who worked on ability to hear indentations via tones). 2. That NVDA ecosystem is vast – not just what you see, hear and read, but source code as well. 3. There are lots more involved than Python and dialogs when it comes to talking about NVDA and its internals (and no, you cannot port NVDA to other operating systems (easily), and if you do, good luck). A tip for those seeking to learn NVDA’s source code inside out: start by asking yourself, “how does NVDA commands work”. Perhaps you can start by reading global commands module where all you need to know about majority of NVDA commands are spelled out, including internals of title bar reading command, object navigation and others. As I stressed many times (including during a lecture series I led concerning writing your first ever NVDA app module this summer), grasping Python is a must. Cheers, Joseph
toggle quoted messageShow quoted text
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Christopher-Mark Gilland Sent: Wednesday, November 23, 2016 9:54 AM To: nvda@nvda.groups.io Subject: Re: [nvda] help menu I know. That was kind of the point that I was attempting to make. Joseph has said to open IE, then while open, try launching the quick commands help after first launching IE. What I was trying to say was, that didn't make sense, as I agree with what you're saying, Gene, that's not generally how file associations work. Alas, looks like Don got it resolved, so that's good to know. --- Christopher Gilland JAWS Certified, 2016. Training Instructor. ----- Original Message ----- Sent: Wednesday, November 23, 2016 12:50 PM Subject: Re: [nvda] help menu That isn't how file associations work. If a browser is opened and another browser is the default, the default browser will open when a file type is clicked on that the browser is supposed to open. ----- Original Message ----- Sent: Wednesday, November 23, 2016 11:40 AM Subject: Re: [nvda] help menu I was gonna say. Wouldn't that just launch whatever browser in a new window with that documentation? In this case, the user's guide? The behavior symptoms Don's describing don't surprise me. Is NVDA supposed to detect what browser is opened ahead of time, hince why you said, open IE first, then launch the guide? --- Christopher Gilland JAWS Certified, 2016. Training Instructor.
info@... Phone: (704) 256-8010. ----- Original Message ----- From: "Don H" <lmddh50@...> To: <nvda@nvda.groups.io> Sent: Wednesday, November 23, 2016 12:00 PM Subject: Re: [nvda] help menu
> Sorry if I follow your instructions and have IE open before opening the > NVDA menu then select the user guide from the help menu it opens in Edge > not IE. > > On 11/23/2016 10:42 AM, Joseph Lee wrote: >> Hi, >> The corrected instruction is to go to IE, then open NVDA menu/help, then >> select the item you want. >> Cheers, >> Joseph >> >> -----Original Message----- >> From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Don H >> Sent: Wednesday, November 23, 2016 8:35 AM >> To: nvda@nvda.groups.io >> Subject: Re: [nvda] help menu >> >> With IE open F1 brings up the IE help using IE. >> >> On 11/23/2016 10:14 AM, Gene wrote: >>> Open Internet Explorer and see what happens if you issue the command f1. >>> >>> Gene >>> ----- Original Message ----- >>> *From:* Don H <mailto:lmddh50@...> >>> *Sent:* Wednesday, November 23, 2016 10:05 AM >>> *To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> >>> *Subject:* Re: [nvda] help menu >>> >>> As I said following your steps I have IE set as my default browser. >>> Help documents still open in Edge. >>> >>> On 11/23/2016 9:58 AM, Andre Fisher wrote: >>>> 1. Press Windows key+I to go to the Settings app. >>>> 2. Depending on which version of Windows 10 you are using, you might >>>> need to Tab till you hear System. Press Enter on it. >>>> 3. Use the Down Arrow until you hear Default Apps. Press Enter 4. >>>> Press Tab continuously till you hear Web browser: Microsoft Edge or >>>> otherwise. >>>> 5. Press Enter and Tab to Internet Explorer. >>>> Press Enter and close the app. >>>> >>>> That's it! >>>> >>>> On 11/23/16, Don H <lmddh50@... <mailto:lmddh50@...>> >>> wrote: >>>>> Running Win 10 and have IE set as my default browser. When I select >>>>> help within the NVDA menu it opens the help documentation in MS Edge. >>>>> Is there a way to get it to open within IE or is there a way to get >>>>> this documentation in txt format? >>>>> Thanks >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> >>> >>> >>> >> >> >> >> >> >> > > >
|
|
Thanks for this info Brian.
toggle quoted messageShow quoted text
On 11/23/2016 9:17 AM, Brian Vogel wrote: Brice,
If you're referring to the Commands Quick Reference then it is in the install folder for NVDA under the documentation folder there then under the language appropriate folder.
In my case that's C:\Program Files(x86)\NVDA\documentation\en
I put a shortcut to this folder on my desktop so that I have quick access to its contents. -- */Brian/*
*/Here is a test to find out whether your mission in life is complete. If you’re alive, it isn’t./*
/ /~ Lauren Bacall
|
|
Christopher-Mark Gilland <clgilland07@...>
I know. That was kind of the point that I was
attempting to make. Joseph has said to open IE, then while open, try launching
the quick commands help after first launching IE. What I was trying to say was,
that didn't make sense, as I agree with what you're saying, Gene, that's not
generally how file associations work. Alas, looks like Don got it resolved, so
that's good to know.
--- Christopher Gilland JAWS Certified, 2016. Training
Instructor.
toggle quoted messageShow quoted text
----- Original Message -----
Sent: Wednesday, November 23, 2016 12:50
PM
Subject: Re: [nvda] help menu
That isn't how file associations work. If a
browser is opened and another browser is the default, the default browser will
open when a file type is clicked on that the browser is supposed to
open.
Gene
----- Original Message -----
Sent: Wednesday, November 23, 2016 11:40 AM
Subject: Re: [nvda] help menu
I was gonna say. Wouldn't that just launch whatever browser in
a new window with that documentation? In this case, the user's guide? The
behavior symptoms Don's describing don't surprise me. Is NVDA
supposed to detect what browser is opened ahead of time, hince why you
said, open IE first, then launch the guide? --- Christopher
Gilland JAWS Certified, 2016. Training Instructor.
info@... Phone:
(704) 256-8010. ----- Original Message ----- From: "Don H" <lmddh50@...> To: <nvda@nvda.groups.io> Sent:
Wednesday, November 23, 2016 12:00 PM Subject: Re: [nvda] help
menu
> Sorry if I follow your instructions and have IE open
before opening the > NVDA menu then select the user guide from the help
menu it opens in Edge > not IE. > > On 11/23/2016 10:42 AM,
Joseph Lee wrote: >> Hi, >> The corrected instruction is to
go to IE, then open NVDA menu/help, then >> select the item you
want. >> Cheers, >> Joseph >> >>
-----Original Message----- >> From: nvda@nvda.groups.io
[mailto:nvda@nvda.groups.io] On Behalf Of Don H >> Sent: Wednesday,
November 23, 2016 8:35 AM >> To: nvda@nvda.groups.io >> Subject:
Re: [nvda] help menu >> >> With IE open F1 brings up the IE
help using IE. >> >> On 11/23/2016 10:14 AM, Gene
wrote: >>> Open Internet Explorer and see what happens if you
issue the command f1. >>> >>> Gene >>>
----- Original Message ----- >>> *From:* Don H <mailto:lmddh50@...> >>>
*Sent:* Wednesday, November 23, 2016 10:05 AM >>> *To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> >>>
*Subject:* Re: [nvda] help menu >>> >>> As I said
following your steps I have IE set as my default browser. >>> Help
documents still open in Edge. >>> >>> On 11/23/2016
9:58 AM, Andre Fisher wrote: >>>> 1. Press Windows key+I to go
to the Settings app. >>>> 2. Depending on which version of
Windows 10 you are using, you might >>>> need to Tab till you
hear System. Press Enter on it. >>>> 3. Use the Down Arrow
until you hear Default Apps. Press Enter 4. >>>> Press Tab
continuously till you hear Web browser: Microsoft Edge or >>>>
otherwise. >>>> 5. Press Enter and Tab to Internet
Explorer. >>>> Press Enter and close the
app. >>>> >>>> That's
it! >>>> >>>> On 11/23/16, Don H <lmddh50@... <mailto:lmddh50@...>> >>>
wrote: >>>>> Running Win 10 and have IE set as my default
browser. When I select >>>>> help within the NVDA menu
it opens the help documentation in MS Edge. >>>>> Is there a
way to get it to open within IE or is there a way to
get >>>>> this documentation in txt
format? >>>>>
Thanks >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> >>> >>> >>> >> >> >> >> >> >> > >
>
|
|
hi. k for next link and shift+k previous link. insert f7 you can list the links, press the first letter of your desired link and activate it by enter key. also u and shift+u are for next and previous unvisited links and v and shift+v are for next and previous visited links respectively. hope thats help and God bless you.
toggle quoted messageShow quoted text
On 11/23/16, Christopher-Mark Gilland <clgilland07@gmail.com> wrote: Sure. K as in kilo and shift K as in kilo instead of l and shift l.
If you wanna move by visited links, that would be V as in victor, and shift
V as in victor. --- Christopher Gilland JAWS Certified, 2016. Training Instructor.
info@gillandmarketing.com Phone: (704) 256-8010. ----- Original Message ----- From: "Don H" <lmddh50@comcast.net> To: <nvda@nvda.groups.io> Sent: Wednesday, November 23, 2016 10:38 AM Subject: [nvda] move by links
With Window Eyes when on a web page you can use the L key to move from link to link on the page. Is there a way to do this with NVDA? Did not see it on the shortcut list. Thanks
-- we have not sent you but as a mercy to the creation. holy quran, chapter 21, verse 107. in the very authentic narration is: imam hosein is the beacon of light and the ark of salvation. best website for studying islamic book in different languages al-islam.org
|
|
That isn't how file associations work. If a
browser is opened and another browser is the default, the default browser will
open when a file type is clicked on that the browser is supposed to open.
Gene
toggle quoted messageShow quoted text
----- Original Message -----
Sent: Wednesday, November 23, 2016 11:40 AM
Subject: Re: [nvda] help menu
I was gonna say. Wouldn't that just launch whatever browser in a
new window with that documentation? In this case, the user's guide? The
behavior symptoms Don's describing don't surprise me. Is NVDA supposed
to detect what browser is opened ahead of time, hince why you said, open IE
first, then launch the guide? --- Christopher Gilland JAWS
Certified, 2016. Training Instructor. info@...Phone:
(704) 256-8010. ----- Original Message ----- From: "Don H" < lmddh50@...> To: < nvda@nvda.groups.io> Sent:
Wednesday, November 23, 2016 12:00 PM Subject: Re: [nvda] help
menu > Sorry if I follow your instructions and have IE open before
opening the > NVDA menu then select the user guide from the help menu it
opens in Edge > not IE. > > On 11/23/2016 10:42 AM, Joseph
Lee wrote: >> Hi, >> The corrected instruction is to go to IE,
then open NVDA menu/help, then >> select the item you
want. >> Cheers, >> Joseph >> >>
-----Original Message----- >> From: nvda@nvda.groups.io
[mailto:nvda@nvda.groups.io] On Behalf Of Don H >> Sent: Wednesday,
November 23, 2016 8:35 AM >> To: nvda@nvda.groups.io>> Subject:
Re: [nvda] help menu >> >> With IE open F1 brings up the IE
help using IE. >> >> On 11/23/2016 10:14 AM, Gene
wrote: >>> Open Internet Explorer and see what happens if you issue
the command f1. >>> >>> Gene >>> -----
Original Message ----- >>> *From:* Don H < mailto:lmddh50@...> >>>
*Sent:* Wednesday, November 23, 2016 10:05 AM >>> *To:* nvda@nvda.groups.io < mailto:nvda@nvda.groups.io> >>>
*Subject:* Re: [nvda] help menu >>> >>> As I said
following your steps I have IE set as my default browser. >>> Help
documents still open in Edge. >>> >>> On 11/23/2016 9:58
AM, Andre Fisher wrote: >>>> 1. Press Windows key+I to go to the
Settings app. >>>> 2. Depending on which version of Windows 10
you are using, you might >>>> need to Tab till you hear System.
Press Enter on it. >>>> 3. Use the Down Arrow until you hear
Default Apps. Press Enter 4. >>>> Press Tab continuously till you
hear Web browser: Microsoft Edge or >>>>
otherwise. >>>> 5. Press Enter and Tab to Internet
Explorer. >>>> Press Enter and close the
app. >>>> >>>> That's
it! >>>> >>>> On 11/23/16, Don H < lmddh50@... < mailto:lmddh50@...>> >>>
wrote: >>>>> Running Win 10 and have IE set as my default
browser. When I select >>>>> help within the NVDA menu
it opens the help documentation in MS Edge. >>>>> Is there a
way to get it to open within IE or is there a way to get >>>>>
this documentation in txt format? >>>>>
Thanks >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> >>> >>> >>> >> >> >> >> >> >> > >
>
|
|
Christopher-Mark Gilland <clgilland07@...>
I was gonna say. Wouldn't that just launch whatever browser in a new window with that documentation? In this case, the user's guide? The behavior symptoms Don's describing don't surprise me. Is NVDA supposed to detect what browser is opened ahead of time, hince why you said, open IE first, then launch the guide? --- Christopher Gilland JAWS Certified, 2016. Training Instructor.
info@gillandmarketing.com Phone: (704) 256-8010.
toggle quoted messageShow quoted text
----- Original Message ----- From: "Don H" <lmddh50@comcast.net> To: <nvda@nvda.groups.io> Sent: Wednesday, November 23, 2016 12:00 PM Subject: Re: [nvda] help menu Sorry if I follow your instructions and have IE open before opening the NVDA menu then select the user guide from the help menu it opens in Edge not IE.
On 11/23/2016 10:42 AM, Joseph Lee wrote:
Hi, The corrected instruction is to go to IE, then open NVDA menu/help, then select the item you want. Cheers, Joseph
-----Original Message----- From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Don H Sent: Wednesday, November 23, 2016 8:35 AM To: nvda@nvda.groups.io Subject: Re: [nvda] help menu
With IE open F1 brings up the IE help using IE.
On 11/23/2016 10:14 AM, Gene wrote:
Open Internet Explorer and see what happens if you issue the command f1.
Gene ----- Original Message ----- *From:* Don H <mailto:lmddh50@comcast.net> *Sent:* Wednesday, November 23, 2016 10:05 AM *To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> *Subject:* Re: [nvda] help menu
As I said following your steps I have IE set as my default browser. Help documents still open in Edge.
On 11/23/2016 9:58 AM, Andre Fisher wrote:
1. Press Windows key+I to go to the Settings app. 2. Depending on which version of Windows 10 you are using, you might need to Tab till you hear System. Press Enter on it. 3. Use the Down Arrow until you hear Default Apps. Press Enter 4. Press Tab continuously till you hear Web browser: Microsoft Edge or otherwise. 5. Press Enter and Tab to Internet Explorer. Press Enter and close the app.
That's it!
On 11/23/16, Don H <lmddh50@comcast.net <mailto:lmddh50@comcast.net>> wrote:
Running Win 10 and have IE set as my default browser. When I select help within the NVDA menu it opens the help documentation in MS Edge. Is there a way to get it to open within IE or is there a way to get this documentation in txt format? Thanks
|
|
Christopher-Mark Gilland <clgilland07@...>
Actually Don, I thought you made yourself perfectly clear. I'm not sure why people are getting confused. --- Christopher Gilland JAWS Certified, 2016. Training Instructor.
info@gillandmarketing.com Phone: (704) 256-8010.
toggle quoted messageShow quoted text
----- Original Message ----- From: "Don H" <lmddh50@comcast.net> To: <nvda@nvda.groups.io> Sent: Wednesday, November 23, 2016 11:57 AM Subject: Re: [nvda] help menu Maybe I didn't make myself clear regarding the problem. When I open the NVDA menu move down and expand the help menu and press enter on user guide the guide opens in Edge. I have IE set as my default browser.
On 11/23/2016 10:48 AM, Gene wrote:
Does that solve the problem? I believe you were specifically asking about how to get help for Internet Explorer in Internet Explorer. For other programs where this happens, you should be able to open at least the main help document from within the program. F1 often brings it up. If not, look in the menus. When getting to know an unfamiliar program, looking through the menus is often a good way to learn many things.
Gee
*From:* Don H <mailto:lmddh50@comcast.net> *Sent:* Wednesday, November 23, 2016 10:34 AM *To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> *Subject:* Re: [nvda] help menu
With IE open F1 brings up the IE help using IE.
On 11/23/2016 10:14 AM, Gene wrote:
Open Internet Explorer and see what happens if you issue the command f1.
Gene ----- Original Message ----- *From:* Don H <mailto:lmddh50@comcast.net> *Sent:* Wednesday, November 23, 2016 10:05 AM *To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> <mailto:nvda@nvda.groups.io>
*Subject:* Re: [nvda] help menu
As I said following your steps I have IE set as my default browser. Help documents still open in Edge.
On 11/23/2016 9:58 AM, Andre Fisher wrote:
1. Press Windows key+I to go to the Settings app. 2. Depending on which version of Windows 10 you are using, you might need to Tab till you hear System. Press Enter on it. 3. Use the Down Arrow until you hear Default Apps. Press Enter 4. Press Tab continuously till you hear Web browser: Microsoft Edge or otherwise. 5. Press Enter and Tab to Internet Explorer. Press Enter and close the app.
That's it!
On 11/23/16, Don H <lmddh50@comcast.net <mailto:lmddh50@comcast.net> <mailto:lmddh50@comcast.net>>
wrote:
Running Win 10 and have IE set as my default browser. When I select help within the NVDA menu it opens the help documentation in MS Edge. Is there a way to get it to open within IE or is there a way to get this documentation in txt format? Thanks
|
|