Hi,

Resource Monitor uses psutil module.

To use external Python modules, you must copy the contents of the module to the place where you need to use it. For example, to use psutil inside a global plugin named “something”, you must copy the psutil module folder itself to globalPlugins/something and import it from __init__.py. This will work well if the module uses Python standard libraries that ships with NVDA (as part of its package process, Python will call py2exe to package NVDA modules and dependencies inside an executable archive powered by NSIS, as py2exe will pick up libraires that NVDA and its dependencies import).

Cheers,

Joseph

Ok I am stuck.  Is there some way to install packages because so far nothing I do has made it so I can use the following packages in a plugin

Aenum, and pillow. 

If I was writing a regular python program I would just pip install the packages and be done.  Since this is enclosed in nvda this does not work.  I don’t see anything in the development documents about this problem.   Is it that no one uses external packages with their plugins?  That is a big shocking.

Ken

Ok that makes since.  And it works partly.   I also need to use the PIL library so when I did the old plugin I put the package for PIL and the package for aenum in the folder. And then referenced them just like I would any other time.  Now that is not working.  The following is the code I used before what do I need to do now.  Is there a better way to include two packages that are not installed with NVDA.

PLUGIN_DIR = os.path.dirname(__file__)

# Add bundled copy of PIL to module search path.

sys.path.append(os.path.join(PLUGIN_DIR, "PIL"))

import ImageGrab

del sys.path[-1]

I have another set of this code in graphit.py to import from aenum but it used to be

From aenum import IntFlag

From aenum import enum

Now that will not work.  I tried doing all kinds of things for the above problem but I am at a loss how to fix it.  Is there a way to install packages into plugins now or is there some python way to fix this.

Hi,

You must use relative import like so:

from . import modname

This, by the way, also works in Python 2.

Cheers,

Joseph

I think this changed in python3 and I usually have to mess around until it works. I don’t know the directory structure you have, but for something like

\addon\appModules\appllicationName

If you then have __init__.py and myModule.py and myFunctions.py you need to tell it to look in the current directory for other files in that folder such as

import .myModule

from .myFunctions import makeBraille, makeSpeech

I have an old global plug in for before NVDA was switched to  3.x   It worked fine and I have fixed all the problems that have to do with the difference in python types.

Here is the problem I have several python files in the global plugin.  The

__init__.py file has an import like this:

Import myclass

Then there is a file in the same folder

Myclass.py

The global plugin can not find the file I am importing.  It used to work fine is there some new thing I have to do to let the global plugin know where my other classes are? Note I have my global plugin in a folder like myplugin under the developer scratchpad folder and I know it is at least being found because if I take the class I am importing out the key press works fine and presents the message I want it to.     In the log though it says it can’t find myclass module.

Ken

Ok I am stuck.  Is there some way to install packages because so far nothing I do has made it so I can use the following packages in a plugin

Aenum, and pillow. 

If I was writing a regular python program I would just pip install the packages and be done.  Since this is enclosed in nvda this does not work.  I don’t see anything in the development documents about this problem.   Is it that no one uses external packages with their plugins?  That is a big shocking.

Ken

Ok that makes since.  And it works partly.   I also need to use the PIL library so when I did the old plugin I put the package for PIL and the package for aenum in the folder. And then referenced them just like I would any other time.  Now that is not working.  The following is the code I used before what do I need to do now.  Is there a better way to include two packages that are not installed with NVDA.

PLUGIN_DIR = os.path.dirname(__file__)

# Add bundled copy of PIL to module search path.

sys.path.append(os.path.join(PLUGIN_DIR, "PIL"))

import ImageGrab

del sys.path[-1]

I have another set of this code in graphit.py to import from aenum but it used to be

From aenum import IntFlag

From aenum import enum

Now that will not work.  I tried doing all kinds of things for the above problem but I am at a loss how to fix it.  Is there a way to install packages into plugins now or is there some python way to fix this.

Hi,

You must use relative import like so:

from . import modname

This, by the way, also works in Python 2.

Cheers,

Joseph

I think this changed in python3 and I usually have to mess around until it works. I don’t know the directory structure you have, but for something like

\addon\appModules\appllicationName

If you then have __init__.py and myModule.py and myFunctions.py you need to tell it to look in the current directory for other files in that folder such as

import .myModule

from .myFunctions import makeBraille, makeSpeech

I have an old global plug in for before NVDA was switched to  3.x   It worked fine and I have fixed all the problems that have to do with the difference in python types.

Here is the problem I have several python files in the global plugin.  The

__init__.py file has an import like this:

Import myclass

Then there is a file in the same folder

Myclass.py

The global plugin can not find the file I am importing.  It used to work fine is there some new thing I have to do to let the global plugin know where my other classes are? Note I have my global plugin in a folder like myplugin under the developer scratchpad folder and I know it is at least being found because if I take the class I am importing out the key press works fine and presents the message I want it to.     In the log though it says it can’t find myclass module.

Ken

Ok that makes since.  And it works partly.   I also need to use the PIL library so when I did the old plugin I put the package for PIL and the package for aenum in the folder. And then referenced them just like I would any other time.  Now that is not working.  The following is the code I used before what do I need to do now.  Is there a better way to include two packages that are not installed with NVDA.

