Joey Hess <joey_at_kite.preferred.com> writes:
>
> > Exactly what clocks can FVWM2's FvwmButtons module swallow? So far I've
> > only be able to get xclock to be swallowed, but I would much rather have
> > it swallow dclock (digital clock). My problem might actually be related
> > to dclock itself, since my version of dclock doesn't support editres, but
> > I'd like to get something like it for my button bar.
>
> I've got my FvwmButton's swallowing xdalicclock, a digital clock with neat
> morphing effects. I use this line to do it:
>
> *FvwmButtons(3x1) - - Swallow "xdaliclock" Exec xdaliclock -noseconds -bg grey -fg darkviolet
>
I've been using xdaliclock for some time, but have a slight problem where if
I restart fvwm, causing xdaliclock to be killed and restarted, sometimes
it won't restart, and I'll have to manually start one. It spits out this
error:
X Error of failed request: BadDrawable (invalid Pixmap or Window parameter)
Major opcode of failed request: 63 (X_CopyPlane)
Resource id in failed request: 0x2000007
Serial number of failed request: 8066
Current serial number in output stream: 8084
I know that I should just figure out the FvwmButtons command that causes a
swallowed program to be regurgitated and reswallowed during a restart, but
it doens't happen often enough to cause me to be motivated. I'm just
curious if anyone else has seen this.
--
Brady Montz
bradym_at_cs.arizona.edu
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Fri Aug 16 1996 - 12:30:40 BST