Makefile(so we can all do it on our local machines should we need to). Perhaps this is even something that could just be built into
pupsince I imagine many packagers would appreciate the "static" just deploy it on a memory stick nature of PortaMu. @tmontes "PortaPup" :-)
pupappeared to JustWork :tm: (link to signed Windows installer coming in a moment)
Publisher: Nicholas Tollervey! Yeah!!!!
After pressing "Run anyway" I got the "Welcome to the Mu Editor" windows and it took like 30 seconds to move on (automatically, without the need to press "Next").
Windows 10 Pro 21H2 (OS Build 19044.1415)
PS: it did a parallel installation, right next to the former 1.1.0b7 not-signed msi.
Hi Everyone, I'm seeing a funny non-working result thart USED to work:
---( CLASSIC BLINK)---
led.value(1) # turn LED on
led.value(0) # turn LED off
So that uses PinName.value(0or1)
BUT I was ReadingTHeDocs and saw you could do led.on or led.off it WORKED:
----( version 2)----
while True: # (FOREVER here )
led.on # turn LED on sleep(0.5) # 1/2 second led.off # turn LED off sleep(0.5) i = i + 1 print("I = ", i) sleep(1.0)
This runs (I can see the prints) but the pin with LED does not light or change...
?? SHould I NOT use that pin.on type statement? I swear it worked the first couple of times...
THANKS, No Functional Problem but I am trying to decrease confusion for newbies...