William F Pokorny <ano### [at] anonymousorg> wrote:
> On 6/9/21 11:46 AM, jr wrote:
> > ...
> > may be 'xwd' (and 'xwud') can help? not sure how you'd automate the syncing
> > though.
> Yeah, maybe. A long while back now, I did play a little with xwd - stand
> alone just snapping a paused preview window. Hit some issue that looked
> to be related to quantization or a shift of color values. I could not
> quickly sort it and I dropped the work - work that's been on the floor a
> long while now. In truth it's 'play' down my list at the moment -
> though(1) ;-).
> I 'believe' in rtr much of the work needed to create an output image is
> still done for each frame, perhaps I just need to figure out how to
> pause and trigger a write to unique output files. ...
had a look at the xwd-1.0.6 source and modified (quick hack) the main function
to create N files from the given window. no syncing though, adding another
option to specify a delay after each file might help a little. patch attached
just in case, but anyway, it would be a "crutch" at best.
tested a couple of times with small number frames, running a 'povr' with the
command-line given in 'rtr_kla.pov'. then the modified 'xwd' ('-nfrm' + '-out'
$ ./xwd -nfrm 10 -out /tmp/foo -name "POV-Ray (povr) 3.8 povr X11 "
creates '/tmp/foo_00.xwd' etc. I used 'xv' for visual check:
$ xv /tmp/foo*.xwd
(curiously, could only identify 'povr' window name + class, but no id shown)
Post a reply to this message
Download 'wfp_xwd1.txt' (4 KB)