ASF error messages

[Angelika]

Dear Jens,
I noticed that the type of error messages ASF provides sometimes
creates confusion.
As an example, if a stimulus cannot be found while ASF reads in
stimuli, ASF correctly points
indicates the missing stimulus, but in addition produces a list of
error messages (Error in ==> ASF>read_stimuli at 965; Error in ==>
ASF>ASFInit at 662; Error in ==> ASF at 322). Another example is the
error message that is produced when trying to run ASF with a screen
resolution that is not available. At some point ASF indicates that
the requested screen resolution is not available, which is helpful,
but users might not see that message because it is followed by a
lengthy output of all available screen resolutions in addition to an
error message in the function ASFInit.
In summary, do you think it would be possible to provide error
messages that are easier to interpret by users that are less familiar
with ASF?
Greetings, and thanks for all the great work you are putting into this
project,
Angelika