Skip to content

Conversation

r10s
Copy link
Contributor

@r10s r10s commented Sep 9, 2025

this PR clarifies some events, also updating to recent changes.

see changed code for details

@r10s r10s requested review from link2xt and adbenitez September 9, 2025 10:04
@r10s r10s moved this to In Progress in Calls Sep 9, 2025
@r10s r10s added this to Calls Sep 9, 2025
@r10s r10s force-pushed the r10s/refine-call-docs branch 3 times, most recently from daac3ea to 9cc323b Compare September 9, 2025 12:23
@r10s r10s force-pushed the r10s/refine-call-docs branch from 9cc323b to 64c651f Compare September 9, 2025 12:27
@@ -1299,7 +1308,12 @@ uint32_t dc_place_outgoing_call (dc_context_t* context, uint32_t ch
* Unaccepted calls ended by the callee are a "decline".
* If the call was accepted, this is a "hangup".
*
* All participant devices get informed about the ended call via #DC_EVENT_CALL_ENDED.
* All participant devices get informed about the ended call via #DC_EVENT_CALL_ENDED unless they are contact requests.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do i correctly understand that for contact requests prepare_send_msg() fails so they aren't informed about the ended call? Shouldn't we explicitly check Chat::why_cant_send_ex() and handle this w/o throwing an error? I just don't see any special code for this in Context::end_call()

* All participant devices get informed about the ended call via #DC_EVENT_CALL_ENDED unless they are contact requests.
* For contact requests, the call times out on all other affected devices.
*
* If the message ID is wrong or does not exist for whatever reasons, nothing happends.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* If the message ID is wrong or does not exist for whatever reasons, nothing happends.
* If the message ID is wrong or does not exist for whatever reasons, nothing happens.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants