03-24-2014, 05:22 PM
As I stated before, I was also quite surprised by his response. His reasons for denying the patch make two things fairly clear to me:
First off, he values his own personal opinion over that of the user community who took the time to design and develop a patch that improves the functionality of Wings3D while not changing the default behavior of Wings3D at all.
Secondly, it seems fairly clear that he did not even take the time to understand what the patch does. His objections seem to center around the fact that he likes the default material the way it is and doesn't want to include the patch because he doesn't want the default material changed. If he had actually taken the time to understand what the patch does he would understand that, by default, the patch does absolutely nothing except provide the user with more options.
If the Wings3D user wants to use the same tired old flat gray material that has been the default material in Wings3D for the last 372 years of development, then all they need to do is… Nothing. By default the patch doesn't change Wings3D's functionality at all. If however, they want to have the default material be something different, the patch now allows them to make that change.
Since when is it against the design tenets of Wings3D to not allow the user to have more options? Heck, every single functionality in Wings3D has 57 different options! Why is this any different?
First off, he values his own personal opinion over that of the user community who took the time to design and develop a patch that improves the functionality of Wings3D while not changing the default behavior of Wings3D at all.
Secondly, it seems fairly clear that he did not even take the time to understand what the patch does. His objections seem to center around the fact that he likes the default material the way it is and doesn't want to include the patch because he doesn't want the default material changed. If he had actually taken the time to understand what the patch does he would understand that, by default, the patch does absolutely nothing except provide the user with more options.
If the Wings3D user wants to use the same tired old flat gray material that has been the default material in Wings3D for the last 372 years of development, then all they need to do is… Nothing. By default the patch doesn't change Wings3D's functionality at all. If however, they want to have the default material be something different, the patch now allows them to make that change.
Since when is it against the design tenets of Wings3D to not allow the user to have more options? Heck, every single functionality in Wings3D has 57 different options! Why is this any different?