🚀 go-pugleaf

   A while back I asked two questions:
	1)  Why won't my TEDINFO accept any characters?
	2)  What is this '_' crash problem?

   Since then, I've gotten answers.  There seems to be some confusion about
these things, so to clear things up, I'll post what I know now:

Answers!

	1) My TEDINFO had the PVALID string set to "XXXXXXXXXX".  This means
	   "accept everything".  Unfortunately, I neglected to set the
	   field in the TEDINFO structure which specifies the length of the
	   input string (I think it's called tr_plength).  I thought at first
	   that this field was set by AES on return from form_do.  Sort of,
	   but that's not all.  Actually, you have to set tr_plength to the
	   MAXIMUM number of character the user is allowed to type.  It
	   was defaulting to zero, so the TEDINFO accepted no characters.

	2) The underscore bug afflicts a "middle" version of TOS -- the 
	   ROM version that isn't in the Mega's.  It causes the ST to
	   crash with nine or ten bombs when you type an underscore in
	   an editable text field (TEDINFO).  It does not only affect the
	   file selector box; it affects all TEDINFO's with 9's or 
	   P's in the PVALID string.  It may affect TEDINFO's with other
	   PVALID specifiers, too -- I haven't tried all of them.  I do
	   know, however, that there is NO PROBLEM with PVALID strings
	   with X's (X's mean "anything goes").  I have tested this; I've
	   got a text field that prompts for a variable name and underscores
	   cause no problem.  The solution, it would seem, is to make all
	   you TEDINFO's "XXXXXX" and then check the string for syntax
	   yourself.  This is kind of hack-ish, but it's guaranteed to wrok
	   on all the ST's (not just the Mega's).  You Mega people should 
	   test your software on 520's and 1040's before putting out if 
	   TEDINFO's are invovled!

Sorry to be so long-winded.  I hope this answers everyone's questions.  Thanks
to all who helped!
				Dave
				arpa: dmb@tis.com