Aline Gondim Santos authored 3 years ago and Sébastien Blin committed 3 years ago

+ remove record video message if no video device available

Change-Id: I35c15709ecd5159dfa02ebcbf7aacd0bbf3d54e9

Change-Id: Ia80632cf2e217e8dd6844a6a8c0d0d8c0f6e1baf

Change-Id: Ia344d9f57a216f2d27ef40153af2d6bd787bfb77

Gitlab: #466
Change-Id: Id7bd241c3c88dfba90505dd399127d5ceedbf028

Aline Gondim Santos authored 3 years ago and Andreas Traczyk committed 3 years ago

Change-Id: Ife36489e1b9dc63e971789ce79047690eb681aeb
GitLab: #389

GitLab: #392
Change-Id: Ifcd29af849c11166158e7f8d39b65a33325b8d4a

- minor cosmetic changes to the call view overlay
- add the ability to change audio/video input during a call
  from the call screen overlay

Gitlab: #411
Change-Id: Id6bbb2278d807f3bd7ad1478db405669088584ce

Unfortunately, QQuickMouseArea force accepts all move events by
design, which makes passthrough events tricky to catch. In-call
overlays for conference participants should be a layer below the
main overlay. So, using QML MouseAreas makes correctly implementing
both overlay fade mechanisms with passthrough for participant menus
too complex. To properly implement the signal relay mechanism we
would need to listen to all the child components with MouseAreas
and relay the positionChanged events to parenting MouseAreas.

To avoid the complexity, we can install an event filter for the
main overlay and listen to global mouse move events that are
contained in it's geometry.

Additionally, we can use Control components instead of transparent
Rectangles to access a hovered property which can be used to
prevent the fade out, and effectively freeze the visibility of menu
components.

Gitlab: #420
Gitlab: #421
Gitlab: #423
Change-Id: I7f05d2bc79ad6a8db0951b7b59e52f671fdf4798