Skip to content

Conversation

MatzElectronics
Copy link
Collaborator

These changes are safe to implement at any point after solo/200 is fully implemented. There are flags in the browser and a try/catch set up to allow "No port" messages to be received whether they are encoded or not.

No need to transmit "No Device", but it is helpful to denote the device that was unable to connect.
Adds flag to let the browser know that it is safe to base64 encode those transmissions
@MatzElectronics
Copy link
Collaborator Author

To test:

Don't connect a device, and open the terminal using the button on the top bar.
Make sure a message appears stating that there are no connected devices
Type into the terminal, make sure characters echo (terminal is simulated)

Then, connect a device
Create a program that parrots user input. Make sure comms work correctly both ways.

@MatzElectronics
Copy link
Collaborator Author

Again, just to reiterate - don't release this fix until solo/200 is fully implemented.

@PropGit
Copy link
Contributor

PropGit commented Jan 16, 2020

Thanks @MatzElectronics - I'll check it out and will wait until Solo/200 is deployed.

@zfi
Copy link
Contributor

zfi commented Jan 27, 2020

Addresses an error identified in parallaxinc/solo#200

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants