🚀 go-pugleaf

The question is about the behavior of string gadgets -- why don't you always
get a gadgetup message when the string becomes deactive, no matter if you 
pressed return or clicked elsewhere?

Actually, the behavior is consistent, at least in my understading, with the
behavior of boolean gadgets with the GADGIMMEDIATE and RELVERIFY flags set.
Note that if you have a boolean gadget with these flags both set, you will
get a message immediately when the user clicks on the gadget, and you will get
another when the user releases the mouse button IFF the pointer is still
over the gadget.  If the user pulls the mouse pointer off the gadget while 
holding down the select button, the gadget will de-select and you will NOT
get a GADGETUP message.

This is exactly analagous to the behavior of string gadgets with these flags 
set.  When the user selects the gadget, you will get a GADGETDOWN message,
and you will get a GADGETUP message IFF the user presses return.  Clicking
elsewhere is like pulling the mouse pointer off the boolean gadget before
relasing the button.

If you need to know when the user is through with the string gadget, just
look for any other message coming from the same {Window|Requester}.  As soon
as one comes, you know the user is done with the gadget, since you can't
get another message until he clicks someplace else or presses return.
-- 
		Stuart Ferguson		(shf@well.UUCP)
		Action by HAVOC		(shf@Solar.Stanford.EDU)