I’ve never gotten it to work, I’ve tried several times since it came out.
Glenn


From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sarah k
Alawami
Sent: Thursday, June 07, 2018 12:58 PM
To: nvda list list
Subject: Re: [nvda] Add-on compatibility notice: NvDA Remote Support add-on
2.1 is not compatible with wxPython 4, new release recommended

I Actually did not take part in the crowd funding as I didn't believe
this add on would ever happen, and I knew one of the devs so perosnally did
not crowd fund it, I just will not go thee, not here.

Anyway yeah any way to get hold of the devs of the remote add on and ask
them to please fix? At least for some of us who use it. I only used it once
and that was this year.

Here's hoping for a fix eh?


On Jun 7, 2018, at 10:23 AM, Mallard
<mallard@kimabe.eu<mailto:mallard@kimabe.eu>> wrote:

Considering that, unlike other add-ons, we all crowdfunded the development
of this very add-on, I'd hope something is done about it very soon,





Il 07/06/2018 18:14, Joseph Lee ha scritto:


Hi all,

The below notice is considered critical:

It’s happening again: with the introduction of wxPython 4 in next snapshots,
users of NVDA Remote add-on are having startup issues related to missing
attribute in wxPython 4.

I propose the following solutions:

* I highly recommend releasing Remote add-on 2.2 to fix this issue.
* Perhaps adding a statement on nvdaremote.com<http://nvdaremote.com>;
website explaining
that Remote add-on should be disabled if using recent NVDA next
snapshots.
* The community should release an updated version of this add-on
with permission from add-on authors and maintainers.

Thanks.

Cheers,

Joseph

I  Actually did not take part in the  crowd funding  as I didn't believe this add on would ever happen, and I knew one of the devs so perosnally did not crowd fund it, I just will not go thee, not here.

On Jun 7, 2018, at 2:56 AM, Shaun Everiss <sm.everiss@...> wrote:

It looks like its not completely the end.

It appears for 7 and 8 users we will have to just not install the skype classic update.

For 10 users, it appears microsoft have left us alone.

Previded we can get the skype classic program, ms doesn't ask us to switch over to the universal.

So at least for the moment they are leaving us alone who knows how long that is but still.

I have not as yet tried this.

The nvda skype group didn't have much traffic and I was thinking of pulling out anyway.

Skype isnot a real issue for me as I hardly use it.

Skype web via miranda works for text, now if I can use it to call skype then fine I guess.

There is zello but I have never figured it out as such.

On the other side those of us on android and ios devices will still be able to use skype,.

This seems to effect desktops, that is windows, mac and linux only.

For group chats there is teamtalk, and tthub.org are offering competitive rates right now.

I am interested though in some kind of voip or sip app that is easy to use, accessible and can use as a protocol skype calls, messages, groups and file shares which are the only things I ever use.

If that can be done and if I can login with my skype account then fine.

Right now skype classic still works.

Eventually that may die but who knows.

The skype interface with miranda ng is a bit different, I will have to get used to it but right now well.

I don't use skype enough to justify upgrading to anything new, I barely use that much of skype's power as it is.




On 6/7/2018 9:00 PM, Brian's Mail list account via Groups.Io wrote:

I have to say its not been used here for almost a year now.
I find it irritating that such a simple system is not being made available in a basic form for low tech users and without the flashy front end changes every fortnight. Skype always had a reputation of bringing out improvements that broke it, and it seems this has not stopped with Microsoft owning it, sadly.
So what else is out there for desktop machines for good quality audio over the internet free?
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Shaun Everiss" <sm.everiss@...>
To: <nvda@nvda.groups.io>
Sent: Wednesday, June 06, 2018 8:31 PM
Subject: [nvda] end of the line for nvda skype group

Hi all of you.

Pulling out of nvda skype group now because of 1, skypes uncertain future and 2. the fact I hardly contribute to it, I will shift all my conversational contributions to this list from now on if I havn't allready.

I will still use skype classic for family, but due to things as they stand I may have to remove skype from my contact and other info, it will be email for internationals only, skype if they need, but I will no longer advertise.

Microsoft has lost another user, skype classic interface is easy to understand, the new one I just don't care for.

Its a pitty its got to end this way but I may as well cut my losses right now rather than having to bother with things going bang.

I will have to either search for another solution or start paying high charges for international calls because skype new versions are inaccessible.

Way to go ms.

Can't skype classic just be pulled from the update loop and still be kept active?

On Jun 7, 2018, at 7:36 AM, Ervin, Glenn <glenn.ervin@...> wrote:

I don’t make folders often enough to have known that command.

