craft-update: say that the drop starts the helper only when the app drops the Updater

This commit is contained in:
dotCooCoo committed 2026-11-07 17:11:33 -08:00
1 parent da46f3ca20
commit cbd9abfdc3
1 file changed
+3 -3
+3 -3
View File
@@ -44,9 +44,9 @@ pub enum Action {
OpenUrl(String),
/// Close the app through its normal close path (which asks about unsaved work): the update is
/// installed and a helper restarts the app once it has exited. On Windows the helper, which
/// installs the update, starts when this is returned. When the app exits another way (the
/// window's close button, a quit with unsaved work, an OS shutdown), dropping the [`Updater`]
/// starts it. An app that ends the process in `on_exit` without dropping the `Updater` calls
/// installs the update, starts when this is returned. When the app exits another way, such as
/// the window's close button or a quit with unsaved work, and drops the [`Updater`] as it exits,
/// the drop starts it. An app that ends the process in `on_exit` without dropping the `Updater` calls
/// [`Updater::start_pending_update`] there first.
Close,
}