[FR] Customizable Button Behavior (Enabled/Disabled) and Fullscreen Workflow Control

[adonboli]

I would like to request the ability to configure the behavior of the main “OK” button (button1) in the workflow, specifically to enable or disable when using Utility window mode instead of Fullscreen.

The primary goal of this feature is to allow users to continue working during the download or prep phases, while preventing them from dismissing the Utility Window and inadvertently forgetting that an update is occurring in the background.

This feature would function similarly to the reboot delay window, where the “OK” button is disabled ( "--button1disabled").

Additionally, it would be beneficial to enable downloads to occur in Utility Window mode (especially for users with slower internet connections who wish to keep working), and then automatically switch to full-screen mode during the “prepping the installer” stage, effectively preventing further work. To prevent a sudden change without warning, it might be helpful to provide users with a warning before transitioning to full-screen mode, with a customizable countdown (e.g., 60 seconds, adjustable by an admin).

Currently, we can either set the full workflow to FS or full workflow to Utility Window mode. Not specifying "--fs" or "--no-fs" seems to default to "no full screen" for the entire workflow.

While I understand that a reboot delay can be used to allow users to save their work, I believe that offering more granular control over button states for each stage in utility mode, as well as the ability to designate which stages should be full-screen or utility mode, would greatly enhance the overall customization experience.

[grahampugh]

I'm not going to implement the way to dismiss the Utility window. I believe the number of choices has reached exhaustion.

Regarding your second point:

To prevent a sudden change without warning, it might be helpful to provide users with a warning before transitioning to full-screen mode, with a customizable countdown (e.g., 60 seconds, adjustable by an admin).

If you use the --confirm option, the transition to full screen only happens once they confirm (of course, you are then giving them the option to prevent the workflow continuing).

Alternatively, use --rebootdelay XY (XY between 10-300) and it won't go to full screen at all. This is the best way to do with Apple Silicon devices, as the user can then continue to work during the prep phase.

Not specifying "--fs" or "--no-fs" seems to default to "no full screen" for the entire workflow.

Not true, the default is a utility window during the download phase and a full screen in the prep phase.