Because bktr(4) signalling is unreliable, the best we can do is capture
authorMatthew Mondor <mmondor@pulsar-zone.net>
Tue, 19 Feb 2008 12:37:18 +0000 (12:37 +0000)
committerMatthew Mondor <mmondor@pulsar-zone.net>
Tue, 19 Feb 2008 12:37:18 +0000 (12:37 +0000)
commit4d7ea5446a3f272be319af77206467a84bc4c623
tree57f414e8910efea81eefa3785ccc8fb749cdd31a
parent6bb2e667b47415a98c25b0c959caec3c095c56e7
Because bktr(4) signalling is unreliable, the best we can do is capture
in single frame mode and to use a custom interval timer if we want to avoid
occasional artifacts like saving an image when it is being updated.
Previously both bktr signalling and a custom interval worked pretty well
but there always was the occasional conflict.
tests/bktr_multicast/src/bktr.c
tests/bktr_multicast/src/bktr.h
tests/bktr_multicast/src/main.c