#Ownload thonny editor install#
#Ownload thonny editor serial#

Unfortunately, when I start it (as explain in the instructions, with the CTRL key), it does not start: it jumps on the dock and then exited automatically without any error prompts.

#Ownload thonny editor install#

I downloaded mu-editor v1.0.3 from ' ' on my Mac (MacOSX 10.11.6 - ElCapitan) and managed to install it. Hi, I am new to this forum and I hope my question has not been answered already. I'll continue working on the last remaining tests and prompts, but let me know if you discover any other problems, annoyances etc.

I found a way to make error messages refer to the right line numbers (finally!).

I've changed a bit in how devices are recognized, making it possible to match on manufacturer strings (this part is especially important to get tested on Windows).

A dropdown in the statusbar has been added, which only shows up when users connect one or more devices.

#Ownload thonny editor serial#

REPL serial connections to MicroPython-devices are maintained as 'REPLConnection' objects, instead of being placed both in UI-code and inside modes.find_devices now returns a list of devices represented as special Device-objects.

Here's the branch with my changes if you want to check it out: It would be nice if some of you could test that it works, especially Windows users and Linux users, as I'm currently only in posession of a Mac This also separates device-connections from the UI-code, so it should be easier to make future improvements. I still lack to do a few prompt ('You have just changed to a micro:bit device, do you want to change mode to the BBC micro:bit mode?') as well as a few tests. Now multiple devices can be connected and a small dropdown will be shown, to select between the devices. I've made a major overhaul of the MicroPython-modes (ESP-mode/micro:bit/CircuitPython). Does anyone have any advice for me? Thanks!

I also tried to navigate directly to the board from the mu file browser but under /Volumes it doesn't 'see' the device.

Would you like to change Mu to the Adafruit CircuitPython mode?' I selected 'OK' but then again received the message 'Could not find an attached Adafruit CiruitPython device'. Then, upon restarting mu, it said 'Detected a new Adafruit CircuitPython device. Here is another experiment I did: I switched to Python3 mode before exiting mu. I have updated to the newest version of CircuitPython, have also erased and redone the filesystem and everything else I could think of (including reinstalling mu). I can, however, enter the REPL via mu in this circumstance and so mu is perfectly capable of talking to the board. I am experimenting with CircuitPython on Metro-series boards and I am having a recurring issue with all of the boards in that mu editor does not recognize that there is a device plugged in (even though it shows up as a drive on my Mac).