CB 1.0 / Win10 Pro 64-bit mouse issue

[airnocker]

I don't recall this happening before now, but then I'm older than ever before ;-).

Win 10 22H2 OS Build 19045.5487

Using an existing CB 1.0 file that is two years old, after double-clicking a polyline that has multiple nodes and hovering the mouse cursor over a node I want to move...the mouse cursor disappears.  If I have accurately positioned the mouse over the node before it disappears the moment the cursor pointer is over the node, and then left-click to move the node, the node does move, but there is a graphics rendering delay before it shows the node position changing.

CB Options for Graphics mode is Open GL as it has always been during my use since 0.9.8 and 1.0.

Since there have been several Windows updates in addition to installing Microsoft's Visual Studio Code with the PlatformIO plugin and all its JS requirements I am wondering whether this is related to the strange cursor behavior I am now seeing in CB 1.0.

BTW:  It does this regardless of Display Graphics Mode being Open GL or GDI.  Also, the latest .NET version is in effect that is much newer than V4.5 and most likely current.

Any ideas anyone?  Thanks in advance.

[lloydsp]

I can't speak to that exact problem, but I recently had terrific mouse-pad problems over two updates of Windows.  My mouse would 'jitter' so badly that I could not hover over an object long enough to click on it.  A re-boot would fix it for an hour or two, then it came right back.

But, after the second update after the problem FIRST showed up, it entirely went away.  I suspect Windows.

L

[pixelmaker]

https://www.wintips.org/mouse-cursor-disappears-on-windows-10-11-fix/

I suspect Windows.

I run Windows under Parallels on the Mac. So I can have several operating systems installed at the same time. The 64-bit version runs most stable on Windows 7. I have installed Windows 10 and 11, but I have problems with them from time to time. However, these are often only caused by Windows 11 wanting something that I don't give it, for example updates or a virus scanner.

I sometimes switch Display Graphics Mode, which fixes errors. Sometimes there is no refresh of the interface, then I can only resize the window a little or switch the Display Graphics Mode from Open GL to Open GL legacy and back.

[lloydsp]

That's all 'mouse milk'.  None of that is reasonable.

Lloyd

[EddyCurrent]

Updating the graphics drivers can help sometimes.

[EddyCurrent]

While this forum was down I saw the reply from Bob about this issue on cnczone forum and he was right about the Snappy plugin, thanks and well spotted Bob.
I will attach a new version of the Snappy plugin to it's thread, it will change the cursor to a Cross when it's over a snap point.

[pixelmaker]

Thank you Eddy

[Dragonfly]

... it will change the cursor to a Cross when it's over a snap point.

Even without this it's a wonderful plugin, I can't imagine working without it.

[airnocker]

While this forum was down I saw the reply from Bob about this issue on cnczone forum and he was right about the Snappy plugin, thanks and well spotted Bob.
I will attach a new version of the Snappy plugin to it's thread, it will change the cursor to a Cross when it's over a snap point.

With this forum being unavailable at times I posted my query for help on the CB section of CNCZone and got a prompt reply from Bob asking if I had the Snappy plugin installed.  (I never got any emails from the CB forum stating there were replies to my query here, oddly enough.)

But yes, I did recently install the Snappy plugin to my CB 1.0 a month or two ago when editing a .cb project that was several years old (a schematic diagram).  I installed the plugin and restarted CB as usual.  Snappy worked wonderfully and I hadn't bothered to check it settings.  It dutifully snapped to on and off grid nodes without hiding the cursor at snap when I needed to move a node during my first session with Snappy.  I loved it!

5-7 weeks passed and I pulled up the same file again to make more changes.  This is when I noticed the cursor disappearing when the mouse hovered over a polyline node point.  At times with the cursor hidden I could move the node to a new position, although it was somewhat of a challenge.  And about half the time, with the cursor hidden, I hadn't actually "snapped" to anything at all in the course of the node move attempt.

It was Bob's raising the Snappy issue that I looked at the Snappy plugin settings again and saw the check mark for "Hide cursor at snap".  I unchecked it and it the cursor stayed in view, as was my initial experience.

Eddy, thank you so much for all you do for us.  Changing the "at snap" cursor to a + sign is a good idea.

Lloyd, I have experienced weird erratic mouse movements under two conditions using Win10 Pro 22H2 and earlier.
1.  After changing to a wireless Logitech mouse when the battery gets too low, or the IR detector LED/lens was dirty (wired or wireless).
2.  Windows is bitchin' because it is past feeding time for a new KB update,  once the update was "eaten" and Windows restarted, all was well.

And thanks to all the rest of you who contribute on this forum!

[dh42]

Hello

I never got any emails from the CB forum stating there were replies to my query here, oddly enough.

Yes notifications and any other mails from the forum no longer works since the last major forum crash. 

++
David