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

[Blockly] Targeted performance fixes #41804

Merged
merged 3 commits into from
Jul 30, 2021
Merged

[Blockly] Targeted performance fixes #41804

merged 3 commits into from
Jul 30, 2021

Conversation

ajpal
Copy link
Contributor

@ajpal ajpal commented Jul 29, 2021

Pulls in code-dot-org/blockly#280 and code-dot-org/blockly#281
Also sets behavior_definition blocks in spritelab to not user visible so we don't have to render them (they're already hidden, we just weren't setting the block property).

Slack threads:
https://codedotorg.slack.com/archives/C0T0PNTM3/p1627571617462700
https://codedotorg.slack.com/archives/C01V27QS9AT/p1627581282013800

@ajpal ajpal requested a review from a team July 29, 2021 20:31
Copy link

@epeach epeach left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! Excited to see the improvements from setting that visibility to false.

@@ -609,7 +609,6 @@ export default {
block.setHSV(136, 0.84, 0.8);
block.parameterNames_ = [i18n.thisSprite()];
block.parameterTypes_ = [Blockly.BlockValueType.SPRITE];
block.setUserVisible(false);
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not 100% sure why, but this is causing behaviors to break entirely - I thought it would be a purely UI change but it doesn't appear to be. I will dig into this more, but I think we should go ahead with this PR without this change since it'll still fix the majority of the lag

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fyi @epeach, but lmk if you have any concerns about this!

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.

None yet

2 participants