--- In LTspice@..., Helmut Sennewald wrote:
We shouldn't attack users when we don't know about their
knowledge and capabilities. Please keep that in mind.
Hello Helmut,
I think you have mistakenly interpreted my response as an attack
when it was not. In fact, a reading or comprehension problem was
one of several reasonable possibilities to ask about, given that
the original poster claimed to have read the Help topic on the
switch element, yet was unable to see that it clearly stated the
he must provide a model statement.
This section of the Help topic is very short and includes a clear
link to an example schematic, something that would have answered
his questions. Yet for some reason, he did not run the example.
I truly would like to know the reason why not (and why so many
other people seem to have trouble with Help). This really is a
puzzle to me.
I am gradually coming to the conclusion that written words, even
if short and simple, are not always "seen." It may be because
the reader is not a native speaker of English, it may be because
they are faced with an information overload, or it may be that
the "Twitter" generation can't always effectively process
traditional "dry" textbook-style information (i.e., a reading
comprehension problem), or it may be simple laziness (which, I
suppose a person has the right to be - as long as they don't try
to steal the labor of others).
Anyway, I wonder if Help would be more effective if it included
graphical examples or at least hot links to graphical examples
or hotlinks to launch example schematics. The question remains:
How to make Help continue to function as a compact and efficient
reference while also being able to effectively provide answers
that neophytes can actually see, process and put to use?
Regards -- analogspiceman
