05-13-2015 07:14 AM
Why not make the second frequency value an indicator if it would be too confusing for the user to only have one?
05-13-2015 07:26 AM
@TToolDev01 wrote:
Why not make the second frequency value an indicator if it would be too confusing for the user to only have one?
That's what the GUI looks like is happening. That makes more sense. So when the frequency is updated for the Signal Generator, all the OP needs to do is write the value to the terminal of the indicator.
05-13-2015 07:35 AM
05-13-2015 08:21 AM
05-13-2015 08:43 AM
@mikeporter wrote:
Well BS or not, if this is what the OP's customer or user is wanting, it's a great idea no matter what we think. I can't count how many times I have been asked to create user interfaces that made no sense to me. The best we can do is explain the problems that we see -- but the customer gets to make the decision.
Mike...
This is likely the worst possible attitude to take here. As a developer, it's your job to help those that contract your work. If they ask for something that doesn't make sense, you should engage in a conversation rather than take it as a "great idea." Part of what they're paying you for is your experience. By not giving it to them, you're cheating them. If they insist on doing something that doesn't make sense, it still doesn't make sense. It's not a great idea simply because they want it. Ideas are great independent of an employer's desire. In this case, it doesn't offer the user any more clarity. It adds more to the screen the user must digest. Once they do understand it, they'll be confused as to why they don't set the frequency in one spot instead of two.
05-13-2015 11:49 AM - edited 05-13-2015 11:54 AM
@natasftw wrote:
@mikeporter wrote:
Well BS or not, if this is what the OP's customer or user is wanting, it's a great idea no matter what we think. I can't count how many times I have been asked to create user interfaces that made no sense to me. The best we can do is explain the problems that we see -- but the customer gets to make the decision.
Mike...This is likely the worst possible attitude to take here. As a developer, it's your job to help those that contract your work. If they ask for something that doesn't make sense, you should engage in a conversation rather than take it as a "great idea." Part of what they're paying you for is your experience. By not giving it to them, you're cheating them. If they insist on doing something that doesn't make sense, it still doesn't make sense. It's not a great idea simply because they want it. Ideas are great independent of an employer's desire. In this case, it doesn't offer the user any more clarity. It adds more to the screen the user must digest. Once they do understand it, they'll be confused as to why they don't set the frequency in one spot instead of two.
I think there is a misunderstanding here because it sounds like both of you just said the same thing to me.
Here is what I translate both of your posts to mean - which I absolutely agree with:
If the customer has an obvious design flaw, you point it out and then you advise. It's up to the customer whether or not they want to take the advice. You don't make the call, they do.
The reason is because you never know the complete picture. Extensive requirements documentation helps, but it never truly tells the whole story. Oftentimes what looks stupid to you has a reasn to be there. (Sometimes the reason is stupid, too - and that's where you can really help.)
05-13-2015 01:05 PM