[Corriewf]

Originally Posted by amykhar

In my opinion, clicking install before the code is actually installed and working is wrong. Let's say I post some code with some awesome sounding feature name. 300 people want that awesome feature and click install to download it. Turns out, my code really doesn't do the awesome thing it says it does. It has bugs and glitches. And, just for giggles, say I never fix the 10 pages of bug reports that get posted.

They click uninstall.

Originally Posted by amykhar

New guy comes along who doesn't read the thread. Sees 300 installs and things AWESOME! and grabs the code. Of course, he has problems too. And, he still doesn't read the thread. He just slaps his own problem report on the end.

And so the next guy comes along and the cycle continues.

Whos fault is that?

Originally Posted by amykhar

The moral of the story is click the install button when the code is installed and it WORKS. 8 people clicked install on a mod I released a little while back. The install directions were missing a critical step, but I assumed all was well because 8 people had successfully installed, right?

Amy

You say click it after its installed and working, yet most coders will not give support if a person hasnt clicked install. Once the code is in place, the functionality is irrelevant to its install status.