We have so many things to remember as it is in our daily lives including all the passwords and changing systems that we have to draw the line sometimes.

On the desktop and elsewhere, I just found it easier to unselect anything and use the applications key to go to “new” and then enter on “Folder”.

 

Glenn

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Gene
Sent: Wednesday, June 06, 2018 7:54 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Addint a Desktop Shortcut for Programs or Apps under Windows 10

 

I expect to see such commands documented when moving threw menus and submenus.  It should not be necessary for a skilled user, who learns a lot about Windows and programs by looking through menus and dialogs to have to look at a commands sheet when it is expected that accelerator or shortcut commands will be shown in menus. 

 

Also, material that I consider to be among the best produced doesn't mention this command.  I doubt that more than perhaps ten or twenty percent of blind users know this command.

 

Gene

----- Oreiginal Message -----

From: Brian Vogel

Sent: Wednesday, June 06, 2018 7:48 PM

To: nvda@nvda.groups.io

Subject: Re: [nvda] Addint a Desktop Shortcut for Programs or Apps under Windows 10

 

On Wed, Jun 6, 2018 at 05:32 pm, Gene wrote:

I'm not surprised. 

Well, I still am.   CTRL+SHIFT+N has been on Microsoft issued keyboard shortcuts lists for a very long time now.

If you go to the Keyboard Shortcuts in Windowswebpage, as it exists today, it shows up whether you choose All Products, Windows 7, Windows 8.1, or Windows 10 from the dropdown for Product Version at the top of the page.

They've also been calling these keyboard shortcuts for as long as I can remember now, but I do recall the "accelerator command" terminology in the mists of memory.  I think that went out as of Windows XP, but can't be certain.  It may have been with the introduction of Windows 7.
 
-- 

Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134  

     Explanations exist; they have existed for all time; there is always a well-known solution to every human problem — neat, plausible, and wrong.

          ~ H.L. Mencken, AKA The Sage of Baltimore

 

 

On Jun 7, 2018, at 10:23 AM, Mallard <mallard@...> wrote:

Considering that, unlike other add-ons, we all crowdfunded the development of this very add-on, I'd hope something is done about it very soon,





Il 07/06/2018 18:14, Joseph Lee ha scritto:

Hi all,

The below notice is considered critical:

It’s happening again: with the introduction of wxPython 4 in next snapshots, users of NVDA Remote add-on are having startup issues related to missing attribute in wxPython 4.

I propose the following solutions:

 * I highly recommend releasing Remote add-on 2.2 to fix this issue.
 * Perhaps adding a statement on nvdaremote.com website explaining
   that Remote add-on should be disabled if using recent NVDA next
   snapshots.
 * The community should release an updated version of this add-on
   with permission from add-on authors and maintainers.

Thanks.

Cheers,

Joseph

will this effect dictation bridge as well?

Hi all,

 

The below notice is considered critical:

 

It’s happening again: with the introduction of wxPython 4 in next snapshots, users of NVDA Remote add-on are having startup issues related to missing attribute in wxPython 4.

 

I propose the following solutions:

 

• I highly recommend releasing Remote add-on 2.2 to fix this issue.
• Perhaps adding a statement on nvdaremote.com website explaining that Remote add-on should be disabled if using recent NVDA next snapshots.
• The community should release an updated version of this add-on with permission from add-on authors and maintainers.

 

Thanks.

Cheers,

Joseph

-- 

check out my song on youtube

https://youtu.be/YeWgx2LRu7Y

While I see this as essential in order to move to current versions of software / packages it is concerning that addons are breaking due to upgrading of the NVDA code base.  I worked in an office where we developed 25 scripts for AT technologies a year and still had a back log of portions of applications that were not fully compliant with Windows accessibility API’s. If in addition to keeping up with Windows and application changes that occur regularily, addon developers have to do regular work on their stock of addons I could see this as a deterrent to wide spread adoption of NVDA. Is this a general problem in the Python community or just an issue from the transition to Python 3.

Thanks,

Jonathan Cohn

While I see this as essential in order to move to current versions of software / packages it is concerning that addons are breaking due to upgrading of the NVDA code base.  I worked in an office where we developed 25 scripts for AT technologies a year and still had a back log of portions of applications that were not fully compliant with Windows accessibility API’s. If in addition to keeping up with Windows and application changes that occur regularily, addon developers have to do regular work on their stock of addons I could see this as a deterrent to wide spread adoption of NVDA. Is this a general problem in the Python community or just an issue from the transition to Python 3.

Thanks,

Jonathan Cohn

Hi all,

The below notice is considered critical:

