1) a new event for self-updates does make sense in principle but it doesn't fit well with the current system, where update events are already being propagated for each user, including the "self" one. check rev 3366 in which i have added a flag in Identity that can be used to cheaply make that "self" check. i would do it in the UserUpdated event outside of the current async calls as setting the tab logo should not be done within the "task" system (reserved for updating the user list).
2) the general best practice is to prefer std::vector by default and use other containers only if they provide a specific advantage. for ex, std::list can be useful to store pointers to contained elements as they are guaranteed never to become invalid. 4) creating an icon (here, an image list containing several) is expensive; especially if it happens every minute or so (updates for free slots...). so i want that check. the additional data would only be 1 set of flags (a number) per hub so negligible. -- 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
