C2LC-107: Disable the run button when program is empty

Metadata

Source
C2LC-107
Type
Task
Priority
N/A
Status
Done
Resolution
N/A
Assignee
N/A
Reporter
Created
2019-12-19T13:28:28.806-0500
Updated
2020-02-20T11:11:40.539-0500
Versions
N/A
Fixed Versions
  1. Coding Env 0.2.1
Component
N/A

Description

We need to determine whether we should allow people to run an empty program. If not, then we should grey out and disable the run button when the program is empty.

Comments

  • Simon Bates commented 2019-12-19T14:15:20.570-0500

    I think this question is very much related to C2LC-89

    If we go forward with C2LC-89, empty blocks now have meaning: they cause the program to pause for some time. So, another perspective on running an empty program would be that it executes all of the empty blocks, pausing for a time on each one.

    Are empty blocks within a program different from emtpry blocks at the end? For example, the following program:

    • Forward, empty, empty, Forward, empty, empty

  • Simon Bates commented 2020-01-06T15:07:03.696-0500

    We decided (2020-01-06):

    • Disable the Run button for empty programs
    • Empty blocks within a program will wait for some time
    • Empty blocks at the end of a program will have not effect

  • Simon Bates commented 2020-02-14T14:23:37.885-0500

    I will rename this issue from "Ability to run an empty program" to "Disable the run button when program is empty" to make the task clearer and to reflect design changes.

    For 0.3, we are redesigning the sequence editing UI so that there are no empty blocks. And for 0.2 we have decided that we will not spend time on any addition improvements for empty blocks, as they will be going away.