Skip to content
Snippets Groups Projects
Select Git revision
  • 7fb102ed45d83e9f0a737cdf336bdc5b7f4194a9
  • master default protected
  • beta/202506161038
  • stable/20250613.0
  • nightly/20250613.0
  • beta/202506101658
  • stable/20250610.0
  • nightly/20250610.0
  • beta/202506091027
  • beta/202506061543
  • nightly/20250605.0
  • beta/202506051039
  • beta/202506051002
  • beta/202506041611
  • beta/202506041335
  • beta/202505231812
  • stable/20250523.0
  • nightly/20250523.0
  • nightly/20250515.0
  • nightly/20250510.0
  • nightly/20250509.1
  • nightly/20250509.0
22 results

jami-client-qt

  • Open with
  • Download source code
  • Your workspaces

      A workspace is a virtual sandbox environment for your code in GitLab.

      No agents available to create workspaces. Please consult Workspaces documentation for troubleshooting.

  • Andreas Traczyk's avatar
    Andreas Traczyk authored
    This is an older issue that has resurfaced where mobile device rotation
    at the beginning of a call cause a frame-copy to a stale buffer because
    the DecodingStarted event is handled asynchronously.
    
    Noticed on Windows but I believe any non-dbus build should have it.
    
    So we make all the connections blocking and adjust some parameters.
    This commit also removes the DecodingStarted handler in CallModel which
    was causing the client's target video frame to be reallocated for each
    account present.
    
    Change-Id: I23ac4e0bd4b446e7a532f0d362f7ecd209d3c790
    GitLab: #536
    15e13330
    History
    Name Last commit Last update