Currently using a Toggle to perform an action in the GUI has a process go from State A to State B OR from State B back to State A.

However, the current visual toggle state appears to move to the next state before the next state is actually reached in the wallet's internals.
.
The wallet's state might be displayed as active/inactive when it actually is not what is displayed.

For this reason, there should be an intermediate state or pop-up that explains the user's action is being processed (Enabling...) (Disabling...) and the toggle should not move until the end state is actually reached by the wallet's internals.

Current Implemenation:

1.(May or May not actually be ENABLED)

2. (May or May not actually be DISABLED)
   

Possible/Proposed Implementation:

1.(Guaranteed to be ENABLED)

2a. Currently in the process of disabling and the GUI shows that the wallet is still precomputing

2b. Currently in the process of disabling and the GUI shows that the wallet is still precomputing

3. (Guaranteed to be DISABLED)
   

Whether or not this is the best way to show the user that their toggle click is being processed is not my place to decide. Maybe disabling the sliding indicator by greying it out will be a better way of showing an action is being performed and the toggle can't be clicked until the current toggle action is completed. Maybe a pop-up and graying out of the toggle switch is the best approach. It is a little tricky because normally toggle switches are immediate response, but if someone else has experience with best way to convey state to the user through toggles with long running processes then that can be an option as well.

However, the current user experience should be better in line with what was described at the start of this Feature Request: Toggle State should be absolutely correct. Users shouldn't be required to go to the console to determine the state of their wallet's staking/precomputing/etc.