Quote:
Originally Posted by LukeA
No, I want a product that works correctly when used as provided.
I don't have a problem with it providing the ability to go under the covers and fiddle with the code. I do have a problem with the thing producing an incorrect result when used in a manner that it appears to support.
The fix is simple - don't duplicate ids. That shouldn't be a major re-design or massive code change.
|
Use as provided is dangerous statement. Every product can be used differently as designed or though up, even 'professional' products. Sometimes it works, sometimes it doesn't. I can't count the times I have had a developer of a product on the line who said: 'I never imagined it to be used for that' for specific functions or calls.
Quite frankly I would be horrified if I had so many id's, but that is me. I wouldn't call the fix simple. I do not know the code, so I cannot make that assesment. I can image that it can be quite difficult to code correctly, since id's may be called upon. How to decide which links to maintain and which links to delete/change? Especially when things are copied/duplicated. The cure might be worse than the problem.