Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.clipper.visual-objects > #11245 > unrolled thread

Performance issues with Textcontrol

Started byArne Ortlinghaus <Arne.Ortlinghaus@acs.it>
First post2017-12-19 17:31 +0100
Last post2018-01-12 11:45 +0100
Articles 5 — 2 participants

Back to article view | Back to comp.lang.clipper.visual-objects


Contents

  Performance issues with Textcontrol Arne Ortlinghaus <Arne.Ortlinghaus@acs.it> - 2017-12-19 17:31 +0100
    Re: Performance issues with Textcontrol Arne Ortlinghaus <Arne.Ortlinghaus@acs.it> - 2017-12-21 12:56 +0100
      Re: Performance issues with Textcontrol "Karl-Heinz" <invalid@invalid.invalid> - 2017-12-21 16:56 +0100
        Re: Performance issues with Textcontrol Arne Ortlinghaus <Arne.Ortlinghaus@acs.it> - 2018-01-04 15:08 +0100
          Re: Performance issues with Textcontrol Arne Ortlinghaus <Arne.Ortlinghaus@acs.it> - 2018-01-12 11:45 +0100

#11245 — Performance issues with Textcontrol

FromArne Ortlinghaus <Arne.Ortlinghaus@acs.it>
Date2017-12-19 17:31 +0100
SubjectPerformance issues with Textcontrol
Message-ID<p1betf$1pbc$1@gioia.aioe.org>
Hello,
there are some users of our programs who suffer under additional wait 
times since some weeks: Currently this happens especially when opening a 
window with the TEControl RTF/HTML-Textcontrol from Subsystems.

One idea is that it could be related to the Windows 10 1709 Creator Fall 
Update. But it is not every computer behaving like this.

What has turned out is that all these uses have a UIAutomationCore.dll 
linked into the program which can be verified using Process Explorer 
from Sysinternals:
UIAutomationCore.dll   Microsoft-Benutzeroberflächenautomatisierung 
        Microsoft Corporation 
C:\Windows\SysWOW64\UIAutomationCore.dll

There are some registry settings that seem to be related to the wait times:
HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows 
NT\CurrentVersion\AppCompatFlags\CaretTracking)
and
HKCU\Software\Microsoft\Windows\CurrentVersion\ImmersiveShell

On my computer the UIAutomationCore.dll is not linked into the program. 
So it does not seem to be on every machine. But until now I have not 
found any programs that may install this "UI Automation API".

Arne Ortlinghaus
INFOMINDS AG

[toc] | [next] | [standalone]


#11249

FromArne Ortlinghaus <Arne.Ortlinghaus@acs.it>
Date2017-12-21 12:56 +0100
Message-ID<p1g7i9$lbu$1@gioia.aioe.org>
In reply to#11245
I could resolve it:
- It was the Windows 10 Update together with certain computer installation
- The funktion NtGdiGetPixel  from the DLL C:\Windows\SysWOW64 
\win32u.dll could become very slow. This function seems to be used to 
create toolbars.
- Installing new Device drivers for the Display Adapter have resolved 
the case, at least having NVIDIA and HP display adapters. Interesting 
how easy it has become to install the device drivers. It wasn't even 
necessary to restart Windows.

Arne

Arne Ortlinghaus wrote:
> Hello,
> there are some users of our programs who suffer under additional wait 
> times since some weeks: Currently this happens especially when opening a 
> window with the TEControl RTF/HTML-Textcontrol from Subsystems.
> 
> One idea is that it could be related to the Windows 10 1709 Creator Fall 
> Update. But it is not every computer behaving like this.
> 
> What has turned out is that all these uses have a UIAutomationCore.dll 
> linked into the program which can be verified using Process Explorer 
> from Sysinternals:
> UIAutomationCore.dll   Microsoft-Benutzeroberflächenautomatisierung 
>         Microsoft Corporation C:\Windows\SysWOW64\UIAutomationCore.dll
> 
> There are some registry settings that seem to be related to the wait times:
> HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows 
> NT\CurrentVersion\AppCompatFlags\CaretTracking)
> and
> HKCU\Software\Microsoft\Windows\CurrentVersion\ImmersiveShell
> 
> On my computer the UIAutomationCore.dll is not linked into the program. 
> So it does not seem to be on every machine. But until now I have not 
> found any programs that may install this "UI Automation API".
> 
> Arne Ortlinghaus
> INFOMINDS AG

