pWidgets 2.5.8
Hi guys
If you have looked into Pwidgets poor theming, please note that it is possible to make individual themes for each widget. See /root/.pwidgets/themes/DeepThought/. Here you see 'main' and 'Ram'. Main theme is used when no individual theme exist. All widgets with DeepThought theme are goldish, but the Ram widget are blue.
Sigmund
If you have looked into Pwidgets poor theming, please note that it is possible to make individual themes for each widget. See /root/.pwidgets/themes/DeepThought/. Here you see 'main' and 'Ram'. Main theme is used when no individual theme exist. All widgets with DeepThought theme are goldish, but the Ram widget are blue.
Sigmund
well, i found a serious bug involving the analog clock in 0.3.
when the analog clock.png loads, the rox pinboard will not let you do anything and the rox filer will not either.
i think it's something in the script for loading the clock.
and i noticed that pwidgets does not seem to like updating itself when you save changes.
these would be good to fix for 0.4. but when a bugfix is made, expect it to be in PupCore, as well as the other DeepThought themes.
- J-Bob
#EDIT: It only refuses to when you have the analogclock.png addon.
i'll remove this in a rebranding, CoreWidgets, if that's fine with you?
when the analog clock.png loads, the rox pinboard will not let you do anything and the rox filer will not either.
i think it's something in the script for loading the clock.
and i noticed that pwidgets does not seem to like updating itself when you save changes.
these would be good to fix for 0.4. but when a bugfix is made, expect it to be in PupCore, as well as the other DeepThought themes.
- J-Bob
#EDIT: It only refuses to when you have the analogclock.png addon.
i'll remove this in a rebranding, CoreWidgets, if that's fine with you?
[img]http://i114.photobucket.com/albums/n248/MedliSage/MAL/thing-4.png[/img]
It's been a long time.
It's been a long time.
J-Bob
I think the trouble with resizing the pinboard comes from the attempt to fix the rendering of the Analog-clock. 01micko has made a fix for that which uses xevent to auto-click on the desktop to show clock. This might give trouble, and you could try to remove/change the code in /usr/sbin/fixwidgets.
Sigmund
I thought there already was such a splash ???what if you made it run a small program which would disappear after pwidgets finishes loading, like a splash screen. that should be harmless and inconspicuous enough.
I think the trouble with resizing the pinboard comes from the attempt to fix the rendering of the Analog-clock. 01micko has made a fix for that which uses xevent to auto-click on the desktop to show clock. This might give trouble, and you could try to remove/change the code in /usr/sbin/fixwidgets.
Sigmund
Depending on the speed of your machine and what WM you use you may have to increase the sleep values for xevent. This may fix your problem. You may have to alter the cursor return coordinates as well. I have discussed this earlier in this thread. I'm working on a better fix.J-Bob wrote:actually, it attempts to resize the current active window. which is often the pinboard.
what if you made it run a small program which would disappear after pwidgets finishes loading, like a splash screen. that should be harmless and inconspicuous enough.
what do you thing Zigbert?
Slight oversight with my fix, there may be problems if you have your task bar at the top of the screen, but that can be addressed maybe in your main post zigbert? My fix is just a basic convenience type of thing designed for JWM with task bar on the bottom with limited testing in Icewm.
Hope that helps.
Puppy Linux Blog - contact me for access
I think it is likely the auto-click, as it moves the mouse to the top-left and apparently drags it.zigbert wrote:J-Bob
I thought there already was such a splash ???what if you made it run a small program which would disappear after pwidgets finishes loading, like a splash screen. that should be harmless and inconspicuous enough.
I think the trouble with resizing the pinboard comes from the attempt to fix the rendering of the Analog-clock. 01micko has made a fix for that which uses xevent to auto-click on the desktop to show clock. This might give trouble, and you could try to remove/change the code in /usr/sbin/fixwidgets.
Sigmund
i'll do some bugfixing in fixwidgets and once i get it working, i'll upload the new script, if i'm able to.
- J-Bob
i'm using the DeepThought theming built by Zigbert. My machine has a 1.13GHz Pentium III Mobile.01micko wrote:Depending on the speed of your machine and what WM you use you may have to increase the sleep values for xevent. This may fix your problem. You may have to alter the cursor return coordinates as well. I have discussed this earlier in this thread. I'm working on a better fix.J-Bob wrote:actually, it attempts to resize the current active window. which is often the pinboard.
what if you made it run a small program which would disappear after pwidgets finishes loading, like a splash screen. that should be harmless and inconspicuous enough.
what do you thing Zigbert?
Slight oversight with my fix, there may be problems if you have your task bar at the top of the screen, but that can be addressed maybe in your main post zigbert? My fix is just a basic convenience type of thing designed for JWM with task bar on the bottom with limited testing in Icewm.
Hope that helps.
I might be able to find a way to fix the error.
@zigbert
i'll mention another thing, it does not show me a splash screen for pwidgets
I did extensive testing on a slower laptop, but I did run into problems like you suggest. The sleep value is the key.J-Bob wrote:i'm using the DeepThought theming built by Zigbert. My machine has a 1.13GHz Pentium III Mobile.01micko wrote:Depending on the speed of your machine and what WM you use you may have to increase the sleep values for xevent. This may fix your problem. You may have to alter the cursor return coordinates as well. I have discussed this earlier in this thread. I'm working on a better fix.J-Bob wrote:actually, it attempts to resize the current active window. which is often the pinboard.
what if you made it run a small program which would disappear after pwidgets finishes loading, like a splash screen. that should be harmless and inconspicuous enough.
what do you thing Zigbert?
Slight oversight with my fix, there may be problems if you have your task bar at the top of the screen, but that can be addressed maybe in your main post zigbert? My fix is just a basic convenience type of thing designed for JWM with task bar on the bottom with limited testing in Icewm.
Hope that helps.
I might be able to find a way to fix the error.
@zigbert
i'll mention another thing, it does not show me a splash screen for pwidgets
Puppy Linux Blog - contact me for access
Have uploaded some files for 'xlideshow'. Pre alpha testing is necessary. Many helpers are welcome!
Puppy Linux Blog - contact me for access
Thank you for pwidgets everyone
How about a docking transparent sidebar with .png files you can easily change? Also skins for each widget, some people maybe don't like transparent..I am very eager and thankful to you guys for this pwidgets
- Attachments
-
- my-vista.jpg
- It shoul look like my current desktop
- (176.91 KiB) Downloaded 771 times
Here is the results of when i ran fixwidgets
yeah... I'd prefer adding the actual clicking onto a script which goes alongside the widget. because if that was the case, it would only be a problem with the analog clock.
@01micko
i think a static sleep variable might be the problem, but it's the fact that it causes a problem exactly after the widgets finish loading gives me a hunch it's the xevent not being friendly with jwm.
i could upload a screenshot of my desktop for those that want to know what it looks like.
- J-Bob
(Wow, feels like i might actually be helping with the bugfixing for a utility for 4.2. Well that's good.)
Edit: I should also mention, that i removed the wallpaper roxapp because removing it saves space, and i let rox manage right clicks on the desktop.
Code: Select all
/usr/sbin/fixwidgets: line 3: kill: (5096) - No such process
cp: cannot stat `[none]': No such file or directory
/root/Choices/ROX-background.jpg: image not found
Conky: Conky: /root/.pwidgets/configs/Cpu: 8: no such configuration: 'HEIGHT=155'/root/.pwidgets/configs/Calender: 8: no such configuration: 'HEIGHT=160'
Conky: Conky: /root/.pwidgets/configs/Cpu: 9: no such configuration: 'OFFSET_X=20'/root/.pwidgets/configs/Calender: 9: no such configuration: 'OFFSET_X=20'
Conky: /root/.pwidgets/configs/Puppylinux: 8: no such configuration: 'HEIGHT=50'
Conky: /root/.pwidgets/configs/Puppylinux: 9: no such configuration: 'OFFSET_X=40'
Conky: /root/.pwidgets/configs/Ram: 8: no such configuration: 'HEIGHT=155'
Conky: /root/.pwidgets/configs/Ram: 9: no such configuration: 'OFFSET_X=20'
Conky: desktop window (60001a) is subwindow of root window (46)
Conky: window type - override
Conky: drawing to created window (0x1600001)
Conky: drawing to double buffer
Conky: desktop window (60001a) is subwindow of root window (46)
Conky: window type - override
Conky: drawing to created window (0x1400001)
Conky: drawing to double buffer
Conky: desktop window (60001a) is subwindow of root window (46)
Conky: window type - override
Conky: drawing to created window (0x1800001)
Conky: drawing to double buffer
Conky: desktop window (60001a) is subwindow of root window (46)
Conky: window type - override
Conky: drawing to created window (0x1200001)
Conky: drawing to double buffer
@01micko
i think a static sleep variable might be the problem, but it's the fact that it causes a problem exactly after the widgets finish loading gives me a hunch it's the xevent not being friendly with jwm.
i could upload a screenshot of my desktop for those that want to know what it looks like.
- J-Bob
(Wow, feels like i might actually be helping with the bugfixing for a utility for 4.2. Well that's good.)
Edit: I should also mention, that i removed the wallpaper roxapp because removing it saves space, and i let rox manage right clicks on the desktop.
Last edited by J-Bob on Sun 21 Dec 2008, 17:14, edited 1 time in total.
[img]http://i114.photobucket.com/albums/n248/MedliSage/MAL/thing-4.png[/img]
It's been a long time.
It's been a long time.
I might as well upload the screenshot of my system.
Just in case anyone wonders, this IS what PupCore will look like.
- J-Bob
Just in case anyone wonders, this IS what PupCore will look like.
- J-Bob
- Attachments
-
- screenshot.png
- (170.48 KiB) Downloaded 657 times
J-Bob
You have a problem with your fonts. The calendar is not aligned. On about page 2 in this thread zigbert has addressed this.
You have a problem with your fonts. The calendar is not aligned. On about page 2 in this thread zigbert has addressed this.
Puppy Linux Blog - contact me for access
i tested it on my desktop WITH the wallpaper setting program. still the same program.
the problem i found out, is that the xevent clicks, but does not release, i noticed this when i tried it on rxvt.
if i knew how to manage xevents i would build a fix, but alas, i do not.
But at least i know what is the entire root of the problem. it's not the sleep, it's the xevent.
if we had it click, and release than it should be fixed.
the problem i found out, is that the xevent clicks, but does not release, i noticed this when i tried it on rxvt.
if i knew how to manage xevents i would build a fix, but alas, i do not.
But at least i know what is the entire root of the problem. it's not the sleep, it's the xevent.
if we had it click, and release than it should be fixed.
There isn't much documentation about xevent, seemed like a good idea at the time. I have noticed just tonight that my clock didn't wake, first time for that. Maybe try editing usr/sbin/fixwidgets by deleting the line refering to xevent and using my 'wakeclock.sh' script and see what happens, don't forget to re-edit fixwidgets.J-Bob wrote:i tested it on my desktop WITH the wallpaper setting program. still the same program.
the problem i found out, is that the xevent clicks, but does not release, i noticed this when i tried it on rxvt.
if i knew how to manage xevents i would build a fix, but alas, i do not.
But at least i know what is the entire root of the problem. it's not the sleep, it's the xevent.
if we had it click, and release than it should be fixed.
Hope that helps.
Merry Christmas.
Puppy Linux Blog - contact me for access
Replace your last four lines in usr/sbin/fixwidgets with thisJ-Bob wrote:i tested it on my desktop WITH the wallpaper setting program. still the same program.
the problem i found out, is that the xevent clicks, but does not release, i noticed this when i tried it on rxvt.
if i knew how to manage xevents i would build a fix, but alas, i do not.
But at least i know what is the entire root of the problem. it's not the sleep, it's the xevent.
if we had it click, and release than it should be fixed.
Code: Select all
sleep 3 #number of seconds before execution
xevent -a 0 0 #number of pixels for cursor to deviate right and down
sleep 1 ; xevent -b 1 2 #simulated left mouse click
sleep 1 ; xevent -a 512 384
Sincerely
Puppy Linux Blog - contact me for access
the results were interesting, it clicks at (0,0) but releases around the center of the screen.01micko wrote:Replace your last four lines in usr/sbin/fixwidgets with thisJ-Bob wrote:i tested it on my desktop WITH the wallpaper setting program. still the same program.
the problem i found out, is that the xevent clicks, but does not release, i noticed this when i tried it on rxvt.
if i knew how to manage xevents i would build a fix, but alas, i do not.
But at least i know what is the entire root of the problem. it's not the sleep, it's the xevent.
if we had it click, and release than it should be fixed.and then I will absolutely agree with you if it does not work.Code: Select all
sleep 3 #number of seconds before execution xevent -a 0 0 #number of pixels for cursor to deviate right and down sleep 1 ; xevent -b 1 2 #simulated left mouse click sleep 1 ; xevent -a 512 384
Sincerely
i think that you might have found the needed fix for this.
Glad i was able to help with checking for bugs.
- J-Bob