-
Notifications
You must be signed in to change notification settings - Fork 96
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
Font size is too large for display, text cut off on ESP S3 Box 3 #331
Comments
We've made a change in Willow Application Server to sanitize the response from command endpoints: toverainc/willow-application-server@5f3fe38. If you run WAS with this change included, and enable WAS Command Endpoint in WAS > Configuration > Advanced, this should solve the issue in the video. |
We have just released WAS 0.2.0-rc.2 which includes the aforementioned change. Please test and close this issue if that solves the problem for you. Thanks! |
Howdy @stintel, Thanks for looking into this. Just tested out WAS 0.2.0-rc.2 with both current stable and 0.3.0-rc2 firmware and unfortunately it's no different - the font size is still quite large and scrolls off the screen (very laggy scrolling too?). I'm just rushing out but I'll take some photos tomorrow. |
Is the font, typeface size, background colour and basic text layout configurable by the user somewhere? In a perfect would I'd like to get rid of the 'welcome to willow' and 'i heard:' and simply have what it heard at the top in small text, then the response (without the word response:) across 2-4 lines |
We're an audio device first. We keep the UI very simple because we don't want to spend a lot of time on it. For the same reason, we don't support customizing it, and it's not planned either. |
Willow-Mistral.mp4
I went to change the font in the configuration but found that it's hard coded to use a binary file that doesn't seem to have any source / build config:
Ideally I'd like to make sure the font doesn't render outside the display, but also make it quite a bit smaller.
The text was updated successfully, but these errors were encountered: