Hi, Loïc, Thanks for the information. I verified the gconf key change again this afternoon, and gconf key does have persistence. And even removing cached theme ~/.gtkrc-2.0, new selected theme could be applied when system is rebooted.
So it is not necessary to monitor gconf key changes in hildon-desktop, I will update the patch and send it out later. I am almost done working out theme update support, with another bug #225238 fixed. Hope new patch could be sent out soon. :-) Regards, Horace -----Original Message----- From: Loïc Minier [mailto:[EMAIL PROTECTED] Sent: 2008年5月21日 15:45 To: Li, Horace Cc: Bill Filler; Kyle Nitzsche; Spencer, Bob; Guo, Young; Whalen, Mauri; Xie, May; [EMAIL PROTECTED]; [email protected] Subject: Re: Marquee panel supports theme update at runtime On Mon, May 19, 2008, Li, Horace wrote: > Hildon-desktop theme update at runtime is working fine without > listening to gconf key changes. Hildon-desktop only listens to gconf > key change to update the cached-theme, which is ~/.gtkrc-2.0. The main > purpose to update the cache is while updating theme of hildon-desktop > at runtime is working fine, it will not keep the change, and fall back > to Default theme setting everytime when X is restarted or system is > rebooted. With cached-theme updated, new theme setting could be saved > and re-applied. You're saying that if you change the gconf key, everything works but there's no persistence. However gconf is supposed to have persistence: gconfd should write in ~/.gconf and save your settings there. So what's not working here? What if you remove the ~/.gtkrc-2.0 completely? Do you see that the theme is saved in the ~/.gconf properly? -- Loïc Minier -- Ubuntu-mobile mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile
