I really support always showing the dialog, the above was a try to make a good compromise between the always, sometimes, and never show (like eg. in BCDC++). And let me remind you that because of using Coral cache by default, many users get the upgrade reminder several days later than it was uploaded so I think the 3 days interval isn't much worse than the current way.
Anyway as an option, we can add a Severity parameter to the Message node in version.xml which can regulate the nag window's behaviour between noshow, 3 days interval and always.... -- You received this bug notification because you are a member of Dcplusplus-team, which is subscribed to DC++. https://bugs.launchpad.net/bugs/377693 Title: Upgrade Dialog Should Only Be Persistent If Necessary Status in DC++: Confirmed Bug description: Recently I reported this bug: https://bugs.launchpad.net/dcplusplus/+bug/344833 . This was resolved as wont fix. The argument against is that new versions of DC++ introduces new network features. If people keep using old versions of DC++, they are holding back the network. My suggestion is to only show the upgrade dialog every time when the user is currently using a client that holds back the network. If the older version the user is using does not affect the network in a negative way, the user should be able to disable the upgrade dialog until the next upgrade of DC++ is available. Also, most people do not understand or read the text presented on the upgrade dialog. Just "Do you want to upgrade?" is way more effective. _______________________________________________ Mailing list: https://launchpad.net/~linuxdcpp-team Post to : [email protected] Unsubscribe : https://launchpad.net/~linuxdcpp-team More help : https://help.launchpad.net/ListHelp
