CODAL has added a way to rotate the display, which is useful to illustrate/teach how phones use an accelerometer to rotate their display.
One API proposal could be:
from microbit import display
display.rotate(display.ROTATION_XX)
Where ROTATION_XX can be ROTATION_0, ROTATION_90, ROTATION_180 or ROTATION_270.
CODAL uses a 0-3 enum for these values, but it makes sense to use 0, 90, 180 and 270 for the user API so that this can still work display.rotate(180).
Should setting an invalid value throw an exception? Some of the other APIs do a "best effort approximation", but I'm not sure if it's a good approach that display.rotate(45) could end up doing a 0 or 90 degree rotation.
With exceptions for incorrect values I think it's important to have the display.ROTATION_XX constants.
If exceptions aren't used I guess we could save a bit of memory by not using the constants and documenting the values. To be fair this argument is easy to guess, it's not like a limited list of words (like the sound expressions).
Another thing that would only work without exceptions is something like:
while True:
for x in range(0, 360):
display.rotate(x)
sleep(10)But to be fair, with exceptions this is also an option.
while True:
for x in (0, 90, 180, 270):
display.rotate(x)
sleep(1000)Right now I'm leaning towards no exceptions, no constants and documenting the values. Thoughts?
CODAL has added a way to rotate the display, which is useful to illustrate/teach how phones use an accelerometer to rotate their display.
One API proposal could be:
Where
ROTATION_XXcan beROTATION_0,ROTATION_90,ROTATION_180orROTATION_270.CODAL uses a 0-3 enum for these values, but it makes sense to use 0, 90, 180 and 270 for the user API so that this can still work
display.rotate(180).Should setting an invalid value throw an exception? Some of the other APIs do a "best effort approximation", but I'm not sure if it's a good approach that
display.rotate(45)could end up doing a 0 or 90 degree rotation.With exceptions for incorrect values I think it's important to have the
display.ROTATION_XXconstants.If exceptions aren't used I guess we could save a bit of memory by not using the constants and documenting the values. To be fair this argument is easy to guess, it's not like a limited list of words (like the sound expressions).
Another thing that would only work without exceptions is something like:
But to be fair, with exceptions this is also an option.
Right now I'm leaning towards no exceptions, no constants and documenting the values. Thoughts?