f25c7a3f04
Inspired by T39315, this commit adds a few more driver "linting" messages used for providing users with tips on how to use drivers better. This time, we specifically address 2 cases: 1) Drivers being abused for procedural animation, due to the misconception that procedurally generating F-Curves using F-Modifiers means that drivers are needed to wire such procedural motion-sources to properties. 2) Setting up Average/Sum/Min/Max driver types without any input variables - you can't expect anything to happen (unless of course, your intention was to lock the property to 0.0)