Well the obvious/easy solution would be to not leave it running and only load it when you actually want to scan for updates... I mean, if you don't want it scanning on its own schedule, why even have it running in the first place?
Ma grandpa always said "If it ain't broken don't fix it"
I apply this to updating my addons...
"If your UI isn't broken don't update it!"
I don't take that approach myself because not every update is a fix. Sometimes authors refine or add new features that significantly increase the usefulness of the addon.
Where does it store its list of what it thinks are the installed addons?
I stopped using a particular addon quite a while ago. Removed it from the Interface directory entirely. CC is still telling me that it's installed, is displaying the version as the last version I had used before deleting the addon, and is tracking the current version number.
There's no trace of the addon itself left, so where the hell is it getting that list?
Where does it store its list of what it thinks are the installed addons?
I stopped using a particular addon quite a while ago. Removed it from the Interface directory entirely. CC is still telling me that it's installed, is displaying the version as the last version I had used before deleting the addon, and is tracking the current version number.
There's no trace of the addon itself left, so where the hell is it getting that list?
In cc, reinstall it then uninstall it.
Curse client is an addon manager program. Either let the program manage your addons hosted on curse or do it manually not both. The program doesn't account for addons you manually delete.
I did that. It "worked" in that the unused addon no longer shows up, but CC also deleted a shared library addon. (Not an Ace/embedded library.) Fortunately I had made a backup not too long ago, so I could restore it. When I reinstall *just* the library addon, then the unused and uninstalled addon appears again.
Quote from Adirelle »
You can hit "refresh" and it will remove from its list the addons you deleted .
No, I tried that before even posting. It thinks the thing is really there. Apparently confusing the nonexistent addon with one of its dependencies or something.
I've got a couple feature requests. If you'd like me to, please point me to a ticket system where I can post them for easier tracking, as I couldn't find one.
First I'd like a "launch WoW" button. I have the "leave running" option turned off, so I know it will only look for updates when I want it to. Would be nice to be able to just launch CC, make sure all my addons are up to date, then start up WoW with one click.
Second, would be to work a deal with WowInterface to be able to get addons from there in addition to addons from Curse. I do understand the problems with getting them from everywhere, and I also understand possible copyright/author permission problems. Just suggesting that, since I know you coordinated with them for the Flash/CAPTCHA/screw you wowmatrix project (which I highly approve of, btw), maybe you could coordinate with them on using a single updater for both sites. If author approval is too much of a stumbling block, perhaps a clause to ask for author approval for this, and prevent wowi addons without approval? Or if CC is "merged" with their updater that would get around this issue? IANAL, so I freely admit I dunno.
CC is VERY good. I'm quite impressed by it, though the WowI updater is, well, not. :)
And yes, I admit I'm one of those scumbags who used the scummy guys' updater. I haven't liked doing so, but ease-of-use trumped moral objections for me. <hangs head> And I've been too lazy to check out the new CC, so I really do thank you for screwing them over and forcing me to give it a try. It's definitely good, and I very much like it.
I was gonna ask for an "ignore this addon" option as my only other feature request, but I found it last night. :)
Yeah but no reason we can't add a feature to launch the launcher.... er... yeah...
Some users may still be running the Curse Client with elevated privileges. Those users may not wish to launch WoW (or the WoW launcher) with elevated privileges, so you might want to warn them if you detect this case.
Some users may still be running the Curse Client with elevated privileges. Those users may not wish to launch WoW (or the WoW launcher) with elevated privileges, so you might want to warn them if you detect this case.
I'm not sure, but would it not be possible to launch it with degraded privileges?
I'm not sure, but would it not be possible to launch it with degraded privileges?
I'm honestly not sure how spawning new processes works in that regard. I just wanted to raise the question so it could be considered and tested for if you decide to implement that feature.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Of course that's your prerogative :)
I don't take that approach myself because not every update is a fix. Sometimes authors refine or add new features that significantly increase the usefulness of the addon.
I stopped using a particular addon quite a while ago. Removed it from the Interface directory entirely. CC is still telling me that it's installed, is displaying the version as the last version I had used before deleting the addon, and is tracking the current version number.
There's no trace of the addon itself left, so where the hell is it getting that list?
In cc, reinstall it then uninstall it.
Curse client is an addon manager program. Either let the program manage your addons hosted on curse or do it manually not both. The program doesn't account for addons you manually delete.
You can hit "refresh" and it will remove from its list the addons you deleted .
Exact paths can vary depending on the filesystem.
I did that. It "worked" in that the unused addon no longer shows up, but CC also deleted a shared library addon. (Not an Ace/embedded library.) Fortunately I had made a backup not too long ago, so I could restore it. When I reinstall *just* the library addon, then the unused and uninstalled addon appears again.
No, I tried that before even posting. It thinks the thing is really there. Apparently confusing the nonexistent addon with one of its dependencies or something.
First I'd like a "launch WoW" button. I have the "leave running" option turned off, so I know it will only look for updates when I want it to. Would be nice to be able to just launch CC, make sure all my addons are up to date, then start up WoW with one click.
Second, would be to work a deal with WowInterface to be able to get addons from there in addition to addons from Curse. I do understand the problems with getting them from everywhere, and I also understand possible copyright/author permission problems. Just suggesting that, since I know you coordinated with them for the Flash/CAPTCHA/screw you wowmatrix project (which I highly approve of, btw), maybe you could coordinate with them on using a single updater for both sites. If author approval is too much of a stumbling block, perhaps a clause to ask for author approval for this, and prevent wowi addons without approval? Or if CC is "merged" with their updater that would get around this issue? IANAL, so I freely admit I dunno.
CC is VERY good. I'm quite impressed by it, though the WowI updater is, well, not. :)
And yes, I admit I'm one of those scumbags who used the scummy guys' updater. I haven't liked doing so, but ease-of-use trumped moral objections for me. <hangs head> And I've been too lazy to check out the new CC, so I really do thank you for screwing them over and forcing me to give it a try. It's definitely good, and I very much like it.
I was gonna ask for an "ignore this addon" option as my only other feature request, but I found it last night. :)
When I have the launcher screen disabled from WoWs options, which I hope still runs the launcher, it does skip that extra click for me.
/e tries to think of valid ways to launch more references to the launch word launch, but fails.
Some users may still be running the Curse Client with elevated privileges. Those users may not wish to launch WoW (or the WoW launcher) with elevated privileges, so you might want to warn them if you detect this case.
I'm not sure, but would it not be possible to launch it with degraded privileges?
I'm honestly not sure how spawning new processes works in that regard. I just wanted to raise the question so it could be considered and tested for if you decide to implement that feature.