PDA

View Full Version : 2011 Inexplicable mouse/keyboard/shortcut behavior in vanilla ACAD 2011



ecleveland
2010-05-18, 01:38 PM
Dear Forumpeople:

I have downloaded and installed the 32-bit version of vanilla ACAD 2011 and have been checking it out for a couple of weeks. Finally obtaining a valid serial number from a new re-seller allowed me to activate it. My machine is a Dell Dimension 4600i running XP Pro, SP3. Also I have updated my display driver with 3DCONFIG as described in this and other forums. And, also, at last, I have set up a workaround so that I can now start the .chm Help files from within ACAD with a new shell command. If anyone replying to this post is having trouble with this I may be able to help you. (It's not that hard to set up).
My issues are the following:

For no apparent reason, when I return to AutoCAD from another application, it is as if a selection window is in progress --- sometimes. And/or, all keyboard or mouse input is prevented. I right-click the ACAD icon on my taskbar and exit CAD this way. The only other applications running at the time are Microsoft Outlook, the .chm Help system and sometimes Notepad if I'm looking at the pgp file. Now, after I close Outlook and the other applications I see some behaviour that is perplexing. When I double-click a desktop icon (program shortcut) to open the program, the dialogue for the shortcut properties opens instead. This is a first for me but I can't believe I am the only one who has experienced this. Have I provided enough data for a prognosis? By the way, re-booting clears up the problem and my desktop shortcut icons resume functioning as expected.

I am somewhat suspicious of this new default PICKADD setting of "2", so I have it set to "1" before the symptoms described above appear to try to eliminate this new "2" setting as a potential trigger.

artisteroi
2010-06-15, 07:25 PM
I beleive it has to do with the new dotnet3.5 system that is at work with acad 2011. It is a minor glitch and is related to "mouse/cursor ownership". It is essentially a microsoft problem and not really related to acad other than it effects acad by causing weird stuff to happen when switching from one windows program to acad modelspace. annoying but hardly fatal

ecleveland
2010-06-21, 02:48 PM
Thanks for the input. I'll check this out.