i can think of 2 main directions: A) add methods in event generating classes to retrieve lists of previously consumed events (what the patch is doing). B) keep a cache on the observer side (the GUI).
pros of #B: - no thread-related problems. - easy to implement. con of #B: - consumes resources even when the transfer panel is hidden. the only advantage i can see of #A is to avoid that resource consumption problem. i am wondering if it is worth the following cons: 1) retrieving connections is probably not enough; there are also downloads and (optionally) HTTP transfers. 2) thread safety (around the todo - std::copy / std::transfer might come in handy). 3) check what happens when the same event is received twice; once by the retrieving func, once through a regular callback. -- You received this bug notification because you are a member of Dcplusplus-team, which is subscribed to DC++. https://bugs.launchpad.net/bugs/666461 Title: All transfers are disappearing from TransferView when enabled/disabled Status in DC++: In Progress Bug description: Existing transfers are disappear from TransferView when you disable and re-enable it with Ctrl-2 XP SP3, r2259 To manage notifications about this bug go to: https://bugs.launchpad.net/dcplusplus/+bug/666461/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~linuxdcpp-team Post to : linuxdcpp-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~linuxdcpp-team More help : https://help.launchpad.net/ListHelp
