Disclosure Statement: This site contains affiliate links, which means that I may receive a commission if you make a purchase using these links. As an eBay Partner, I earn from qualifying purchases.
If you find these projects useful please consider becoming a sponsor with Patreon, GitHub or Liberapay.

Shifted display on terminal server

Post Reply
win568neu
Posts: 34
Joined: Thu May 23, 2024 6:36 am

Shifted display on terminal server

Post by win568neu »

Hi Salvador

With the upgrade to version 136, we're experiencing a strange issue on our terminal server environments. The website's display is shifted.

Everything works fine on regular computers or via remote sessions.

Here are some examples. Is there any information available about this?
You do not have the required permissions to view the files attached to this post.
User avatar
salvadordf
Posts: 4620
Joined: Thu Feb 02, 2017 12:24 pm
Location: Spain
Contact:

Re: Shifted display on terminal server

Post by salvadordf »

Hi,

Please, check these points :
  • The application has the right DPI settings in the manifest.
  • Try the official CEF sample application in a terminal server session : https://cef-builds.spotifycdn.com/cef_binary_136.1.5%2Bg723b52b%2Bchromium-136.0.7103.93_windows64_client.tar.bz2
win568neu
Posts: 34
Joined: Thu May 23, 2024 6:36 am

Re: Shifted display on terminal server

Post by win568neu »

Hi Salvador

We have been using this manifest in our application for years. The error first appeared when we switched from Chrome 134 to 136.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity
version="1.0.0.0"
processorArchitecture="*"
name="DelphiApplication"
type="*"/>
<description>ERP-Software</description>
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">
<security>
<requestedPrivileges>
<requestedExecutionLevel
level="asInvoker"
uiAccess="false"/>
</requestedPrivileges>
</security>
</trustInfo>
<dependency>
<dependentAssembly>
<assemblyIdentity
type="win32"
name="Microsoft.Windows.Common-Controls"
version="6.0.0.0"
publicKeyToken="6595b64144ccf1df"
language="*"
processorArchitecture="*"/>
</dependentAssembly>
</dependency>
<dependency>
<dependentAssembly>
<assemblyIdentity
type="win32"
name="GdPicture.NET.14"
version="14.2.100.0"
publicKeyToken="F52A2E60AD468DBB"
language="*"/>
</dependentAssembly>
</dependency>
</assembly>
win568neu
Posts: 34
Joined: Thu May 23, 2024 6:36 am

Re: Shifted display on terminal server

Post by win568neu »

Hi Salvador

The test with the official CEF application worked. The page also displays correctly on the terminal servers.
We created the 136 version ourselves because of the audio codec. But that's never been a problem so far.
What could be the cause?
User avatar
salvadordf
Posts: 4620
Joined: Thu Feb 02, 2017 12:24 pm
Location: Spain
Contact:

Re: Shifted display on terminal server

Post by salvadordf »

It might be caused by the lack of information for DPI awareness in the manifest.

Try building one of the CEF4Delphi demos in Delphi 12 or add this information to your manifest :
https://stackoverflow.com/questions/51820148/delphi-application-not-high-dpi-although-the-manifest-looks-good
https://docwiki.embarcadero.com/RADStudio/Athens/en/Customizing_the_Windows_Application_Manifest_File
win568neu
Posts: 34
Joined: Thu May 23, 2024 6:36 am

Re: Shifted display on terminal server

Post by win568neu »

Hi Salvador

Thanks for the information. I'll go through it.

What I don't understand is that we just switched from version 134 to version 136 and then this issue occurred.

We're not currently using a HighDPI manifest because we're still in the process of adapting the components for it. The display is fine on Windows and remote, but on the terminal servers it looks like the examples I sent you.
win568neu
Posts: 34
Joined: Thu May 23, 2024 6:36 am

Re: Shifted display on terminal server

Post by win568neu »

Hi Salvador

I've looked at your links. As I already wrote, the main application doesn't use a HighDPI manifest (dpiAware isn't set) because we're still in the process of adapting our custom components.

We use MultiExeProcessing with its own subprocess for our application. The dpiAware manifest was set for this EXE. I've now disabled it, thus aligning it with the main application. However, this manifest had been set since the first version of Chrome we used.

We'll now try this with selected customers.
Post Reply