@watson @world101 @ajb2k3 @hetzer
I would still consider adding it. I understand it only exists in m5go and fire but then under hardware blocks call the block m5go mic. I just think new users would experiment more with that function exposed as a block. I totally understand I can now make a custom block for this but I still think it makes sense to see it as a default block. It should definitely be exposed for StickC since with that board there is no confusion as they all have a mic. What about having a toggle when the user selects core that designates fire, go, grey, etc. (just like you do with stick and stickC) and have that toggle load the appropriate on board hardware blocks. What about a block that exposes the hall effects sensor too while you are at it. I guess I feel like expose it all since it encourages development and you never know what someone makes with it. At the very least it helps encourage learning and ease of use which seems like the point of block based visual coding.

If you install uiflow firmware you have also installed micropython. You can connect to a repl shell, load libraries, and modify main.py. You can use any micropython ide and you aren't required to use uiflow. It is a good option though. I like using upycraft. Even if I am running uiflow I'll still keep a connection to the board open with upycraft to get immediate feedback. With upycraft you have direct access to the filesystem and you can drag and drop files to and from the board. You can also run
help('modules')
dir(module)
where module is one of the listed modules. To learn more of all the built in functions available.

I think what was happening was, for some reason, flow.py was never being loaded. I manually ran flow.py from the console and it allowed the m5stick to finally go to the api key screen. I noticed in the code it mentions you can press button A to generate a new api key but for some reason it wasn't working. Anyways now it's good and I am successfully programming the stick as we speak. thanks

@ajb2k3 That's impressive work. I really like the new additions. I definitely want to read over it more but thanks so much for sharing.

I am using IFTTT with webhook based on an ok google "turn light on" and "turn light off" command. That message is relayed to io.adafruit and then transmits back to m5stack which performs a function based on the string received. Optionally data can also be sent to the cloud from the board using publish topic.

Got it that is what I thought but I wasn't sure and just thought I'd ask. Thank you both for your response.

I love seeing the graphic icons of the two new boards they look really cool in the simulator. I am sure you are already working on this but there needs to be a way, after selecting the leds in the simulator, to save a page of the toggled leds for the atom and then play back or trigger those pages. I picture something like the emoji interface you had in previous releases would be helpful to bring back since it had multipage options for crerating animations.
I imagine much of the code used used on the 5x5 microbit screen would be helpful if ported to UIflow. Things like the various 5x5 fonts they have avaiable as well as the various scrolling routines https://makecode.microbit.org/#editor FONTS. I know this is just the beginning and it already looks great but I thought I would state the obvious benefit of adding in some of this capability in future releases. thanks for the new release it's always fun to see what new tools you've made for us.

I have a few more suggestions.

1. It would be great to be able to add comments in uiflow. Microbit has this option and it's very helpful.
2. It would be great to be able to double click on the canvas and type, at which point a list of the common blocks with that typed letter would be listed and able to be selected for use. This would allow the user to more quickly access the blocks required and to stay in the flow - no pun intended. Here is an example in grasshopper.

I think it would make sense to add forum categories for MicroPython topics and a separate category for arduino topics. Also there needs to be a release notes page for uiflow that indicates the new changes whenever an update occurs for this tool. It would be helpful to see documentation on the changes so users can help to more easily contribute.

I did come across this info about on screen repl https://forum.micropython.org/viewtopic.php?t=5589

i2c = machine.I2C(scl=machine.Pin(4), sda=machine.Pin(5))
oled = ssd1306.SSD1306_I2C(128, 64, i2c)
from FBConsole import FBConsole
console = FBConsole(oled)
os.dupterm(console)

I am still getting a "can't convert float to int" error whenever I use a variable in the by argument in the count with i from to block. If I use an integer block in by it works fine. If I set a variable to the same integer it gives me an error and if I convert to int or convert to float I get the same error. If I click on details it reads: File<'string'> line57 in <module> TypeError: can't convert float to int. This is a bummer since I need to use a variable in the by argument of the block. Any help would be appreciated

@Zontex
Thanks @felmue that helps and thanks for sharing that image. I misunderstood the bar widget. I thought I could interact with it in a similar way as you interact with a slider and didn’t realize it was only meant as an visual indicator. I like the minimal look of the bar but I still want the functionality of the slider. It would be great to be able to define the touch dot on the slider either by setting visibility, setting color, and or setting size.

The bar widget only renders as a solid color and I can’t manage to get it to output any value change on touch event. Also is it possible to offer control over the center of the slider widget. If the function to change the slider dot color already exists can you please tell me how to do that.

Is it possible to add the speaker.tone() and speaker.sing() blocks to the core2 speaker block functions. Also it would be great to see some midi blocks especially since you added ble. Perhaps you can offer midi over serial and also using midi device ble profile. By the way, it’s really cool to see the ble blocks added. Last thing, you have some nice helpers when writing micro python such as select all, copy, paste, find and replace, and pallete which are all accessed at the icon shown at the end of each line. These are great when working on a tablet but it would be good if you broke out select all into two functions. If you click on select it would select only one line and if you click on all it would select all. I haven’t figured out what the pallete does. Can you please tell me how the pallete helper is used.

Just checking back to see if and when bluetooth block will be added to core 2 in uiflow. thanks

I've installed core2 beta4. I see ble is listed when I run help('modules'). I notice that I can import ble without an error, however when I run the code that uses ble it reports an error that bluetooth module is not available. It looks like there is plenty of memory available for the module. I am requesting that bluetooth is enabled for core2 uiflow firmware. If there is a way to add the module to the current uiflow firmware I'd welcome the info.

I just got mine today and I am so impressed. It just feels, sounds, and responds in such a great way. This is such an impressive device on many levels. At first I wasn't sure if I needed one since I have a few m5Stacks but I am so glad I purchased one. I have a few questions:

1. since the core2 has enough memory can you enable bluetooth in the uiflow firmware and please add the blocks. I know they are only available for fire but I am assuming they should work with core2.
2. if I wanted to use the core2 in a classroom do you offer any kits for these purposes. I have purchased microbit class packs. I guess I am asking you about availability, for example I know the c plus was unavailable for a time, and I want to make sure things are readily available. It would be great if you have any suggestions on how best to deal with purchasing m5stack for the classroom in order to make sure the students can easily get your product. I know in the states adafruit and digikey are resellers and I might have seen them at microcenter too but to be honest it's easiest and fastest to just send the students to amazon but amazon doesn't offer enough of the m5stack product range. I encourage you to offer a much wider range of your products on amazon, especially including the core2.

What a great device. I was just wondering what happened to the variety of default fonts. I liked that UIflow had a few default font styles available but those are not available in this release. I know fonts can be added but it would be good to a few readily available in UIflow.

@m5stack
Very cool. Thanks and it's really great to see bluetooth in micropython and uiflow. At one time you mentioned the micropython firmwares would be open source and made available on github, I know you have a uiflow micropython repo https://github.com/m5stack/UIFlow-Code but it doesn't always get updated with new releases, it would be great to see the repo get updated and have branches for each major release. I think so much great development can happen if the code is made available.

@robalstona @m5stack Thanks for that suggestion. I'll try the blocks you developed out on StickC. The new ble blynk blocks work it"s just they require a little tinkering with the micropython code to get them connected. At least that is my experience of using them. I am still very happy to see them included in the latest beta version of uiflow. Also I look forward to seeing a screen_shot showing all the blocks operating together in a single setup because I might be setting them up in a way that introduces the minor issues I've come across.