pWidgets 2.5.8
battery and eeepc widgets
zigbert,
I have the same problem with battery vanishing refered by omskates in page 171. I'm running NOP431r1 in an eeepc 701.
I did everything you ask onskates to do with the same result: no change.
I did not have this problem in the same computer with NOP413r1.
01micko,
I installed your eeepc widget in my eeepc 701 running NOP431r1. Before installation the temp widget was showing the right temp and something like "FAN: are you sure you have one?". Using your widget the temp is OK but the FAN shows the unit rpm with no number before it.
I have the same problem with battery vanishing refered by omskates in page 171. I'm running NOP431r1 in an eeepc 701.
I did everything you ask onskates to do with the same result: no change.
I did not have this problem in the same computer with NOP413r1.
01micko,
I installed your eeepc widget in my eeepc 701 running NOP431r1. Before installation the temp widget was showing the right temp and something like "FAN: are you sure you have one?". Using your widget the temp is OK but the FAN shows the unit rpm with no number before it.
Please be sure you have all the correct eee drivers installed for your kernel version or it wont work. They are available in the "Drivers" sub forum....the temp is OK but the FAN shows the unit rpm with no number before it.
Cheers
Puppy Linux Blog - contact me for access
eeepc drivers
@ 01micko
Thanks. I will check if I have all the eee drivers.
Thanks. I will check if I have all the eee drivers.
Hi Sigmund
A bug. if you choose "theme" in the clock chooser the hour hand turns up black. I didn't investigate so I didn't fix it...
Cheers
edit: hmmm.. there seems to be a theme bug, I switched themes and the clock hands are ok, but the text retained the "deepthought" theme. I will investigate further and also start fixing the heavy bling package. May take some time but it will get done.
A bug. if you choose "theme" in the clock chooser the hour hand turns up black. I didn't investigate so I didn't fix it...
Cheers
edit: hmmm.. there seems to be a theme bug, I switched themes and the clock hands are ok, but the text retained the "deepthought" theme. I will investigate further and also start fixing the heavy bling package. May take some time but it will get done.
Puppy Linux Blog - contact me for access
Bugger!
I found quite a bug in the Reminder widget.. totally my fault ... but bash can be an ass!!!
Sigmund, remember I asked that question about addition in bash? Patriot explained to me about the base 8 if you add something with a preceding "0" or base 16 with preceding "0x"... well that bug is .. er "built-in" to the reminder widget . ...hence "Bugger!!!"
It is too complex to remove all the "0"s... the bug occurs from day "8" (January 8 ) to day "100" (April 10). I'll fix it with the "dc" command... same way I fixed my "PCountdown" timer. Hopefully that will work, I have 9 cases that could trip me up.. days "001" to "009" (January 1 to 9). Ah well.. we'll see...
Seems you didn't change anything in Plugins , just moved them for 2.2.1, but they seem to work ok... shouldn't be hard to fix the heavy bling stuff, I should have it ready soon.
While on the topic of the heavy bling, I think it is better not to include the imlib2 dependency. Dpup has it already, as do many puplets. Perhaps a link would be better.. of course only my opinion... (hehe, and everyone has one of those!)
Cheers
Edit:Hooray! "dc" works!
I found quite a bug in the Reminder widget.. totally my fault ... but bash can be an ass!!!
Sigmund, remember I asked that question about addition in bash? Patriot explained to me about the base 8 if you add something with a preceding "0" or base 16 with preceding "0x"... well that bug is .. er "built-in" to the reminder widget . ...hence "Bugger!!!"
It is too complex to remove all the "0"s... the bug occurs from day "8" (January 8 ) to day "100" (April 10). I'll fix it with the "dc" command... same way I fixed my "PCountdown" timer. Hopefully that will work, I have 9 cases that could trip me up.. days "001" to "009" (January 1 to 9). Ah well.. we'll see...
Seems you didn't change anything in Plugins , just moved them for 2.2.1, but they seem to work ok... shouldn't be hard to fix the heavy bling stuff, I should have it ready soon.
While on the topic of the heavy bling, I think it is better not to include the imlib2 dependency. Dpup has it already, as do many puplets. Perhaps a link would be better.. of course only my opinion... (hehe, and everyone has one of those!)
Cheers
Edit:Hooray! "dc" works!
Puppy Linux Blog - contact me for access
Ok
Here is the fixed Reminder widget updated for new structure of Pwidgets-2.2.1. It won't work in older Pwidgets.
-bugfix.... script failed from Jan 9 to April 10.
I have also added a patch in case you are running older pwidgets. It won't work in latest Pwidgets.
Have fun
Here is the fixed Reminder widget updated for new structure of Pwidgets-2.2.1. It won't work in older Pwidgets.
-bugfix.... script failed from Jan 9 to April 10.
I have also added a patch in case you are running older pwidgets. It won't work in latest Pwidgets.
Have fun
- Attachments
-
- Reminder-0.5.pet
- ONLY for latest Pwidgets 2.2.1
- (4.07 KiB) Downloaded 398 times
-
- Reminder-patch-0.5.pet
- ONLY for older Pwidgets
- (717 Bytes) Downloaded 394 times
Puppy Linux Blog - contact me for access
battery eeepc widgets
Thanks 01micko.
I found the right eeepc pets and now temp&fan are OK in NOP431r1 running in my eeepc701.
Only battery that was a good widget in NOP413r1 is vanished after upgrade to the new NOP.
I found the right eeepc pets and now temp&fan are OK in NOP431r1 running in my eeepc701.
Only battery that was a good widget in NOP413r1 is vanished after upgrade to the new NOP.
Hi sincsinc wrote:i want to add the start/stop button onto my jwm tray can you tell me where i can find that script so I can copy it to the tray? thanks
look in "/usr/local/pwidgets/func -stopstart"
The "stopstart" is a case which you should be able to call from a tray button with something like
Code: Select all
exec /usr/local/pwidgets/func -stopstart &
_______________________________________________________________
Sigmund.
Is this what's wrong with themes in pwidgets 2.2.1?
Code: Select all
#THEME - overwrite color-codes in conky config
ls -1 $HOME/.pwidgets/widgets > $HOME/.pwidgets/tmp/pwidgets-tmp
while read CONFIG_FILE; do
OLD="`grep -m 1 color0 $HOME/.pwidgets/widgets/$CONFIG_FILE | tr -d \n`"
NEW="`grep -m 1 color0 /usr/local/pwidgets/widgets/themes/$THEME/main | tr -d \n`"
[ "$OLD" ] && sed -i -e "s%$OLD%$NEW%g" $HOME/.pwidgets/widgets/$CONFIG_FILE
OLD="`grep -m 1 color1 $HOME/.pwidgets/widgets/$CONFIG_FILE | tr -d \n`"
NEW="`grep -m 1 color1 /usr/local/pwidgets/widgets/themes/$THEME/main | tr -d \n`"
[ "$OLD" ] && sed -i -e "s%$OLD%$NEW%g" $HOME/.pwidgets/widgets/$CONFIG_FILE
OLD="`grep -m 1 color2 $HOME/.pwidgets/widgets/$CONFIG_FILE | tr -d \n`"
NEW="`grep -m 1 color2 /usr/local/pwidgets/widgets/themes/$THEME/main | tr -d \n`"
[ "$OLD" ] && sed -i -e "s%$OLD%$NEW%g" $HOME/.pwidgets/widgets/$CONFIG_FILE
OLD="`grep -m 1 color3 $HOME/.pwidgets/widgets/$CONFIG_FILE | tr -d \n`"
NEW="`grep -m 1 color3 /usr/local/pwidgets/widgets/themes/$THEME/main | tr -d \n`"
[ "$OLD" ] && sed -i -e "s%$OLD%$NEW%g" $HOME/.pwidgets/widgets/$CONFIG_FILE
OLD="`grep -m 1 color5 $HOME/.pwidgets/widgets/$CONFIG_FILE | tr -d \n`"
NEW="`grep -m 1 color5 /usr/local/pwidgets/widgets/themes/$THEME/main | tr -d \n`"
[ "$OLD" ] && sed -i -e "s%$OLD%$NEW%g" $HOME/.pwidgets/widgets/$CONFIG_FILE
OLD="`grep -m 1 color6 $HOME/.pwidgets/widgets/$CONFIG_FILE | tr -d \n`"
NEW="`grep -m 1 color6 /usr/local/pwidgets/widgets/themes/$THEME/main | tr -d \n`"
[ "$OLD" ] && sed -i -e "s%$OLD%$NEW%g" $HOME/.pwidgets/widgets/$CONFIG_FILE
#check for indiviual themes
[etc]
Code: Select all
*)
cp -u /usr/local/pwidgets/widgets/configs/$TREE_WIDGET $HOME/.pwidgets/widgets/$TREE_WIDGET
echo "conky -a $POS_CONKY -x $OFFSET_X -y $OFFSET_Y --config=$HOME/.pwidgets/widgets/$TREE_WIDGET &" >> $HOME/.pwidgets/tmp/pwidgets-exec_conky
Cheers
Mick
EDIT: It occurs to me too, that if this method did work there would still be a bug. If you added a new widget it would have the "DeepThought" theme (or it's default if it is "Ram" or "Horoscope" ) no matter what theme your exixting widgets have.
________________________________
ANOTHER EDIT: The theming does work using your method as long as you don't use "Apply" in the main gui. But, the clock doesn't show. That's why I clicked "Apply" to see if the clock would come back... it did.. with the chosen theme but the conky dependent widgets came back with the default theme.
Cheers
Puppy Linux Blog - contact me for access
In a multiuser system, the user doesn't have write access to /usr/local. I will look at it, but I have ran out of time..... It is added to the todo-list, so it won't be forgotten.Mick wrote:Perhaps change the code to change the stored configs in "/usr/local/pwidgets/widgets/configs/"?
Thank you
Sigmund
Of course! ( ). Perhaps just find out why the clock fails to show up. I'll keep digging..In a multiuser system, the user doesn't have write access to /usr/local.
I suppose that a user can always reset the theme if they add a widget and it is a different theme.
Cheers
___________________________
Sigmund
EDIT:: two of these and . One for you and one for me.. the fix is too easy.
in "/root/.xonclockrc" it is
Code: Select all
# path to clock skin
skin =/root/.pwidgets/misc/Clock-analog.png
Ah well it's solved now!
Cheers
Puppy Linux Blog - contact me for access
micko thank you for your response, i finally got around to trying to add the stop/start option in my jwmrc-tray and I can't get it to work.
i added as you suggested but it doesn't seem to do anything. Am I typing something in wrong maybe? Also where would I find the icon that is used in the drop-down menu? ANy other ideas would be appreciated. Thanks.
i added
Code: Select all
<TrayButton popup="Start/Stop Pwidgets" icon="mini-hdisk.xpm">exec:/usr/local/pwidgets/func -stopstart &</TrayButton>
Sorry sinc.. it's not as simple as that... variables need to be defined that's why it won't work.
It is doable . "/usr/local/pwidgets/pwidgets" is where the variables are defined. The important ones for you are "#Puppy specific" and "#Set language". Hope this helps.
Of course you will need to make a separate script to call the "stopstart".
Cheers
It is doable . "/usr/local/pwidgets/pwidgets" is where the variables are defined. The important ones for you are "#Puppy specific" and "#Set language". Hope this helps.
Of course you will need to make a separate script to call the "stopstart".
Cheers
Puppy Linux Blog - contact me for access
Pwidgets 2.2.1
I installed Pwidget 2.2.1 in puppy linux 3.01. It works fine, but I would like to have the analog clock on the top layer. How to do so?