maemo.org - Talk - View Single Post - Flip clock pre pre pre pre release

jolouis	2009-03-26 , 12:49
Posts: 631 \| Thanked: 837 times \| Joined on May 2007 @ Milton, Ontario, Canada	#375

Thanks wax4213, that helps tremendously!! Two things:
1) lol no background image, of course! That would do it... as Ciro said before, sometimes we miss the most obvious things that are right infront of us. Okay, try updating the ci_init.py file, line's 264 - 280ish should now read:

Code:

userbg = ""
try:              
  config=ConfigParser.ConfigParser()
  config.read (userpath+"/.osso/hildon-desktop/home-background.conf")
  userbg = config.get("Hildon Home", "BackgroundImage")
  userbg = userbg.replace("file://", "")
  #replace spaces
  userbg = userbg.replace("%20", " ")
  us_bground=pygame.image.load(userbg).convert()   #Background user
except:
  if (len(userbg) > 0):
	if tablet==1:
		osso_c = osso.Context("osso_test_note", "0.0.1", False)
		note = osso.SystemNote(osso_c)
		result = note.system_note_dialog("Can't read the user wallpaper", type='notice') 
		print result

  #Use default background
  us_bground=pygame.image.load(path+"sosbg.png").convert()

That adds the check to see if the background is set to nothing, and it loads the default background if so (I'll add a bit of code to draw your default background colour, but for now should at least keep that annoying popup away!)

2) Aha! So it's a dbus crashing thing, that makes sense and lines up with the problems others have been having... Can you try a few little things for me?
A) Open ci_deviceMonitor.py, goto line 31, and change:

Code:

name = dbus.service.BusName(BME_REQ_IFC, bus=self.bus)

to read

Code:

self.name = dbus.service.BusName(BME_REQ_IFC, bus=self.bus)

Save it, try again and see if the problem still exists or not.

B) If problem still exists, please try opening up ci_dbus.py, line 73 reads:

Code:

		self.HelloSignal("Ok");

Try just adding the # to comment it out like this:

Code:

		#self.HelloSignal("Ok");

And again give it a shot, see if the problem is still there, and please let me know so that if one of the above does fix the problem I can roll it into an update!

LABAUDIO, one quick thought I just had... when you set an alarm, exit the app, and open it up again manually (i.e. before the alarm is triggered), if you go to the alarms page, does the alarm actually still show up there?? Did you remember to erase the old config file manually before installing the latest build (I mentioned before that the config file from Ciro's clock didn't work with the latest builds so you had to manually remove it).... the more I think about it, the more this sounds like exactly the cause of your problem...

Thanks!

Last edited by jolouis; 2009-03-26 at 12:56.

Quote & Reply |

The Following 2 Users Say Thank You to jolouis For This Useful Post:
LABAUDIO, timsamoff