*	provide on-screen indicator for gerd's states (recording/playback/idle)
	e.g. the gerd.xcf in some screen corner
*	feature message dialog and let users post-process event files to insert
	tutorial (demo) messages
*	let users set arbitrary scale factors for the recorded delays (can make
	races much mworse though)
*	the window identification code relies on mapping order in the final
	stage, that prevents us from starting recording/playback at arbitrary
	times during a programs lifetime
*	if the toplevel windows aren't jumped to the screen position they had
	during recording, dnd events are off by a few pixels. this is probably
	related to window managers not being ICCCM compliant by interpreting
	the XMoveWindow coordinates as coordinates for their frame window,
	instead of as absolute coordinates for the client window (if that's
	really the problem, the new window manager spec will solve it).
*	we don't fully handle complicated programs like the gimp yet, it
	invokes children that will need to have their own event lists recorded
