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
Currently, when right-clicking the tray icon and hovering over Pause idleness checks, it displays four options:
30 minutes
1 hour
2 hours
3 hours
4 hours
This may be fine for basic usage, the the user really should have the ability to customize these. Perhaps on the "Idle" menu, those four options are displayed, and are editable by the user.
A start to this feature may include adding configuration settings for these options, and using those defaults instead of hardcoded values. The user could then change those values manually via the config file.
A next step may be the UI actually configuring those options. Careful thought needs to be put into how many options we actually want to support (or if we want to limit them at all).
Also, there needs to be additional information somewhere for when that timer actually expires. If a value is selected, it should not still show those four checkboxes. Instead, it should show the (localized) time idleness checks resume, and the opportunity to cancel and set a new one.
A bonus feature for this may be adding support for manually specifying a time. Instead of clicking a checkbox, there would be one last option with e.g. Manual, which would pop up a simple dialog box asking for the time it should stop (with the current time as a placeholder).
The text was updated successfully, but these errors were encountered:
Currently, when right-clicking the tray icon and hovering over
Pause idleness checks
, it displays four options:This may be fine for basic usage, the the user really should have the ability to customize these. Perhaps on the "Idle" menu, those four options are displayed, and are editable by the user.
A start to this feature may include adding configuration settings for these options, and using those defaults instead of hardcoded values. The user could then change those values manually via the config file.
A next step may be the UI actually configuring those options. Careful thought needs to be put into how many options we actually want to support (or if we want to limit them at all).
Also, there needs to be additional information somewhere for when that timer actually expires. If a value is selected, it should not still show those four checkboxes. Instead, it should show the (localized) time idleness checks resume, and the opportunity to cancel and set a new one.
A bonus feature for this may be adding support for manually specifying a time. Instead of clicking a checkbox, there would be one last option with e.g.
Manual
, which would pop up a simple dialog box asking for the time it should stop (with the current time as a placeholder).The text was updated successfully, but these errors were encountered: