1
CamBam help (General usage) / CB 1.0 / Win10 Pro 64-bit mouse issue
« on: February 19, 2025, 21:02:51 pm »
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.
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.