lee@sq.sq.com (Liam R. E. Quin) (07/12/90)
[note slightly changed subject line]
jpc@fctunl.rccn.pt (Jose Pina Coelho) writes
>Error messages (I mean with a few more bits of information)
and goes on to give a very good (IHMO...) case for more precise error
messages.
On the other hand, the messages are already verbose and a little on
the cryptic side for non-technical users.
Perhas the error-message-level should be configurable? Or should there
be provision for an error daemon, like syslogd, that can try to pop up
a little window with a picture of a bomb and a red border?
Lee
--
Liam R. E. Quin, lee@sq.com, {utai,utzoo}!sq!lee, SoftQuad Inc., Toronto
``Sun. n.s., Any thing eminently splendid'' [Johnson's dictionary (1837)]jpc@fctunl.rccn.pt (Jose Pina Coelho) (07/13/90)
In article <1990Jul11.184523.28676@sq.sq.com> lee@sq.sq.com (Liam R. E. Quin) writes: > > On the other hand, the messages are already verbose and a little on > the cryptic side for non-technical users. > > Perhas the error-message-level should be configurable? Or should there > be provision for an error daemon, like syslogd, that can try to pop up > a little window with a picture of a bomb and a red border? Guess so, we could have a variable in Xlib to give the message level. #define XEL_Low 1 /* Low level: X invalid request, for non-techincal users */ #define XEL_Medium 2 /* Medium level: Like X11R4 */ #define XEL_Hight 3 /* High level: what parameter, full arguments etc... */ #define XEL_Philosofical 4 /* Try to analyze the arguments> Arg 1 is a 320x200x8 pixmap, etc ... extern int XErrorLevel; /* defaults to XEL_Medium */ PS: As usual I speak for myself, my cat prefers FORTRAN and a card puncher. -- Jose Pina Coelho | BITNET/Internet: jpc@fctunl.rccn.pt Rua Jau N 1, 2 Dto | UUCP: jpc@unl.uucp 1300 Lisboa, PORTUGAL | ARPA: jpc%hara.fctunl.rccn.pt@mitvma.mit.edu Home phone: (+351) (1) 640767 - If all men were brothers, would you let one marry your sister ?