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

Subsets of proximity sensors #10

Open
motib opened this issue Apr 7, 2017 · 4 comments
Open

Subsets of proximity sensors #10

motib opened this issue Apr 7, 2017 · 4 comments

Comments

@motib
Copy link

motib commented Apr 7, 2017

What is really cool about VPL is that you can set an event for an arbitrary subset of the sensors detecting or not detecting. While it might be difficult to provide the same functionality in Blockly, some thought should be given to improving the current situation. Even something as simple as stopping the Thymio when the end of the table is reached is difficult because a compound logically condition is needed:
on proximity sensors updated
if left not detect and right not detect

@stephanemagnenat
Copy link

I agree, it is a interesting question, maybe there could be semi-visual blocks a bit closer to VPL ones. This is not likely to be done within this version of Blockly, but with the new one from Google that merges with Scratch, this should be easier.

@motib
Copy link
Author

motib commented Apr 10, 2017

I am perfectly OK with having only text blocks; if you want visual blocks, VPL is fantastic and you don't need Blockly or Scratch. Even in Scratch, fields of blocks are limited to text, numbers and colors. All I was asking for is more (text) choices in the pulldown menus of the blocks.

@stephanemagnenat
Copy link

Suggestions and mockups on how to improve the current situation with purely text blocks is welcome :-)

@motib
Copy link
Author

motib commented Apr 10, 2017

Horizontal sensors: on X sensor detecting Y: add "all" and "none" to the pulldown for X.

Ground sensors: on X ground sensor detecting Y: add "both" and "neither" to the pulldown for X.
Alternatively (better), add a block: on left ground sensor detecting Y1 and right ground sensor detecting Y2.

This is important because you want to avoid the difficult topic of logical operators in order to implement line following. If the alternative block is implemented then the "and" just looks like natural language and shouldn't be a problem.

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

No branches or pull requests

2 participants