It’s happening again: with the introduction of wxPython 4 in next snapshots, users of NVDA Remote add-on are having startup issues related to missing attribute in wxPython 4.

I propose the following solutions:

* I highly recommend releasing Remote add-on 2.2 to fix this issue.
* Perhaps adding a statement on nvdaremote.com website explaining
that Remote add-on should be disabled if using recent NVDA next
snapshots.
* The community should release an updated version of this add-on
with permission from add-on authors and maintainers.

Thanks.

Cheers,

Joseph

While I see this as essential in order to move to current versions of software / packages it is concerning that addons are breaking due to upgrading of the NVDA code base.  I worked in an office where we developed 25 scripts for AT technologies a year and still had a back log of portions of applications that were not fully compliant with Windows accessibility API’s. If in addition to keeping up with Windows and application changes that occur regularily, addon developers have to do regular work on their stock of addons I could see this as a deterrent to wide spread adoption of NVDA. Is this a general problem in the Python community or just an issue from the transition to Python 3.

Thanks,

Jonathan Cohn

Hi,
Which next snapshot build do you have?
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Michel
Such
Sent: Thursday, June 7, 2018 9:44 AM
To: nvda@nvda.groups.io
Subject: [nvda] Latest next, cannot add entries to a dictionnary

Hi all,


I guess it comes from migration to WXPython 4.01 which needs some adjustments, bu I just noticed that at this point it is impossible to add something to a pronunciation dictionnary.


Another thing I'm not completely sure of, it seems that, when closing some dialogs, the window which contained them remains on screen but is nomore accessible.

I suppose that because my wife looked at my sreen and told me I had 6
or
7 NVDA Windows on it.

Hi,
Which next snapshot build do you have?
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Michel Such
Sent: Thursday, June 7, 2018 9:44 AM
To: nvda@nvda.groups.io
Subject: [nvda] Latest next, cannot add entries to a dictionnary

Hi all,


I guess it comes from migration to WXPython 4.01 which needs some adjustments, bu I just noticed that at this point it is impossible to add something to a pronunciation dictionnary.


Another thing I'm not completely sure of, it seems that, when closing some dialogs, the window which contained them remains on screen but is nomore accessible.

I suppose that because my wife looked at my sreen and told me I had 6 or
7 NVDA Windows on it.

Hi,
And there has been no update since then? Looks like another community ad-on compatibility notice is in order...
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Ângelo Abrantes
Sent: Thursday, June 7, 2018 8:56 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Problem with last "NVDA next" and "Remote Support

Version 2.1, downloaded today from "remote support" page.

Thanks.

Ângelo Abrantes


Às 16:45 de 07-06-2018, Joseph Lee escreveu:

Hi,
Which version of this add-on do you have? The below log is a well-known problem, and I thought add-on authors would have released an updated version to fix this.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Ângelo
Abrantes
Sent: Thursday, June 7, 2018 8:40 AM
To: nvda@nvda.groups.io
Subject: [nvda] Problem with last "NVDA next" and "Remote Support

Hi,


Here's a part of my log file:


"DEBUG - addonHandler.Addon.__init__ (16:33:01.305):
Using manifest translation from
C:\Users\Angelo\AppData\Roaming\nvda\addons\systrayList\locale\pt_PT\m
anifest.ini ERROR - globalPluginHandler.initialize (16:33:01.361):
Error initializing global plugin <class
'globalPlugins.remoteClient.GlobalPlugin'>
Traceback (most recent call last):
File "globalPluginHandler.pyc", line 32, in initialize
File
"C:\Users\Angelo\AppData\Roaming\nvda\addons\remote\globalPlugins\remo
teClient\__init__.py",
line 56, in __init__
File
"C:\Users\Angelo\AppData\Roaming\nvda\addons\remote\globalPlugins\remo
teClient\__init__.py",
line 104, in create_menu
AttributeError: 'MenuItem' object has no attribute 'SetCheckable'
DEBUG - addonHandler.Addon.__init__ (16:33:01.382):
Using manifest translation from
C:\Users\Angelo\AppData\Roaming\nvda\addons\poeditMadeEasy\locale\en\m
anifest.ini
DEBUG - core.main (16:33:01.413):
Initializing core pump
DEBUG - core.main (16:33:01.413):
Initializing watchdog
DEBUG - core.main (16:33:01.414):
initializing updateCheck
INFO - core.main (16:33:01.414):
NVDA initialized"


Thanks

Ângelo Abrantes


---
Este e-mail foi verificado em termos de vírus pelo software antivírus Avast.
https://www.avast.com/antivirus