Quote:
Originally Posted by knc1
If what you want to be notified about has a related event, then about all you will need to do is change the event name your waiting for.
Of course, you'll still have to remove any code not suitable for your purpose.
But the author of that thing knew his business, so it should be a good example.
All after you identify an event name from the logs.
You may not have a "Periodical update complete" event to wait for.
But if those periodicals get indexed, then you should see indexer event messages.
And there are 'job queues' in the system with related messages.
I would expect if the system checked and found something that needed to be downloaded, that 'job' would be entered into a queue.
I.E: If there isn't an exact message to wait for, there should be related messages that you could wait for.
= = = =
And while your at it -
Make a version that waits for: "OTA update available" and pops up a message panel, warning the user that their Kindle is about to update its firmware.
- - - -
The principles remain the same, only the names and actions change.
|
Hmmm...maybe better than a message that the Kindle is about to update the firmware would be a message saying that new firmware got downloaded to the Kindle. Would that be possible?
Shari