From time to time I'm a little impatient (especially if there's a nice new feature announced in fbink I'd really like to have - such as the padding for true type fonts a couple of months ago - thank you very much for this), so I sometimes scan the
trac site for new versions if there's not yet an official release.
So, until yesterday, I used fbink@16051 on my Kobo Glo HD without any problems. After the update to fbink@17028, two of my shell scripts stopped working. A little research showed the same problem for fbink@16952.
In one case the previous screen is not completely cleared before the script freezes/crashes. I'm left with faint parallel lines. The relevant part (for displaying stuff with fbink) starts with:
Code:
# Show animation
$fbink -k
sleep 2
i=0
for FILE in $ICONFOLDER/$ICONNAME*.png ; do
i=$(($i+1))
done
j=1
while [ $j -le $i ] ; do
$fbink -g file=$ICONFOLDER/$ICONNAME$j.png,halign=CENTER,valign=TOP,w=0,h=$iconheight,y=$icontop -h -W A2 #-c
sleep 0.1
j=$(($j+1))
done
sleep 5
Do you have any ideas what I'm doing wrong? Or why it stopped working?
Another script now stops during/after(?) the display of the icon file:
Spoiler:
Code:
# Extract information line for line from download queue:
if [[ "$QUEUEFILE" ]] ; then
$fbink -mMc -t regular=$font_directory/$font-Regular.otf,$viewport,padding=HORIZONTAL "Download queue found in $QUEUEFILE."
sleep 3
$fbink -k
while read LINE ; do
$fbink -g file=$ICONFILE,halign=CENTER,valign=TOP,w=0,h=$iconheight,y=$icontop
if [ $(echo $LINE | cut -c 1) != '#' ] ; then
LIST=$(echo "$LINE" | sed 's/ /\n/g')
.
.
.
fbink_info=$($fbink -m -t regular=$font_directory/$font-Regular.otf,top=$top,left=$left,right=$right,padding=HORIZONTAL "$title.epub
downloaded to
$target_directory
" -l)
fbink_infolist=$(echo "$fbink_info" | sed 's/;/\n/g')
top=$(echo -e "$fbink_infolist" | grep "next_top" | sed -r 's/^next_top=(.*)$/\1/g')
sleep 5
fi
done < "$QUEUEFILE"
else
$fbink -mMc -t regular=$font_directory/$font-Regular.otf,$viewport,padding=HORIZONTAL "No download queue found."
sleep 5
fi
It's probably obvious what's going wrong but I can't see it.