Skip to content

Restore handytech COM server#8213

Merged
michaelDCurran merged 5 commits into
masterfrom
restoreHandytechServer
May 16, 2018
Merged

Restore handytech COM server#8213
michaelDCurran merged 5 commits into
masterfrom
restoreHandytechServer

Conversation

@michaelDCurran

Copy link
Copy Markdown
Member

Link to issue number:

None.

Summary of the issue:

Although NVDA now supports Handytech braille displays natively, user still must use the old Handytech COM server driver if they want auto detection of Handytech displays, and support for ATC.
Recently the Handytech COM server was removed from NVDA making this impossible.
Handytech has requested we reintroduce this for now until Braille Display Auto Detection and ATC support is in NVDA.

Description of how this pull request fixes the issue:

The PR does the following:

  1. Adds the Handytech files back into miscDeps.
  2. Adds the Handytech specific COM registration back into NVDA's manifest.
  3. Upgrades comtypes from 1.1.3 to 1.1.4, which fixes a bug causing the Handytech COM server to not work correctly. This was a regression from comtypes 0.6.3.

Testing performed:

It would be good if @FelixGruetzmacher could test the following build with the Handytech COM server driver and ensure everything works correctly:
https://ci.appveyor.com/api/buildjobs/94ol47g4nf1wfbk2/artifacts/output%2Fnvda_snapshot_try-restoreHandytechServer-15069%2C7c747931.exe

Known issues with pull request:

None.

Change log entry:

Bug fixes:

  • It is again possible to use the older Handytech braille display driver in order to access some manufacturer-specific features.

@LeonarddeR

Copy link
Copy Markdown
Collaborator

@michaelDCurran commented on 30 apr. 2018 05:59 CEST:

Bug fixes:

  • It is again possible to use the older Handytech braille display driver in order to access some manufacturer-specific features.

It would be good to explicitly state that this applies to the handy tech driver that is shipped in their add-on.

@LeonarddeR LeonarddeR left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There used to be an entry in readme.md, I don't insist on having that one restored though.

It would be good to have this incubate in next to make sure the comtypes update doesn't regress something else.

@zstanecic

zstanecic commented Apr 30, 2018 via email

Copy link
Copy Markdown
Contributor

@michaelDCurran

michaelDCurran commented Apr 30, 2018 via email

Copy link
Copy Markdown
Member Author

@LeonarddeR

Copy link
Copy Markdown
Collaborator

I agree with @michaelDCurran.

michaelDCurran added a commit that referenced this pull request May 1, 2018
michaelDCurran added a commit that referenced this pull request May 1, 2018
@LeonarddeR

LeonarddeR commented May 1, 2018

Copy link
Copy Markdown
Collaborator

I'm afraid comtypes 1.1.4 introduces another regression, see enthought/comtypes#145. I've seen this error in Outlook as well as when creating new comtypes wrappers.

To reproduce:

comtypes.client.CreateObject("HtBrailleDriverServer.HtBrailleDriver")

@LeonarddeR

Copy link
Copy Markdown
Collaborator

It looks like enthought/comtypes@98f6a42 is the culprit. I suggest reverting comtypes to enthought/comtypes@edbaf3b

michaelDCurran added a commit that referenced this pull request May 1, 2018
Comment thread readme.md
For reference, the following dependencies are included in Git submodules:

* [comtypes](https://github.com/enthought/comtypes), version 1.1.3
* [comtypes](https://github.com/enthought/comtypes), version 1.1.4

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Strictly spoken, tthis is not true any more. However functionally, this is equal to 1.1.4 minus the gen_path patch Python 2 doesn't benefit from anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants