andrewfstratton

You can also use TinyGo. I've used this myself for reading buttons, updating display, flashing the led, acting as a USB HID keyboard and mouse with serial comms over USB...

I have update the issue with further clarification when I discovered that the error happens for values of >2 for an axis range of -32767..32767

Note: This isn't about resetting the leds (since they are reset on powerup) but about being able to change them immediately after power on.

> How much delay do you need here to fix the problem? The delay was for me to bodge it by resetting the leds after they have been switched on...

Another experiment: Here's the code this time there's a half second delay before setting the leds Off. The result is that many resets show Green (then go off), less often...

So I tried this with a `Cytron Maker Pi RP2040` which has 2 RGB Leds - this is my last RP2040 with WS2812 Leds - so I don't have any...

I've discovered that the first WS2812 write after power off or reset writes green as 0xff (or a high value - it's hard to be sure) to led 0 instead...

These are all onboard rgb leds - 4 different board types with two different manufacturers. Power might be an issue but seems unlikely with one RGB led and the issue...

Possibly related/relevant: When you get the screen width and height - this is of all the monitors (the workspace?), e.g. ``` width, height := robotgo.GetScreenSize() fmt.Println("width = ", width, "height...

Aha - the wierd relative movement behaviour seems to be **down to scaling** This can be repeated (on windows) by changing the scaling to (say) 125%. The relative movement seems...