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.

Sign up for GitHub

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

Jump to bottom

Bluetooth connection state messes up apps #102

Closed
gfwilliams opened this issue Feb 14, 2020 · 4 comments
Closed

Bluetooth connection state messes up apps #102

gfwilliams opened this issue Feb 14, 2020 · 4 comments

Comments

@gfwilliams
Copy link
Member

The console was moved permanently onto Bluetooth, but I moved it back to 'auto' (so it goes to the screen if BT is disconnected) recently as it seemed good for debugging (so any errors get shown to the user).

But this means that BT connection state scrolls the screen and messes stuff up.

So we could:

  • Add a 'debug' option that, when false (default) moves the console to Bluetooth. When true you get the scrolling, but as you're developing you put up with it :)
  • Add an option to Espruino to disable the Connection State messages
  • Change apps/widgets to clear their backgrounds all the time, so scrolling was less of a big deal
  • Leave the console on Bluetooth permanently - but then you don't see app erros
@gfwilliams gfwilliams mentioned this issue Feb 24, 2020
Closed
@conoro
Copy link
Contributor

conoro commented Feb 24, 2020

That connection state message is so annoying when you are not in dev mode. Ditto any console type errors/messages. We've held off from sending watches to a few of our new employees as the immediate GPS error message on the watchface just makes it look like it's broken.

So I'd be a fan of option 1. When I'm not in dev mode, I never want to see any messages on the watch screen, including JS errors etc.

@gfwilliams
Copy link
Member Author

Thanks - option 1 is an easy fix at least, but it does make it more likely that apps will get included that have errors in them :)

@conoro
Copy link
Contributor

conoro commented Feb 24, 2020

Yeah true! We just need a CI/CD pipeline on the emulator and machine vision to interpret the error messages ;-)

@gfwilliams
Copy link
Member Author

Fixed with 9a76d6d

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@conoro @gfwilliams