Bug 7798

Need for accessibility NOT 0 17 January, 2022

Miguel Leeuwe
14 January, 2022
Product: PowerBuilder Category: Other
Version: 2021 Build: 1311
Classification: Appeon bug Publishing: Public
Priority: P2
Status: Scheduling Reason:
Miguel Leeuwe 17 January, 2022
#4
Hi Ken,
Well, at least it's good to know that you guys are working on it!
regards
Ken Guo @Appeon 17 January, 2022
#3
Hi Miguel,

PB 2019 versions support Microsoft UI Automation, which we implemented by calling MS Windows API. But we found calling these MS Windows API slowers the performance greatly in some Windows environments.

We’ve spent lots of time analyzing this but so far no specific cause is found, so we decide to work around this issue by setting accessibility=0 for the time being.

We will continue to try to find out the root cause of this issue but I can’t tell you exactly when this will be fixed as it’s entirely up to the progress the developers make.

Regards,
Ken
Miguel Leeuwe 14 January, 2022
#2
Thank you Chris!,
I'm counting 25 tickets mentioning the word ACCESSIBILITY, not counting my own
:)
Chris Pollach @Appeon 14 January, 2022
#1
Hi Miguel;

  A great question!

  I will now transfer this ticket over to Engineering to see if they plan on addressing this issue for PB2022.

Regards ... Chris
Miguel Leeuwe 14 January, 2022
*Phenomenon:
Right now, there's loads of problems when in the pb.ini we don't set 
[Data Window]
ACCESSIBILITY=0

What if I NEED this to be a "1", when I'm dealing with impaired users? Is Appeon going to do anything to fix the performance problems when:
[Data Window]
ACCESSIBILITY=1

?
That's all, thank you,
regards,
MiguelL

*Reproduce Steps:


Remarks:
OS:
Windows 10
Platform:
64-bit
Database Type:
Database Version: