| Age | Commit message (Collapse) | Author |
|---|
|
This allows clients to agree on what numbers mean what without having
it be set in core.
|
|
in the requested chunk callback.
For zero size transfers if the data sent is not the same length, the
file is assumed to be done.
|
|
|
|
|
|
This is done so that the function now has the same parameters as the
request chunk callback.
|
|
|
|
|
|
If data is NULL and length non zero, TOX_ERR_NEW_NULL is set.
error is set to TOX_ERR_NEW_LOAD_BAD_FORMAT when load fails.
|
|
The first commit's message is:
TOX_STATUS -> TOX_USER_STATUS, is more specific
This is the 2nd commit message:
I pretty strongly believe tox_iteration needs to be renamed to a verb
There are several other noun functions in the API, but none of them *do* things.
I think even tox_do is better than tox_iteration.
tox_do_interval is one possibility, but I'm open to suggestions.
This is the 3rd commit message:
private_key -> secret_key
This is more consistent with modern/NaCl/elliptic cryptography, and also "pk", meaning public key, is all over other toxcore code and documentation. This will eliminate ambiguity.
This is the 4th commit message:
Rename some functions for pseudo-namespace consistency
The enum change results in long enum types, but I think consistency trumps
having a few less characters.
This is the 5th commit message:
TOX_FILE_KIND -> TOX_FILE_TYPE
This is more of an English thing than a consistency thing, but
TOX_FILE_KIND sounds funnier/stranger to me than TOX_FILE_TYPE.
This is the 6th commit message:
More specific file control function names
This is the 7th commit message:
Rename custom packet functions for pseudo-namespace consistency
This also has the issue with long enums... but I still think consistent enum names are better
This is the 8th commit message:
Rename functions for pseudo-namespace consistency
This is the 9th commit message:
Consistency with https://github.com/sonOfRa/tox4j/blob/master/doc/core-design.md#naming-conventions and the rest of the api
This is the 10th commit message:
Fix errors in previous function rename commits
This is the 11th commit message:
Shorten one error enum name
|
|
Attempted fix of connection checking to make it more stable.
|
|
|
|
Added tox_get_udp_port() to tests.
|
|
Since the functions are not new api like I put them in tox_old.{c,h}
|
|
Everything should work except resuming.
|
|
|
|
|
|
|
|
|
|
Internal message functions now return better error codes.
|
|
Changes in Messenger to call the callback every time the connection
type changes from TCP to UDP.
|
|
|
|
|
|
(Done with two applications of "sed -i -r "s/(\\w+) const\\b/const \\1/g" toxcore/tox.*" )
Conflicts:
toxcore/tox.c
|
|
Some small self explainatory changes to the api.
|
|
m_copy_self_statusmessage no longer takes a buffer length argument.
|
|
|
|
|
|
|
|
|
|
TOX_CLIENT_ID_SIZE renamed to TOX_PUBLIC_KEY_SIZE.
Renamed client_id to public_ke in public api.
|
|
|
|
|
|
|
|
|
|
https://github.com/nurupo/InsertProjectNameHere
|
|
Put bootstrap nodes in a separate list than known good nodes.
|
|
|
|
|
|
|
|
https://github.com/wrouesnel/toxcore
|
|
Change the custom_packet_handler callback function interface to be
consistent with other callback interfaces.
The new interface takes the Messenger object calling as the first
parameter, and moves the user data object to be the last parameter.
This makes it comparable to the callbacks for file transfer and the
like, and should simplify building interfaces.
The new prototype is: int (*)(Messenger *m, int32_t friendnumber, const
uint8_t *data, uint32_t len, void *object)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
