-
Notifications
You must be signed in to change notification settings - Fork 5
Description
Describe the bug
Not really a bug, but a potential user experience (UX) improvement.
To Reproduce
- Write NQC code
- Press the "Build" button
- Press the "Download program to RCX" button
- Play around with user program on the RCX
- Modify code
- Press the "Download program to RCX" button
- Play around with user program on the RCX
- Wonder why code changes do not have any effects
Expected behavior
When downloading, the user could be informed that they made changes to the code that have not been compiled and hence the built binary may not include the expected changes.
Alternatively, we could combine the build step into a "Build & download" step as there's probably only a very small majority of users who only want to build their code - and maybe expect the binary.
Screenshots
N/A
Operating system & webbrowser:
Considered irrelevant here.
RCX hardware & firmware:
Considered irrelevant here.
Additional context
There may be users with web browsers that only support WebAssembly (WASM) but not Web Serial or WebUSB APIs and therefore only play around with writing NQC code and compiling it, i.e. press the "Build" button and want to see what happens.
(EDIT) Suggestion: Replace the two buttons ("🧱 Build" and "⬇️ Download program to RCX") with a "universal" button.
Dependent on web browser capabilities, label that button and use different functionalities. Only WASM available? Stick with "🧱 Build" as no IR communication is available for download. WASM + WebSerial available? Then re-label the button "🧱 Build + ⬇️ Download program to RCX" and have both functionalities executed after each other automatically.