I spent this morning making my "set the root background" work properly, and was looking at fvwm-root. I noticed that the manual doesn't match the code. Appended is a patch for the manual (against current CVS) to address this lack. The color-limit stuff is a bit vague because I didn't read that code in depth.
While on this topic, I'm using Esetroot instead of fvwm-root. Why? Purely because it sets the ESETROOT_PMAP_ID pixmap property, and aterms listen for that. I notice fvwm-root can _clear_ this property but not set it. Is there any special reason for this? Merely that you use a different property for this? I was thinking of adding this facility (as an option, like -fe, since it is otherwise a resource waste). I presume it's a bad bad idea to hand the same pixmap to both properties, yes? -- Cameron Simpson, DoD#743 [EMAIL PROTECTED] http://www.zip.com.au/~cs/ --- fvwm-root.1.orig Tue Oct 15 10:13:10 2002 +++ fvwm-root.1 Tue Oct 15 10:19:27 2002 @@ -10,6 +10,8 @@ .B fvwm-root .RB [ \-d ] .RB [ \-fe ] +.RB [ \-dither ] +.RB [ \-no-dither ] .I image_file .SH DESCRIPTION @@ -33,6 +35,21 @@ Causes fvwm-root to free the memory associated with the ESETROOT_PMAP_ID property. This is useful if you alternately use fvwm-root and an Esetroot compatible program. +.TP +.BI "-dither" +Causes fvwm-root to dither images for "smoother" rendition on displays +with color depth of 16 or lower. +.TP +.BI "-no-dither" +Causes fvwm-root NOT to dither images. +.TP +.BI "-color-limit" ncolors +Causes fvwm-root to limit its color use to +.I ncolors +(if specified). +.TP +.BI "-no-color-limit" +Causes fvwm-root NOT to limit its color use. .SH COMPATIBILITY In the past this utility was called -- 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]
