Re: CodeFactory Eloquence with NVDA 2022.1?
Steve Wettlaufer
Unfortunately you can't. It seems like very obvious functionality though and I really wish they would add it. Steve
On 2022-05-16 11:02 a.m., Sarah k
Alawami wrote:
|
|
locked
Re: Saving Outlet
On Mon, May 16, 2022 at 09:55 AM, Jon W Parsons wrote:
How do I backup and save my outlet program and all my messages so I can put- I am guessing, as Sarah has, that this is a question about how to port all existing email in an Outlook instance on one computer to another. Per the group rules, and my frequent reminders about same, this question has nothing whatsoever to do with NVDA. It should be addressed either on the Chat Subgroup, Microsoft Office Accessibility Discussion Group, or any one of a number of other more generally focused blind-centric tech groups, of which there are many. ---- NVDA Chat Subgroup Archive: https://nvda.groups.io/g/chat/topics NVDA Chat Subgroup Addresses To join: chat+subscribe@nvda.groups.io To post: chat@nvda.groups.io To unsubscribe: chat+unsubscribe@nvda.groups.io To receive a message containing the group description, and a list of these commands: chat+help@nvda.groups.io To stop receiving messages via email (you may still read messages on the Web): chat+nomail@nvda.groups.io This can also be used to put a vacation stop on group messages, then use one of the addresses below to resume delivery in the format of your choice. To receive each group messages individually: chat+single@nvda.groups.io This is the default delivery unless you send a message to one of the addresses that follows. To receive group messages in an HTML formatted digest: chat+fulldigest@nvda.groups.io To receive group messages in a plain text digest: chat+digest@nvda.groups.io To receive a daily summary instead of individual messages: chat+summary@nvda.groups.io To receive only special messages: chat+special@nvda.groups.io To contact the group owner(s): chat+owner@nvda.groups.io
-------------------------------------------------------- Windows Access with Screen Readers Group (Formerly: Windows 10 for Screen Reader Users Group) Group Archive: https://winaccess.groups.io/g/winaccess/topics Subscribe: winaccess+subscribe@winaccess.groups.io Post: winaccess@winaccess.groups.io Unsubscribe: winaccess+unsubscribe@winaccess.groups.io Group Owner: winaccess+owner@winaccess.groups.io Help: winaccess+help@winaccess.groups.io
-------------------------------------------------------- BlindTech Group Group Archive: https://groups.io/g/blindtech/topics
----------------------------------------------------------
Microsoft Office Accessibility Discussion Group Archive: https://groups.io/g/office-accessibility/topics
This topic is now locked. -- Brian - Windows 10, 64-Bit, Version 21H2, Build 19044 You can't crush ideas by suppressing them. You can only crush them by ignoring them.
|
|
Re: Add-on update notice: fixed Add-on Updater offering incompatible add-ons
Janet Brandly
We appreciate all the work you do. You definitely deserve a long disconnected vacation.
Janet
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: May 16, 2022 8:45 AM To: nvda@nvda.groups.io Subject: [nvda] Add-on update notice: fixed Add-on Updater offering incompatible add-ons
Hi all, Recently a number of add-ons were updated that require NVDA 2022.1, and these were approved for distribution on community add-ons website around 7:52 PM Pacific (UTC-7) on May 15, 2022. Around 1:11 AM on May 16th, I received a report from the add-ons list about compatibility messages with NVDA 2021.3.5 (the latest stable version as of time of this writing) and confirm that Add-on Updater was offering incompatible add-on updates to users. I have stopped Add-on Updater from offering add-on updates requiring NVDA 2022.1 around 1:36 AM Pacific. While the update issue is resolved, I decided to inform you of what happened as Add-on Updater is my responsibility, and the described issue was part of a chain of events that led to folks experiencing confusion for a while. My sincerest apologies for this mishap. P.S. A bigger factor: mental exhaustion due to me being a workaholic when it comes to everything NVDA. The events that led to the mishap described cannot be explained fully here, but what I can say is that as soon as graduate final exam is done this week and Windows App Essentials 22.06 is released next week, I’ll be looking for a great distraction from NVDA before I crash with mental exhaustion. This can partly explain why I’m not my usual self these days. Cheers, Joseph
|
|
locked
Re: Saving Outlet
If your email is iMap no need to save, it will all be in the cloud, just put
toggle quoted messageShow quoted text
in your info and it will all dl to your computer, or at least the headers will. Then you can click the messages to have the pics and text dl as well.
-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Jon W Parsons Sent: Monday, May 16, 2022 6:55 AM To: nvda@nvda.groups.io Subject: [nvda] Saving Outlet I am buying a new computer. How do I backup and save my outlet program and all my messages so I can put them on my new computer?
|
|
Re: CodeFactory Eloquence with NVDA 2022.1?
Can you update the add on from within the add on? that is, can I hit a button to go to the website where the update is? As I don’t think I’ve updated this thing in a year, when I bought this thing in July, ok, not quite a year, but soon enough.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Supanut Leepaisomboon
Sent: Monday, May 16, 2022 4:04 AM To: nvda@nvda.groups.io Subject: Re: [nvda] CodeFactory Eloquence with NVDA 2022.1?
A few days ago I submitted a ticket asking about exactly the same thing and they replied that they're working on it and that a new version should be out before the stable release of NVDA 2022.1.
|
|
Add-on update notice: fixed Add-on Updater offering incompatible add-ons
Hi all, Recently a number of add-ons were updated that require NVDA 2022.1, and these were approved for distribution on community add-ons website around 7:52 PM Pacific (UTC-7) on May 15, 2022. Around 1:11 AM on May 16th, I received a report from the add-ons list about compatibility messages with NVDA 2021.3.5 (the latest stable version as of time of this writing) and confirm that Add-on Updater was offering incompatible add-on updates to users. I have stopped Add-on Updater from offering add-on updates requiring NVDA 2022.1 around 1:36 AM Pacific. While the update issue is resolved, I decided to inform you of what happened as Add-on Updater is my responsibility, and the described issue was part of a chain of events that led to folks experiencing confusion for a while. My sincerest apologies for this mishap. P.S. A bigger factor: mental exhaustion due to me being a workaholic when it comes to everything NVDA. The events that led to the mishap described cannot be explained fully here, but what I can say is that as soon as graduate final exam is done this week and Windows App Essentials 22.06 is released next week, I’ll be looking for a great distraction from NVDA before I crash with mental exhaustion. This can partly explain why I’m not my usual self these days. Cheers, Joseph
|
|
locked
Saving Outlet
Jon W Parsons
I am buying a new computer.
How do I backup and save my outlet program and all my messages so I can put them on my new computer?
|
|
Re: NVDA repeating every Chinese character twice in Windows PowerShell
Rowen Cary
Hi, Please check 'Use UI Automation to access the Windows Console when available' in the advanced settings panel.
On Sat, May 14, 2022 at 07:59 PM, William wrote:
|
|
Re: Python pring function with flush=True NVDA not reading the updated messages in Windows PowerShell
Ken Perry
I tried running your code and it has errors. Can you try your code and make sure it works before you send it? Note things like the range function in the for loop and the sec variable is what I am talking bout.
toggle quoted messageShow quoted text
-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of William Sent: Saturday, May 14, 2022 5:04 AM To: nvda@nvda.groups.io Subject: [nvda] Python pring function with flush=True NVDA not reading the updated messages in Windows PowerShell Hello, This question is partly related to NVDA and partly related to Windows PowerShell. Supposed I have the following python script and stored in a python file 'test.py', which print out a new string of text after every second. import time for i in np.arange(10): print('Sleeping', f"{str(round((i-1)/secs*100, 0)).removesuffix('.0')}%", end="\r", flush=True) time.sleep(1) 1. I open Windows PowerShell 2. type python test.py 3. the script starts running I am expecting that NVDA can automatically speak out the new string of text, but in my test, after the first 'Spleeping...' was spoken, NVDA did not speak the updated messages. What can I do to make NVDA speak the updated messages? Thanks. William
|
|
Re: Python pring function with flush=True NVDA not reading the updated messages in Windows PowerShell
Gabriele Battaglia
Reply to William's message, wrote on
16/05/2022 at 12:10:
>do you have an example? I'm not able to reproduce it at the moment. I tried this and it works.
#test import time
for i in range(4): print(f"\nThis is number {i}",end="") time.sleep(0.8) Could you please show me once more the piece of code you posted at the beginning? Thanks.
|
|
Re: CodeFactory Eloquence with NVDA 2022.1?
A few days ago I submitted a ticket asking about exactly the same thing and they replied that they're working on it and that a new version should be out before the stable release of NVDA 2022.1.
Note this is the second time submitting a ticket about it; this time I chose the high priority. When I submitted a ticket first time I chose medium priority and got no response. So...fingers cross for now and hope a new version of Codefactory is indeed released prior to the release of 2022.1 stable.
|
|
Re: Python pring function with flush=True NVDA not reading the updated messages in Windows PowerShell
William
Hi
Do you have the same issue also if you print a return, \n, after thevalue? do you have an example? Gabriele Battaglia via groups.io 於 16/5/2022 17:45 寫道:
|
|
Re: Python pring function with flush=True NVDA not reading the updated messages in Windows PowerShell
Gabriele Battaglia
FYI
Powershell is not involved itself. It's matter of all console app. I don't use Powershell but I have the same issue on command prompt. Gabe.
|
|
Re: Python pring function with flush=True NVDA not reading the updated messages in Windows PowerShell
Gabriele Battaglia
Reply to William's message, wrote on 16/05/2022 at 11:26:
Hi Gabe. Ops. I hope someone answer later. Do you have the same issue also if you print a return, \n, after the value? Gabe.
|
|
Re: Python pring function with flush=True NVDA not reading the updated messages in Windows PowerShell
William
Hi Gabe.
toggle quoted messageShow quoted text
I just posted this question in nvda-dev but so far I have not received any feedback. Gabriele Battaglia via groups.io 於 16/5/2022 16:51 寫道:
Hi William.
|
|
Re: Python pring function with flush=True NVDA not reading the updated messages in Windows PowerShell
Gabriele Battaglia
Hi William.
I just joined the dev's group but I'm asking if you already posted this question there and if you got some answers. I'm very interested in this topic because I have this issue also. Thanks. Gabe.
|
|
Re: CodeFactory Eloquence with NVDA 2022.1?
Yeah, ATGuys indeed supportive than CF, but unfortunately they just a reseller, so they can't do anything in term of compatibility breaking release.
------ Original Message ------
From "Sarah k Alawami" <marrie12@...>
Date 5/15/2022 11:43:23 PM
Subject Re: [nvda] CodeFactory Eloquence with NVDA 2022.1?
|
|
Re: Python pring function with flush=True NVDA not reading the updated messages in Windows PowerShell
William
Noted, thanks. Quentin Christensen 於 16/5/2022 11:22
寫道:
|
|
Re: Punctuation
Yes and the slash is called a stroke. Makes sence if you think about it. It looks like the stroke of a pen. Interesting history of words etc. I love history of words, but then again I am a teacher for what ever that’s worth.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen
Sent: Sunday, May 15, 2022 8:08 PM To: nvda@nvda.groups.io Subject: Re: [nvda] Punctuation
Apparently the "!" being called "bang" goes back to the 1950s and either comic books (which portrayed a speech bubble with ! in it coming out of a gun to signify it being fired, hence 'bang') - or typesetting manuals: https://english.stackexchange.com/questions/62918/why-is-the-exclamation-mark-called-a-bang. I've never heard it used anywhere other than screen readers (not just NVDA).
I can't readily find a reference for the apostrophe being called tick. In ASCII the grave accent is called the "back tick", and I assume that would have come from the same source.
I assume screen readers picked up those two names from the ascii and other similar references, but also because both are shorter to say than their more common names. (Or at least more common here in Australia, I'm not sure whether either term is used - outside screen readers - to describe those symbols in other countries?
Fiddlesticks, I used my linguistic nerd quota in In-Process for the month last edition, maybe I can explore this in a future In-Process!
(Fiddlesticks of course from "Fiddle Sticks", the bows used to play violins, from the 15th century "fydylstyks").
Ok I'll stop now :)
On Fri, May 13, 2022 at 11:27 PM Steve Nutt <steve@...> wrote:
-- Quentin Christensen
Web: www.nvaccess.org Training: https://www.nvaccess.org/shop/ Certification: https://certification.nvaccess.org/ User group: https://nvda.groups.io/g/nvda Facebook: http://www.facebook.com/NVAccess
|
|
Re: what's up with this player?
Gene
I tried that and it didn't work when I did. If it did when you
tried it, that's fine.
toggle quoted messageShow quoted text
Gene
On 5/15/2022 10:04 PM, Bob Cavanaugh
wrote:
Okay, I finally got it to work. Even in browse mode, it works. Just click the link that says 4, and then the audio will start and the link will now display as visited, and will change to say 6. That is completely not logical though. On 5/15/22, Gene <gsasner@...> wrote:Here is how you get the player to play. When you are in the player, make sure you are at the top. Turn browse mode off with NVDA space. Tab until you get to a link that just says link. It will be two or three times. Use NVDA numpad enter to activate the link. Then use the same command again to activate it again. The audio will play. Gene On 5/15/2022 7:35 PM, Bob Cavanaugh wrote:Gene, Try again. The link you provided directed me to WHTE in Charlottesville, VA. The station in question is KRSQ in Billings, MT. That website is hot1019.com, and the player linked to in my original message on this topic is the one linked from their website. Jackie, what browser and operating system are you on? I don't get any audio when I use that link, hence my post to this list. I'm currently running Windows 10 with Firefox, but have tried this player with IE on both Windows 10 and Windows 7 also with no luck. On 5/15/22, Gene <gsasner@...> wrote:Also, what I described as buttons are actually links so you can't use b to move to them. NVDA says link button, so treat them like links. Gene On 5/15/2022 4:10 PM, Gene wrote:Go to the actual station: https://www.1019hot.com/ Make sure you are at the top of the page. Move to an unlabeled link that says 58201 and press enter. You are now on a page with the kind of buttons you would expect, one of which is a play button. You were going to the player but it is not being used to stream the site. Stations may change their streaming address from time to time. Check the actual site if something stops working. Gene On 5/15/2022 2:38 PM, Bob Cavanaugh wrote:Hi all, Hopefully I still get an answer to my other question, but while I'm on here, what's up with this audio player? I'm currently running Windows 10 with Firefox as my default browser, but this has been a problem with this station through two operating systems, two browsers, and at least three computers. Can anyone tell me why I can't get any audio? The station used to have a prerol add and that would play, but the station audio wouldn't. http://m.commotion.com/player/9A14E259-76F4-47D4-AF94-0ED5394282E1_E6C462BB-968B-46CF-B159-C0619A75A171/ .
|
|