I know what you're saying seems logical, but it is simply not the case.

from m5stack import *
from m5ui import *
from uiflow import *

setScreenColor(0x111111)
label0 = M5TextBox(16, 38, "A", lcd.FONT_DejaVu72,0xFFFFFF, rotate=0)
angle = None
x = None
angle = 0
for count in range(90):
  label0.setRotate(angle)
  angle = (angle if isinstance(angle, int) else 0) + 1
x = 16
for count2 in range(25):
  label0.setPosition(x=x)
  x = (x if isinstance(x, int) else 0) + 1

And the video:
https://youtu.be/qsKmaJEeI6A

What I was really trying to do was to center letters rotated 90 degrees, but even with that rotation the D disappears. You can change the angle in my code example to see this.

Here's a video of my output.

https://www.youtube.com/watch?v=nYwlS4ADqOg&feature=youtu.be

I tried firmware versions 1.4.4, 1.4.5, and 1.4.5.1 thinking maybe that's related but they all behaved the same.

I'm not really sure what else I can do to troubleshoot this since it seems unique to my device.

I'm having an odd problem displaying text. Certain coordinates do not display certain characters, etc.

See the code below. The D does not display in label1. This came up initially when I was trying to position text to be correctly centered at 90 degree rotation.

from m5stack import *
from m5ui import *
from uiflow import *

@timerSch.event('timer1')
def ttimer1():
global curLetter

if curLetter == "A":
curLetter = "B"
else:
if curLetter == "B":
curLetter = "C"
else:
if curLetter == "C":
curLetter = "D"
else:
if curLetter == "D":
curLetter = "A"
label0.setText(curLetter)
label1.setText(curLetter)
pass

setScreenColor(0x000000)
curLetter = "A"
label0 = M5TextBox(25, 20, curLetter, lcd.FONT_DejaVu72,0xFFFFFF, rotate=0)
label1 = M5TextBox(29, 80, curLetter, lcd.FONT_DejaVu72,0xFFFFFF, rotate=0)
timerSch.run('timer1', 500, 0x00)

Is there any comprehensive documentation for the python modules such as m5stack, m5ui and uiflow?

I would like to figure out what functionality exists outside of what is presented in the Blockly UI.

Thanks!

Noise

Scratch that, I figured it out, it was completely my error, I had the wrong "Series" selected in M5Burner. It was set to Stack-EN and once I switch it back to StickC all was well.

I must have switched that accidentally at some point. So glad I finally spotted that, such a dumb mistake.

Thank you very much for your help @ajb2k3

@ajb2k3 1.4.2 is not listed as a download in my M5Burner. The manual download I found (http://firmware-repo-list.m5stack.com/firmware/UIFlow-v1.4.2.zip) caused an exception in M5Burner and stopped M5Burner from working until I deleted that firmware directory.

I tried both both that download and a download of the 1.4.2 commit on github with the same result.

I also tried the other versions of the firmware that are available in M5Burner (1.3.2, 1.4.4) with no joy, same results.

It's too bad really, because I was ready to pull the trigger on 2-3 more m5stick's, but it seems like a bad idea if I'm just potentially going to end up frustrating new programmers when the device half bricks.

To get around this I saved the Example sketch to disk, deleted the file Dices.ino and then opened Dices_MPU6886.iso. You will get a message about requiring that the directory name be changed, which it does for you.

You should now be able to successfully compile the sketch to the m5stick.

If you're referring to the Erase function in M5Burner, then yes I've tried that.

This is the output from that so it seems successful. Although if there is anything on the screen left over from an arduino sketch it doesn't clear that.

esptool.py v2.5.0
Serial port COM6
Connecting....
Detecting chip type... ESP32
Chip is ESP32-PICO-D4 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, Embedded Flash, VRef calibration in efuse
MAC: d8:a0:1d:55:f1:50
Uploading stub...
Running stub...
Stub running...
Erasing flash (this may take a while)...
Chip erase completed successfully in 2.4s
Hard resetting via RTS pin...
Finished