Date   

Re: Outlook Extended: Can't read headers in meting request

Cyrille
 

Hi Daniel

Thanks for the log.

Could you also provide answers to the following questions:
* What is your version of Outlook? Did you test (if possible) on various version?
* Has this issue always been here or did it appear recently?
* When you speak about cancelled meeting request, are you referring to a message received in your Inbox informing you that a meeting that was previoulsy sent to you has been cancelled by the meeting organizer? Or are you refering to something you open from the calendar view?


Thanks.

Cheers,

Cyrille

Le 19/05/2020 à 10:25, Daniel Gartmann a écrit :

 

Hi Cyrille and Ralf,

 

A log has been sent privately. Thanks to both of you for following up so quickly.

 

Daniel

 

 

Fra: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> På vegne af Ralf Kefferpuetz
Sendt: 19. maj 2020 07:59
Til: nvda-addons@nvda-addons.groups.io
Emne: Re: [nvda-addons] Outlook Extende: Can't read headers in meting request

 

Good morning Cyrille and Daniel,

I tried to reproduce it with Office 365 but it works fine for me within cancelled and deleted appointments.

Daniel, please try to reproduce it with the steps Cyrille pointed out and come back to us with the results.

 

Cheers,

  Ralf

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Cyrille via groups.io
Sent: Montag, 18. Mai 2020 19:10
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Outlook Extende: Can't read headers in meting request

 

Hello Daniel

Thanks for reporting this issue. Any feedback from other people on this topic is also welcome.

Maybe Ralf?

To help debugging this, could you please execute the following actions:

* Ensure that your log level is on DEBUG in NVDA's General settings
* Open NVDA's python console and execute the following commands:
import globalVars
globalVars.olexDebug = True
(Note that this debug setting will not be active anymore after NVDA restart)
* Open Outlook and open a cancelled meeting request
* Press various shortcut to read headers such as Alt+1, Alt+2, etc..
* Send me the log.

Note that the log in debug mode may contain personal information about your e-mail titles, cancelled meeting request headers and content, etc. If this information is sensitive, you may want to send me directly the log (if you want) rather than on this list.

Some additional questions:
* What is your version of Outlook? Did you test (if possible) on various version?
* Has this issue always been here or did it appear recently?
* When you speak about cancelled meeting request, are you referring to a message received in your Inbox informing you that a meeting that was previoulsy sent to you has been cancelled by the meeting organizer?

I do not remember if I have checked this type of messages. And I am not sure to be able to test myself for now due to work at home. Anyway, I will try to fix it. If I do not succeed in fixing it now, I will do it as soon as I can test.

Cheers,

 

Cyrille

 

 

 

Le 18/05/2020 à 16:56, Daniel Gartmann a écrit :

 

Hi,

 

In a cancelled meeting request, I can’t use Alt+1 through Alt+0 to read the headers.

 

Is there any interest in more details? I don’t know what kind of input is needed for the authors to be able to work on a fix, so any advice appreciated.

 

Daniel

 


Re: Outlook Extended: Can't read headers in meting request

Daniel Gartmann
 

 

Hi Cyrille and Ralf,

 

A log has been sent privately. Thanks to both of you for following up so quickly.

 

Daniel

 

 

Fra: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> På vegne af Ralf Kefferpuetz
Sendt: 19. maj 2020 07:59
Til: nvda-addons@nvda-addons.groups.io
Emne: Re: [nvda-addons] Outlook Extende: Can't read headers in meting request

 

Good morning Cyrille and Daniel,

I tried to reproduce it with Office 365 but it works fine for me within cancelled and deleted appointments.

Daniel, please try to reproduce it with the steps Cyrille pointed out and come back to us with the results.

 

Cheers,

  Ralf

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Cyrille via groups.io
Sent: Montag, 18. Mai 2020 19:10
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Outlook Extende: Can't read headers in meting request

 

Hello Daniel

Thanks for reporting this issue. Any feedback from other people on this topic is also welcome.

Maybe Ralf?

To help debugging this, could you please execute the following actions:

* Ensure that your log level is on DEBUG in NVDA's General settings
* Open NVDA's python console and execute the following commands:
import globalVars
globalVars.olexDebug = True
(Note that this debug setting will not be active anymore after NVDA restart)
* Open Outlook and open a cancelled meeting request
* Press various shortcut to read headers such as Alt+1, Alt+2, etc..
* Send me the log.

Note that the log in debug mode may contain personal information about your e-mail titles, cancelled meeting request headers and content, etc. If this information is sensitive, you may want to send me directly the log (if you want) rather than on this list.

Some additional questions:
* What is your version of Outlook? Did you test (if possible) on various version?
* Has this issue always been here or did it appear recently?
* When you speak about cancelled meeting request, are you referring to a message received in your Inbox informing you that a meeting that was previoulsy sent to you has been cancelled by the meeting organizer?

I do not remember if I have checked this type of messages. And I am not sure to be able to test myself for now due to work at home. Anyway, I will try to fix it. If I do not succeed in fixing it now, I will do it as soon as I can test.

Cheers,

 

Cyrille

 

 

 

Le 18/05/2020 à 16:56, Daniel Gartmann a écrit :

 

Hi,

 

In a cancelled meeting request, I can’t use Alt+1 through Alt+0 to read the headers.

 

Is there any interest in more details? I don’t know what kind of input is needed for the authors to be able to work on a fix, so any advice appreciated.

 

Daniel

 


Re: Outlook Extende: Can't read headers in meting request

Ralf Kefferpuetz
 

Good morning Cyrille and Daniel,

I tried to reproduce it with Office 365 but it works fine for me within cancelled and deleted appointments.

Daniel, please try to reproduce it with the steps Cyrille pointed out and come back to us with the results.

 

Cheers,

  Ralf

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Cyrille via groups.io
Sent: Montag, 18. Mai 2020 19:10
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Outlook Extende: Can't read headers in meting request

 

Hello Daniel

Thanks for reporting this issue. Any feedback from other people on this topic is also welcome.

Maybe Ralf?

To help debugging this, could you please execute the following actions:

* Ensure that your log level is on DEBUG in NVDA's General settings
* Open NVDA's python console and execute the following commands:
import globalVars
globalVars.olexDebug = True
(Note that this debug setting will not be active anymore after NVDA restart)
* Open Outlook and open a cancelled meeting request
* Press various shortcut to read headers such as Alt+1, Alt+2, etc..
* Send me the log.

Note that the log in debug mode may contain personal information about your e-mail titles, cancelled meeting request headers and content, etc. If this information is sensitive, you may want to send me directly the log (if you want) rather than on this list.

Some additional questions:
* What is your version of Outlook? Did you test (if possible) on various version?
* Has this issue always been here or did it appear recently?
* When you speak about cancelled meeting request, are you referring to a message received in your Inbox informing you that a meeting that was previoulsy sent to you has been cancelled by the meeting organizer?

I do not remember if I have checked this type of messages. And I am not sure to be able to test myself for now due to work at home. Anyway, I will try to fix it. If I do not succeed in fixing it now, I will do it as soon as I can test.

Cheers,

 

Cyrille

 

 

 

Le 18/05/2020 à 16:56, Daniel Gartmann a écrit :

 

Hi,

 

In a cancelled meeting request, I can’t use Alt+1 through Alt+0 to read the headers.

 

Is there any interest in more details? I don’t know what kind of input is needed for the authors to be able to work on a fix, so any advice appreciated.

 

Daniel

 


Re: Compatible Microsoft Speech mobile

Marco Oros
 

saying letters.

So, try use Windows Narator and press one letter. So, in Narator letters are pronounced good, as in MS Speech mobile addon.


