I put together some commands to do the following:

1) Load .torrent files from a primary watch location, leaving custom3 empty
2) Load .torrent files from a secondary watch location, which also
sets the custom3 variable with a directory
3) Check for torrents with custom3 unset on event.download.opened, and
set to a default if empty

Unfortunately, every torrent regardless of start location gets custom3
set to the default value by the event.download.opened function below,
overwriting the directory set in step 2 above. Is there a reliable
order the event.download triggers are fired, or is there a better way
to handle this functionality? Does it take time for d.set_custom3 to
complete?

Also, what specifically triggers event.download.opened and
event.download.resumed? Are both triggered on the initial load?
_______________________________________________
Libtorrent-devel mailing list
[email protected]
http://rakshasa.no/mailman/listinfo/libtorrent-devel

Reply via email to