I have a function that used to work under 2.2, but does not under 2.4.8 nor
2.5.2. It is part of a window print capture form:
*CaptureButton continue "Capture" ^M
*CaptureCommand CaptureCommand "$(file)" "$(Options)"
AddToFunc CaptureCommand
+ "I" Current [Capture] Iconify
+ "I" PipeRead "exec xwd -out \"$0\" $1"
+ "I" Prev [Capture] Iconify
A message from xwd complains that it cannot grab the mouse. It works fine if I
use an Exec instead of PipeRead, except for the obvious timing: I want the
Capture form to disappear while I grab the window image.
If there is a good reason for PipeRead being less liberal with X resources
than Exec is, would it be feasible to offer a version of Exec that does not
start a separate thread / process? Or, to offer a WaitExec command that waits
for the most recently started Exec?
Best wishes, John Latham
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Mon Aug 12 2002 - 12:36:03 BST