1) As far as I could see, the normal user-update event is triggered for all users, meaning that the code will need to constantly check if the user is actually 'self' before proceeding. If I'm wrong in that assumption, then yes, you're right.
2) Why? What difference does it make here? 3) Those changes should change the icon since the code will be triggered for each update. The procedure when 'acquiring' the OP/reg status is the same as when losing it... 4) I didn't do this to avoid storing additional data. The current triggering should happen relatively seldom (each time the 'self' info changes), so I felt the additional verification was kind of pointless. But sure, it's not a problem to add... -- 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
