pendean wrote:
are you sure, while typing, AutoCAD stops being the active program in Windows (aka loses focus)?
Yes, I'm sure. When an incident happens, I can use the mouse to click "outside" of AutoCAD and in another program, such as Word or Outlook Email, Keyboard works. Click back into AutoCAD, Keyboard is dead. Closing the program and restarting the computer clears the issue up for a while.
pendean wrote:
Does the keyboard require a driver from a third party to run?
Broken USB port? if you plug in the back, plug it in the front for example (ganged USB ports are all tied to one spot on a motherboard usually, so moving it to another next to the one you use is not a good way to diagnose issues).
We are using the Windows universal driver according to our IT department on all of our machines.
We have switch USB ports and no effect. On one machine, we even plugged in a PS2 keyboard and still have the same results.
We are up to 4 machines (out of 38 in our current office) having the problem. I am going to check the frequency of how often it happens on each machine. I have also got IT looking into other possibilities, such as Windows KB patches to see if there is anything that could be interfering. One machine I would thought it was the keyboard. But multiple machines, I'm thinking its something else.
FYI......Our IT department is also going to scan for virus's and malware.
Hi,
>> Mouse still works but keyboard doesn't work at all
Two questions to that: when you say you can use the mouse in AutoCAD ==> does that mean you can move and see the moving mouse on top of the AutoCAD application window or can you really use the mouse to start commands from ribbon and draw e.g. a line?
When you say the keyboard does not work when the AutoCAD window has the focus ==> does that mean turn on/off caps-lock and/or numlock does also not work (pressing capslock multiple times does not turn on and turn off the led for capslock?
To try: next time that issue happens pull out the USB connector and plug it in into another USB-socket.
- alfred -
FYI.....In the situation of the wireless keyboard, the same characteristics are seen as with the USB wired keyboard. Responses below apply to both.
Alfred.NESWADBA wrote:
when you say you can use the mouse in AutoCAD ==> does that mean you can move and see the moving mouse on top of the AutoCAD application window
Yes. Cursor moves across drawing pane, ribbons, menu area. cursor Moves across screen to select desktop items.
or can you really use the mouse to start commands from ribbon and draw e.g. a line?
Yes.
When you say the keyboard does not work when the AutoCAD window has the focus ==> does that mean turn on/off caps-lock and/or numlock does also not work (pressing capslock multiple times does not turn on and turn off the led for capslock?
Did not try that exactly. When incident occurs, you cannot enter a command in the command prompt or type text in MTEXT editor. I did not try PROPERTIES, ATTRIBUTE EDITOR or any other command that accepts a numerical value or text string. I will add those to the list of things to try during the next incident.
To try: next time that issue happens pull out the USB connector and plug it in into another USB-socket.
We did that already. Tried Ports on both the back and front of the machine.
We will give it a try.
You've maybe already solved this, but for the sake of others...
Did you verify that the mouse is positioned over the area you want to type in while using the Keyboard?
This is a known bug/feature/quirk of some versions of AutoCad which certainly took me some time to troubleshoot;
If your mouse is not over the text field while you are typing, the keyboard is disabled. Even if you click on a field first, if the mouse moves away from the dialog box, then it loses focus and the keyboard becomes inactive.
Solution:
It takes some extra dexterity, but you need to mouse over the dialog box with one hand while you type with the other.
I have searched extensively and believe there is no fix to this behavior.
To be honest, I forgot to check with the colleague after suggesting Dean's solutions. This has been a while back. If memory serves me correct, I think it ended up being an issue with the mouse.
My apology for not following up. Thanks for your input.