nisus.com

NWP has an excellent Feedback mechanism, and the most recent enhancements improved it immensely.

Yet when a file has changed, NWP asks if you want to send the file with or without changes. But I sometimes don't know and so would like a third option - both. Then when it's not clear to me which to send, I could send both.

Option #2. It would require less thinking on the part of the user if NWP were to automatically send both, thus avoiding the minor extra effort of thinking about which to send...

Cris

Thanks for the suggestion Cris, I know it's a pet peeve of yours, and a good idea for an enhancement.

Yes, indeed it is. But why?

Don't I recall you responding one time that I'd chosen the wrong one to send, and I should mostly send the original? So it's something that would benefit us all...

CrisB wrote:Don't I recall you responding one time that I'd chosen the wrong one to send, and I should mostly send the original?

In general we want to try and reproduce any bugs or misbehaviors our users are encountering. The best way for us to do that is to have a clear roadmap that gets us from normal behavior (point A) to unwanted behavior (point B). A perfect roadmap includes the original correctly-behaving document (point A) and an exact list of steps that reproduces the misbehavior (point B). Sometimes it's useful to see point B (either as a screenshot or saved document), but it's not nearly as helpful as having the original materials that get us there in the first place.

So yes, in general the best is to send along the original document and a list of instructions that reproduces the misbehavior. If such a thing isn't possible, perhaps because the cause of the misbehavior isn't clear, or a user doesn't have time to put that together, etc, then seeing just the current/misbehaving document might be enough for a diagnosis.

So it's something that would benefit us all...

Right, which is why it's a good idea for an enhancement.