Re: [android-developers] WallpaperManager.sendWallpaperCommand() doesn't work?

2011-01-14 Thread String
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 defined above.

Separate from this, it's also possible - though rare - for other apps to use 
wallpapers as their own background. If your app is doing this, then it can 
send commands to THAT wallpaper.

In no circumstance, AFAIK, can an app which isn't the Launcher (or a 
replacement) send commands to the wallpaper running on the device's home 
screen. The documentation is not at all clear on this, but I've been down 
this road in the past. If you want to ping your own wallpaper (running on 
the home screen) from your app, one method which does work is to fire off a 
custom intent, and listen for that intent in your WallpaperService.

String


-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] WallpaperManager.sendWallpaperCommand() doesn't work?

2011-01-14 Thread John Lussmyer
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 sterling.ud...@googlemail.comwrote:

 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 defined above.

 Separate from this, it's also possible - though rare - for other apps to
 use wallpapers as their own background. If your app is doing this, then it
 can send commands to THAT wallpaper.

 In no circumstance, AFAIK, can an app which isn't the Launcher (or a
 replacement) send commands to the wallpaper running on the device's home
 screen. The documentation is not at all clear on this, but I've been down
 this road in the past. If you want to ping your own wallpaper (running on
 the home screen) from your app, one method which does work is to fire off a
 custom intent, and listen for that intent in your WallpaperService.




-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] WallpaperManager.sendWallpaperCommand() doesn't work?

2011-01-14 Thread Dianne Hackborn
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
interact with the wallpaper (change its offset, send commands, etc) only
because it is currently the app on top of the wallpaper.

If your own app is running on top of the wallpaper in the same way, then you
too can interact with it.  If not, you can't.  If this wasn't the cause, no
launcher replacements would be able to interact with the wallpaper either.

On Fri, Jan 14, 2011 at 5:38 AM, String sterling.ud...@googlemail.comwrote:

 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 defined above.

 Separate from this, it's also possible - though rare - for other apps to
 use wallpapers as their own background. If your app is doing this, then it
 can send commands to THAT wallpaper.

 In no circumstance, AFAIK, can an app which isn't the Launcher (or a
 replacement) send commands to the wallpaper running on the device's home
 screen. The documentation is not at all clear on this, but I've been down
 this road in the past. If you want to ping your own wallpaper (running on
 the home screen) from your app, one method which does work is to fire off a
 custom intent, and listen for that intent in your WallpaperService.

 String


  --
 You received this message because you are subscribed to the Google
 Groups Android Developers group.
 To post to this group, send email to android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en




-- 
Dianne Hackborn
Android framework engineer
hack...@android.com

Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails.  All such
questions should be posted on public forums, where I and others can see and
answer them.

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] WallpaperManager.sendWallpaperCommand() doesn't work?

2011-01-14 Thread John Lussmyer
Thanks.  Another point where the documentation could use some updating.

On Fri, Jan 14, 2011 at 9:36 AM, Dianne Hackborn hack...@android.comwrote:

 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
 interact with the wallpaper (change its offset, send commands, etc) only
 because it is currently the app on top of the wallpaper.

 If your own app is running on top of the wallpaper in the same way, then
 you too can interact with it.  If not, you can't.  If this wasn't the cause,
 no launcher replacements would be able to interact with the wallpaper
 either.


-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] WallpaperManager.sendWallpaperCommand() doesn't work?

2011-01-13 Thread John Lussmyer
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 command.
(There are logging statements in the onCommand() handler.)

Is there some permission or other settings I have to enable to get this to
work?

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] WallpaperManager.sendWallpaperCommand() doesn't work?

2011-01-13 Thread Dianne Hackborn
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 johnlussm...@gmail.comwrote:

 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 command.
 (There are logging statements in the onCommand() handler.)

 Is there some permission or other settings I have to enable to get this to
 work?

  --
 You received this message because you are subscribed to the Google
 Groups Android Developers group.
 To post to this group, send email to android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en




-- 
Dianne Hackborn
Android framework engineer
hack...@android.com

Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails.  All such
questions should be posted on public forums, where I and others can see and
answer them.

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] WallpaperManager.sendWallpaperCommand() doesn't work?

2011-01-13 Thread John Lussmyer
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 hack...@android.comwrote:

 You must be the current foreground activity sitting on top of the wallpaper
 to use the command.


-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] WallpaperManager.sendWallpaperCommand() doesn't work?

2011-01-13 Thread John Lussmyer
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 johnlussm...@gmail.comwrote:

 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 hack...@android.comwrote:

 You must be the current foreground activity sitting on top of the
 wallpaper to use the command.




-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] WallpaperManager.sendWallpaperCommand() doesn't work?

2011-01-13 Thread Dianne Hackborn
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 johnlussm...@gmail.comwrote:

 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 johnlussm...@gmail.comwrote:

 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 hack...@android.comwrote:

 You must be the current foreground activity sitting on top of the
 wallpaper to use the command.



  --
 You received this message because you are subscribed to the Google
 Groups Android Developers group.
 To post to this group, send email to android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en




-- 
Dianne Hackborn
Android framework engineer
hack...@android.com

Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails.  All such
questions should be posted on public forums, where I and others can see and
answer them.

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] WallpaperManager.sendWallpaperCommand() doesn't work?

2011-01-13 Thread John Lussmyer
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, Jan 13, 2011 at 4:55 PM, Dianne Hackborn hack...@android.comwrote:

 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 johnlussm...@gmail.comwrote:

 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 johnlussm...@gmail.comwrote:

 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 
 hack...@android.comwrote:

 You must be the current foreground activity sitting on top of the
 wallpaper to use the command.



  --
 You received this message because you are subscribed to the Google
 Groups Android Developers group.
 To post to this group, send email to android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en




 --
 Dianne Hackborn
 Android framework engineer
 hack...@android.com

 Note: please don't send private questions to me, as I don't have time to
 provide private support, and so won't reply to such e-mails.  All such
 questions should be posted on public forums, where I and others can see and
 answer them.

  --
 You received this message because you are subscribed to the Google
 Groups Android Developers group.
 To post to this group, send email to android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en


-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] WallpaperManager.sendWallpaperCommand() doesn't work?

2011-01-13 Thread Dianne Hackborn
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, 2011 at 5:37 PM, John Lussmyer johnlussm...@gmail.comwrote:

 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, Jan 13, 2011 at 4:55 PM, Dianne Hackborn hack...@android.comwrote:

 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 johnlussm...@gmail.comwrote:

 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 
 johnlussm...@gmail.comwrote:

 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 
 hack...@android.comwrote:

 You must be the current foreground activity sitting on top of the
 wallpaper to use the command.



  --
 You received this message because you are subscribed to the Google
 Groups Android Developers group.
 To post to this group, send email to android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en




 --
 Dianne Hackborn
 Android framework engineer
 hack...@android.com

 Note: please don't send private questions to me, as I don't have time to
 provide private support, and so won't reply to such e-mails.  All such
 questions should be posted on public forums, where I and others can see and
 answer them.

  --
 You received this message because you are subscribed to the Google
 Groups Android Developers group.
 To post to this group, send email to android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en


  --
 You received this message because you are subscribed to the Google
 Groups Android Developers group.
 To post to this group, send email to android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en




-- 
Dianne Hackborn
Android framework engineer
hack...@android.com

Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails.  All such
questions should be posted on public forums, where I and others can see and
answer them.

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en