Here's a basic rundown of the sequence we'd like to present to our users:
1. The app silently checks for updates at startup only2. If updates aren't available, the app proceeds as normal3. If updates ARE available, a small modal dialog appears stating so4. If the user chooses not to install updates, the app exits (e.g. all updates are required)5. If the user chooses to install updates, a download progress bar displays (maybe not necessary for small updates)6. The downloaded updates are installed--without requiring user intervention--and the app restarts as normal
(Our business rules are a bit different; we'll be requiring updates.)
Can most if not all of this be accomplished without heavy customization of the AutomaticUpdater source? Are there various property settings that can accomodate this approach?
Thanks,Jeff Bowman
After some review of the documentation, it seems I'll be better able to accomplish all of this by foregoing the use of AutomaticUpdater altogether and just using wyUpdate. We may not get the download progress bar (yet to be determined), but we can live without that if we have to.
Would you agree?
Thanks,Jeff Bowman
Since what you're trying to do is almost completely synchronous, then yes, wyUpdate is a better choice. The AutomaticUpdater is used best when you let it do work in the background and, by extension, let the user update at their leisure.
OK, I'll work in that direction.
Thanks,Jeff Bowman
