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

Allow custom blocks to return values - blocks part #3

Merged
merged 26 commits into from
Jul 29, 2023
Merged

Conversation

GarboMuffin
Copy link
Member

No description provided.

GarboMuffin and others added 26 commits July 2, 2023 16:53
This is consistent with "item of list"
This reverts commit 730b8f33819653cf8cd95e0cf1e714b709fbfcac.
If all return statements in a procedure definition contain a hexagon-shaped block, the call block for that procedure will itself become hexagon shaped.
We store information about every procedure before the change happens,
then diff it later. Should improve performance.
…call types

Blockly.Procedures.USER_CAN_CHANGE_CALL_TYPE:
`true` is the behavior for TurboWarp
`false` will restore behavior from two commits ago
Blockly.Procedures.ENFORCE_TYPES:
I currently intend to have this set to `false` for TurboWarp
You can set it to `true` for the old behavior.
In TW we will make this an "extension" for people to enable.
The return block will be hidden until that extension is enabled, or a
return block or non-statement shaped procedure call exists in the workspace.

There is a constant to restore the previous behavior.
Let's actually try to explain what this does.
Also serves as a separator and makes it clear return is not a normal block
@GarboMuffin GarboMuffin merged commit 98462bf into develop Jul 29, 2023
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants