1) is the new self-user-update event really needed? can't one use current user-update events and act from there if the user is the "self" one? (this came out haughty but i am genuinely asking.) avoid execTasks as it is too generic; this should only be applied to certain kinds of tasks (user update).
2) use an std::vector instead of an std::list to carry icon IDs. 3) what happens when a user looses his op/reg status while being connected? 4) only set the new icon when there actually is a change worthy of setting a new icon, not on every user update. -- You received this bug notification because you are a member of Dcplusplus-team, which is subscribed to DC++. https://bugs.launchpad.net/bugs/309815 Title: [Feature Request] Different hub icons for different user status (User/Reg/Admin) Status in DC++: In Progress Bug description: I usually have 40~50 hub open and some times hubs lost your reg, and you must register agian. But checking where you are a normal user (not reg/not admin) is a pain, so i'd like to have different icons in the hub tabs to show you if yo you are a normal user, reg or admin of each hub in tab list. To manage notifications about this bug go to: https://bugs.launchpad.net/dcplusplus/+bug/309815/+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
