Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After some timeout, return to Brief or Overview page #700

Closed
blammit opened this issue Jan 31, 2024 · 4 comments
Closed

After some timeout, return to Brief or Overview page #700

blammit opened this issue Jan 31, 2024 · 4 comments
Labels

Comments

@blammit
Copy link
Contributor

blammit commented Jan 31, 2024

After 10 minutes of inactivity, return to the Brief or Overview page, whichever one was viewed last. (As per Slack discussion)

Current proposal is to do this without adding a user option on whether this behavior should occur.

Implementation details:
gui-v2 can use the existing com.victronenergy.settings/Settings/Gui/DefaultOverview setting, as configured by gui-v1, to avoid adding a new setting. In this case, OverviewHub = Brief page, and OverviewTiles = Overview page. If the existing setting is used, then only use these two values, otherwise gui-v1 cannot use the setting.

@chriadam
Copy link
Contributor

Not for 1.0.0, marking as low_prio.

@kwindrem
Copy link
Collaborator

There are times when I'll leave something other than the overview screen active. For example, leaving a temps page up so I can quickly check temps during the night. So I'm opposed to automatically changing what's displayed.

gui-v1 puts the name of the qml object to go to in the default overview parameter so it can be anything you want it to be. Current behavior is to select the first overview page if the value in the parameter can't be found so this should be fine if gui-v2 puts some other string in that parameter.

@mr-manuel
Copy link
Collaborator

Is it possible to use this as startup screen after a reboot or after the wasm build is loaded? Right now every time the brief page is shown.

@blammit
Copy link
Contributor Author

blammit commented Sep 23, 2024

Have discussed an alternative solution that will obsolete this one: #1496

Closing.

@blammit blammit closed this as completed Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants