NVDA does not read in the Fast Log Entry #8996
Milestone
Comments
|
Problem still persists in NVDA 2019.1 |
|
Problem still persists in NVDA 2019.3.1 |
|
This seems to be a regression. |
|
@HegrJan I assume this is still reproducible. Is this correct? |
|
Yes, it is.
…On 5/11/20, Adriani90 ***@***.***> wrote:
@HegrJan I assume this is still reproducible. Is this correct?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#8996 (comment)
|
|
Problem still persists in NVDA 2020.1 |
lukaszgo1
added a commit
to lukaszgo1/nvda
that referenced
this issue
Aug 12, 2020
|
Yes, it works like a charm (Windows 7 64bit). Thank you!
…On 8/12/20, Łukasz Golonka ***@***.***> wrote:
@HegrJan Just to make sure this is fixed for you coulld you please test with
this [try
build](https://ci.appveyor.com/api/buildjobs/4ym0fbmj2tubts35/artifacts/output%2Fnvda_snapshot_pr11488-20731%2C594e2dab.exe)?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#8996 (comment)
|
feerrenrut
pushed a commit
that referenced
this issue
Sep 9, 2020
Fixes #8996 In #8165 we started using Unidentifiededit for editable text fields in which there is a caret and which seems to support Edit API. While both of these criterion's are true for Fast Log Entry edit fields their WindowText contains complete garbage and UnidentifiedEdit relies on Windowtext being correct. Instead: 1. For edit field in Fast Log Entry DisplayModelEditableText is used similar to the pre #8165 2. DisplayModelEditableText no longer inherits from EditableText rather from EditableTextWithoutAutoSelectDetection which makes selection announced when the color used for highlight in a particular app is the default Windows highlight color - This has been suggested by @jcsteh in #4535
dawidpieper
pushed a commit
to dawidpieper/nvda
that referenced
this issue
Sep 13, 2020
…s#11488) Fixes nvaccess#8996 In nvaccess#8165 we started using Unidentifiededit for editable text fields in which there is a caret and which seems to support Edit API. While both of these criterion's are true for Fast Log Entry edit fields their WindowText contains complete garbage and UnidentifiedEdit relies on Windowtext being correct. Instead: 1. For edit field in Fast Log Entry DisplayModelEditableText is used similar to the pre nvaccess#8165 2. DisplayModelEditableText no longer inherits from EditableText rather from EditableTextWithoutAutoSelectDetection which makes selection announced when the color used for highlight in a particular app is the default Windows highlight color - This has been suggested by @jcsteh in nvaccess#4535
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce:
-1. Download Fast Log Entry installer from http://df3cb.com/fle/
0. Install FLE
Actual behavior:
The text (log content) is not read. There are unknown symbols on the braille display eg. '\x2023''\x6548''\x6461''\x7265'...
Expected behavior:
An edit field similar to Notepad filled with example log should be readable.
System configuration:
NVDA Installed/portable/running from source:
Installed
NVDA version:
2018.3.2
Windows version:
Windows 7 64bit Version 6.1.7601 Service Pack 1 Build 7601
Name and version of other software in use when reproducing the issue:
Fast Log Entry 2.12
Other information about your system:
Other questions:
Does the issue still occur after restarting your PC?
Yes
Have you tried any other versions of NVDA?
Remarks
The text was updated successfully, but these errors were encountered: