So it appears to be a remote desktop issue.
My machines don't have a screen and I do it all from my laptop using remote desktop.
Just tested using splashtop and it seems to be working perfectly!
Hi Pluto,
Ah, I believe there is some interference between how the platform abstraction library that PixelCNC uses, SDL, and Virtual Desktop. When a layer handle is grabbed the mouse cursor is no longer actually being used and mouse motion itself is the only input that is being interpreted until the handle is released. Then the mouse cursor is positioned on top of where the handle was released.
I will do some digging to see if I can find anything about this being a known issue with SDL and Virtual Desktop.
Thanks for the headsup! :]
- Charlie
Hi Charlie. If this helps, I have the same issue. When I use my MacBook M1 with Parallels and Windows 11 Arm PixelCNC exhibits the same cursor behaviour. I always type in the coordinates such as canvas or layer sizes or positions as mouse control ends up with coordinates in the thousands. The other area is value adjustment eg simulation speed, can’t get anything inverted min and max. So I use it for convenience in the lounge room. Detailed work is on the PC in the workshop.
Russ
Hi Russ,
Yes, I've discovered the same issue using VNC as well. This is apparently a bug in SDL, which is the platform-abstraction library that PixelCNC uses, and it results in the mouse motion messages from the OS being read incorrectly when there is a remote control application sending event messages to PixelCNC, like Virtual Desktop/VNC/etc. If there has been a fix in a newer version of SDL we'll be updating everything to that. Right now we're just working on getting v1.81b out for the moment, which the build for is pretty much locked for any major changes, and we should have it out by the end of the day :]
Thanks!
- Charlie