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

Feedback: Switch default view to 'embedded' #532

Closed
klauer opened this issue Jan 18, 2023 · 3 comments · Fixed by #595
Closed

Feedback: Switch default view to 'embedded' #532

klauer opened this issue Jan 18, 2023 · 3 comments · Fixed by #595
Labels
feedback Feedback for discussion good first issue

Comments

@klauer
Copy link
Contributor

klauer commented Jan 18, 2023

Expected Behavior

  • Feedback indicates that the default screens show too much information
  • Suggestion was that 'embedded' be the default

However, if we work on the existing templates to be more compact or space-efficient may result in a different desired default.

Current Behavior

Engineering screens are the default

Related to

#533

@tangkong
Copy link
Contributor

tangkong commented Sep 5, 2023

An alternate reading of this request is that users might want to individually specify their default template. Previously there was no place to store this, but maybe we can hijack the notes file to store this info.

I do think the original writing of this issue is likely addressed by #563.

@klauer
Copy link
Contributor Author

klauer commented Sep 5, 2023

If they are the primary users of the device, the custom screen can be stored in happi in the current implementation

@ZLLentz
Copy link
Member

ZLLentz commented Nov 14, 2023

There was a DM request today from Patrick to switch the default to embedded/vertical (so the row widgets display nicely) and/or introduce environment variables to set the defaults

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feedback Feedback for discussion good first issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants