Main index > Installation problems > new widget does not show up?

By patrick295767 (User), on Sun Nov 12 03:22:49 2006: new widget does not show up?.

[Adesklets] new widget does not show up?

Hi,

I installed TK and python2.4-tk

adesklets -i works.
I have the weather working and the clock, but the third one in this config is not working:

Code:

# This is adesklets configuration file.
#
# It gets automatically updated every time a desklet main window
# parameter is changed, so avoid manual modification whenever
# a desklet is running. In fact, manual changes to this file
# should rarely be needed. See `info adesklets'.

[/home/patrick/adesklets/weatherforecast-0.2.0/weatherforecast.py]
id=0 screen=0 x=158 y=265

[/home/patrick/adesklets/adeskclock-0.1.0/adeskclock.py]
id=0 screen=0 x=861 y=623

[/home/patrick/adesklets/SystemMonitor-0.1.3/SystemMonitor.py]
id=0 screen=0 x=0 y=0

The folders and files are present and ok.

the config. looks fine but no system monitor showed up. The two others are there.

SystemMonitor. never worked, I registered it like i did for the others.

Can it be working ?

thank you

===
I tried further:
volume works
mailer does not work

By syfou (Core Developer & Desklet Author), on Sun Nov 12 14:32:09 2006.

As indicated in the manual, never register a desklet without testing it first, since it prevents you catching potential error messages due to improper configuration, etc. SystemMonitor is undoubtedly a desklet you want to test "manually" from a console, as the error messages help you see what is not tailored to your system; same applies to mailer.

So fire-up a pseudo-terminal, kill your desklets (adesklets --killall, go to your problematic desklet directory, and start (t)esting. If you don't understand the error outputs, refer to the desklet-specific topic on this forum (in About existing desklets). There is a fair chance an explanation will already be there for most the problems you might encounter. Yours,

By patrick295767 (User), on Mon Nov 13 14:45:26 2006.

syfou wrote:

As indicated in the manual, never register a desklet without testing it first, since it prevents you catching potential error messages due to improper configuration, etc. SystemMonitor is undoubtedly a desklet you want to test "manually" from a console, as the error messages help you see what is not tailored to your system; same applies to mailer.

So fire-up a pseudo-terminal, kill your desklets (adesklets --killall, go to your problematic desklet directory, and start (t)esting. If you don't understand the error outputs, refer to the desklet-specific topic on this forum (in About existing desklets). There is a fair chance an explanation will already be there for most the problems you might encounter. Yours,


Thank you for the information, Not so easy, ...I hope it will work out.
Let's try !

Sincerely,

adesklets is proud to be hosted on:

SourceForge.net Logo

Back to adesklets.sf.net.