Re: Console Timer and NVDA 2019.3+

Timothy
 


Believe your timing issue is found under NVDA Setting --> Advanced --> Caret movement timeout (in ms), though I am not sure if it corresponds directly to what the console timer add-on provided having never used it (see section 11.1.16 of the NVDA user guide).
 
Timothy
 

----- Original Message -----
Sent: Monday, May 18, 2020 2:23 PM
Subject: [nvda-addons] Console Timer and NVDA 2019.3+

Hi

What is the compatibility status for the Console Timer add-on with Python 3 versions of NVDA? I am a sysadmin who still finds this add-on useful as network delay between my computer and another server can often times mess up text navigation in SSH terminals.

Cheers,

Noah


Re: Compatible Microsoft Speech mobile

Timothy
 

Ah, yes. There's an issue for this in NVDA's repository, though I don't think anyone has contributed code for it:
https://github.com/nvaccess/nvda/issues/8237

Timothy

----- Original Message -----
From: "Marco Oros" <marco.oros93@...>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Monday, May 18, 2020 4:22 PM
Subject: Re: [nvda-addons] Compatible Microsoft Speech mobile


This bad pronunciation of typing echo by microsoft voices.


Re: Compatible Microsoft Speech mobile

Brian's Mail list account
 

Is there a dictionary, or are we talking bout the way they say letters?
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "Marco Oros" <marco.oros93@...>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Monday, May 18, 2020 9:22 PM
Subject: Re: [nvda-addons] Compatible Microsoft Speech mobile


This bad pronunciation of typing echo by microsoft voices.


Re: Compatible Microsoft Speech mobile

Marco Oros
 

This bad pronunciation of typing echo by microsoft voices.


Re: Console Timer and NVDA 2019.3+

Adriani Botez
 

This addon is not needed anymore. Nvda works well now regarding to thiss. The addon is therefore deprecated as far as I know

Best
Adriani


Von meinem iPhone gesendet

Am 18.05.2020 um 20:23 schrieb Noah Carver via groups.io <ntclists@...>:

Hi

What is the compatibility status for the Console Timer add-on with Python 3 versions of NVDA? I am a sysadmin who still finds this add-on useful as network delay between my computer and another server can often times mess up text navigation in SSH terminals.

Cheers,

Noah


Console Timer and NVDA 2019.3+

 

Hi

What is the compatibility status for the Console Timer add-on with Python 3 versions of NVDA? I am a sysadmin who still finds this add-on useful as network delay between my computer and another server can often times mess up text navigation in SSH terminals.

Cheers,

Noah


Re: Outlook Extende: Can't read headers in meting request

Ralf Kefferpuetz
 

I’m Going to check this tomorrow morning 😊

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Cyrille via groups.io
Sent: Montag, 18. Mai 2020 19:10
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Outlook Extende: Can't read headers in meting request

 

Hello Daniel

Thanks for reporting this issue. Any feedback from other people on this topic is also welcome.

Maybe Ralf?

To help debugging this, could you please execute the following actions:

* Ensure that your log level is on DEBUG in NVDA's General settings
* Open NVDA's python console and execute the following commands:
import globalVars
globalVars.olexDebug = True
(Note that this debug setting will not be active anymore after NVDA restart)
* Open Outlook and open a cancelled meeting request
* Press various shortcut to read headers such as Alt+1, Alt+2, etc..
* Send me the log.

Note that the log in debug mode may contain personal information about your e-mail titles, cancelled meeting request headers and content, etc. If this information is sensitive, you may want to send me directly the log (if you want) rather than on this list.

Some additional questions:
* What is your version of Outlook? Did you test (if possible) on various version?
* Has this issue always been here or did it appear recently?
* When you speak about cancelled meeting request, are you referring to a message received in your Inbox informing you that a meeting that was previoulsy sent to you has been cancelled by the meeting organizer?

I do not remember if I have checked this type of messages. And I am not sure to be able to test myself for now due to work at home. Anyway, I will try to fix it. If I do not succeed in fixing it now, I will do it as soon as I can test.

Cheers,

 

Cyrille

 

 

 

Le 18/05/2020 à 16:56, Daniel Gartmann a écrit :

 

Hi,

 

In a cancelled meeting request, I can’t use Alt+1 through Alt+0 to read the headers.

 

Is there any interest in more details? I don’t know what kind of input is needed for the authors to be able to work on a fix, so any advice appreciated.

 

Daniel

 


Re: Outlook Extende: Can't read headers in meting request

Cyrille
 

Hello Daniel

Thanks for reporting this issue. Any feedback from other people on this topic is also welcome.

Maybe Ralf?

To help debugging this, could you please execute the following actions:

* Ensure that your log level is on DEBUG in NVDA's General settings
* Open NVDA's python console and execute the following commands:
import globalVars
globalVars.olexDebug = True
(Note that this debug setting will not be active anymore after NVDA restart)
* Open Outlook and open a cancelled meeting request
* Press various shortcut to read headers such as Alt+1, Alt+2, etc..
* Send me the log.

Note that the log in debug mode may contain personal information about your e-mail titles, cancelled meeting request headers and content, etc. If this information is sensitive, you may want to send me directly the log (if you want) rather than on this list.

Some additional questions:
* What is your version of Outlook? Did you test (if possible) on various version?
* Has this issue always been here or did it appear recently?
* When you speak about cancelled meeting request, are you referring to a message received in your Inbox informing you that a meeting that was previoulsy sent to you has been cancelled by the meeting organizer?

I do not remember if I have checked this type of messages. And I am not sure to be able to test myself for now due to work at home. Anyway, I will try to fix it. If I do not succeed in fixing it now, I will do it as soon as I can test.

Cheers,


Cyrille




Le 18/05/2020 à 16:56, Daniel Gartmann a écrit :

 

Hi,

 

In a cancelled meeting request, I can’t use Alt+1 through Alt+0 to read the headers.

 

Is there any interest in more details? I don’t know what kind of input is needed for the authors to be able to work on a fix, so any advice appreciated.

 

Daniel

 


Re: bme2 nvda addon: 2020.04.4 is here

Iván Novegil
 

Hi.


Download link is still broken... Gianluca, could you take a look on it? Maybe you've forgotten of pushing the file? On the packages folder there isn't any file named simply 2020.04.4, but 2020.04.4_ReleaseCandidate and 2020.04.4_pre-release.


Regards.

Iván Novegil Cancelas
Editor
ivan.novegil@...


NVDA.es Logo
Comunidad hispanohablante de NVDA | Proyecto NVDA.es
- www.NVDA.es
- @nvda_es

Usuario do NVDA en galego

***Esta mensaxe e/ou os seus adxuntos están dirixidos ao seu destinatario e poden conter información privilexiada ou confidencial. A utilización, copia ou divulgación dos mesmos por parte de alguén diferente do destinatario mencionado non están permitidas sen autorización. Se recibiu esta mensaxe por erro pregámoslle o comunique por esta mesma vía e a destrúa.***

O 15/05/2020 á(s) 0:38, DaVid escribiu:

Hi!

The link available in the readme, provided to download the packaged
addon, is not working. It says file not found.

I suggest you to use the releases feature of github, you can get the
direct link of the latest release. Currently you have releasess, but
only the source code can be downloaded there.
You could even use automatic process of appveyor if you want.

Regards,
DaVid.




Outlook Extende: Can't read headers in meting request

Daniel Gartmann
 

 

Hi,

 

In a cancelled meeting request, I can’t use Alt+1 through Alt+0 to read the headers.

 

Is there any interest in more details? I don’t know what kind of input is needed for the authors to be able to work on a fix, so any advice appreciated.

 

Daniel

 


[nvda-devel] About QT4 accessibility

