Aline Gondim Santos authored 3 years ago and Aline Gondim Santos committed 2 years ago

GitLab: client-qt#476
Change-Id: I23723bf6fcca42ba2fc5cbca29e408facff7e337

Aline Gondim Santos authored 3 years ago and Aline Gondim Santos committed 2 years ago

GitLab: #478
Change-Id: I023454c727ebdd9c5921fd484e3b9a50a09e3b00

CMake doesn't add this flag and it must be done manually. This
was not caught early as reconfiguring adds the flag for some
reason. It's to be determined if this is expected behavior. I hope
not, it's just confusing.

+ Add the `/EHsc` flag
+ remove CMAKE_BUILD_TYPE from configure step in helper script
+ remove useless Window definitions from qtwrapper that are defined
  in the parent CMakeLists.txt

Gitlab: #504
Change-Id: I8b03d81cae7ebed6a31cb69642db2f9f09a0c91b

Change-Id: Idb714e7264ffee4725c4bd1f672efaff15caf79b

Because admins are able to re-add banned contact (after a vote),
interactions must be shown.

https://git.jami.net/savoirfairelinux/jami-product-backlog/-/issues/51
Change-Id: I9350a26e9ada6528f08065f9a55b842cd6848d5f

This avoid to do any logic in the client, like discardTrustRequest

jami-client-qt#340

Change-Id: Iea92009693aea9ca30f42e2f5caf7ad7d27b188f

jami-client-qt#670

Change-Id: I9a59a127fdbf1f360b60b2821f67fd06cd93f600

if the cache is cleaned but not the latest interaction, when
reloading, if the lastMessageUid is a merge commit, it will
not reload until the latest interaction

jami-client-qt#340

Change-Id: I91ade5b2e80957bb97fe711e95f2837330553b0e

Use best name in notifications and show banned members

jami-client-qt#340
Change-Id: I79b76bdf036f32558414a949aebfec0f4700fa10

jami-client-qt#670
Change-Id: I852cac2f19a0fb87bcf4316722acc57e8b77b116

jami-client-qt#670

Change-Id: Ifbf8ba04a7a00f583ec0ec932ca07c8e1a9cf4fc

If a member presence is updated, the swarm presence can be updated

jami-client-qt#670

Change-Id: I00450e4dadd4c614bec2b548be5f675555492344

jami-client-qt#670

Change-Id: I76773579f7460a599d0a760acc2d32027e657e82

Change-Id: Ie113db781e50d72791558dbb8261c4233a07dbc9

Change-Id: I1cf2846a0685b6d2f303d76222abeda32cb9c184

Follow changes from https://review.jami.net/c/jami-daemon/+/21262
Follow changes from https://review.jami.net/c/jami-daemon/+/21271

Change-Id: I61368a625aa4320c524b05f1df52f503d7932ec1

Amin Bandali authored 3 years ago and Sébastien Blin committed 3 years ago

Change-Id: I9bcf6f8ef76ea003a57e017eefa319d056f773a9

Andreas Traczyk authored 3 years ago and Sébastien Blin committed 3 years ago

pluginmodel.cpp has no private class declaration.

Change-Id: I67b6bba1c32101116e0a3d9ca208535c0a2ba1b2

Change-Id: Icda40920d38d83cea6ed5cb68f027c8745997e74

Andreas Traczyk authored 3 years ago and Adrien Béraud committed 3 years ago

Just read the binary data to avoid time consuming text processing
during the read in the case of oversized vcard images.

Change-Id: I009332a99b7057549da57fd7c432d6731ab752b8

Change-Id: Ia018b22b05f71237a9f3f86aaaf80e27399bc604

If the frameBufferRequested signal fails to set the AVFrame data
pointer, return null.

Change-Id: Iefb0d4670ca5e94c6ace2759fc941b9af39e682e

Jenkins authored 3 years ago and Amin Bandali committed 3 years ago

Change-Id: I50e22b8bd80d403cdaf5ab7decf6aef1c6fd2546

+ Reduce the complexity of, and refactor the video management code.
+ Replace the directrenderer pipeline with one that permits clients
  to map and provide a custom video buffer.

Note: this removes the "useAVFrame" path for now.

Gitlab: #500
Also jami-client-qt#536

Change-Id: Ia326c452c7887086acc75e8eb52fa24b7f4cf25b

+ Removes the signal/slot relay mechanism(Note: Signals can be
  connected to signals and don't need a relay slot as long as the
  signature is the same).
+ renames startedDecoding to decodingStarted and the same for
  stoppedDecoding.

Depends on: https://review.jami.net/c/jami-daemon/+/21147

Gitlab: #500
Also jami-client-qt#536

Change-Id: I02746137efeefa24f8ac65bde073f230b58c1e9c

Change-Id: I7b1be79b029654b9960a60507b36f742bb184395

Change-Id: Iecc1b8b2afae012f3bf073c21d1674d6b0b186c0

Be able to change all the details we want

Change-Id: Ic06b25d1595e61e285431a6d9cd4d0963488e5cb

Change-Id: I0d374efce72138a7777d1303ab75f6558ef95d3d

Kateryna Kostiuk authored 3 years ago and Kateryna Kostiuk committed 3 years ago

Set application container as path for audio/video recordings in
the chat.

jami-client-qt#672

Change-Id: I39ad0a72fc36b7dc2c5a3d50da5fa2c9b6fa78bc

Change-Id: I2d8ee62f84ad689d9cd35b679f47aa41bfa3d451

Change-Id: I06a24efad889587b16f63d137d34e9f8f5786033

Change-Id: Ib8cec0adadf76a34106f9a6b38fdda7edb0be5ff

Change-Id: I6e94fc7017a356212a13f6b0fcb0e4cf64abdaaa

Change-Id: I628ce5a793e8fb8285c73e5a9f24dc2fc2e647f0

Change-Id: I897e49cd131d3cbffef9fb1d5c9be3c0bc9bcb3f
GitLab: #495

Change-Id: I7171dd8aa0b9767951042409fe4fcc1381e494ab

This avoid any potential crash. Also do some cleanup

Change-Id: I92acdb6fe1f55b7061fbe73aac06bd60b4d3216e

It should return uri or registeredName

Change-Id: I2e4f3013c6ab9e89538f8a9cd9ab0ba658a4e9fa

Change-Id: I81d4519c5f4bc3bc7b2fb9194b2e1689b1b0d430