mirror of
https://github.com/pybricks/pybricks-code.git
synced 2026-09-12 09:36:27 +00:00
hub/sagas: don't stop user program after connect
Since we now have periodic status messages, we don't need to do anything to get into a known state. This caused unexpected behavior when connecting to a hub that is already connected in a second window.
This commit is contained in:
committed by
David Lechner
parent
337209744c
commit
02a0d974f3
@@ -14,7 +14,6 @@ import {
|
||||
takeEvery,
|
||||
} from 'typed-redux-saga/macro';
|
||||
import { alertsShowAlert } from '../alerts/actions';
|
||||
import { bleDidConnectPybricks } from '../ble/actions';
|
||||
import { didFailToWrite, didWrite, write } from '../ble-nordic-uart-service/actions';
|
||||
import { nordicUartSafeTxCharLength } from '../ble-nordic-uart-service/protocol';
|
||||
import {
|
||||
@@ -429,6 +428,4 @@ export default function* (): Generator {
|
||||
yield* takeEvery(downloadAndRun, handleDownloadAndRun);
|
||||
yield* takeEvery(hubStartRepl, handleHubStartRepl);
|
||||
yield* takeEvery(hubStopUserProgram, handleStopUserProgram);
|
||||
// calling stop right after connecting should get the hub into a known state
|
||||
yield* takeEvery(bleDidConnectPybricks, handleStopUserProgram);
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user