xinabox / pxt-sl06 Goto Github PK

The Gesture blocks make it very difficult for microbit MakeCode users to use the gesture sensing.

1 = users have no scope of the return values (e.g. they have a no way of knowing what is returned for a left swipe - is it "LEFT", "Left", "left", "West" etc.

Finding this out through trial-and-error is not a positive user experience. Quite the opposite:

2 = Non-sophisticated users should not be expected to have the skills to easily find this out.

3 = Writing a test program to output the values onto the microbit 5x5 LED matrix is just not feasible due to how rubbish the display is. I have an OD01, we can't rely on everyone who has an SL06 having an OD01).

Note also the snippet attached. I understand why it doesn't work, but our core target market for this product won't:

UX requirements follow...

Please enable gesture sensing blocks for micro:bit

We have 2 functions that do the same thing:

1= SL06 enable proximity sensor (boolean)
2 = SL06 disable proximity sensor

NB - the same is true for Light and Gesture modes.

I cannot see a need for (2) - it just confuses me having both options.

Please can do either of the following:
... let me know if there is a good reason for the duplication
... remove the (2) functions.

Note - the library is long so removing (2) is my preferred approach.

Now that we have our set mode blocks sorted I find there is a UX issue.

... when a user tries to set SL06 to Gesture mode WE KNOW that we need to turn off Proximity and Light mode.

... why would we make them do it explicitly?
It leads to scenarios where the BEST (safest) way to enable any single mode is with 3 blocks:

[Image is meant to show SL06 Disable Light as second block]

Please can we consider the possibilitity of have ONE block to set mode. It has options (Gesture, Light and Proximity) and whichever one is explicitly being turned onm we implicitly turn the other 2 off.

This new Set Mode block would be available through the extension in a group called Mode. This group would be displayed at the top.

There are 3 issues this ticket will address:

1 - The lux values being reported on the SL06 are way too high
2 - the lux values being reporting on the SL06 are way out of kilter with the values from the SL01.
3 - the functions in SL06 and SL01 return the exact same value - they should be exactly the same: name and input parameters, and when side by side should return similar values (see image)

Note - in image above the values were recorded when a strong torch was shone onto the sensors - it was shone on both at the same time. This pattern of results (SL06 much higher than SL01) is consistent. SL01 readings conform much more with expectations for lux.

Please:
... calibrate SL06 in line with SL01
... rename function in SL06 so it is in line with SL01.

NB - there is a lot of documentation about SL01 so please no changes there.