Just realized that your link points to the i386 package. Don't know if it's relevant but if the votes are counted separately it would be more useful counting for the armel version: http://maemo.org/packages/package_in...on-pack-2/1.2/
Ah, sorry, my fault. Don't know if it makes a difference so I voted for armel too.
black plastic theme - wont alter from browny (coffee) bg
marina theme - works as its meant to....
Don't have a glue how maenotify works. Maybe it caches the images from each theme somehow and it won't change the image if it's changed after first launch of maenotify. Just guessing.
No no no, sorry, I'm not good at explaining complicated things in english
You're welcome, I'm not that good in english too
Originally Posted by
Each theme has these backgrounds (separate images):
- desktop wallpapers (there's four of these)
- wallpaper for clock
- wallpaper for lockscreen
- wallpaper for application manager
With Pleego I have used the same "Meego people" background for all of those, but they still are all separate images and chaning one won't change the others. If you change the homescreen wallpaper, it won't change images for the rest of the things mentioned earler.
OK, now I understand.
Originally Posted by
If you wan't to change those backgrounds, you need to manually overwrite these images with your own:
/opt/plastic-schemes/SCHEMENAME/backgrounds/clock.png
/opt/plastic-schemes/SCHEMENAME/backgrounds/lockslider.png
/opt/plastic-schemes/SCHEMENAME/backgrounds/applicationmanager.png
And then run the setup again.
That would get overwritten with next update, right? So it's seems not to be the best possible solution. How about adding a file dialog for the user to enable him to select these images manually? You could add some kind of "special settings" page to not overload the standard settings page.
Originally Posted by
About that lockscreen -issue. You have rebooted after changing scheme have you?
Of course, many times. But I remember maenotify doing some crude things to the background image. Not easy to understand when and why it updates the basic image it operates on.
That would get overwritten with next update, right? So it's seems not to be the best possible solution. How about adding a file dialog for the user to enable him to select these images manually? You could add some kind of "special settings" page to not overload the standard settings page.
Yeah, update would overwrite those.
But I notified the developer of fapman to change the background-behaviour so it would take the actual desktop-image instead of theme's image. Maybe he will change that in future update
And about that file-dialog to use own images; it's doable quite easily, but then again the user's image should be in right format (png) and sized properly already to be fully functional. I have no idea what would happen if user tries to set image which has wrong dimensions etc. So propably I'll leave the "heavy" customizing for power users who will do it manually.
Of course, many times. But I remember maenotify doing some crude things to the background image. Not easy to understand when and why it updates the basic image it operates on.
Yeah, propably the maenotify does some caching it's own, dunno. But what do you need the maenotify for with PR1.2? I though maenotify only adds notifications to lockscreen which now comes with PR1.2 automaticly? Or does it do something else usefull also?
