FVWM Bug Tracking notification
new message incoming/923
Message summary for PR#923
From: [EMAIL PROTECTED]
Subject: FvwmTaskBar & complex functions
Date: Fri, 20 Sep 2002 17:39:04 -0500
0 replies 0 followups
====> ORIGINAL MESSAGE FOLLOWS <====
>From [EMAIL PROTECTED] Fri Sep 20 17:39:05 2002
Received: from util2.math.uh.edu ([129.7.128.23])
by malifon.math.uh.edu with esmtp (Exim 3.20 #1)
id 17sWQS-0006Zw-00
for [EMAIL PROTECTED]; Fri, 20 Sep 2002 17:39:04 -0500
Received: from malifon.math.uh.edu ([129.7.128.13] ident=mail)
by util2.math.uh.edu with esmtp (Exim 4.10)
id 17sWQS-0003jT-00
for [EMAIL PROTECTED]; Fri, 20 Sep 2002 17:39:04 -0500
Received: from localhost ([127.0.0.1] ident=65534)
by malifon.math.uh.edu with esmtp (Exim 3.20 #1)
id 17sWQS-0006Zs-00
for [EMAIL PROTECTED]; Fri, 20 Sep 2002 17:39:04 -0500
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: FvwmTaskBar & complex functions
Message-Id: <[EMAIL PROTECTED]>
Date: Fri, 20 Sep 2002 17:39:04 -0500
Full_Name: Rastislav Galia
Version: 2.4.9
CVS_Date:
OS: Red Hat Linux 7.1
X_Server:
Submission from: (NULL) (195.163.152.136)
Enhancement suggestion : FvwmTaskBar has very limited means of cooperation
with complex functions. They can only contain "I" statements to work
correctly. It is caused by triggering function only after button release.
Consistent way would be to call function after button is pressed, not
released. While release-triggering makes sense with non-function actions,
there should be alternative scheme for use with functions. Something like
*FvwmTaskBar: Action ClickRelease1 ...
--
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]
