| Commit message (Collapse) | Author | Age | Lines |
|---|
| |
|
|
|
| |
Followup to 701ab81 (included in 3.5) which was a partial fix which only
improved things for non-libpurple file transfers (that is, just jabber)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This means cancelling transfers on logout to avoid crashes, keeping
track of timeouts, reffing and unreffing the xfers, listening to the
callbacks from UI and purple more carefully and using the correct
functions to free the correct things at the correct moments.
Originally intended to fix a crash triggered when the dcc stall timeout
kicks in after the account is offline, which is apparently very frequent
with telegram (it sends file transfers while fetching history, and
randomly disconnects a while later).
Trying to fix that meant opening a can of worms, but after three days of
work on this bug I'm pretty sure I've finished dealing with the
resulting mess and tested all the typical edge cases.
|
| | |
|
| |
|
|
| |
More fixing warnings.
|
| | |
|
| |
|
|
|
|
|
| |
Used uncrustify, with the configuration file in ./doc/uncrustify.cfg
Commit author set to "Indent <please@skip.me>" so that it's easier to
skip while doing git blame.
|
| | |
|
| |
|
|
|
|
|
|
| |
the file in it; protocol modules are mostly hardcoded to use the filename
from the filesystem with no way to override this.
Also improved robustness a little bit.
|
| |
|
|
|
|
|
|
| |
for numerous reasons. Maybe libpurple 2.7.0 is less crappy and will
eventually allow (working) direct ft's again.
This somewhat works, but filename info is lost with some protocols.
|
| |
|
|
|
| |
beginning of the download already to make sure it doesn't stick around.
|
| |
|
|
|
| |
cancellation/timeout/etc).
|
| |
|
|
|
|
|
| |
I don't have time to work out all the details, I doubt if this is supposed
to work reliably yet at all. Let's go for the simple via-disk approach for
now.
|
| |
|
