You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Background:
Because elevated permissions are needed there was pop-up to let the user know that install was about to start so that the elevated permission question was not seen as suspicious. This was in the state machine module. The UI pop-up was decoupled and placed into the main start-up code of all of kmshell. This is working well for most scenarios there is still cases where the state machine will just advance through all states and start installing and the user first nows about it via kmshell permissions popup. The proposal for now is to always have go from downloading to waitingrestart state unless the apply now flag is set.
Example
Keyman has not run. Keyman Configuration is opened, background update kicks off and finds a download, downloads it checks if keyman as run, it hasn't so it starts the install without notifying the user. With the proposed solution it would go to WaitingRestart. So the next time kmshell is run for configuration, keyman etc the install pop-up can request permssion from the user.
In stage 2 we can improve this.
The text was updated successfully, but these errors were encountered:
rc-swag
changed the title
feat(windows): Always go from downloading to waitingrestart online updates
feat(windows): Always go from downloading to waitingrestart - online updates
Feb 7, 2025
rc-swag
changed the title
feat(windows): Always go from downloading to waitingrestart - online updates
feat(windows): condition to go from downloading to waitingrestart changed for keyman update state machine \
Feb 7, 2025
rc-swag
changed the title
feat(windows): condition to go from downloading to waitingrestart changed for keyman update state machine \
feat(windows): condition to go from downloading to waitingrestart changed for keyman update state machine
Feb 7, 2025
Background:
Because elevated permissions are needed there was pop-up to let the user know that install was about to start so that the elevated permission question was not seen as suspicious. This was in the state machine module. The UI pop-up was decoupled and placed into the main start-up code of all of kmshell. This is working well for most scenarios there is still cases where the state machine will just advance through all states and start installing and the user first nows about it via kmshell permissions popup. The proposal for now is to always have go from downloading to waitingrestart state unless the apply now flag is set.
Example
Keyman has not run. Keyman Configuration is opened, background update kicks off and finds a download, downloads it checks if keyman as run, it hasn't so it starts the install without notifying the user. With the proposed solution it would go to WaitingRestart. So the next time kmshell is run for configuration, keyman etc the install pop-up can request permssion from the user.
In stage 2 we can improve this.
The text was updated successfully, but these errors were encountered: