Thanks. I'm looking into this.
At first glance, it appears that... whenever the app is not running...
this method will only tell the user that a local notification is waiting
to be viewed. It cannot display the actual message until the user
presses the "View" button, which then opens the app to display the
message. Do I understand this correctly?
Thanks.
Richard
On 7/14/2012 10:09 AM, Colin Holgate wrote:
Try local notifications. This is how you set up one notification:
mobileCreateLocalNotification alertBody, alertButtonMessage, alertPayload,
alertTime, playSound
alertTime is the Unix time that you want the alert to happen. See the help
entry for more details on the other things.
At the time that the notification happens, the user will see a message pop up
on their screen. If they touch the message it will open your app, and a message
is sent to you. Here's a handler for receiving that message:
on localNotificationReceived pMsg
answer "Local Notification:" && pMsg
end localNotificationReceived
The pMsg received is the same as the alertPayload sent in, and that can be as
complex as you like.
There isn't a way to have a notification happen that automatically opens your
app.
Working out the Unix time for the event is an entertaining little aspect to the
problem.
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
