Skip to content
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

Round Block-Inserting Suggestion #267

Open
5YSTM opened this issue Oct 11, 2024 · 2 comments
Open

Round Block-Inserting Suggestion #267

5YSTM opened this issue Oct 11, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@5YSTM
Copy link

5YSTM commented Oct 11, 2024

What Happened

is:open label:enhancement Allow "Round" blocks to be placed in any round slot.

Ex: [Play sound "(variable value used as sound name)"] or [Change rotation degrees by "(Ui _Up pressed)"]

The "True" or "False" output, being replaced with a 1 or 0 output instead. Also maybe add small symbols on each block type and allow us to right click a block to delete it, or duplicate it. (It would just help coding feel more natural to me since I often use scratch)

How to Reproduce

Just a suggestion

Block Coding Plugin Version

v0.7.1

Godot Engine Version

v4.3

Operating System

Windows 11

Logs or command-line output

No response

Anything else?

No response

@cassidyjames cassidyjames added the enhancement New feature or request label Oct 23, 2024
@manuq
Copy link
Contributor

manuq commented Dec 18, 2024

Round blocks may have different types, so they can't be placed anywhere. For example a Vector3 round block can't be placed into a slot that expects a String block.

There are however some conversions happening and they could be improved.

@DoomTas3r
Copy link
Contributor

In my personal opinion, type conversion should be explicit, such as using a string to integer block, that way it's value can be accurately inferred. Then, types can also have unique visual indicators, such as shapes or icons, to avoid confusion about which type it is. In Scratch, if some code accidentally adds a string and an integer, the issue might be misinterpreted. Also, in GDScript, using the + operator between a string and an integer produces an error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants