I think I found the problem. You can test the fix in version 0.5.5 which should be available in the PPA in next 24h.
It was probably caused by global dict object which was not copied when assigned to a local variable and because of that local variable modified accidentally the global object. I think this caused the bug to appear only when you run Freemeteo for interval of full week or so. And about threading. I implemented threading again. We had it before, but it was causing problems, so we removed it. I think you have to implement threading in a special class to avoid problems. I have tried that in other screenlets and it seems to work fine. So if there appear problems now, they are probably because of the threading code I implemented. I hope it works though. -- You received this bug notification because you are a member of Individual Screenlets Developers, which is subscribed to Individual Screenlets. https://bugs.launchpad.net/bugs/791874 Title: freemeteo loses day information Status in Screenlets — individual widgets development: Fix Committed Bug description: As time goes by (days) all the days become listed as Today. The only way I have found to get the day to display correctly again is to reboot the system (As the system is on 24/7 this hardly ever happens) or to kill the process then restart it. Using Screenlets manager to stop the screenlet does nothing, restarting all autostart screenlets restarts other ones but not freemeteo though freemeteo does bring up another instance and asks for a zip code. In fact the none configured freemeteo appears on every startup alongside the configured one, deleting the empty config file does not prevent it reappearing on the next restart. To manage notifications about this bug go to: https://bugs.launchpad.net/indiv-screenlets/+bug/791874/+subscriptions -- Mailing list: https://launchpad.net/~indiv-screenlets-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~indiv-screenlets-dev More help : https://help.launchpad.net/ListHelp