Alberto Buffolino
 

Hi all,
main question: is there a qtaccessiblewidgets4.dll publicly available and redistributable?
Explanation: in these years I have encountered many programs with QT4 GUI - the old Calibre, SPFlashTool (familiar to Android modders), Lightscreen, Lazesoft Recovery Suite, and others that I forgot - for which putting that DLL in a folder called "accessible" in their main path magically turns them from completely inaccessible to at least usable... but I got this DLL from an old Kindle for PC installation, so it obviously signed by Amazon LLc, that sounds very bad for my previous question. 😅
If there is a way to compile a generic version, I'm thinking, maybe we could make an add-on for this situation, or even include it in NVDA directly, like which was done for JAB...
I know that with QT5 the situation is better, but in my experience QT4 is still largely present and, unfortunately, often in software quite specialised.
Just a thought...
Alberto


Re: perform tasks while add-on install

Alberto Buffolino
 

Christopher Pross, il 18/05/2020 14.33, ha scritto:
a short question, it is possible to do some tasks while add-on installations?
Alberto:
Hi Christopher,
yes, there is onInstall() function, called during add-on installation. It must be contained in installTasks.py, that must be located in add-on root directory (where is manifest.ini, to be clear).
There is onUninstall() too.
I need to register a python package in the python enviroment from nvda for my current project. and I don't know how to do that, while the add-on installing.
Alberto:
hmm, what you mean exactly with "register a python package"?
Because you cannot (you should not) register a package in strict and static sense. The thing usually done is:
- include the package sources/binaries in a folder called "mypackage" (for example);
- put this folder in a folder called "lib" (for example) in add-on root directory;
- where necessary, do:
import sys
libPath = os.path.join(os.path.dirname(__file__), "..", "lib")
sys.path.append(libPath)
import mypackage
del sys.path[-1]
...your code using mypackage...
At my knowledge, this should be the better organized and most secure way.
Alberto


Re: Compatible Microsoft Speech mobile

Andre Fisher
 

Hi.

What exactly is "not very good" about it?


perform tasks while add-on install

Christopher Pross
 

Hey,

a short question, it is possible to do some tasks while add-on installations?

I need to register a python package in the python enviroment from nvda for my current project. and I don't know how to do that, while the add-on installing.

Any ideas?


Compatible Microsoft Speech mobile

Marco Oros
 

Hello.

I don't know, if somebody works on Speech mobile for NVDA.

It will be good to improve It for new NVDA compatibility. It was good add-on for NVDA users, because Windows Onecore voices installed with NVDA are not very good.

Thank You.

Best regards

Marco Oros


Re: FW: [program-l] NVDA add-on development questions

 

Hi,

The following message will contain geeky material, so please hold on:

An NVDA object is NVDA’s way of looking at graphical elements. A given NVDA object has a name, role, value, states, location, among other things. But in order to represent what is seen as “real” by users, it also remembers what kind of object it is: MSAA/IAccessible, UI Automation, JAB, and many others, as evidenced by developer info listing attributes coming from these API’s. As Javi pointed out, changing the attributes of NVDA objects will not change what accessibility API’s say about a particular control – it just tells NVDA objects to act like something else, give users something other than what is actually shown on screen, among other tricks.

Technical: an NVDA object is an abstract representation of a user interface element on screen – visible or invisible, differing roles, across apps, across accessibility API’s, and many other things. A base class named NVDAObjects.NVDAObject is responsible for specifying the blueprints of this abstract class: name, role, states, app module, events, among others. Although the base NVDA object class isn’t marked as an abstract base class (ABC), you don’t really want to instantiate this class (technically, you can but under specific circumstances such as providing gestures), and several descriptors in this base class are marked with “NotImplementedError”.

Because the base NVDA object class is primitive at best, you won’t find them in real life; rather ,you’ll interact with one concrete implementation, which serves as the “real” NVDA object: NVDAObjects.window.Window. Every control you see (or can interact with) on screen is a window (including windows that are invisible). Apart from specific exceptions, every window is represented by a window handle (hwnd). Window handles shield apps (including NVDA) from direct manipulation, and without this shield, it introduces security problems. Window handles are also important for NVDA (and the next component described below) as NVDA can use it to query certain things about a window or a control such as window text and such. Unless you need a way to direct Windows to talk to controls in a controlled fashion, you won’t have to interact with window objects.

Window handle is also needed to construct what’s termed “API class”. An API class is a specification of an NVDA object based on an accessibility API’s notion of an element. Each API class (or for that matter, accessibility API’s) have differing notions as to what the screen element should say to screen readers (technically termed “accessibility clients”) and how apps and assistive technologies communicate. In short, an accessibility API such as MSAA and UI Automation serves as a “bridge” between apps (termed “servers”) and screen readers such as NVDA (clients), and as such, one of their duties is to provide information about a graphical element to NVDA based on what the app reports about a given control (now you know why I and others get frustrated about UIA implementation issues from Microsoft). Again, without a window handle for the element in question, accessibility API’s cannot do its job, and for NVDA, it cannot instantiate API classes.

Another thing an API class must have is a way to talk to the control in question via accessibility API. Each API class includes a reference to the control as seen by accessibility API. For MSAA/IAccessible, it is object.IAccessibleObject; for UIA, it is object.UIAElement. And since API classes are objects representing a control as reported by the app through accessibility API, NVDA receives directions from API’s as to how to present things such as name, role, states, location, value, among other things. Because apps are imperfect (think about what I just said for a second before moving on), information reported by IAccessible/UIA/JAB might be incomplete or incorrect; for this reason, NVDA employs tricks to provide more accurate information to the best of a developer’s knowledge (for a practical example, see Windows 10 App Essentials add-on, and many other examples from community add-ons website). And this last family of classes is what NVDA ships with, and can be used by add-ons for specific purposes (this last point is called an “overlay class”).

There is a special family of NVDA objects that doesn’t take a window handle as a required constructor argument: behaviors. Behavior classes are used to teach NVDA as to how to behave for specific controls such as terminal windows (announce incoming text automatically if given a chance), notification messages and alerts, table navigation, and auto-suggest accessibility (playing a sound when suggestions appear). Because behavior classes are meant to enhance user experience, they don’t require window handles or other fancy footwork to get them to work; rather, they are added to existing API/overlay classes (see UIA console code for practical examples).

Cheers,

Joseph

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Javi Domínguez
Sent: Sunday, May 17, 2020 1:18 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] FW: [program-l] NVDA add-on development questions

 

Hello, Adil.

I think that's a typical beginner mistake. You've done:

editBox = api.getFocusObject ()

and you thin that editBox it is the authentic, original object, that of the applicationn but no, editBox is a virtual object created by NVDA with the attributes that it has been able to extract from the application object.

All NVDAObjects are reflections of the original objects, you can't act on the object of the application modifying the NVDA objects.

If you do:


editBox.value = "some text

you make the user see "some text", but the edit box in the screen, the reflected object, the source, I don't know how to say it, doesn't change.

So you have to call the operating system through the winUser module, as James has explained to you.


This is what I think but there are people here who know much more than I do. Correct me if I'm wrong, please.

Greetings

Javi Dominguez

El 15/05/2020 a las 20:44, Adil Shaikh escribió:

thanks to everyone who answered my query. 
I got that part of the add-on working. now, I am trying to add the selected text to a third party application.  initially, I  was considering to use clipboard to pass the selected text to third party application by just using simple copy and paste. but it doesn't feel quite right to me as it messes up with the clipboard content.  

I've already tried this code:

editBox = api.getFocusObject ()

editBox.value = "some text

it's not working. 

thanks josephly for forwarding my post to this mailing list.