Community
Participate
Working Groups
If you put a plugin the target directory and reload, normally the plugin shows up and everything is fine. If the plug-in is missing some prerequisites (i.e., is not resolved) then it does not show up in the target. Users need to be very alert to notice that some plugins are missing. Many will not notice and will endup later with compile errors or missing search results etc. One possibility is to show the unresolved plugins in the target but grayed out. Of course, this will lead to the following dialog Q: why are these gray? A: Because they are unresolved. Q: why are they unresolved? A: because plugins A and B are missing. C: Oh. thanks and the user goes off to get A and B. (of course, ultra deluxe would be for the user to then get help to find A and B but that's for another day). Back in reality, there is enough information to support the above dialog. Question is if/how to expose the information to the user.
We do log all unresolved restraints to the log along with reasons. I think that's the place for such problems is in the viewer itself. The problem here is that we may be too silent. We should direct the user to the log view.
sounds good. A slightly better version would be to capture the information and pop up a message box. some sort of feedback would be good.
*** This bug has been marked as a duplicate of 88578 ***
