2 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• pleasereset commented  ·  December 6, 2011 6:33 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Yes I definitively want to do that too : defining a callback executed when a (toast/tile/raw notification) is received by the app, this way I could prepare data, or update the tile in a more complex way than what is feasible now !

• Hades32 commented  ·  July 11, 2011 10:55 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Raw Notifications are quite useless at the moment, as the app has to be running.
  And e.g. Toast Notifications are stupid because you can't get (much) data to the actual app. So after clicking your toast, the app still has to refresh your data.

  I want:
  A background task which is invoked when a raw notification arrives. This task could then process the data, save it locally, and (maybe based on some conditions) display a toast notification.
  That way everything would work much faster and more convenient.