-
Notifications
You must be signed in to change notification settings - Fork 1
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
Handle radio connect/ reconnect error scenarios #281
Conversation
This mimics the existing behaviour and also means that the radio remote micro:bit does not need to be flashed in order to find the device id so that step can be skipped in development mode
Preview build will be at |
Aligning with existing reconnecting design
...(stage === "local" | ||
? { | ||
linkTextId: "connectMB.connectCable.skip", | ||
onLink: LinkType.Skip, | ||
} | ||
: { | ||
onLink: LinkType.None, | ||
}), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For radio connection dev purposes, when locally developing, a skip button is visible for micro:bit 1 and the device Id is stored in the local storage.
@@ -44,7 +44,7 @@ const AddDataPage = () => { | |||
|
|||
const noStoredData = useMemo<boolean>(() => { | |||
const gestureData = gestures.data; | |||
return ( | |||
return !( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small fix in logic in Add Data page so that data can be visible without connecting
@@ -22,13 +22,20 @@ const StartResumeActions = ({ ...props }: Partial<StackProps>) => { | |||
}, [navigate]); | |||
|
|||
const handleStartNewSession = useCallback(() => { | |||
startOverWarningDialogDisclosure.onClose(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small fix: Close start over session warning dialog when new session is selected
If you reset the bridge micro:bit, we await the connection timeout, then show a dialog saying that the connection to micro:bit 1 has been lost, which isn't right. In the nextgen/prototype version, the reconnection attempt succeeds. |
Clicking "disconnect" now causes the following error EDIT: The It is not clear if this is version or device specific. EDIT: This has been resolved by adding software reset to the serial state change queue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've skimmed through the code changes so far. I've hit a snag with the disconnect button with the radio bridge noted in a separate comment and can't review all of the potential flows until this has been ammended.
…plicitly or automatically
|
Related PR: microbit-foundation/microbit-connection#25 |
Code changes look good. Will test tomorrow morning. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. All previous change requests have been resolved.
Task: https://microbit-global.monday.com/boards/1125389526/pulses/1575488964
Expected behaviour: Error connection cases logic https://paper.dropbox.com/doc/Reconnect-scenarios-copy--CTKwX5AyHNMod6Uq0Qosp8ZtAg-RWeX90ac5YQ9erncFZmWN can be used as reference
EDITED
Also implemented bluetooth connection fail dialog since there were conflicting changes
https://microbit-global.monday.com/boards/1125389526/pulses/1576736316
Other minor changes