Tim Ward said:
Come on, that was a perfectly reasonable initial question,
inviting an answer that would split the problem space at least
in half: either "no, you can't do it that way, because of yyy,
you need to look at xxx instead" or "yes, you can do it that
way, you must have a bug in your code" or even "yes, you
can do it that way, but you should be aware of the following
bog-standard gotcha".
Unfortunately the OP didn't mention quite basic things as whether it was
compilation or runtime problems that were experienced, or, assuming
successful compilation, elaborate on what 'didn't work' - e.g. the button
wasn't visible, or the wrong colour, or didn't respond to events, and so on.
The failure to provide more specific details, or post the relevant 'problem'
code, makes it impossible to diagnose the problem, and honestly answer [as
opposed to guess at] the question:
'What's wrong ?'
In hindsight I do admit that I could have been less abrupt and sought
additional details. In fact, when answering queries containing fairly
sketchy details, I often do do this, or make a 'best guess' attempt, and
reply with some sample code snippets. I believe, however, being asked to
answer such a fundamental question [i.e. 'What's wrong ?'] without being
given enough of the facts [IMO] with which to do so caused momentary
annoyance, hence the curtness of my reply.
My client relationship skills are [usually] excellent
!
Cheers,
Anthony Borla
