Good question, and it goes straight to the heart of many Blender usability issues. Do we ask the developers to code in coverage for our lack of understanding of what makes a feature work?.. (in ALL the many possible variations) or do we work with the attitude that Blender is a tool that requires a thorough understanding of what is happening “behind the curtain” as it were. Which in my opinion is one sign of a “pro” application.
Personally, I’ve found that HAVING to understand what’s going on has made it possible for me to have confidence in my ability to get things done in Blender. I’ve had previous experience with an a different app. (Animation Master) which went to get lengths to hide most of the realities of working in 3d behind an “easy to use” interface. There anything that went wrong WAS a show stopper, with no understanding of how things worked beyond “click this / and set that… etc.”
So, to answer your question… if there were a developer free (who was interested) in setting up the many possible error conditions with some form of warning as to the error condition and how to resolve it, I guess I wouldn’t mind the help. But I generally would NOT want automatically assumed conditions to be set based on the users input. As an example of this look no further than the “no image to bake too” error message. In this case it’s totally misleading!
I’m sure a lot of people would disagree with my position, so you should keep this in the bug tracker as a usability issue.
Good documentation would/should make this a moot point.
Oh, I moved the hat as it was making the render very slow. Don’t know why I pointed it out as part of the fix.