I'm reasonably sure I am on the right tram with this...
I have always hoped that my beloved red tail-light MS Intellimouse Explorer would die after I did. This turned out not to be the case, and no mouse worked as well ever since - until I replaced the computer.
I have only recently concluded that the snapping situation had gotten progressively worse over a couple of years, indeed I had finally been reduced to using the N key. So, the situation was intolerable, but I couldn't see what the villain was. For unrelated reasons, I was obliged to relocate DCad to an old laptop, and I found that the newish wireless mouse worked well. It so happened that the file I was using was huge, full of PDFs, with a fairly trivial DCad markup over. The desktop was groaning under the strain as I scrolled around but the laptop handled it a lot better. I got the hint.... Other than desktop having an additional 2Gb video card and W7 64bit, while laptop is W8.1 32bit, there isn't much difference in the specs between the two.
The desktop has now been replaced, DataCad is fine, and the Logitech M705 snaps just like it oughta. There is just no comparison.
I have concluded that DataCad, and the mice various, were innocent all along. The snapping problem was all to do with memory being progressively being clogged up. There may even have been some shared memory issue that I knew nothing about. I'm well pleased with the replacement desktop but, if I simply restored a clean operating system, I may have redeemed the old one. The demise of the Intellimouse may have been coincidental with the onset of the problem. It definitely was the best mouse.
So I wonder if this is a known problem, and post this for anybody who suffers a mysterious deterioration in snapping accuracy. Memory, not mouse, and definitely not DataCad.
I have always hoped that my beloved red tail-light MS Intellimouse Explorer would die after I did. This turned out not to be the case, and no mouse worked as well ever since - until I replaced the computer.
I have only recently concluded that the snapping situation had gotten progressively worse over a couple of years, indeed I had finally been reduced to using the N key. So, the situation was intolerable, but I couldn't see what the villain was. For unrelated reasons, I was obliged to relocate DCad to an old laptop, and I found that the newish wireless mouse worked well. It so happened that the file I was using was huge, full of PDFs, with a fairly trivial DCad markup over. The desktop was groaning under the strain as I scrolled around but the laptop handled it a lot better. I got the hint.... Other than desktop having an additional 2Gb video card and W7 64bit, while laptop is W8.1 32bit, there isn't much difference in the specs between the two.
The desktop has now been replaced, DataCad is fine, and the Logitech M705 snaps just like it oughta. There is just no comparison.
I have concluded that DataCad, and the mice various, were innocent all along. The snapping problem was all to do with memory being progressively being clogged up. There may even have been some shared memory issue that I knew nothing about. I'm well pleased with the replacement desktop but, if I simply restored a clean operating system, I may have redeemed the old one. The demise of the Intellimouse may have been coincidental with the onset of the problem. It definitely was the best mouse.
So I wonder if this is a known problem, and post this for anybody who suffers a mysterious deterioration in snapping accuracy. Memory, not mouse, and definitely not DataCad.
Nick Pyner
Dee Why Beach NSW
Dee Why Beach NSW