You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(connector): expose SUPPORT_DYN_VC_GFX_PROTOCOL early-cap flag for EGFX clients
Currently, `early_capability_flags` in the GCC core data is built
from a fixed set in `connection.rs`. Clients that want to use the
Graphics Pipeline Extension (MS-RDPEGFX) — by attaching a
DvcClientProcessor for `Microsoft::Windows::RDS::Graphics` — have
no way to set `SUPPORT_DYN_VC_GFX_PROTOCOL` without forking the
connector, and modern Windows servers won't open the EGFX channel
unless the client advertises support.
This commit adds an opt-in `Config.support_dyn_vc_gfx_protocol: bool`
(default `false`). When set, the flag is OR'd into
`early_capability_flags` alongside the existing
`WANT_32_BPP_SESSION` conditional. Existing consumers are
unaffected; the doc comment includes a safety note that setting
this without an EGFX implementation will cause Windows to stop
sending legacy bitmap updates, leaving the desktop blank.
Used downstream by Haven (an Android RDP/VNC client) which
implements EGFX with ClearCodec + RemoteFxProgressive decoders;
this lets us drop the vendored ironrdp-connector fork.
Default `false` to preserve current behaviour.
0 commit comments