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

Make use of targetWorkspace where applicable #2626

Merged
merged 1 commit into from May 12, 2022

Conversation

ewpatton
Copy link
Member

@ewpatton ewpatton commented Jan 8, 2022

Fixes #2625

Change-Id: I24592add7f7416befc3ecc4a37b860c985f818e9

Change-Id: I24592add7f7416befc3ecc4a37b860c985f818e9
Copy link
Collaborator

@BeksOmega BeksOmega left a comment

Choose a reason for hiding this comment

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

LGTM! Still fuzzy on how this was breaking things though. Does AppInventor use targetWorkspace for things besides flyouts?

@ewpatton
Copy link
Member Author

ewpatton commented Jan 8, 2022

@BeksOmega The underlying issue I saw was that mainWorkspace was becoming the fly out, which I believe is fixed by my monkey patch to markFocused. We should probably move to using options.parentWorkspace from targetWorkspace in the future. I may clean this up a bit further because I do think somewhere we have a getTopWorkspace method that always returns the real workspace.

@ewpatton ewpatton added this to the nb189 milestone May 10, 2022
@ellelili2025 ellelili2025 merged commit 94be1e2 into mit-cml:master May 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Asset blocks cannot be dragged into the workspace (sometimes)
3 participants