|
Brian's Mail list account
Unless you were moving at 78 and a bit mph at the time...:-
Sorry...
Brian
bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
toggle quoted messageShow quoted text
----- Original Message ----- From: "Don H" <lmddh50@...> To: <nvda@nvda.groups.io> Sent: Tuesday, March 19, 2019 12:59 PM Subject: [nvda] weather plus Got a update to weather plus this morning that indicated a change in its name. Installed just fine but still show bad info when you check the weather. Said we had 88 mile an hour winds in Quincy this morning. I am sure it is probably really 8.8 miles per hour.
|
|
|
Re: another Zotero question
|
|
|
Brian's Mail list account
Yes and in the previous log, the brailed interface was also implicated. Might be worth finding out if the driver used is the one that everyone else uses with nvda, it might be that simple.
Brian
bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
toggle quoted messageShow quoted text
----- Original Message ----- From: "Jaffar Sidek" <jaffar.sidek10@...> To: <nvda@nvda.groups.io> Sent: Saturday, March 23, 2019 1:04 AM Subject: Re: [nvda] It Happened Again Hi. from what I have read from your log, Pyo.braille is causing some
problems. Try loading NVDA and Microsoft Office without your braille
display and see what happens. Cheers!
On 3/23/2019 1:06 AM, Abbie Taylor wrote:
I was just now trying to open a file in Word when I lost speech and
had to restart NVDA. I’m using the latest version of Microsoft Office
with the latest version of NVDA. Below is the log. Hope this helps.
Abbie Johnson Taylor, Author _https://abbiescorner.wordpress.com_
http://www.abbiejohnsontaylor.com
abbietaylor945@...
INFO - __main__ (11:00:20.681):
Starting NVDA
INFO - core.main (11:00:22.480):
Config dir: C:\Users\Abbie T\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (11:00:22.480):
Loading config: C:\Users\Abbie T\AppData\Roaming\nvda\nvda.ini
INFO - core.main (11:00:22.726):
NVDA version 2018.4.1
INFO - core.main (11:00:22.726):
Using Windows version 10.0.17134 workstation
INFO - core.main (11:00:22.727):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018,
16:22:17) [MSC v.1500 32 bit (Intel)]
INFO - core.main (11:00:22.727):
Using comtypes version 1.1.3
INFO - core.main (11:00:22.727):
Using configobj version 5.1.0 with validate version 1.0.1
INFO - synthDriverHandler.setSynth (11:00:25.005):
Loaded synthDriver vocalizer
INFO - core.main (11:00:25.006):
Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5
INFO - brailleInput.initialize (11:00:25.009):
Braille input initialized
INFO - braille.initialize (11:00:25.009):
Using liblouis version 3.7.0
INFO - braille.BrailleHandler.setDisplayByName (11:00:25.020):
Loaded braille display driver noBraille, current display has 0 cells.
WARNING - core.main (11:00:25.111):
Java Access Bridge not available
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (11:00:25.119):
UIAutomation: IUIAutomation5
INFO - core.main (11:00:27.221):
NVDA initialized
INFO - braille.BrailleHandler.setDisplayByName (11:00:30.226):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - config.ConfigManager._loadConfig (11:00:48.809):
Loading config: C:\Users\Abbie
T\AppData\Roaming\nvda\profiles\microsoft word.ini
INFO - braille.BrailleHandler.setDisplayByName (11:00:53.941):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - braille.BrailleHandler.setDisplayByName (11:00:59.075):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - brailleDisplayDrivers.brailliantB.BrailleDisplayDriver.__init__
(11:01:46.911):
Found display with 32 cells connected via serial (COM4)
INFO - braille.BrailleHandler.setDisplayByName (11:01:46.911):
Loaded braille display driver brailliantB, current display has 32 cells.
ERROR - core.CorePump.run (11:03:03.316):
errors in this core pump cycle
Traceback (most recent call last):
File "core.pyo", line 490, in run
File "braille.pyo", line 2156, in pumpAll
File "braille.pyo", line 1898, in handlePendingCaretUpdate
File "braille.pyo", line 1904, in _doCursorMove
File "braille.pyo", line 949, in update
File "braille.pyo", line 791, in _getSelection
File "documentBase.pyo", line 24, in makeTextInfo
File "NVDAObjects\UIA\__init__.pyo", line 297, in __init__
RuntimeError
--
Abbie Johnson Taylor, Author
http://www.abbiejohnsontaylor.com
http://abbiescorner.wordpress.com
abbietaylor945@...
|
|
|
Jaffar Sidek <jaffar.sidek10@...>
Hi. from what I have read from your log, Pyo.braille is causing
some problems. Try loading NVDA and Microsoft Office without your
braille display and see what happens. Cheers!
toggle quoted messageShow quoted text
On 3/23/2019 1:06 AM, Abbie Taylor
wrote:
I was just now trying to open a file in
Word when I lost speech and had to restart NVDA. I’m using the
latest version of Microsoft Office with the latest version of
NVDA. Below is the log. Hope this helps.
Abbie Johnson Taylor, Author https://abbiescorner.wordpress.com
http://www.abbiejohnsontaylor.com
abbietaylor945@...
INFO - __main__ (11:00:20.681):
Starting NVDA
INFO - core.main (11:00:22.480):
Config dir: C:\Users\Abbie
T\AppData\Roaming\nvda
INFO -
config.ConfigManager._loadConfig (11:00:22.480):
Loading config: C:\Users\Abbie
T\AppData\Roaming\nvda\nvda.ini
INFO - core.main (11:00:22.726):
NVDA version 2018.4.1
INFO - core.main (11:00:22.726):
Using Windows version 10.0.17134
workstation
INFO - core.main (11:00:22.727):
Using Python version 2.7.15
(v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17) [MSC v.1500 32
bit (Intel)]
INFO - core.main (11:00:22.727):
Using comtypes version 1.1.3
INFO - core.main (11:00:22.727):
Using configobj version 5.1.0 with
validate version 1.0.1
INFO - synthDriverHandler.setSynth
(11:00:25.005):
Loaded synthDriver vocalizer
INFO - core.main (11:00:25.006):
Using wx version 4.0.3 msw (phoenix)
wxWidgets 3.0.5
INFO - brailleInput.initialize
(11:00:25.009):
Braille input initialized
INFO - braille.initialize
(11:00:25.009):
Using liblouis version 3.7.0
INFO -
braille.BrailleHandler.setDisplayByName (11:00:25.020):
Loaded braille display driver
noBraille, current display has 0 cells.
WARNING - core.main (11:00:25.111):
Java Access Bridge not available
INFO -
_UIAHandler.UIAHandler.MTAThreadFunc (11:00:25.119):
UIAutomation: IUIAutomation5
INFO - core.main (11:00:27.221):
NVDA initialized
INFO -
braille.BrailleHandler.setDisplayByName (11:00:30.226):
Loaded braille display driver
noBraille, current display has 0 cells.
INFO -
config.ConfigManager._loadConfig (11:00:48.809):
Loading config: C:\Users\Abbie
T\AppData\Roaming\nvda\profiles\microsoft word.ini
INFO -
braille.BrailleHandler.setDisplayByName (11:00:53.941):
Loaded braille display driver
noBraille, current display has 0 cells.
INFO -
braille.BrailleHandler.setDisplayByName (11:00:59.075):
Loaded braille display driver
noBraille, current display has 0 cells.
INFO -
brailleDisplayDrivers.brailliantB.BrailleDisplayDriver.__init__
(11:01:46.911):
Found display with 32 cells connected
via serial (COM4)
INFO -
braille.BrailleHandler.setDisplayByName (11:01:46.911):
Loaded braille display driver
brailliantB, current display has 32 cells.
ERROR - core.CorePump.run
(11:03:03.316):
errors in this core pump cycle
Traceback (most recent call last):
File "core.pyo", line 490, in run
File "braille.pyo", line 2156, in
pumpAll
File "braille.pyo", line 1898, in
handlePendingCaretUpdate
File "braille.pyo", line 1904, in
_doCursorMove
File "braille.pyo", line 949, in
update
File "braille.pyo", line 791, in
_getSelection
File "documentBase.pyo", line 24,
in makeTextInfo
File
"NVDAObjects\UIA\__init__.pyo", line 297, in __init__
RuntimeError
--
Abbie Johnson Taylor, Author
http://www.abbiejohnsontaylor.com
http://abbiescorner.wordpress.com
abbietaylor945@...
|
|
|
Kerryn Gunness <k_gunness@...>
thanks everyone for the info
----- Original Message -----
Sent: Friday, March 22, 2019 1:57
AM
Subject: Re: [nvda] auto run file
Search thoroughly on the internet and you will find there are risk free
ways to do this. I wouldn't, however, recommend it to anyone without
technical knowledge.
On 3/22/2019 1:48 PM, Gene wrote:
Also, you said, if you put yourself at risk, not others. If a
machine becomes infected, it may cause problems for others, not just
you. It may be part of a botnet and take part in denial of service
attacks, shutting down web sites. It may be used by malware to mail
spam, thus exposing people to phishing and other kinds of fraud. The
malware may try to spread itself to other machines on your network.
Gene
----- Original Message -----
Sent: Friday, March 22, 2019 12:43 AM
Subject: Re: [nvda] auto run file
The whole point of having NVDA on a thumb drive is to run it on other
machines where it isn't installed. Why would you want to run it on
your own machine from a thumb drive in the first place? I don't know
anything about disabling this feature but it sounds to me as though if you
do, you open yourself up to malicious software if you use a thumb drive from
someone else. I see no reason to take risks just to make running
something easier.
And you can run it very easily on your own machine without lowering
security. Create a short cut to the exe file on the thumb drive.
Then assign a short cut command such as control alt d or control alt a or
whatever such combination you like. That is so fast and convenient
that there isn't any remotely justifiable reason to needlessly lower
security for convenience.
Gene
----- Original Message -----
Sent: Friday, March 22, 2019 12:32 AM
Subject: Re: [nvda] auto run file
Yes. But there are ways, and there are ways. And as long as you run
it on your own computer and put yourself at risk and not others, then
it will still work just as long as you know what you're doing.
Cheers!
On 3/22/2019 11:32 AM, Gene wrote:
Windows doesn't run autorun files automatically any longer from thumb
drives as a security measure against malicious code running. You can
run Narrator, run NVDA, then close Narrator.
Gene
----- Original Message -----
Sent: Thursday, March 21, 2019 8:38 PM
Subject: Re: [nvda] auto run file
Hi Keryn. Here is a sample of an Autorun.inf file.
Copy the below code:
[autorun]
;Open=NVDA.exe
ShellExecute=NVDA.exe
UseAutoPlay=1
Save the autorun.inf file onto the root of your USB drive.
Cheers!
On 3/22/2019 8:36 AM, Kerryn Gunness via
Groups.Io wrote:
hi guys
is it possible to create an auto run file to place on a flash
drive, so that the portable copy of NVDA will launch as soon as the
flash drive is placed into the USB port?
if so how can it be done?
thanks
kerryn
|
|
|
Re: changing when Windows automatically checks for updates
Travis, REM in command prompt batch scripts is short for REMark. You are correct that this is how a comment line is noted in this scripting language. --
Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763
A great deal of intelligence can be invested in ignorance when the need for illusion is deep.
~ Saul Bellow, To Jerusalem and Back
|
|
|
Re: changing when Windows automatically checks for updates
Thank you Brian. Much appreciated.
Out of curiosity, what does REM stand for? I'm guessing it's code
to tell Windows that the said line has nothing to act on, but
wondered past that as I'm sure that rapid eye movement is not the
correct answer here. LOL!
Travis
toggle quoted messageShow quoted text
On 3/22/2019 9:21 AM, Brian Vogel
wrote:
I have gotten no definitive answer as to how or whether one can
actually determine the time of checking. My gut is telling me
that this may be a two-way communication where MS can "knock on
the door" of the Windows Update process or vice versa, depending
on the situation.
The following, when put into a .bat file and run under an elevated
command prompt (Run as Admin), will make the changes in Windows
Update noted by the remark line ahead of each (and don't
copy/paste the lines of hyphens):
----------------------------------------------------------------------------
@echo OFF
REM The following entries tweak Windows Update's Auto-Update
features
REM and will prevent Windows 10 from restarting automatically
if any user is logged in to the system.
REM This does still apply under Windows 10 though the above
noted page was written for an earlier Windows
REM Still permit Windows Update to do Automatic Updates
reg add
"HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU" /v
NoAutoUpdate /t REG_DWORD /d 0 /f
REM Make Windows Update notify you before downloading
anything
reg add
"HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU" /v
AUOptions /t REG_DWORD /d 2 /f
REM Allow User the choice of whether to reboot now or keep
postponing
reg add
"HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU" /v
NoAutoRebootWithLoggedOnUsers /t REG_DWORD /d 1 /f
REM The following two keys are valid only if the value for
the AUOptions key is equal to 4, full automatic, which we reset
to 2 above
REM They're being set only in case you ever go back to full
automatic.
REM The scheduled install day would be every day of the week
if full automatic install were in force
reg add
"HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU" /v
ScheduledInstallDay /t REG_DWORD /d 0 /f
REM The scheduled install time would be 3 AM (hour specified
on 24-hour time, 0-23) if full automatic install were in force
reg add
"HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU" /v
ScheduledInstallTime /t REG_DWORD /d 3 /f
REM This key is not related to Windows Update scheduling, but
regards whether it will try to update drivers
REM The following sets Windows Update such that it will NOT
attempt to update drivers
reg add
"HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v
ExcludeWUDriversInQualityUpdate /t REG_DWORD /d 1 /f
----------------------------------------------------------------------------
--
Brian - Windows 10
Home, 64-Bit, Version
1809, Build 17763
A great
deal of intelligence can be invested in ignorance when the
need for illusion is deep.
~ Saul Bellow, To Jerusalem and
Back
|
|
|
Brian's Mail list account
Hi what happens if you tell your system you
have no braile display at all?
toggle quoted messageShow quoted text
----- Original Message -----
Sent: Friday, March 22, 2019 5:06
PM
Subject: [nvda] It Happened Again
I was just now trying to open a file in Word when I lost
speech and had to restart NVDA. I’m using the latest version of Microsoft
Office with the latest version of NVDA. Below is the log. Hope this
helps.
Abbie Johnson Taylor, Author https://abbiescorner.wordpress.com
http://www.abbiejohnsontaylor.com
abbietaylor945@...
INFO - __main__
(11:00:20.681):
Starting
NVDA
INFO - core.main
(11:00:22.480):
Config dir:
C:\Users\Abbie T\AppData\Roaming\nvda
INFO -
config.ConfigManager._loadConfig (11:00:22.480):
Loading config:
C:\Users\Abbie T\AppData\Roaming\nvda\nvda.ini
INFO - core.main
(11:00:22.726):
NVDA version
2018.4.1
INFO - core.main
(11:00:22.726):
Using Windows
version 10.0.17134 workstation
INFO - core.main
(11:00:22.727):
Using Python
version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17) [MSC v.1500 32 bit
(Intel)]
INFO - core.main
(11:00:22.727):
Using comtypes
version 1.1.3
INFO - core.main
(11:00:22.727):
Using configobj
version 5.1.0 with validate version 1.0.1
INFO -
synthDriverHandler.setSynth (11:00:25.005):
Loaded synthDriver
vocalizer
INFO - core.main
(11:00:25.006):
Using wx version
4.0.3 msw (phoenix) wxWidgets 3.0.5
INFO -
brailleInput.initialize (11:00:25.009):
Braille input
initialized
INFO -
braille.initialize (11:00:25.009):
Using liblouis
version 3.7.0
INFO -
braille.BrailleHandler.setDisplayByName (11:00:25.020):
Loaded braille
display driver noBraille, current display has 0 cells.
WARNING - core.main
(11:00:25.111):
Java Access Bridge
not available
INFO -
_UIAHandler.UIAHandler.MTAThreadFunc (11:00:25.119):
UIAutomation:
IUIAutomation5
INFO - core.main
(11:00:27.221):
NVDA
initialized
INFO -
braille.BrailleHandler.setDisplayByName (11:00:30.226):
Loaded braille
display driver noBraille, current display has 0 cells.
INFO -
config.ConfigManager._loadConfig (11:00:48.809):
Loading config:
C:\Users\Abbie T\AppData\Roaming\nvda\profiles\microsoft
word.ini
INFO -
braille.BrailleHandler.setDisplayByName (11:00:53.941):
Loaded braille
display driver noBraille, current display has 0 cells.
INFO -
braille.BrailleHandler.setDisplayByName (11:00:59.075):
Loaded braille
display driver noBraille, current display has 0 cells.
INFO -
brailleDisplayDrivers.brailliantB.BrailleDisplayDriver.__init__
(11:01:46.911):
Found display with
32 cells connected via serial (COM4)
INFO -
braille.BrailleHandler.setDisplayByName (11:01:46.911):
Loaded braille
display driver brailliantB, current display has 32
cells.
ERROR -
core.CorePump.run (11:03:03.316):
errors in this core
pump cycle
Traceback (most
recent call last):
File
"core.pyo", line 490, in run
File
"braille.pyo", line 2156, in pumpAll
File
"braille.pyo", line 1898, in handlePendingCaretUpdate
File
"braille.pyo", line 1904, in _doCursorMove
File
"braille.pyo", line 949, in update
File
"braille.pyo", line 791, in _getSelection
File
"documentBase.pyo", line 24, in makeTextInfo
File
"NVDAObjects\UIA\__init__.pyo", line 297, in __init__
RuntimeError
--
Abbie Johnson Taylor,
Author
http://www.abbiejohnsontaylor.com
http://abbiescorner.wordpress.com
abbietaylor945@...
|
|
|
Re: woman/person fassabumming
Fassabum, facepalm. Fassabumming, facepalming. Wow, those are
still pronounced the same.
Ok, time to experiment.
As I'm using Eloquence, I know how that sounds already.
Ok, it's up to the synth. Both eSpeak and Windows OneCore
pronounce facepalm(ing) correctly.
Thanks all for the clarification.
Travis
toggle quoted messageShow quoted text
On 3/22/2019 8:54 AM, Brian Vogel
wrote:
Heaven only knows how "fassabumming" might have come about.
The emoji is, specifically, "woman facepalming," where the term
facepalm is a single word made up of face and palm.
As a gesture of embarrassment or frustrated embarrassment, the
wikipedia description is accurate: https://en.wikipedia.org/wiki/Facepalm
--
Brian - Windows 10
Home, 64-Bit, Version
1809, Build 17763
A great
deal of intelligence can be invested in ignorance when the
need for illusion is deep.
~ Saul Bellow, To Jerusalem and
Back
|
|
|
Re: woman/person fassabumming
Face palming? LOL, I never would have guessed that the way it was bing pronounced, and I couldn't get emojis to spell out the letters of the description given, so truly had no idea. Jackie, thanks.
Travis
toggle quoted messageShow quoted text
On 3/22/2019 8:52 AM, Jackie wrote: "person face palming". It's an emoji of a person slapping themselves
in the face.
On 3/22/19, Kwork <istherelife@...> wrote:
Ok, I'm assuming it's some sort of emoji, but I'll read a symbol on the
web using NVDA that says something that is pronounced as "woman
fassabumming." In fact, here it is. 🤦 Oh, interesting, before copying,
it was "woman fassabumming." Now it's "person fassabumming" after being
copied and pasted. Anyway, what is this, and what is the proper
pronunciation?
Travis
|
|
|
Re: changing when Windows automatically checks for updates
To be honest, I had a strange issue where a system had all sorts
of issues due to a dead wireless card.
The card was not compatible with windows 10 though, and it was
certainly a dead card, like its company was allready in bit heaven
and the card was allready unsupported.
A new card fixed all issues.
Sadly there are places you can buy a computer for cheap with bits
in it.
Those bits may be outdated and scrap themselves though.
toggle quoted messageShow quoted text
On 23/03/2019 4:24 AM, Sarah k Alawami
wrote:
Set your active hours and it will check. I
prsonaly have mine set between 8 and 5. It checks outside of
that and if Im' on the computer Oh well. I personally don't
feel the lag but the system has mostly good parts in it.
Take care
On 21 Mar 2019, at 22:22, Kwork wrote:
Hi, I've done that, but it only seems to effect when
Windows won't start to complete updates, not when
Windows actually automatically checks for updates.
Travis
On 3/21/2019 9:33 PM, Sarah k
Alawami wrote:
Settings, last item, then windows
update. It's there. Check for active hours. I've
done this w/ nvda.
Take care
On 21 Mar 2019, at 21:22, Kwork wrote:
How do I change the time of day when
Windows 10 automatically checks for updates.
Right now it's doing so exactly at 7:29 pm, and
I feel the slight bit of sluggishness when it
does. I'd like it to check and update outside of
my active usage hours. Thanks for any help. I've
looked through settings, and haven't found
anything that will let me do it so far. If there
is something I'm missing that may not be NVDA
accessible, even that info would be helpful.
Thanks.
Travis
|
|
|
Re: woman/person fassabumming
Fassabuming is illegal is 23 states and puerto Rico.
|
|
|
I was just now trying to open a file in Word when I lost speech and had to restart NVDA. I’m using the latest version of Microsoft Office with the latest version of NVDA. Below is the log. Hope this helps. Abbie Johnson Taylor, Author https://abbiescorner.wordpress.com http://www.abbiejohnsontaylor.com abbietaylor945@... INFO - __main__ (11:00:20.681): Starting NVDA INFO - core.main (11:00:22.480): Config dir: C:\Users\Abbie T\AppData\Roaming\nvda INFO - config.ConfigManager._loadConfig (11:00:22.480): Loading config: C:\Users\Abbie T\AppData\Roaming\nvda\nvda.ini INFO - core.main (11:00:22.726): NVDA version 2018.4.1 INFO - core.main (11:00:22.726): Using Windows version 10.0.17134 workstation INFO - core.main (11:00:22.727): Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17) [MSC v.1500 32 bit (Intel)] INFO - core.main (11:00:22.727): Using comtypes version 1.1.3 INFO - core.main (11:00:22.727): Using configobj version 5.1.0 with validate version 1.0.1 INFO - synthDriverHandler.setSynth (11:00:25.005): Loaded synthDriver vocalizer INFO - core.main (11:00:25.006): Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 INFO - brailleInput.initialize (11:00:25.009): Braille input initialized INFO - braille.initialize (11:00:25.009): Using liblouis version 3.7.0 INFO - braille.BrailleHandler.setDisplayByName (11:00:25.020): Loaded braille display driver noBraille, current display has 0 cells. WARNING - core.main (11:00:25.111): Java Access Bridge not available INFO - _UIAHandler.UIAHandler.MTAThreadFunc (11:00:25.119): UIAutomation: IUIAutomation5 INFO - core.main (11:00:27.221): NVDA initialized INFO - braille.BrailleHandler.setDisplayByName (11:00:30.226): Loaded braille display driver noBraille, current display has 0 cells. INFO - config.ConfigManager._loadConfig (11:00:48.809): Loading config: C:\Users\Abbie T\AppData\Roaming\nvda\profiles\microsoft word.ini INFO - braille.BrailleHandler.setDisplayByName (11:00:53.941): Loaded braille display driver noBraille, current display has 0 cells. INFO - braille.BrailleHandler.setDisplayByName (11:00:59.075): Loaded braille display driver noBraille, current display has 0 cells. INFO - brailleDisplayDrivers.brailliantB.BrailleDisplayDriver.__init__ (11:01:46.911): Found display with 32 cells connected via serial (COM4) INFO - braille.BrailleHandler.setDisplayByName (11:01:46.911): Loaded braille display driver brailliantB, current display has 32 cells. ERROR - core.CorePump.run (11:03:03.316): errors in this core pump cycle Traceback (most recent call last): File "core.pyo", line 490, in run File "braille.pyo", line 2156, in pumpAll File "braille.pyo", line 1898, in handlePendingCaretUpdate File "braille.pyo", line 1904, in _doCursorMove File "braille.pyo", line 949, in update File "braille.pyo", line 791, in _getSelection File "documentBase.pyo", line 24, in makeTextInfo File "NVDAObjects\UIA\__init__.pyo", line 297, in __init__ RuntimeError -- Abbie Johnson Taylor, Author http://www.abbiejohnsontaylor.comhttp://abbiescorner.wordpress.comabbietaylor945@...
|
|
|
Re: woman/person fassabumming
Sarah k Alawami
No, it's correct. I facepalm a lot. That is a term used here in the USA I believe. At least tha'ts the only plac i've heard it and I've trveled mostly everywhare. Lol!
toggle quoted messageShow quoted text
On 22 Mar 2019, at 9:49, Brian's Mail list account via Groups.Io wrote:
Agree, I was just thinking of an alternative we should use. hand over face maybe?
Brian
bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "JM Casey" <jmcasey@...>
To: <nvda@nvda.groups.io>
Sent: Friday, March 22, 2019 4:04 PM
Subject: Re: [nvda] woman/person fassabumming
You got your answer.
This topic made me laugh for some reason.
I'm sure sometimes these lists cause a lot of facepalming.
:P
-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Kwork
Sent: March 22, 2019 11:48 AM
To: nvda@nvda.groups.io
Subject: [nvda] woman/person fassabumming
Ok, I'm assuming it's some sort of emoji, but I'll read a symbol on the web using NVDA that says something that is pronounced as "woman fassabumming." In fact, here it is. 🤦 Oh, interesting, before copying, it was "woman fassabumming." Now it's "person fassabumming" after being copied and pasted. Anyway, what is this, and what is the proper pronunciation?
Travis
|
|
|
Re: woman/person fassabumming
Sarah k Alawami
It is "woman facepalming."
Take care
toggle quoted messageShow quoted text
On 22 Mar 2019, at 8:48, Kwork wrote:
Ok, I'm assuming it's some sort of emoji, but I'll read a symbol on the web using NVDA that says something that is pronounced as "woman fassabumming." In fact, here it is. 🤦 Oh, interesting, before copying, it was "woman fassabumming." Now it's "person fassabumming" after being copied and pasted. Anyway, what is this, and what is the proper pronunciation?
Travis
|
|
|
Re: woman/person fassabumming
Brian's Mail list account
Agree, I was just thinking of an alternative we should use. hand over face maybe?
Brian
bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
toggle quoted messageShow quoted text
----- Original Message -----
From: "JM Casey" <jmcasey@...>
To: <nvda@nvda.groups.io>
Sent: Friday, March 22, 2019 4:04 PM
Subject: Re: [nvda] woman/person fassabumming
You got your answer.
This topic made me laugh for some reason.
I'm sure sometimes these lists cause a lot of facepalming.
:P
-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Kwork
Sent: March 22, 2019 11:48 AM
To: nvda@nvda.groups.io
Subject: [nvda] woman/person fassabumming
Ok, I'm assuming it's some sort of emoji, but I'll read a symbol on the web using NVDA that says something that is pronounced as "woman fassabumming." In fact, here it is. 🤦 Oh, interesting, before copying, it was "woman fassabumming." Now it's "person fassabumming" after being copied and pasted. Anyway, what is this, and what is the proper pronunciation?
Travis
|
|
|
Re: woman/person fassabumming
Brian's Mail list account
Oh how funny in Espeak I'd suggest what it actually sounded like is anatomically impossible!
Brian
bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
toggle quoted messageShow quoted text
----- Original Message ----- From: "Kwork" <istherelife@...> To: <nvda@nvda.groups.io> Sent: Friday, March 22, 2019 3:48 PM Subject: [nvda] woman/person fassabumming Ok, I'm assuming it's some sort of emoji, but I'll read a symbol on the web using NVDA that says something that is pronounced as "woman fassabumming." In fact, here it is. 🤦 Oh, interesting, before copying, it was "woman fassabumming." Now it's "person fassabumming" after being copied and pasted. Anyway, what is this, and what is the proper pronunciation?
Travis
|
|
|
Re: My Log from Yesterday
Brian's Mail list account
So you have a profile set up for outlook, and the problem looks like it has something to do with Braille.
But then I guess you saw that as well. One assumes you were browsing a web site so what has an outlook profile got to do with that one wonders.
Brian
bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
toggle quoted messageShow quoted text
----- Original Message ----- From: "Abbie Taylor" <abbietaylor945@...> To: "NVDA" <nvda@nvda.groups.io> Sent: Friday, March 22, 2019 2:21 PM Subject: [nvda] My Log from Yesterday The problem I experienced happened yesterday, and all seems to be working
well here now. Anyway, here's the log I inquired about sending yesterday. I
would have replied to that particular message, but for some reason, the
Reply link isn't showing up on the site, and since I get messages from this
group in daily summary mode, that's the only way I can reply. Anyway, here's
the log. If this issue happens again, I'll send another.
Abbie Johnson Taylor, Author <https://abbiescorner.wordpress.com>
https://abbiescorner.wordpress.com
http://www.abbiejohnsontaylor.com
abbietaylor945@...
INFO - __main__ (07:44:59.566):
Starting NVDA
INFO - core.main (07:45:00.490):
Config dir: C:\Users\Abbie T\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (07:45:00.490):
Loading config: C:\Users\Abbie T\AppData\Roaming\nvda\nvda.ini
INFO - core.main (07:45:00.677):
NVDA version 2018.4.1
INFO - core.main (07:45:00.677):
Using Windows version 10.0.17134 workstation
INFO - core.main (07:45:00.677):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17) [MSC
v.1500 32 bit (Intel)]
INFO - core.main (07:45:00.677):
Using comtypes version 1.1.3
INFO - core.main (07:45:00.677):
Using configobj version 5.1.0 with validate version 1.0.1
INFO - synthDriverHandler.setSynth (07:45:06.408):
Loaded synthDriver vocalizer
INFO - core.main (07:45:06.671):
Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5
INFO - brailleInput.initialize (07:45:06.671):
Braille input initialized
INFO - braille.initialize (07:45:06.671):
Using liblouis version 3.7.0
INFO - braille.BrailleHandler.setDisplayByName (07:45:06.687):
Loaded braille display driver noBraille, current display has 0 cells.
WARNING - core.main (07:45:06.809):
Java Access Bridge not available
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (07:45:07.125):
UIAutomation: IUIAutomation5
INFO - core.main (07:45:08.233):
NVDA initialized
INFO - braille.BrailleHandler.setDisplayByName (07:45:12.289):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - brailleDisplayDrivers.brailliantB.BrailleDisplayDriver.__init__
(07:45:49.243):
Found display with 32 cells connected via serial (COM4)
INFO - braille.BrailleHandler.setDisplayByName (07:45:49.243):
Loaded braille display driver brailliantB, current display has 32 cells.
ERROR - scriptHandler.executeScript (07:47:42.365):
error executing script: <bound method ChromeVBuf.script_activatePosition of
<NVDAObjects.IAccessible.chromium.ChromeVBuf object at 0x062FFB50>> with
gesture u'enter'
Traceback (most recent call last):
File "scriptHandler.pyo", line 187, in executeScript
File "browseMode.pyo", line 475, in script_activatePosition
File "browseMode.pyo", line 1206, in _activatePosition
File "browseMode.pyo", line 466, in _activatePosition
File "treeInterceptorHandler.pyo", line 119, in _set_passThrough
File "review.pyo", line 127, in setCurrentMode
File "api.pyo", line 196, in setReviewPosition
File "braille.pyo", line 1980, in handleReviewMove
File "braille.pyo", line 1856, in _doNewObject
File "braille.pyo", line 1539, in getFocusRegions
File "braille.pyo", line 1018, in update
File "documentBase.pyo", line 24, in makeTextInfo
File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 83, in __init__
File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 201, in
_findContentDescendant
COMError: (-2147467259, 'Unspecified error', (None, None, None, 0, None))
ERROR - scriptHandler.executeScript (07:53:30.957):
error executing script: <bound method ChromeVBuf.script_activatePosition of
<NVDAObjects.IAccessible.chromium.ChromeVBuf object at 0x062FFB50>> with
gesture u'enter'
Traceback (most recent call last):
File "scriptHandler.pyo", line 187, in executeScript
File "browseMode.pyo", line 475, in script_activatePosition
File "browseMode.pyo", line 1206, in _activatePosition
File "browseMode.pyo", line 466, in _activatePosition
File "treeInterceptorHandler.pyo", line 119, in _set_passThrough
File "review.pyo", line 127, in setCurrentMode
File "api.pyo", line 196, in setReviewPosition
File "braille.pyo", line 1980, in handleReviewMove
File "braille.pyo", line 1856, in _doNewObject
File "braille.pyo", line 1539, in getFocusRegions
File "braille.pyo", line 1018, in update
File "documentBase.pyo", line 24, in makeTextInfo
File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 83, in __init__
File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 201, in
_findContentDescendant
COMError: (-2147467259, 'Unspecified error', (None, None, None, 0, None))
INFO - config.ConfigManager._loadConfig (07:55:03.604):
Loading config: C:\Users\Abbie T\AppData\Roaming\nvda\profiles\outlook.ini
ERROR - RPC process 6636 (nvda_slave.exe) (07:55:04.312):
__main__.main:
slave error
Traceback (most recent call last):
File "nvda_slave.pyw", line 94, in main
File "comHelper.pyo", line 22, in _lresultFromGetActiveObject
File "comtypes\client\__init__.pyo", line 180, in GetActiveObject
File "comtypes\__init__.pyo", line 1247, in GetActiveObject
File "_ctypes/callproc.c", line 950, in GetResult
WindowsError: [Error -2147221021] Operation unavailable
|
|
|
Re: My Log from Yesterday
Were I you, Abbie, I'd be checking my hard drive for errors right about now.
toggle quoted messageShow quoted text
On 3/22/19, Abbie Taylor <abbietaylor945@...> wrote: The problem I experienced happened yesterday, and all seems to be working
well here now. Anyway, here's the log I inquired about sending yesterday. I
would have replied to that particular message, but for some reason, the
Reply link isn't showing up on the site, and since I get messages from this
group in daily summary mode, that's the only way I can reply. Anyway,
here's
the log. If this issue happens again, I'll send another.
Abbie Johnson Taylor, Author <https://abbiescorner.wordpress.com>
https://abbiescorner.wordpress.com
http://www.abbiejohnsontaylor.com
abbietaylor945@...
INFO - __main__ (07:44:59.566):
Starting NVDA
INFO - core.main (07:45:00.490):
Config dir: C:\Users\Abbie T\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (07:45:00.490):
Loading config: C:\Users\Abbie T\AppData\Roaming\nvda\nvda.ini
INFO - core.main (07:45:00.677):
NVDA version 2018.4.1
INFO - core.main (07:45:00.677):
Using Windows version 10.0.17134 workstation
INFO - core.main (07:45:00.677):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17)
[MSC
v.1500 32 bit (Intel)]
INFO - core.main (07:45:00.677):
Using comtypes version 1.1.3
INFO - core.main (07:45:00.677):
Using configobj version 5.1.0 with validate version 1.0.1
INFO - synthDriverHandler.setSynth (07:45:06.408):
Loaded synthDriver vocalizer
INFO - core.main (07:45:06.671):
Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5
INFO - brailleInput.initialize (07:45:06.671):
Braille input initialized
INFO - braille.initialize (07:45:06.671):
Using liblouis version 3.7.0
INFO - braille.BrailleHandler.setDisplayByName (07:45:06.687):
Loaded braille display driver noBraille, current display has 0 cells.
WARNING - core.main (07:45:06.809):
Java Access Bridge not available
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (07:45:07.125):
UIAutomation: IUIAutomation5
INFO - core.main (07:45:08.233):
NVDA initialized
INFO - braille.BrailleHandler.setDisplayByName (07:45:12.289):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - brailleDisplayDrivers.brailliantB.BrailleDisplayDriver.__init__
(07:45:49.243):
Found display with 32 cells connected via serial (COM4)
INFO - braille.BrailleHandler.setDisplayByName (07:45:49.243):
Loaded braille display driver brailliantB, current display has 32 cells.
ERROR - scriptHandler.executeScript (07:47:42.365):
error executing script: <bound method ChromeVBuf.script_activatePosition of
<NVDAObjects.IAccessible.chromium.ChromeVBuf object at 0x062FFB50>> with
gesture u'enter'
Traceback (most recent call last):
File "scriptHandler.pyo", line 187, in executeScript
File "browseMode.pyo", line 475, in script_activatePosition
File "browseMode.pyo", line 1206, in _activatePosition
File "browseMode.pyo", line 466, in _activatePosition
File "treeInterceptorHandler.pyo", line 119, in _set_passThrough
File "review.pyo", line 127, in setCurrentMode
File "api.pyo", line 196, in setReviewPosition
File "braille.pyo", line 1980, in handleReviewMove
File "braille.pyo", line 1856, in _doNewObject
File "braille.pyo", line 1539, in getFocusRegions
File "braille.pyo", line 1018, in update
File "documentBase.pyo", line 24, in makeTextInfo
File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 83, in __init__
File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 201, in
_findContentDescendant
COMError: (-2147467259, 'Unspecified error', (None, None, None, 0, None))
ERROR - scriptHandler.executeScript (07:53:30.957):
error executing script: <bound method ChromeVBuf.script_activatePosition of
<NVDAObjects.IAccessible.chromium.ChromeVBuf object at 0x062FFB50>> with
gesture u'enter'
Traceback (most recent call last):
File "scriptHandler.pyo", line 187, in executeScript
File "browseMode.pyo", line 475, in script_activatePosition
File "browseMode.pyo", line 1206, in _activatePosition
File "browseMode.pyo", line 466, in _activatePosition
File "treeInterceptorHandler.pyo", line 119, in _set_passThrough
File "review.pyo", line 127, in setCurrentMode
File "api.pyo", line 196, in setReviewPosition
File "braille.pyo", line 1980, in handleReviewMove
File "braille.pyo", line 1856, in _doNewObject
File "braille.pyo", line 1539, in getFocusRegions
File "braille.pyo", line 1018, in update
File "documentBase.pyo", line 24, in makeTextInfo
File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 83, in __init__
File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 201, in
_findContentDescendant
COMError: (-2147467259, 'Unspecified error', (None, None, None, 0, None))
INFO - config.ConfigManager._loadConfig (07:55:03.604):
Loading config: C:\Users\Abbie T\AppData\Roaming\nvda\profiles\outlook.ini
ERROR - RPC process 6636 (nvda_slave.exe) (07:55:04.312):
__main__.main:
slave error
Traceback (most recent call last):
File "nvda_slave.pyw", line 94, in main
File "comHelper.pyo", line 22, in _lresultFromGetActiveObject
File "comtypes\client\__init__.pyo", line 180, in GetActiveObject
File "comtypes\__init__.pyo", line 1247, in GetActiveObject
File "_ctypes/callproc.c", line 950, in GetResult
WindowsError: [Error -2147221021] Operation unavailable
-- Subscribe to a WordPress for Newbies Mailing List by sending a message to: wp4newbs-request@... with 'subscribe' in the Subject field OR by visiting the list page at http://www.freelists.org/list/wp4newbs& check out my sites at www.brighter-vision.com & www.mysitesbeenhacked.com
|
|
|
Rui, that was pretty confusing. At first I thought this was Abbie's
log, because she was the thread starter. Made even more confusing by
the fact that she'd sent a log very much different from the 1 in this
thread. I haven't had my full coffee quota yet, thus the main reason
for the confusion, but I also think it would likely help if you
started your own thread to avoid my poor little pea brain from getting
all tangled up around itself in future. Maybe others get confused as
well, I dunno, but I know it took me a minute or 2 to figure out
precisely what was occurring.
Normally when I ask folks for logs--& I do so quite regularly--I ask
them to put their name & date in the subject, ie, Rui Fontes log for
2019/03/21 or similar. That way I'm very clear on what I'm looking
at--& it often helps me know better what I'm looking for. Just a
suggestion--& no--I'm not vying for Brian V's job at all--that's not
my intent here. Just a conversation between folks who've known 1
another for years, asking for help so as not to get all tangled up in
the confusion zone.
toggle quoted messageShow quoted text
On 3/22/19, Rui Fontes <rui.fontes@...> wrote: Here is my log:
I was sending a message through Mozilla Thunderbird...
INFO - __main__ (10:23:39.753):
Starting NVDA
INFO - core.main (10:23:39.907):
Config dir: C:\Users\tiflo\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (10:23:39.907):
Loading config: C:\Users\tiflo\AppData\Roaming\nvda\nvda.ini
INFO - core.main (10:23:40.003):
Developer Scratchpad mode enabled
DEBUG - core.main (10:23:40.125):
setting language to pt_PT
INFO - core.main (10:23:40.174):
NVDA version 2019.1rc1
INFO - core.main (10:23:40.174):
Using Windows version 10.0.17763 workstation
INFO - core.main (10:23:40.174):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17)
[MSC v.1500 32 bit (Intel)]
INFO - core.main (10:23:40.174):
Using comtypes version 1.1.3
INFO - core.main (10:23:40.174):
Using configobj version 5.1.0 with validate version 1.0.1
DEBUG - core.main (10:23:40.184):
Initializing add-ons system
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.196):
Listing add-ons from C:\Users\tiflo\AppData\Roaming\nvda\addons
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.196):
Loading add-on from C:\Users\tiflo\AppData\Roaming\nvda\addons\addonUpdater
DEBUG - addonHandler.Addon.__init__ (10:23:40.203):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\addonUpdater\locale\pt_PT\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.213):
Found add-on addonUpdater - 19.03. Requires API: (2018, 4, 0).
Last-tested API: (2019, 1, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.213):
Loading add-on from
C:\Users\tiflo\AppData\Roaming\nvda\addons\applicationsDictionary
DEBUG - addonHandler.Addon.__init__ (10:23:40.232):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\applicationsDictionary\locale\pt_PT\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.246):
Found add-on applicationsDictionary - 1.0-beta. Requires API: (2017, 1,
0). Last-tested API: (2019, 1, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.246):
Disabling add-on applicationsDictionary
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.246):
Loading add-on from C:\Users\tiflo\AppData\Roaming\nvda\addons\brailleme
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.250):
Found add-on brailleme - 0.5. Requires API: (2018, 2, 0). Last-tested
API: (2019, 1, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.250):
Loading add-on from C:\Users\tiflo\AppData\Roaming\nvda\addons\browsernav
DEBUG - addonHandler.Addon.__init__ (10:23:40.260):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\browsernav\locale\pt_PT\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.270):
Found add-on browsernav - 1.1. Requires API: (2018, 1, 0). Last-tested
API: (2019, 1, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.276):
Loading add-on from
C:\Users\tiflo\AppData\Roaming\nvda\addons\clipContentsDesigner
DEBUG - addonHandler.Addon.__init__ (10:23:40.282):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\clipContentsDesigner\locale\pt_PT\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.282):
Found add-on clipContentsDesigner - 8.8. Requires API: (2018, 2, 0).
Last-tested API: (2019, 1, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.282):
Loading add-on from C:\Users\tiflo\AppData\Roaming\nvda\addons\clock
DEBUG - addonHandler.Addon.__init__ (10:23:40.292):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\clock\locale\pt_PT\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.302):
Found add-on clock - 19.03. Requires API: (2014, 3, 0). Last-tested API:
(2019, 1, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.306):
Loading add-on from
C:\Users\tiflo\AppData\Roaming\nvda\addons\controlUsageAssistant
DEBUG - addonHandler.Addon.__init__ (10:23:40.322):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\controlUsageAssistant\locale\pt_PT\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.335):
Found add-on controlUsageAssistant - 2.4. Requires API: (2014, 3, 0).
Last-tested API: (2019, 1, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.335):
Disabling add-on controlUsageAssistant
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.335):
Loading add-on from C:\Users\tiflo\AppData\Roaming\nvda\addons\DelightGames
DEBUG - addonHandler.Addon.__init__ (10:23:40.351):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\DelightGames\locale\pt_PT\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.361):
Found add-on DelightGames - 1.0-dev. Requires API: (2018, 3, 0).
Last-tested API: (2019, 1, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.361):
Disabling add-on DelightGames
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.361):
Loading add-on from C:\Users\tiflo\AppData\Roaming\nvda\addons\emoticons
DEBUG - addonHandler.Addon.__init__ (10:23:40.381):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\emoticons\locale\pt_PT\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.385):
Found add-on emoticons - 9.1. Requires API: (2018, 3, 0). Last-tested
API: (2019, 1, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.385):
Disabling add-on emoticons
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.391):
Loading add-on from C:\Users\tiflo\AppData\Roaming\nvda\addons\goldenCursor
DEBUG - addonHandler.Addon.__init__ (10:23:40.391):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\goldenCursor\locale\pt_PT\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.401):
Found add-on goldenCursor - 3.4. Requires API: (2017, 3, 0). Last-tested
API: (2019, 1, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.401):
Disabling add-on goldenCursor
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.421):
Loading add-on from
C:\Users\tiflo\AppData\Roaming\nvda\addons\ImageDescriber
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.430):
Found add-on ImageDescriber - 1.2.1. Requires API: (2013, 1, 0).
Last-tested API: (2019, 1, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.430):
Loading add-on from C:\Users\tiflo\AppData\Roaming\nvda\addons\inputLock
DEBUG - addonHandler.Addon.__init__ (10:23:40.440):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\inputLock\locale\pt_PT\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.451):
Found add-on inputLock - 1.7. Requires API: (2017, 3, 0). Last-tested
API: (2019, 1, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.451):
Disabling add-on inputLock
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.451):
Loading add-on from C:\Users\tiflo\AppData\Roaming\nvda\addons\Mozilla
DEBUG - addonHandler.Addon.__init__ (10:23:40.460):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\Mozilla\locale\pt_PT\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.460):
Found add-on Mozilla - 1.7. Requires API: (2018, 1, 0). Last-tested API:
(2019, 1, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.460):
Loading add-on from
C:\Users\tiflo\AppData\Roaming\nvda\addons\NVDAExtensionGlobalPlugin
DEBUG - addonHandler.Addon.__init__ (10:23:40.476):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\NVDAExtensionGlobalPlugin\locale\pt\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.496):
Found add-on NVDAExtensionGlobalPlugin - 7.3.1dev10. Requires API:
(2018, 2, 0). Last-tested API: (2019, 1, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.496):
Loading add-on from
C:\Users\tiflo\AppData\Roaming\nvda\addons\outlookExtended
DEBUG - addonHandler.Addon.__init__ (10:23:40.506):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\outlookExtended\locale\pt_PT\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.522):
Found add-on outlookExtended - 1.1. Requires API: (2018, 3, 0).
Last-tested API: (2019, 1, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.522):
Loading add-on from C:\Users\tiflo\AppData\Roaming\nvda\addons\partialLines
DEBUG - addonHandler.Addon.__init__ (10:23:40.532):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\partialLines\locale\pt\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.546):
Found add-on partialLines - 0.1. Requires API: (2017, 4, 0). Last-tested
API: (2019, 1, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.546):
Loading add-on from
C:\Users\tiflo\AppData\Roaming\nvda\addons\poeditMadeEasy
DEBUG - addonHandler.Addon.__init__ (10:23:40.556):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\poeditMadeEasy\locale\en\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.562):
Found add-on poeditMadeEasy - 3.2. Requires API: (2017, 4, 0).
Last-tested API: (2019, 1, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.562):
Loading add-on from
C:\Users\tiflo\AppData\Roaming\nvda\addons\profilesSwitcher
DEBUG - addonHandler.Addon.__init__ (10:23:40.572):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\profilesSwitcher\locale\pt_PT\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.591):
Found add-on profilesSwitcher - 1.1. Requires API: (2018, 3, 0).
Last-tested API: (2018, 4, 1)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.591):
Loading add-on from C:\Users\tiflo\AppData\Roaming\nvda\addons\QTranslate
DEBUG - addonHandler.Addon.__init__ (10:23:40.614):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\QTranslate\locale\pt_PT\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.631):
Found add-on QTranslate - 1.0-dev. Requires API: (2018, 3, 0).
Last-tested API: (2019, 1, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.631):
Loading add-on from C:\Users\tiflo\AppData\Roaming\nvda\addons\remote
DEBUG - addonHandler.Addon.__init__ (10:23:40.647):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\remote\locale\pt\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.651):
Found add-on remote - 2.2. Requires API: (2017, 4, 0). Last-tested API:
(2019, 1, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.651):
Loading add-on from
C:\Users\tiflo\AppData\Roaming\nvda\addons\sayProductNameAndVersion
DEBUG - addonHandler.Addon.__init__ (10:23:40.661):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\sayProductNameAndVersion\locale\pt_PT\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.677):
Found add-on sayProductNameAndVersion - 1.0.2012060901. Requires API:
(2013, 1, 0). Last-tested API: (2019, 1, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.680):
Loading add-on from
C:\Users\tiflo\AppData\Roaming\nvda\addons\screenCurtain
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.690):
Found add-on screenCurtain - 20190114. Requires API: (2018, 2, 0).
Last-tested API: (2019, 1, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.690):
Disabling add-on screenCurtain
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.690):
Loading add-on from
C:\Users\tiflo\AppData\Roaming\nvda\addons\screenRapping
DEBUG - addonHandler.Addon.__init__ (10:23:40.706):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\screenRapping\locale\pt\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.732):
Found add-on screenRapping - 1.4. Requires API: (2017, 3, 0).
Last-tested API: (2019, 1, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.732):
Loading add-on from C:\Users\tiflo\AppData\Roaming\nvda\addons\SentenceNav
DEBUG - addonHandler.Addon.__init__ (10:23:40.746):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\SentenceNav\locale\pt_PT\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.762):
Found add-on SentenceNav - 2.5. Requires API: (2018, 1, 0). Last-tested
API: (2019, 1, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.765):
Loading add-on from C:\Users\tiflo\AppData\Roaming\nvda\addons\skype
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.766):
Found add-on skype - 2018.03.1. Requires API: (0, 0, 0). Last-tested
API: (0, 0, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.766):
Disabling add-on skype
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.772):
Loading add-on from
C:\Users\tiflo\AppData\Roaming\nvda\addons\textInformation
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.785):
Found add-on textInformation - 1.0. Requires API: (2014, 3, 0).
Last-tested API: (2019, 1, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.786):
Loading add-on from C:\Users\tiflo\AppData\Roaming\nvda\addons\textnav
DEBUG - addonHandler.Addon.__init__ (10:23:40.796):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\textnav\locale\pt_PT\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.806):
Found add-on textnav - 1.2. Requires API: (2018, 1, 0). Last-tested API:
(2019, 1, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.806):
Loading add-on from
C:\Users\tiflo\AppData\Roaming\nvda\addons\toolbarsExplorer
DEBUG - addonHandler.Addon.__init__ (10:23:40.816):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\toolbarsExplorer\locale\pt_PT\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.826):
Found add-on toolbarsExplorer - 1.1. Requires API: (2017, 3, 0).
Last-tested API: (2019, 1, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.826):
Loading add-on from C:\Users\tiflo\AppData\Roaming\nvda\addons\translate
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.842):
Found add-on translate - 2019.03.3. Requires API: (2018, 3, 0).
Last-tested API: (2018, 4, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.842):
Loading add-on from
C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer-driver
DEBUG - addonHandler.Addon.__init__ (10:23:40.855):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer-driver\locale\pt_PT\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.858):
Found add-on vocalizer-driver - 2.0.3. Requires API: (2017, 4, 0).
Last-tested API: (2019, 1, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.861):
Loading add-on from
C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer-expressive-voice-catarina
Plus
DEBUG - addonHandler.Addon.__init__ (10:23:40.871):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer-expressive-voice-catarina
Plus\locale\pt\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.878):
Found add-on vocalizer-expressive-voice-catarina Plus - 1.1.1. Requires
API: (2013, 2, 0). Last-tested API: (2099, 4, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.878):
Loading add-on from
C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer-expressive-voice-english
Compact
DEBUG - addonHandler.Addon.__init__ (10:23:40.898):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer-expressive-voice-english
Compact\locale\pt\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.918):
Found add-on vocalizer-expressive-voice-english Compact - 1.1.1.
Requires API: (2013, 2, 0). Last-tested API: (2099, 4, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.918):
Loading add-on from
C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer-expressive-voice-kyoko
Plus
DEBUG - addonHandler.Addon.__init__ (10:23:40.931):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer-expressive-voice-kyoko
Plus\locale\pt\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.951):
Found add-on vocalizer-expressive-voice-kyoko Plus - 1.1.1. Requires
API: (2013, 2, 0). Last-tested API: (2099, 4, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.951):
Loading add-on from
C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer-expressive-voice-portugueseAndSpanish
Compact Voices
DEBUG - addonHandler.Addon.__init__ (10:23:40.971):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer-expressive-voice-portugueseAndSpanish
Compact Voices\locale\pt\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.990):
Found add-on vocalizer-expressive-voice-portugueseAndSpanish Compact
Voices - 1.1.1. Requires API: (2013, 2, 0). Last-tested API: (2099, 4, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:40.990):
Loading add-on from
C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer-voice-joana
DEBUG - addonHandler.Addon.__init__ (10:23:41.002):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer-voice-joana\locale\pt\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:41.009):
Found add-on vocalizer-voice-joana - 5.5. Requires API: (2013, 2, 0).
Last-tested API: (2099, 4, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:41.009):
Loading add-on from
C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer_expressive_driver
DEBUG - addonHandler.Addon.__init__ (10:23:41.022):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\locale\pt_PT\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:41.081):
Found add-on vocalizer_expressive_driver - 3.0.14. Requires API: (2013,
2, 0). Last-tested API: (2019, 1, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:41.081):
Loading add-on from C:\Users\tiflo\AppData\Roaming\nvda\addons\Weather Plus
DEBUG - addonHandler.Addon.__init__ (10:23:41.121):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\Weather
Plus\locale\pt_PT\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:41.141):
Found add-on Weather Plus - 5.0_13.03.2019. Requires API: (2017, 3, 0).
Last-tested API: (2019, 1, 0)
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:41.141):
Loading add-on from C:\Users\tiflo\AppData\Roaming\nvda\addons\wintenApps
DEBUG - addonHandler.Addon.__init__ (10:23:41.157):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\wintenApps\locale\pt_PT\manifest.ini
DEBUG - addonHandler._getAvailableAddonsFromPath (10:23:41.161):
Found add-on wintenApps - 19.03.2. Requires API: (2018, 3, 0).
Last-tested API: (2019, 1, 0)
DEBUGWARNING - touchHandler.touchSupported (10:23:41.325):
No touch devices found
DEBUG - core.main (10:23:41.424):
Initializing appModule Handler
DEBUG - addonHandler.Addon.addToPackagePath (10:23:41.424):
Addon Mozilla added to appModules package path
DEBUG - addonHandler.Addon.addToPackagePath (10:23:41.424):
Addon outlookExtended added to appModules package path
DEBUG - addonHandler.Addon.addToPackagePath (10:23:41.438):
Addon poeditMadeEasy added to appModules package path
DEBUG - addonHandler.Addon.addToPackagePath (10:23:41.438):
Addon QTranslate added to appModules package path
DEBUG - addonHandler.Addon.addToPackagePath (10:23:41.438):
Addon wintenApps added to appModules package path
DEBUG - core.main (10:23:41.438):
Initializing NVDAHelper
DEBUG - core.main (10:23:41.512):
Speech Dictionary processing
DEBUG - speechDictHandler.SpeechDict.load (10:23:41.512):
Loading speech dictionary
'C:\Users\tiflo\AppData\Roaming\nvda\speechDicts\default.dic'...
DEBUG - speechDictHandler.SpeechDict.load (10:23:41.539):
3 loaded records.
DEBUG - speechDictHandler.SpeechDict.load (10:23:41.539):
Loading speech dictionary 'builtin.dic'...
DEBUG - speechDictHandler.SpeechDict.load (10:23:41.539):
3 loaded records.
DEBUG - core.main (10:23:41.539):
Initializing speech
DEBUG - addonHandler.Addon.addToPackagePath (10:23:41.539):
Addon vocalizer-driver added to synthDrivers package path
DEBUG - addonHandler.Addon.addToPackagePath (10:23:41.539):
Addon vocalizer_expressive_driver added to synthDrivers package path
INFO - core.main (10:23:41.900):
Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5
DEBUG - core.main (10:23:41.900):
Initializing braille input
INFO - brailleInput.initialize (10:23:41.900):
Braille input initialized
DEBUG - core.main (10:23:41.900):
Initializing braille
DEBUG - addonHandler.Addon.addToPackagePath (10:23:41.900):
Addon brailleme added to brailleDisplayDrivers package path
INFO - braille.initialize (10:23:41.914):
Using liblouis version 3.8.0
INFO - braille.BrailleHandler.setDisplayByName (10:23:41.914):
Loaded braille display driver noBraille, current display has 0 cells.
DEBUG - core.main (10:23:41.914):
Initializing displayModel
DEBUG - core.main (10:23:41.914):
Initializing GUI
DEBUG - core.main (10:23:42.013):
initializing Java Access Bridge support
WARNING - core.main (10:23:42.013):
Java Access Bridge not available
DEBUG - core.main (10:23:42.013):
Initializing winConsole support
DEBUG - core.main (10:23:42.013):
Initializing UIA support
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (10:23:42.026):
UIAutomation: IUIAutomation6
DEBUG - core.main (10:23:42.200):
Initializing IAccessible support
DEBUG - core.main (10:23:42.200):
Initializing input core
DEBUG - core.main (10:23:42.214):
Initializing keyboard handler
DEBUG - core.main (10:23:42.214):
initializing mouse handler
DEBUG - core.main (10:23:42.334):
Initializing touchHandler
DEBUGWARNING - touchHandler.touchSupported (10:23:42.334):
No touch devices found
DEBUG - core.main (10:23:42.334):
Initializing global plugin handler
DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.334):
Addon addonUpdater added to globalPlugins package path
DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.334):
Addon browsernav added to globalPlugins package path
DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.334):
Addon clipContentsDesigner added to globalPlugins package path
DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.334):
Addon clock added to globalPlugins package path
DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.342):
Addon ImageDescriber added to globalPlugins package path
DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.342):
Addon NVDAExtensionGlobalPlugin added to globalPlugins package path
DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.342):
Addon partialLines added to globalPlugins package path
DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.344):
Addon profilesSwitcher added to globalPlugins package path
DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.344):
Addon remote added to globalPlugins package path
DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.344):
Addon sayProductNameAndVersion added to globalPlugins package path
DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.344):
Addon screenRapping added to globalPlugins package path
DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.344):
Addon SentenceNav added to globalPlugins package path
DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.344):
Addon textInformation added to globalPlugins package path
DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.344):
Addon textnav added to globalPlugins package path
DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.344):
Addon toolbarsExplorer added to globalPlugins package path
DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.344):
Addon translate added to globalPlugins package path
DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.344):
Addon vocalizer-driver added to globalPlugins package path
DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.351):
Addon vocalizer_expressive_driver added to globalPlugins package path
DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.351):
Addon Weather Plus added to globalPlugins package path
DEBUG - addonHandler.Addon.addToPackagePath (10:23:42.351):
Addon wintenApps added to globalPlugins package path
DEBUG - external:globalPlugins.wintenObjs.GlobalPlugin.__init__
(10:23:42.394):
W10: adding additional events
DEBUG - external:globalPlugins.wintenObjs.GlobalPlugin.__init__
(10:23:42.404):
W10: added event ID 20036, assigned to UIA_activeTextPositionChanged
DEBUG - external:globalPlugins.wintenObjs.GlobalPlugin.__init__
(10:23:42.404):
W10: added event ID 20026, assigned to UIA_dragStart
DEBUG - external:globalPlugins.wintenObjs.GlobalPlugin.__init__
(10:23:42.414):
W10: added event ID 20027, assigned to UIA_dragCancel
DEBUG - external:globalPlugins.wintenObjs.GlobalPlugin.__init__
(10:23:42.414):
W10: added event ID 20028, assigned to UIA_dragComplete
INFO - brailleDisplayDrivers.handyTech.BrailleDisplayDriver.__init__
(10:23:42.473):
Found Basic Braille 20 connected via serial (COM4)
DEBUG - braille.BrailleHandler.setDisplayByName (10:23:42.473):
Switching braille display from noBraille to handyTech
INFO - braille.BrailleHandler.setDisplayByName (10:23:42.473):
Loaded braille display driver handyTech, current display has 20 cells.
DEBUG - addonHandler.Addon.__init__ (10:23:42.875):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\Weather
Plus\locale\pt_PT\manifest.ini
DEBUG - NVDAObjects.NVDAObject._get_placeholder (10:23:42.888):
Potential unimplemented child class: <NVDAObjects.window.Desktop object
at 0x0490DD70>
IO - braille.BrailleBuffer.update (10:23:42.894):
Braille regions text: [u'Ambiente de trabalho jan']
IO - braille.BrailleHandler.update (10:23:42.894):
Braille window dots: 17 134 12 24 15 1345 2345 15 - 145 15 - 2345 1235 1
12 1 123 125 135
DEBUGWARNING - Python warning (10:23:43.838):
C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\synthDrivers\vocalizer_expressive\_config.py:11:
DeprecationWarning: Importing validate directly is deprecated. Please
use configobj.validate instead
DEBUG -
external:synthDrivers.vocalizer_expressive.storage._loadLicenseData
(10:23:44.243):
Loading license data from
C:\Users\tiflo\AppData\Roaming\vocalizer-for-nvda\activation.dat
DEBUGWARNING - Python warning (10:23:44.796):
C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\globalPlugins\vocalizer_expressive_globalPlugin\__init__.py:246:
wxPyDeprecationWarning: Call to deprecated item. Use Append instead.
DEBUGWARNING - Python warning (10:23:44.796):
C:\Program Files (x86)\NVDA\library.zip\wx\core.py:2337:
DeprecationWarning: Menu.Append() is deprecated
DEBUGWARNING - Python warning (10:23:44.796):
C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\globalPlugins\vocalizer_expressive_globalPlugin\__init__.py:267:
wxPyDeprecationWarning: Call to deprecated item. Use Insert instead.
DEBUG -
external:globalPlugins.vocalizer_expressive_globalPlugin.LicenseRenewer.__init__
(10:23:44.796):
License renewal starting in 0
DEBUG - addonHandler.Addon.__init__ (10:23:44.898):
Using manifest translation from
C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer-driver\locale\pt_PT\manifest.ini
DEBUGWARNING - Python warning (10:23:45.549):
C:\Users\tiflo\AppData\Roaming\nvda\addons\vocalizer-driver\globalPlugins\vocalizer_globalPlugin\__init__.py:119:
wxPyDeprecationWarning: Call to deprecated item. Use Insert instead.
INFO - external:globalPlugins.translate.GlobalPlugin.__init__
(10:23:45.963):
Translate module initialized, translating to pt_PT
ERROR - external:globalPlugins.translate.GlobalPlugin.loadLocalCache
(10:23:46.036):
Cannot read or decode data from
C:\Users\tiflo\AppData\Roaming\nvda\translation-cache: No JSON object
could be decoded
INFO -
external:globalPlugins.NVDAExtensionGlobalPlugin.GlobalPlugin.__init__
(10:23:50.631):
Loaded NVDAExtensionGlobalPlugin version 7.3.1dev10
IO - braille.BrailleBuffer.update (10:23:53.036):
Braille regions text: [u'NVDA iniciado']
IO - braille.BrailleHandler.update (10:23:53.036):
Braille window dots: 13457 12367 1457 17 - 24 1345 24 14 24 1 145 135
DEBUG - core.main (10:23:53.036):
Initializing core pump
DEBUG - core.main (10:23:53.036):
Initializing watchdog
DEBUG - core.main (10:23:53.040):
initializing updateCheck
INFO - core.main (10:23:53.051):
NVDA initialized
DEBUG - core.main (10:23:53.051):
entering wx application main loop
DEBUG -
external:globalPlugins.vocalizer_expressive_globalPlugin.LicenseRenewer._renew
(10:23:53.325):
Renewal data not available, checking later.
DEBUGWARNING -
external:globalPlugins.NVDAExtensionGlobalPlugin.utils.keyboard.getKeyboardKeysIniFilePath
(10:23:53.661):
keyboard.ini file loaded from locale\pt folder
IO -
external:globalPlugins.NVDAExtensionGlobalPlugin.commandKeysSelectiveAnnouncement.MyInputManager.executeGesture
(10:47:20.013):
Input: kb(desktop):downArrow
DEBUG - editableText.EditableText._hasCaretMoved (10:47:20.059):
Caret move detected using bookmarks. Elapsed: 0 ms
IO - speech.speak (10:47:20.148):
Speaking [u'Rui Fontes']
IO -
external:globalPlugins.NVDAExtensionGlobalPlugin.commandKeysSelectiveAnnouncement.MyInputManager.executeGesture
(10:47:21.190):
Input: kb(desktop):downArrow
DEBUG - editableText.EditableText._hasCaretMoved (10:47:21.250):
Caret move detected using bookmarks. Elapsed: 10 ms
IO -
external:globalPlugins.NVDAExtensionGlobalPlugin.commandKeysSelectiveAnnouncement.MyInputManager.executeGesture
(10:47:22.065):
Input: kb(desktop):downArrow
IO -
external:globalPlugins.NVDAExtensionGlobalPlugin.commandKeysSelectiveAnnouncement.MyInputManager.executeGesture
(10:47:22.621):
Input: kb(desktop):downArrow
IO -
external:globalPlugins.NVDAExtensionGlobalPlugin.commandKeysSelectiveAnnouncement.MyInputManager.executeGesture
(10:47:23.033):
Input: kb(desktop):downArrow
IO -
external:globalPlugins.NVDAExtensionGlobalPlugin.commandKeysSelectiveAnnouncement.MyInputManager.executeGesture
(10:47:24.210):
Input: kb(desktop):control+enter
IO -
external:globalPlugins.NVDAExtensionGlobalPlugin.commandKeysSelectiveAnnouncement.MyInputManager.executeGesture
(10:47:29.437):
Input: kb(desktop):control+enter
DEBUGWARNING - watchdog._watcher (10:47:31.296):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 233, in <module>
File "core.pyo", line 519, in main
File "wx\core.pyo", line 2134, in MainLoop
File "gui\__init__.pyo", line 1003, in Notify
File "core.pyo", line 490, in run
File "queueHandler.pyo", line 86, in pumpAll
File "queueHandler.pyo", line 53, in flushQueue
File "scriptHandler.pyo", line 145, in _queueScriptCallback
File "scriptHandler.pyo", line 187, in executeScript
File "editableText.pyo", line 185, in script_caret_moveByLine
File
"C:\Users\tiflo\AppData\Roaming\nvda\addons\NVDAExtensionGlobalPlugin\globalPlugins\NVDAExtensionGlobalPlugin\clipboardCommandAnnouncement\__init__.py",
line 210, in _caretMovementScriptHelper
File "editableText.pyo", line 144, in _caretMovementScriptHelper
File "editableText.pyo", line 130, in _caretScriptPostMovedHelper
File "speech.pyo", line 781, in speakTextInfo
File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 341, in
getTextWithFields
File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 295, in _getText
File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 251, in
_iterRecursiveText
File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 251, in
_iterRecursiveText
File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 251, in
_iterRecursiveText
File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 251, in
_iterRecursiveText
File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 251, in
_iterRecursiveText
File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 251, in
_iterRecursiveText
File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 241, in
_iterRecursiveText
File "compoundDocuments.pyo", line 135, in _getControlFieldForObject
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "NVDAObjects\IAccessible\mozilla.pyo", line 71, in _get_states
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "NVDAObjects\IAccessible\ia2Web.pyo", line 57, in _get_states
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "NVDAObjects\IAccessible\__init__.pyo", line 854, in _get_states
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "NVDAObjects\IAccessible\__init__.pyo", line 1072, in
_get_IA2Attributes
File "IAccessibleHandler.pyo", line 1059, in splitIA2Attribs
And it repeats untill:
WARNING - watchdog._watcher (10:52:33.105):
Core frozen in stack:
File "nvda.pyw", line 233, in <module>
File "core.pyo", line 519, in main
File "wx\core.pyo", line 2134, in MainLoop
File "gui\__init__.pyo", line 1003, in Notify
File "core.pyo", line 490, in run
File "queueHandler.pyo", line 86, in pumpAll
File "queueHandler.pyo", line 53, in flushQueue
File "scriptHandler.pyo", line 145, in _queueScriptCallback
File "scriptHandler.pyo", line 187, in executeScript
File "editableText.pyo", line 185, in script_caret_moveByLine
File
"C:\Users\tiflo\AppData\Roaming\nvda\addons\NVDAExtensionGlobalPlugin\globalPlugins\NVDAExtensionGlobalPlugin\clipboardCommandAnnouncement\__init__.py",
line 210, in _caretMovementScriptHelper
File "editableText.pyo", line 144, in _caretMovementScriptHelper
File "editableText.pyo", line 130, in _caretScriptPostMovedHelper
File "speech.pyo", line 781, in speakTextInfo
File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 341, in
getTextWithFields
File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 295, in _getText
File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 251, in
_iterRecursiveText
File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 251, in
_iterRecursiveText
File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 251, in
_iterRecursiveText
File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 251, in
_iterRecursiveText
File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 251, in
_iterRecursiveText
File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 251, in
_iterRecursiveText
File "NVDAObjects\IAccessible\ia2TextMozilla.pyo", line 241, in
_iterRecursiveText
File "compoundDocuments.pyo", line 135, in _getControlFieldForObject
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "NVDAObjects\IAccessible\mozilla.pyo", line 71, in _get_states
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "NVDAObjects\IAccessible\ia2Web.pyo", line 57, in _get_states
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "NVDAObjects\IAccessible\__init__.pyo", line 854, in _get_states
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "NVDAObjects\IAccessible\__init__.pyo", line 1072, in
_get_IA2Attributes
File "IAccessibleHandler.pyo", line 1059, in splitIA2Attribs
Rui Fontes
Às 02:29 de 22/03/2019, zahra escreveu:
hi.
send it hear, (but copy peist the content), because if i am correct,
you cant send attachment hear.
or send it to
info@...
On 3/21/19, Abbie Taylor <abbietaylor945@...> wrote:
For quite some time, I've been having the same intermittent issues as
Rosemary and others with NVDA losing speech. For me, it happens most of
the
time when I'm in Word but occasionally occurs in Outlook and Firefox.
This
morning after installing the latest add-on update, I had to restart my
computer twice before it would work properly. I figured out how to
access
the log through the NVDA tools menu. Where can I send it? Thank you.
Abbie Johnson Taylor, Author https://abbiescorner.wordpress.com
http://www.abbiejohnsontaylor.com
abbietaylor945@...
Order my new memoir at http://www.abbiejohnsontaylor.com/memoir.htm
--
Abbie Johnson Taylor, Author
http://www.abbiejohnsontaylor.com
http://abbiescorner.wordpress.com
abbietaylor945@...
-- Subscribe to a WordPress for Newbies Mailing List by sending a message to: wp4newbs-request@... with 'subscribe' in the Subject field OR by visiting the list page at http://www.freelists.org/list/wp4newbs& check out my sites at www.brighter-vision.com & www.mysitesbeenhacked.com
|
|
|
