Like the title says, this isn't about ONE and TWO. This is about the little things. Small, minor bugs that make you wish SOLIDWORKS was a person so that you could build a time machine to go back and murder its parents. Bonus points if the problem is just intermittent enough to make you forget about it, until it happens again.
Be sure to post your SOLIDWORKS version and service pack, just in case someone wants to verify your bug or let you know that it is fixed in later versions. I'll give one for starters.
SW2016 SP 2.0
- Often, but not always, when typing in the property manager (renaming features, entering dimension text, etc) the hotkey for the letter I type will activate. I suspect it has to do with typing speed. It has done this for as long as I can remember.
Jim,
Reason in IMHO why people are reluctant to spend time reporting SPR's
Reason #1
is that it takes lots of time to do the running around, explaining how and what goes wrong where, making RX, phoning VAR, explaining step by step once more, getting them to contact SW finding/adding to an SPR or making a new SPR and if one is really unlucky, one gets some kind of statement from SW that is neither here nor there and having to press to make it clear that the solution provided has nothing to do with the issue, spending time to test this and test that by recommendation of SW, oh and perhaps switch this off or that on and repair, reboot, re-install . Which result in anything from an hour to several hours spread over days or even weeks....if one is lucky one gets to bypass all that and go straight to reason #2
Reason #1.b
Sending an email to a VAR to state something is amiss will result in being contacted by the VAR ....which takes us back to reason #1. Unless of course one fully documents the issue with screenshots, Rx and verbose explanation then it might be that it's clear enough so as to warrant the VAR directly doing the SPR thing. Either way, it takes more then a few minutes.
So a simple nuisance issue can either be sighed over or spend the better part of an hour on it with as result an SPR. If it's reproducible enough of course because else one is SOL.
Reason #2
An SPR has been made and we might (or might not) be contacted to let us know it's implemented, which can take years. In fact, it can take so long, and it has, that by the time it should be fixed one doesn't even remember what the problem with it was any more being so used to working around it.
Reason #3 why people are reluctant to phone in SPR's.
(See also https://forum.solidworks.com/message/201162?q=spr%20fi )
In short,when reporting a bug I got notified that it was taking care of in 2009 A1. Which I found strange because I was faced with a bug that officially no longer was there.
It took more then 4 years or so since the time it was marked as implemented for the bug to be truly resolved. Never the less, even today the SPR in question is still marked as implemented in 2009 A1.
I guess implemented in SW speak means that someone took a look at it, saw that it needed to be fixed and jotting it down on his to-do list instead of meaning resolved, realised, carried out,enabled or fixed.
A database with an error in the data, that doesn't get fixed, is not a database that inspires confidence because if there's 1 then there's no telling how many more there are.
So when face with a show stopping issue, yes one will take the time, mostly. But for something 'minor' we know in advance that it's priority will never be high because there are far more pressing and important issues that need to be tackled. So yes,most of the time I can't be bothered.