Quote:
Originally Posted by Morkl
I agree that the screensaver shouldn't be regenerated unnecessarily every time a book is launched; but what if the screensaver itself is updated to regenerate on startup when the book it was generated from last is not the latest read one? A slight delay shouldn't be a problem when the unit is going into standby, should it?
|
It is easier that that - standby picture is set (and it's generation is requested) by settings as the result of intent broadcast. It could keep last _id for which picture is generated and check if the id is different and only initiate generation if necessary. Then content manager and home page could both initiate screensaver update. Unfortunately it does not plug all the holes (and leaves the question of how many places book could be launched from - at least in content manager there are many). I will take a look at the code anyway...