>> You have a render buffer (gdi->primary_buffer) where you have the >> rendered image >> you have the invalid region which tells you which areas have changed >> and you have the *end_paint callbacks which tell you when an update is ready >> > I'm afraid I can't find those. Nothing matches that pattern in the > source tree of FreeRDP. Sorry, from the top of my head, try case insensitive and parts of that. As mentioned, try the android client folder, it is simpler. Just check the C code there, it is much more manageable. > >> There are also a lot of other hooks to implement optimized versions >> (which are implemented in xfreerdp) but to see a basic implementation >> look at the android client. >> > So you mean by default the client will receive compressed bitmaps like VNC? Yes and no. The decoding is done by the library and you always access the rendered frame. To put it simple, there are roughtly 3 modes of RDP: 1. old legacy RDP where you get drawing instructions similar to the windows API drawing primitives 2. RFX mode which is a MS video codec 3. GFX mode being similar to RFX but transport is different. This mode is used by windows 8 and up and is nowadays using H264 to encode the screen data
>> p.s. please respond to the mailing list ;) >> > My client is set to "reply all" as various lists do not repeat the > message to the "participants" in the CC field. Are you receiving > duplicate messages? It may be a problem with the FreeRDP list, I can > try to work around it by deleting you from the CC or TO fields. Got the last messages only on my personal address, strange. > Cheers, > R0b0t1 > Cheers Armin ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ FreeRDP-devel mailing list FreeRDP-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
