Thanks. Another point where the documentation could use some updating.
On Fri, Jan 14, 2011 at 9:36 AM, Dianne Hackborn wrote:
> No, that is not true. Launcher does not own the wallpaper. It uses
> Theme.Wallpaper to have itself displayed on top of the wallpaper -- that is,
> its own window ha
No, that is not true. Launcher does not own the wallpaper. It uses
Theme.Wallpaper to have itself displayed on top of the wallpaper -- that is,
its own window has translucency so you can see the wallpaper surface (owned
by the current wallpaper) behind it. During this time, it is allowed to
inte
Thanks for the clarification.
So the statement "Finally, applications can send arbitrary commands to the
live wallpaper." is just plain wrong in the documentation at:
http://developer.android.com/resources/articles/live-wallpapers.html
On Fri, Jan 14, 2011 at 5:38 AM, String wrote:
> I think you'
I think you're misunderstanding Dianne's posts.
When most people (including you, I think) talk about "the wallpaper", they
mean the one on the home screen. The app that's running that wallpaper is
the Launcher, and so the Launcher is the only app which can send commands to
"the wallpaper" as de
Hm, well there isn't enough information for me to help much more. All I can
say is that I know this works, for example it is how the launcher tells the
wallpaper you have dropped an icon which results in things like the nexus
wallpaper to react with its flying nexi from that point.
On Thu, Jan 13
It is showing. It's the active wallpaper.
I then launch my app, and select the menu item that sends the wallpaper
command. (Note that this checks to see that the active wallpaper IS the one
it's expecting.)
The log shows my app sending the command, but the wallpaper never receives
it.
On Thu, Ja
Yes you must be showing the wallpaper, such as by settings your theme to
Theme.Wallpaper.
On Thu, Jan 13, 2011 at 4:39 PM, John Lussmyer wrote:
> Hmm, question on that. By "sitting on top of the wallpaper", do you mean
> an app that leaves the wallpaper partially visible? (like the desktop)
>
>
Hmm, question on that. By "sitting on top of the wallpaper", do you mean an
app that leaves the wallpaper partially visible? (like the desktop)
On Thu, Jan 13, 2011 at 2:10 PM, John Lussmyer wrote:
> My app is the one the user is working with, and the command is sent during
> the onOptionsItemSe
My app is the one the user is working with, and the command is sent during
the onOptionsItemSelected() processing.
On Thu, Jan 13, 2011 at 12:26 PM, Dianne Hackborn wrote:
> You must be the current foreground activity sitting on top of the wallpaper
> to use the command.
>
--
You received this
You must be the current foreground activity sitting on top of the wallpaper
to use the command.
On Thu, Jan 13, 2011 at 7:56 AM, John Lussmyer wrote:
> I just noticed this method, and since I have a Live Wallpaper I've written,
> I decided it might be fun to use this.
>
> So in one of my apps, it
I just noticed this method, and since I have a Live Wallpaper I've written,
I decided it might be fun to use this.
So in one of my apps, it checks to see if my Live Wallpaper is the current
wallpaper, and sends a command if it is.
I get no errors in the log, but the wallpaper never receives the co
11 matches
Mail list logo
