[EMAIL PROTECTED] writes: > FVWM Bug Tracking notification > > new message incoming/775 > > Message summary for PR#775 > From: [EMAIL PROTECTED] > Subject: FvwmForm behavioural anomaly. > Date: Wed, 12 Sep 2001 04:20:44 -0500 > 0 replies 0 followups > > ====> ORIGINAL MESSAGE FOLLOWS <==== > > To: [EMAIL PROTECTED] > Subject: FvwmForm behavioural anomaly. > Date: Wed, 12 Sep 2001 04:20:44 -0500 > > Full_Name: George Beckett > Version: 2.4.0 > OS: Solaris 2.6 SPARC > > Just built the new version of Fvwm (ver. 2.4.0) on our network, both for > Solaris 2.6 and Redhat Linux 6.2. We use a standard FvwmForm for a logout > prompt - taken from FvwmForm man page - details of config. listed at end > of message. Using fvwm 2.2.4 there are no problems. However, for fvwm > 2.4.0 > actions are taken immediately when a button (either Cancel or Logout in > this case) is pressed, and not when it is released. This behaviour is only > on Solaris installation (I've tried using both Sun cc and gcc), the Linux > installation works fine. My temporary fix is to use the FvwmForm from > 2.2.4, > which seems to cause no problems.
I'm the culprit on this one. Actually, I like the immediate action. Looking at FvwmScript, I get the impression it does the same thing. I remember the old logic didn't work very well, perhaps it wasn't robust enough. So far, all the solutions that look like they might be robust seem to be pretty big too. Anyone have an opinion about whether this should be "fixed" and if so, what to use as a model? -- Dan Espen 444 Hoes Lane Room RRC 1C-214 E-mail: [EMAIL PROTECTED] Piscataway, NJ 08854 Phone: (732) 699-5570 -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
