On Thu, Mar 09, 2000 at 10:05:44PM -0600, David J. Kanter wrote:
> My biggest problem with the wharf is that even with MaxSwallow, some apps
> run too wide and are cut off. Here's the relevant section of my .fvwm2rc:
>
> # FVWM WHARF
>
> *FvwmWharfGeometry +1076+0
> *FvwmWharfTextureType 1
> *FvwmWharfTextureColor midnightblue lightblue
> *FvwmWharfFullPush
> *FvwmWharfMaxColors 256
>
> # The actual wharf apps:
> # *FvwmWharf wmtime nil MaxSwallow "wmtime" wmtime -digital &
> # *FvwmWharf wmdate nil MaxSwallow "wmdate" wmdate -s &
> # *FvwmWharf wmcpu nil MaxSwallow "wmcpu" wmcpu -l &
> # *FvwmWharf wmsysmon nil MaxSwallow "wmsysmon" wmsysmon &
> # *FvwmWharf wmppp nil MaxSwallow "wmppp" wmppp -t 1 &
> *FvwmWharf astime - MaxSwallow "astime" astime &
> *FvwmWharf asmon - MaxSwallow "asmon" asmon &
> # *FvwmWharf asload - MaxSwallow "asload" asload -shape &
> *FvwmWharf asmem - MaxSwallow "asmem" asmem &
> *FvwmWharf asmounter - MaxSwallow "asmounter" asmounter &
> *FvwmWharf wmppp - MaxSwallow "wmppp" wmppp -t 1 &
>
> Asmon and wmppp are the troublemakers. Any idea why, and what I can do?
Sorry for the late reply. I tried this with xload, and for
me FvwmWharf simply refuses to swallow it if it's larger than
48x48 pixels. This seems to be a bug in FvwmWharf. We'll
investigate this.
Bye
Dominik ^_^
--
Dominik Vogt, dominik.vogt_at_gmx.de
Reply-To: dominik.vogt_at_gmx.de
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Sun Apr 16 2000 - 21:52:12 BST