laptop
533 242
533 242
pc
810 346
810 346
I fiddled with center_rect a little bit more and I found this out, I typed "xoffset" "yoffset" lines again and the error is now gone with my laptop, maybe I had an extra empty space/line?
]]>echo "$xoffset $yoffset"
after
xoffset=$1
yoffset=$2
in center_rect
And give me the output of
center_rect 300x40
?
]]>xoffset=1580
yoffset=52
sres (laptop)
1366x768
sres (pc)
1920x1080
mkfifo "$TMP_FIFO"
(dzen2 -h "$bar_height" -w "$bar_width" $xy_pos -fn "$bar_font" -bg "$bar_bg" -fg "$bar_fg" < "$TMP_FIFO"
rm "$TMP_FIFO") &
This should be replaced with:
if mkfifo "$TMP_FIFO" ; then
(dzen2 -h "$bar_height" -w "$bar_width" $xy_pos -fn "$bar_font" -bg "$bar_bg" -fg "$bar_fg" < "$TMP_FIFO"
rm "$TMP_FIFO") &
fi
(This has nothing to do with Shinryuu's issue.)
]]>Mhh, I get an error but it shouldn't be that critical, what might cause this?
What's the output of
sres
?
]]>[~] dvol lower
/home/shn/bin/center_rect: line 30: printf: /home/shn/bin/center_rect: invalid number
[~]
if [ ! -p "$TMP_FIFO" ] ; then
[ -e "$TMP_FIFO" ] && rm "$TMP_FIFO"
instead of
if [ ! -e "$TMP_FIFO" ] ; then
]]>where are the dzen colors?
Light and dark schemes shown in normal and muted states:
]]>To use gdbar you have to install https://aur.archlinux.org/packages.php?ID=14470
]]>I m pasting the new script with the recommended changes.
Also now the volume bar centers itself accordingly as per the resolution.
But the setting of volume through mpd still does not reflect as the script reads/sets the main output volume, but mpd sets/reads the application volume. (Correct me if I am wrong as I am new to pulseaudio)
I dont get how this works. It does change volume, but the dzen stuff is not working. I only get a completely purple rectangle, which always looks the same.
Also what is "dzen2-gdbar"?
➜ ~ ./pulsevolbar.sh increase
./pulsevolbar.sh: line 100: dzen2-gdbar: command not found
hey guys! how did you find out which were your keys? I'm using dwm/monsterwm. I remember I used something like XF86audioMute or something like that, for the key's name in the config file.
The command `xev` could help you find that out, as well.
]]>