| Age | Commit message (Collapse) | Author |
|---|
|
Print own messages to FTEXT_OUT as well,
for compatability with lchat (own messages
just vanish if they are not reprinted in
one of these files).
|
|
|
|
I'm currently staying in India, and strangely enough ratox
could not connect using tox_bootstrap(). It would just
continue attempting to connect until the end of time.
Using tox_add_tcp_relay() additionally fixes this isssue.
It is also the strategy utox uses:
https://github.com/uTox/uTox/blob/49bc764d23a02ab8286ef6f2085e8e592bccde1e/src/tox.c#L137
Also, nodes.h needed to be regenerated for using
tcp ports and relays.
|
|
eprintf() is used with only the function name that failed
(and possibly a parameter) and then exits. Example:
eprintf("read %s:", f->name);
weprintf() is used when another function failed, but the
program does not exit. The error message is a sentence.
Example: weprintf("No friend with id %s found for %s\n", buf, c->numstr);
logmsg() is not used when anything failed, it is just for
displaying useful information for the user. There should be
three logmsg formats:
The first format consists of the area the logmsg() is concerned
with, for example "Name", followed by a ">" sign, and then
followed by the change within that area.
This format deals with non-group and non-friend specific changes.
Example: logmsg("State > %s\n", buf);
The second format displays friend-specific information. It
consists of a colon, followed by the friend name, followed by
another colon, followed by the value that was changed and then
the change itself.
Example: logmsg(": %s : Rx > Accepted\n", f->name);
The third format is similar to the second one, it consists of
a dash ("-"), followed by a conference number, a colon,
followed by the value that was changed and then the change itself.
This format tells the user about conference-specific changes.
Example: logmsg("- %s : Title > %s\n", c-numstr, title);
Errors when trying to change something in the gslots are written
with dprintf into the gslots .fd[ERR] and with weprintf() on
the screen.
This commit and the last one are attempts at implementing these rules.
|
|
|
|
|
|
|
|
|
|
|
|
Update error messages.
NUM/invite now also accepts ID's (not only public keys).
The title is now also changed for the changer.
|
|
This merge updates ratox to toktoks toxcore, which is being developed, and
adds groupchats (although lacking audio group chats at the moment).
|
|
|
|
Update type of cookie.
Unify error messages.
Delete invite-fifo if joining fails.
|
|
|
|
|
|
|
|
|
|
The title of a conference is apparently not known immediately after joining the
conference, so don't print a warning in confcreate(), just wait for the
cbconftitle() callback immediately afterwards.
Friends that are not online can't be invited to conferences, logmsg' in that case.
Print the name of the conference before messages in cbconfmessage().
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
It is not used anywhere and it is unlikely that this will
change anytime.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
When f->av.state equals TRANSMITTING, it means that we're neither
receiving, nor sending data, thus, we can cancel the call.
This doesn't apply to RINGING mode because this state is possible when
someone calls us, and we didn't answer yet.
|
|
Actually passes the friend number returned by tox_friend_add_norequest()
to the friendcreate() function.
|
|
|
|
|
|
If we're not initiating the call, we might be in TRANSMITTING mode even
if call_in hasn't been openned by the user. In this case, we shouldn't
send any data.
sednfriendcalldata() should only be called when resources are allocated
for an OUTGOING call, which is triggered when the friend accepts audio.
|
|
|
