Remote desktop friendly

[Fr0sT.Brutal 900]

12 hours ago, David Heffernan said:

https://stackoverflow.com/q/4854534/505088

Hmm, how about setting ParentDoubleBuffered to True for all components and changing only form's DoubleBuffered property? I did so for now and see no issues. Probably I'm missing something?

I also did it the simplest way setting DoubleBuffered on startup only - I've no machines accessed both locally and remotely

Edited March 10, 2021 by Fr0sT.Brutal

[pyscripter 689]

@Fr0sT.BrutalSure, you could also optimize DoubleBuffering (if you do use DoubleBuffering).  But @Stephen Ball's fix addresses crashes that may occur during connection and disconnection, not the general slowness in painting.

Edited March 10, 2021 by pyscripter

[Fr0sT.Brutal 900]

@pyscripter

I mostly addressed David's answer on that SO topic where he calls TBaseForm.UpdateDoubleBuffered. AFAIU the issue with crashes only affects apps using styles or FMX which is not my case for now so I'm not dealing with all this registering and messaging

 

 

 

[David Heffernan 2345]

33 minutes ago, Fr0sT.Brutal said:

Hmm, how about setting ParentDoubleBuffered to True for all components and changing only form's DoubleBuffered property? I did so for now and see no issues. Probably I'm missing something?

I also did it the simplest way setting DoubleBuffered on startup only - I've no machines accessed both locally and remotely

The point is that many Delphi developers use double buffering to solve problems with flickering when resizing, rather than solving the root cause of the flickering. My experience of double buffering is that whilst it might deal with flickering, it also introduces its own problems. For instance, it changes the appearance of your program if you are using the Windows theme.  I don't want that.  So I don't use double buffering.  And I don't have flicker on resize.

[David Heffernan 2345]

9 hours ago, pyscripter said:

See DestroyWnd not called at destruction of WinControls - VCL - Delphi-PRAXiS [en]

FWIW, my current codebase has this:

procedure TOrcForm.DestroyWindowHandle;
// DestroyWnd is not called from the form destructor, so we override DestroyWindowHandle instead
begin
  FreeAndNil(FDropTarget);
  WTSUnRegisterSessionNotification(WindowHandle);
  inherited;
end;

So I guess that's why I said "it rings some bells" in an earlier post.

[mvanrijnen 123]

20 hours ago, Stephen Ball said:

As @David Millington mentioned, we have been working with the R&D team to share tips learned to help speed up VCL applications under remote desktop - to read about it, including a code sample see:

https://blogs.embarcadero.com/how-to-speed-up-remote-desktop-applications/ 

And if we go to the documentation:

Vcl.Forms.TApplication Methods - RAD Studio API Documentation (embarcadero.com)

 

there is no link to: Vcl.Forms.TApplication.UpdateMetricSettings - RAD Studio API Documentation (embarcadero.com)

 

@Embarcadero, update documentation please !, or do we have to guess the methods? 😉

 

 

[Kyle Miller 1]

I was working with a project over RDP using 10.4.1. My usual session was to connect, do work, and disconnect (not logoff). When I reconnected in a subsequent session, the IDE would very slowly redraw itself onto the screen. It's much better with 10.4.2 from start and while working.