Skip to content

[Feature] DriveBase block is too complicated #2628

@laurensvalk

Description

@laurensvalk

Is your feature request related to a problem? Please describe.
By popular request, we have added features such as absolute turns and arcs.

Since these are movements, they are part of the drive block. While they are all arguably useful, it leaves users confused when faced with this list of 7 (!) options:

Image

Not all of these are final yet, so this would be a good time to decide if we should add them at all, and how.

Alternative: separate blocks
Instead of having all movement in one block, we could have separate blocks. Variations can be options instead, so we have just 5 blocks instead of 7 options.

Image

This also maps much better to the underlying Python methods, so the code is easier to follow and document.

Still, if you consider the other blocks that exist, that's a lot of blocks.

Consideration: no block for coordinate turns
In either case, we could in principle omit the new move_by method since it hasn't been officially released.

Backwards compatibility
As always, existing blocks will continue to work.

New programs can begin using the new blocks, if we decide to introduce them.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions