Posts: 143
Joined: Dec 2012
Reputation:
2
Hi.
Give to the user more information why addon shows broken or incompatible. Its very hard to find/explain what's wrong.. e.g. what module is missing..
Thanks
Posts: 1,506
Joined: Nov 2013
yeah! where do you plan to get your PhD in log reading?
Posts: 17,859
Joined: Jul 2011
Reputation:
371
2013-11-19, 17:04
(This post was last modified: 2013-11-19, 17:05 by Martijn.)
It's mentioned in the default log and also says contact author. He should be sufficient knowledgeable to tell you.
Even if we would tell in GUI most of the users won't even know what to do
Posts: 143
Joined: Dec 2012
Reputation:
2
2013-11-19, 18:25
(This post was last modified: 2013-11-19, 18:26 by fightnight.)
ironic i already had one...
Ok I agree with you +-, could show on GUI with the new "expert" level.
Posts: 17,859
Joined: Jul 2011
Reputation:
371
Too much information too display. Just check the log (as that is the intention of a log)
Posts: 26,215
Joined: Oct 2003
Reputation:
187
It's not that it's too much information, it's that it's quite a bit of code that needs adding/rearranging to enable it.
I'd welcome a patch to do so. You'd need to check AddonInstaller::CheckDependencies() or thereabouts and change it to produce a list of required dependencies (and dependencies of dependencies). You'd then need to go through and eliminate ones already available to get down to the ones that cause the add-on to be marked as incompatible. And finally, format that up for the user-interface. Note that ideally you'd only want the first dependency in the tree (i.e. you probably don't want to list dependencies of dependencies).
