maemo.org - Talk - [hildon-home] Icons Become Unclickable

maemo.org - Talk (https://talk.maemo.org/index.php)

- Applications (https://talk.maemo.org/forumdisplay.php?f=41)

- - [hildon-home] Icons Become Unclickable (https://talk.maemo.org/showthread.php?t=50801)

Re: Desktop Icons Become Unclickable

Re: [hildon-home] Icons Become Unclickable

Ok, I removed the all of DECW widgets and now it's looks better. I tried to use the Queen BeeCon Widget, it's like DECW, and my problem returned... I get freeze of desktops after 3-4 calls... I also removed the Queen BeeCon Widget and now again looks ok.
I think, maybe the problem not only in the DECW or Queen BeeCon Widget, maybe we have a little conflict with one or more another widgets... :confused: Something like DECW + FMXT or other...
I like the DECW, but I cant using this... :mad:

Re: [hildon-home] Icons Become Unclickable

scripts with rootsh and desktop widget from queen beecon messed my cell up all of the time

Re: [hildon-home] Icons Become Unclickable

I'm still using the widgets I listed earlier and I haven't had a freeze in ages.

Re: [hildon-home] Icons Become Unclickable

Quote:

Originally Posted by GameboyRMH (Post 635665)

I'm still using the widgets I listed earlier and I haven't had a freeze in ages.

Which the other widgets you are use ?

Re: [hildon-home] Icons Become Unclickable

Quote:

Originally Posted by Schturman (Post 636623)

Which the other widgets you are use ?

Media widget
OMWeather
IP Address
Calendar

Re: [hildon-home] Icons Become Unclickable

Quote:

Originally Posted by GameboyRMH (Post 636637)

Media widget
OMWeather
IP Address
Calendar

If your widgets not conflicting with DECW, Now is the question, which from them is conflicting with DECW and Queen BeeCon Widget :confused:

* bluezwitch
* recaller
* sleeper
* conversation
* simple note
* FM transmitter
* Personal photo
* Personal data plane
* Touch Search

Re: [hildon-home] Icons Become Unclickable

Quote:

Originally Posted by Schturman (Post 636916)

Hi, could you please post a backup of all your Queen Beecon Widget Instances as per this procedure: Export/Save/Backup Procedure for Beecon Instance Data

Maybe it's just a matter of run scripts, commands or update policies.

Re: [hildon-home] Icons Become Unclickable

Quote:

Originally Posted by No!No!No!Yes! (Post 639156)

Hi.
Here is backup of 3 widgets from Queen Beecon Widget:

Code:

Uptime: 



[queen-beecon-header] 

version=1.000000  

checksum=876790 

[queen-beecon-exported-instance] 

widgetType=1  

operationalStatus=0 

hideCanvas=true 

snippetBgRGB=0  

beecon_lt0_ImgZoom=0 

beecon_lt0_BgRGB=2  

beecon_lt0_ImgFilename=queen-beecon-syserr.png 

beecon_eq0_ImgZoom=0  

beecon_eq0_BgRGB=3 

beecon_eq0_ImgFilename=queen-beecon-appok.png  

beecon_eq1_ImgZoom=0 

beecon_eq1_BgRGB=4  

beecon_eq1_ImgFilename=queen-beecon-appwrn.png 

beecon_ge2_ImgZoom=0  

beecon_ge2_BgRGB=5 

beecon_ge2_ImgFilename=queen-beecon-apperr.png  

beecon_idxge2_ImgZoom=0 

beecon_idxge2_BgRGB=11  

beecon_idxge2_ImgFilename=queen-beecon-index.png 

widWidth=270  

widHeight=34 

instanceTitle=Uptime: 

instanceCmd=uptime|cut -d" "  -f4-|sed 's/\\, *load.*//' 

cmdImgFilename= 

cmdImgZoom=0 

cmdFgRGB=1  

cmdVisibilityPosition=4 

cmdImgVisibilityPosition=5 

cmdJustify=0  

cmdFontName=3 

cmdFontSize=16 

resImgFilename= 

resImgZoom=0  

resFgRGB=1 

resVisibilityPosition=6 

resImgVisibilityPosition=9  

resJustify=0 

resFontName=3 

resFontSize=16 

updOnStartup=true  

updOnClick=true 

updOnDesktop=true 

delayIndex=0 

updNeworkPolicy=0  



------------------------------------- 



FreeRootFS:  



[queen-beecon-header] 

version=1.000000 

checksum=880524  

[queen-beecon-exported-instance] 

widgetType=1 

operationalStatus=0  

hideCanvas=true 

snippetBgRGB=0 

beecon_lt0_ImgZoom=0  

beecon_lt0_BgRGB=2 

beecon_lt0_ImgFilename=queen-beecon-syserr.png  

beecon_eq0_ImgZoom=0 

beecon_eq0_BgRGB=3  

beecon_eq0_ImgFilename=queen-beecon-appok.png 

beecon_eq1_ImgZoom=0  

beecon_eq1_BgRGB=4 

beecon_eq1_ImgFilename=queen-beecon-appwrn.png  

beecon_ge2_ImgZoom=0 

beecon_ge2_BgRGB=5  

beecon_ge2_ImgFilename=queen-beecon-apperr.png 

beecon_idxge2_ImgZoom=0  

beecon_idxge2_BgRGB=11 

beecon_idxge2_ImgFilename=queen-beecon-index.png  

widWidth=270 

widHeight=36 

instanceTitle=Free Rootfs:  

instanceCmd=df -h | awk ' $1 == "rootfs" {print $4"B"}' 

cmdImgFilename=  

cmdImgZoom=0 

cmdFgRGB=1 

cmdVisibilityPosition=4  

cmdImgVisibilityPosition=5 

cmdJustify=0 

cmdFontName=3  

cmdFontSize=16 

resImgFilename= 

resImgZoom=0 

resFgRGB=1  

resVisibilityPosition=6 

resImgVisibilityPosition=9 

resJustify=0  

resFontName=3 

resFontSize=16 

updOnStartup=true 

updOnClick=true  

updOnDesktop=true 

delayIndex=0 

updNeworkPolicy=0  



------------------------------------------- 



Date:  



[queen-beecon-header] 

version=1.000000 

checksum=826234  

[queen-beecon-exported-instance] 

widgetType=1 

operationalStatus=0  

hideCanvas=true 

snippetBgRGB=0 

beecon_lt0_ImgZoom=0  

beecon_lt0_BgRGB=2 

beecon_lt0_ImgFilename=queen-beecon-syserr.png  

beecon_eq0_ImgZoom=0 

beecon_eq0_BgRGB=3  

beecon_eq0_ImgFilename=queen-beecon-appok.png 

beecon_eq1_ImgZoom=0  

beecon_eq1_BgRGB=4 

beecon_eq1_ImgFilename=queen-beecon-appwrn.png  

beecon_ge2_ImgZoom=0 

beecon_ge2_BgRGB=5  

beecon_ge2_ImgFilename=queen-beecon-apperr.png 

beecon_idxge2_ImgZoom=0  

beecon_idxge2_BgRGB=11 

beecon_idxge2_ImgFilename=queen-beecon-index.png  

widWidth=270 

widHeight=36 

instanceTitle=Date: 

instanceCmd=date  '+%A %e %B %Y' 

cmdImgFilename= 

cmdImgZoom=0 

cmdFgRGB=1  

cmdVisibilityPosition=4 

cmdImgVisibilityPosition=5 

cmdJustify=0  

cmdFontName=3 

cmdFontSize=16 

resImgFilename= 

resImgZoom=0  

resFgRGB=1 

resVisibilityPosition=6 

resImgVisibilityPosition=9  

resJustify=0 

resFontName=3 

resFontSize=16 

updOnStartup=true  

updOnClick=true 

updOnDesktop=true 

delayIndex=0 

updNeworkPolicy=0  



---------------------------------------

Re: [hildon-home] Icons Become Unclickable

It would seem that this a common unwelcoming effect! I've found a temp fix (as mention in this thread) which can by done powering on and then off (or rebooting some how).