WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: bibletime stops wbar  (Read 1908 times)

Offline jur

  • Hero Member
  • *****
  • Posts: 863
    • cycling photo essays
bibletime stops wbar
« on: April 24, 2010, 12:18:05 AM »
When loading bibletime, wbar disappears, due to the icon not conforming or being missing or something similar. (wbar will not load if there is a icon or command problem with any of the apps.)

Offline maro

  • Hero Member
  • *****
  • Posts: 1228
Re: bibletime stops wbar
« Reply #1 on: April 24, 2010, 01:11:14 AM »
Looks like as if 'wbar' does not "like" SVG files. After I changed in '/usr/local/tce.wbar' the entry
   i: /usr/local/share/icons/bibletime.svg
to
   i: /usr/local/share/bibletime/icons/bibletime.png
I was able to restart 'wbar'.

Edit: If my theory is correct that wbar only "plays nice" with PNG files an enhancement of the new '/usr/bin/wbar_icon_upd.sh' might be required. A check for the file type could be able to prevent this issue and in case of a SVG file fall back to the "old" way to pick an icon file.

« Last Edit: April 24, 2010, 01:34:58 AM by maro »

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9730
Re: bibletime stops wbar
« Reply #2 on: April 24, 2010, 05:09:49 AM »
Bilbletime fixed.

Offline robc

  • Sr. Member
  • ****
  • Posts: 447
Re: bibletime stops wbar
« Reply #3 on: April 25, 2010, 08:46:06 PM »
I'm not sure where the svg came from, my build script for this extension has the png icon used for wbar...
"Never give up! Never surrender!" - Commander Peter Quincy Taggart

"Make it so." - Captain Picard

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9730
Re: bibletime stops wbar
« Reply #4 on: April 25, 2010, 09:01:28 PM »
I have been converting existing extensions to be compliant with the freedesktop standards mentioned in this thread:

http://forum.tinycorelinux.net/index.php?topic=5810.0

Batch converting was used, and there was a glitch in the icon used for the X-FullPathIcon entry in some extensions.  That has been fixed since the first pass.  A final conversion/correction will be done in the near future to make extensions compatible with TC 2.11.