The tip has hit the problem. I have implemented a query of the key A in the callback routine after 1 ms. Only if the key is still pressed the routine is executed. Otherwise nothing is done. Now there are no more key presses from the ghost.
Thanks
The tip has hit the problem. I have implemented a query of the key A in the callback routine after 1 ms. Only if the key is still pressed the routine is executed. Otherwise nothing is done. Now there are no more key presses from the ghost.
Thanks
@felmue
Thank you for the information.
I will have a look at the links. At first glance it might fit.
Peter
I discovered by accident that the M5Core sends out a command via MQTT, even if the associated button was not pressed at all. Has anyone ever observed something similar. What can be the reason. It only occurs with key A.
I have written a program to control my marquee in UIFlow. Here is the resulting Micropython code:
def buttonA_wasPressed():
global temp, prog_name, lfd_nummer, version, data_update, balkon, wohn_zimmer, testraum, message
m5mqtt.publish(str('whg/balkon/markiese/strg'),str(lfd_nummer))
lab_status.setText(str(lfd_nummer))
lab_status.show()
lfd_nummer = (lfd_nummer if isinstance(lfd_nummer, Number) else 0) + 1
pass
btnA.wasPressed(buttonA_wasPressed)
Unfortunately, the indentations are swallowed. Is there a way to format code?
Peter
alternativ kannst Du auch bei [https://www.distrelec.de/de/manufacturer/m5stack/man_msa?no-cache=true&page=1&pageSize=50](link url) bestellen.
Mit UIFlow 1.8.4 habe ich auch keine Probleme. Der Prefix mqtt/ ist bei mir nicht erforderlich. Lag wohl an der Version der IDE.
@world101
Then M5Stack must have taken over the problem.
I will try again with replacing "\\n" with "\n" with the appropriate text block. But still got to it because my computer had to be reinstalled. I will report back.
I want to output multiline text. If I enter the text as a literal in the properties of a label, the line break is executed correctly. But if the text with the line break is in a variable \n becomes \\n. This means that the line break is no longer executed. Is this behavior intentional?
I think it is a bug that should be corrected as soon as possible.
Thanks a lot