Subject: render vs. xclock/4.3.0
To: None <firstname.lastname@example.org>
From: Chuck Cranor <email@example.com>
Date: 08/15/2003 20:57:45
i upgraded my laptop to the latest xsrc from the netbsd CVS and
it broke my xclock --- the colors in the clock are so dim i can hardly
i run xclock with the following resources:
i've found that if i start xclock with "xclock -norender" things
are back to normal (i.e. the clock is easy to read once again, like
it was before my upgrade).
is the new behavior of xclock really desirable? i don't really
understand why it was changed, maybe someone can explain?