Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

How will we support Scratch 2.0 projects that have multiple "current ()" monitors? #1218

Closed
fsih opened this issue Jan 9, 2018 · 5 comments · Fixed by scratchfoundation/scratch-vm#1742
Assignees
Milestone

Comments

@fsih
Copy link
Contributor

fsih commented Jan 9, 2018

In Scratch 2.0, it was possible to have monitors for "current second," "current minute," "current hour" etc. simultaneously. In 3.0, they will all share 1 monitor. We should figure out how projects with multiple monitors will behave in 3.0.

https://scratch.mit.edu/projects/196922245/

  • When I open the project in 3.0, will all of the different monitors still be present, or will they all merge into 1 monitor?
  • If I change the value on the dropdown on the "current ()" block, will all of the monitors change? One of them? Will a new monitor appear?
@CatsAreFluffy
Copy link

Currently, no monitors appear.

@tomrow
Copy link

tomrow commented Jun 26, 2018

I think it should behave like Scratch 1.4's (sensor[v]) block in that it makes a new monitor when the dropdown is changed and the checkbox is ticked.

@bates64
Copy link

bates64 commented Oct 24, 2018

In 3.0, they will all share 1 monitor

Why

@towerofnix
Copy link
Contributor

@heyitsmeuralex In Scratch 3.0 it's only possible for each block to have one monitor (not multiple). There's not a big "why" design reason for this - it's just an effect of how it was programmed. (NB: I don't actually know how monitors are programmed, I'm just guesstimating this. :P)

@fsih
Copy link
Contributor Author

fsih commented Oct 24, 2018

/cc @kchadha relevant to monitor save and load

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

9 participants