PLUGIN_DIR = os.path.dirname(__file__)

# Add bundled copy of PIL to module search path.

sys.path.append(os.path.join(PLUGIN_DIR, "PIL"))

import ImageGrab

del sys.path[-1]

I have another set of this code in graphit.py to import from aenum but it used to be

From aenum import IntFlag

From aenum import enum

Now that will not work.  I tried doing all kinds of things for the above problem but I am at a loss how to fix it.  Is there a way to install packages into plugins now or is there some python way to fix this.

Hi,

You must use relative import like so:

from . import modname

This, by the way, also works in Python 2.

Cheers,

Joseph

I think this changed in python3 and I usually have to mess around until it works. I don’t know the directory structure you have, but for something like

\addon\appModules\appllicationName

If you then have __init__.py and myModule.py and myFunctions.py you need to tell it to look in the current directory for other files in that folder such as

import .myModule

from .myFunctions import makeBraille, makeSpeech

I have an old global plug in for before NVDA was switched to  3.x   It worked fine and I have fixed all the problems that have to do with the difference in python types.

Here is the problem I have several python files in the global plugin.  The

__init__.py file has an import like this:

Import myclass

Then there is a file in the same folder

Myclass.py

The global plugin can not find the file I am importing.  It used to work fine is there some new thing I have to do to let the global plugin know where my other classes are? Note I have my global plugin in a folder like myplugin under the developer scratchpad folder and I know it is at least being found because if I take the class I am importing out the key press works fine and presents the message I want it to.     In the log though it says it can’t find myclass module.

Ken

I cannot currently work on figuring this out, but if I don't respond to you by next week, please ping me.

On Sat, Jan 1, 2022 at 3:57 AM Héctor Javier Benítez Corredera <hebolah@...> wrote:

Hello, first of all happy new year to everyone.
I would like to see if someone can give me a hand.

I need to have the checklistboxes that NVDA has in an external program
and well I managed to port the necessary from NVDA to my program and it
works.

But I find that it only works in 32 Bits and not in 64 Bits.

I think it's all about ctypes and honestly this issue is completely out
of my hands.
I share with you an example with a small window that brings a
checklistbox accessible in 32 bits for Python and wxpython 4.1.1.

I would like it to work indifferently in 32 and 64 bits.

https://www.dropbox.com/s/qcojipr7zggdwcf/checklistbox_accesible.py?dl=1

I'm sharing this here because coming from NVDA development I thought I
could get some help here.

I apologize if this is considered off-topic.

Thank you very much in advance.

Regards

--

Derek Riemer
Improving the world one byte at a time!        ⠠⠊⠍⠏⠗⠕⠧⠬ ⠮ ⠸⠺ ⠐⠕ ⠃⠽⠞⠑ ⠁⠞ ⠁ ⠐⠞⠖
•    Accessibility enthusiast.
•    Proud user of the NVDA screen reader.
•    Open source enthusiast.
•    Skier.

•    Personal website: https://derekriemer.com

Will this work with Notepad and other apps that use ribbons?

Roger







On 1/13/2022 9:14 AM, Alberto Buffolino wrote:

Hi all,
as you may have read on NVDA general list, after a restricted testing phase, I released to the public a new add-on, to simplify exploration of Ribbon menu, in Office 2019, 365 and 2021 (for the moment).
Just install, open an Office application, press Alt... and familiarize with new menu layout (an enhanced version of object navigation, as advanced users will see).
It's in dev state, but it already works quite well, in my opinion.
Remaining problems concern primarily how to set focus in particular circumstances (forceFocus method), and I'd be very grateful if someone could suggest a better solution than mine (focusing a previous obj and then simulating a moving gesture, substantially).
Latest build is at:
https://github.com/ABuffEr/ribbonExplorer/releases/download/dev/ribbonExplorer-20220112-dev.nvda-addon
and repository at:
https://github.com/ABuffEr/ribbonExplorer/
Good tests 🙂
Alberto




.

Hi,

You must use relative import like so:

from . import modname

This, by the way, also works in Python 2.

Cheers,

Joseph

I think this changed in python3 and I usually have to mess around until it works. I don’t know the directory structure you have, but for something like

\addon\appModules\appllicationName

If you then have __init__.py and myModule.py and myFunctions.py you need to tell it to look in the current directory for other files in that folder such as

import .myModule

from .myFunctions import makeBraille, makeSpeech

I have an old global plug in for before NVDA was switched to  3.x   It worked fine and I have fixed all the problems that have to do with the difference in python types.

Here is the problem I have several python files in the global plugin.  The

__init__.py file has an import like this:

Import myclass

Then there is a file in the same folder

Myclass.py

The global plugin can not find the file I am importing.  It used to work fine is there some new thing I have to do to let the global plugin know where my other classes are? Note I have my global plugin in a folder like myplugin under the developer scratchpad folder and I know it is at least being found because if I take the class I am importing out the key press works fine and presents the message I want it to.     In the log though it says it can’t find myclass module.

Ken

I think this changed in python3 and I usually have to mess around until it works. I don’t know the directory structure you have, but for something like

\addon\appModules\appllicationName

If you then have __init__.py and myModule.py and myFunctions.py you need to tell it to look in the current directory for other files in that folder such as

import .myModule

from .myFunctions import makeBraille, makeSpeech

I have an old global plug in for before NVDA was switched to  3.x   It worked fine and I have fixed all the problems that have to do with the difference in python types.

Here is the problem I have several python files in the global plugin.  The

__init__.py file has an import like this:

Import myclass

Then there is a file in the same folder

Myclass.py

The global plugin can not find the file I am importing.  It used to work fine is there some new thing I have to do to let the global plugin know where my other classes are? Note I have my global plugin in a folder like myplugin under the developer scratchpad folder and I know it is at least being found because if I take the class I am importing out the key press works fine and presents the message I want it to.     In the log though it says it can’t find myclass module.

Ken

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Travis Roth
Sent: Friday, January 14, 2022 10:04 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] A global plugin problem

I think this changed in python3 and I usually have to mess around until it works. I don’t know the directory structure you have, but for something like

\addon\appModules\appllicationName

If you then have __init__.py and myModule.py and myFunctions.py you need to tell it to look in the current directory for other files in that folder such as

import .myModule

from .myFunctions import makeBraille, makeSpeech

I have an old global plug in for before NVDA was switched to  3.x   It worked fine and I have fixed all the problems that have to do with the difference in python types.

Here is the problem I have several python files in the global plugin.  The

__init__.py file has an import like this:

Import myclass

Then there is a file in the same folder

Myclass.py

The global plugin can not find the file I am importing.  It used to work fine is there some new thing I have to do to let the global plugin know where my other classes are? Note I have my global plugin in a folder like myplugin under the developer scratchpad folder and I know it is at least being found because if I take the class I am importing out the key press works fine and presents the message I want it to.     In the log though it says it can’t find myclass module.

Ken

I have an old global plug in for before NVDA was switched to  3.x   It worked fine and I have fixed all the problems that have to do with the difference in python types.

Here is the problem I have several python files in the global plugin.  The

__init__.py file has an import like this:

Import myclass

Then there is a file in the same folder

Myclass.py

The global plugin can not find the file I am importing.  It used to work fine is there some new thing I have to do to let the global plugin know where my other classes are? Note I have my global plugin in a folder like myplugin under the developer scratchpad folder and I know it is at least being found because if I take the class I am importing out the key press works fine and presents the message I want it to.     In the log though it says it can’t find myclass module.

Ken

I don't have a problem with ribbons in Office, but I'm glad that such an
add-on was created. Thank you very much. It even works well in Office 2016.

kind regards - Sylwek

W dniu 13.01.2022 o 16:14, Alberto Buffolino pisze:
> Hi all,
> as you may have read on NVDA general list, after a restricted testing
> phase, I released to the public a new add-on, to simplify exploration
> of Ribbon menu, in Office 2019, 365 and 2021 (for the moment).
> Just install, open an Office application, press Alt... and familiarize
> with new menu layout (an enhanced version of object navigation, as
> advanced users will see).
> It's in dev state, but it already works quite well, in my opinion.
> Remaining problems concern primarily how to set focus in particular
> circumstances (forceFocus method), and I'd be very grateful if someone
> could suggest a better solution than mine (focusing a previous obj and
> then simulating a moving gesture, substantially).
> Latest build is at:
> https://github.com/ABuffEr/ribbonExplorer/releases/download/dev/ribbonExplorer-20220112-dev.nvda-addon
>
> and repository at:
> https://github.com/ABuffEr/ribbonExplorer/
> Good tests 🙂
> Alberto
>
>
>
>
>

Hi all,
as you may have read on NVDA general list, after a restricted testing phase, I released to the public a new add-on, to simplify exploration of Ribbon menu, in Office 2019, 365 and 2021 (for the moment).
Just install, open an Office application, press Alt... and familiarize with new menu layout (an enhanced version of object navigation, as advanced users will see).
It's in dev state, but it already works quite well, in my opinion.
Remaining problems concern primarily how to set focus in particular circumstances (forceFocus method), and I'd be very grateful if someone could suggest a better solution than mine (focusing a previous obj and then simulating a moving gesture, substantially).
Latest build is at:
https://github.com/ABuffEr/ribbonExplorer/releases/download/dev/ribbonExplorer-20220112-dev.nvda-addon
and repository at:
https://github.com/ABuffEr/ribbonExplorer/
Good tests 🙂
Alberto

Hi,

I must say this is one of the well-documented add-ons as far as source code is concerned. A note about object presentation type at the beginning was really helpful, too.

Regarding license: I understand that this add-on is licensed under GNU GPL 3, which is incompatible with GPL 2. Have you considered re-licensing the add-on?

Subsequent to the publication of the add-on dev snapshot, there has been a discussion on the users list about using native interface versus an add-on like this (see the NvDA list archive for details). The only thing I would add is that at least give folks a chance to demonstrate their skills with an add-on like this - who knows, it might be useful for some.

Cheers,

Joseph