[toc] | [prev] | [next] | [standalone]


#11250

From"Karl-Heinz" <invalid@invalid.invalid>
Date2017-12-21 16:56 +0100
Message-ID<fa23ukF3enkU1@mid.individual.net>
In reply to#11249
Hi Arne,

> I could resolve it:
> - It was the Windows 10 Update together with certain computer installation
> - The funktion NtGdiGetPixel  from the DLL C:\Windows\SysWOW64
> \win32u.dll could become very slow. This function seems to be used to
> create toolbars.
> - Installing new Device drivers for the Display Adapter have resolved
> the case, at least having NVIDIA and HP display adapters. Interesting
> how easy it has become to install the device drivers. It wasn't even
> necessary to restart Windows.
> restart Windows.

is it correct that your issue has nothing to do with the initial mentioned
"UI Automation"  ? Your only problem are not uptodate  Display drivers ??

I´m asking, because when i search "UI Automation slow" there are a lot of
hints ...

regards
Karl-Heinz 

[toc] | [prev] | [next] | [standalone]


#11269

FromArne Ortlinghaus <Arne.Ortlinghaus@acs.it>
Date2018-01-04 15:08 +0100
Message-ID<p2lcgt$1kb8$1@gioia.aioe.org>
In reply to#11250
Hi Karl-Heinz,

yes, this is correct, although there may be some relations. Users told 
that disabling the UI Automation via registry keys helped a little bit, 
but was resolved completely only with installing a new graphics adapter. 
In the meantime PCs have appeared without these UI automation Dlls loaded.

The reason is an graphics driver to be updated. Until now this happened 
with NVIDIA and HP graphics adapters.

Arne

Karl-Heinz wrote:
> Hi Arne,
> 
>> I could resolve it:
>> - It was the Windows 10 Update together with certain computer 
>> installation
>> - The funktion NtGdiGetPixel  from the DLL C:\Windows\SysWOW64
>> \win32u.dll could become very slow. This function seems to be used to
>> create toolbars.
>> - Installing new Device drivers for the Display Adapter have resolved
>> the case, at least having NVIDIA and HP display adapters. Interesting
>> how easy it has become to install the device drivers. It wasn't even
>> necessary to restart Windows.
>> restart Windows.
> 
> is it correct that your issue has nothing to do with the initial mentioned
> "UI Automation"  ? Your only problem are not uptodate  Display drivers ??
> 
> I´m asking, because when i search "UI Automation slow" there are a lot of
> hints ...
> 
> regards
> Karl-Heinz

[toc] | [prev] | [next] | [standalone]


#11288

FromArne Ortlinghaus <Arne.Ortlinghaus@acs.it>
Date2018-01-12 11:45 +0100
Message-ID<p3a3jr$1831$1@gioia.aioe.org>
In reply to#11269
It seems that Microsoft has done something regarding this behavior. With 
the newest cumulative update that my computer installed today the 
controls are displayed quickly as before.

Arne

Arne Ortlinghaus wrote:
> Hi Karl-Heinz,
> 
> yes, this is correct, although there may be some relations. Users told 
> that disabling the UI Automation via registry keys helped a little bit, 
> but was resolved completely only with installing a new graphics adapter. 
> In the meantime PCs have appeared without these UI automation Dlls loaded.
> 
> The reason is an graphics driver to be updated. Until now this happened 
> with NVIDIA and HP graphics adapters.
> 
> Arne
> 
> Karl-Heinz wrote:
>> Hi Arne,
>>
>>> I could resolve it:
>>> - It was the Windows 10 Update together with certain computer 
>>> installation
>>> - The funktion NtGdiGetPixel  from the DLL C:\Windows\SysWOW64
>>> \win32u.dll could become very slow. This function seems to be used to
>>> create toolbars.
>>> - Installing new Device drivers for the Display Adapter have resolved
>>> the case, at least having NVIDIA and HP display adapters. Interesting
>>> how easy it has become to install the device drivers. It wasn't even
>>> necessary to restart Windows.
>>> restart Windows.
>>
>> is it correct that your issue has nothing to do with the initial 
>> mentioned
>> "UI Automation"  ? Your only problem are not uptodate  Display drivers ??
>>
>> I´m asking, because when i search "UI Automation slow" there are a lot of
>> hints ...
>>
>> regards
>> Karl-Heinz
> 

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.clipper.visual-objects


csiph-web