Anuncios

The Autodesk Community Forums has a new look. Read more about what's changed on the Community Announcements board.

AutoComplete and AutoCorrect and InputSearchOptions

sbrusco
Collaborator

AutoComplete and AutoCorrect and InputSearchOptions

sbrusco
Collaborator
Collaborator

Hi All,

 

The attached PNG shows what i see when i start typing "Erase" but only enter the "E" but on another computer, a user's suggestions in the shortcut menu has "Explode" first and "Erase" second. How can we get "Erase" to be at the top of his list like it is on mine?

 

I looked at the three hopes listed in the subject line but the best i can determine is that AutoCAD will "learn" the order with frequency of use. This does not seem to work for us.

 

Any suggestions?

 

TIA,

 

Sal


0 Me gusta
Responder
Soluciones aceptadas (1)
2.795 Vistas
8 Respuestas
Respuestas (8)

ToddRogers-WPM
Mentor
Mentor

I would first check to see if his "E" was changed in the ALIASEDIT.  If his EXPLODE is referencing an "E", change it to "X".

Todd Rogers
0 Me gusta

sbrusco
Collaborator
Collaborator

Hi Todd,

 

Thanks for your interest. I have checked the alias listings and all is as it should be; "E" is set to "Erase" and "X" is set to "Explode." I'm pretty sure the problem lies in one of these three commands (AutoComplete, AutoCorrect or InputSearchOptions) but I'm not having any success.

 

Any other suggestions?

 

TIA

 

Sal


0 Me gusta

pendean
Community Legend
Community Legend
Solución aceptada
Turn off autocomplete for the single user if it interferes with their desired input: it can be problematic for some users and there is no real cure honestly.
0 Me gusta

sbrusco
Collaborator
Collaborator

Hi Dean,

 

This is the 'work-around' we settled on but since it disables a feature that I consider helpful, i would prefer to continue to use it.

 

Oh well, maybe Autodesk will see to a 'cure' sometime in the future.

 

Thanks,

 

Sal


0 Me gusta

pendean
Community Legend
Community Legend
4+ versions and counting, I would not hold your breath just yet :cara_de_decepción:
0 Me gusta

ToddRogers-WPM
Mentor
Mentor

In the settings, I changed the milliseconds to 800 and I don't have that problem anymore. I had issues with the copy command initiating circle. Very annoying, but the milliseconds change worked.

Todd Rogers
0 Me gusta

sbrusco
Collaborator
Collaborator

Hi Todd,

 

I actually considered that but i just hate to wait for a computer for anything, for any amount of time.

 

What happened was that the AutoCorrect feature finally "learned according to frequency of usage. Sorts the command suggestion list based on how often you have used the command" per the "Input Search Options Dialog Box" online help file, and this made the user happy. HOWEVER, there are several commands that start with "E" (erase, explode, extend...) so the order will change again, i'm sure.

 

I think Dean's suggestion is our best setting, at least for now.

 

Sal


0 Me gusta

userlevel6
Advocate
Advocate

Just wanted to add my 2 cents... been running & LISP/Script programming ACAD since 1986.

I've had command entry issues ever since moving to the Windows platform, not that I'd want to go back to DOS days.

 

For me, what originally seemed to be an issue from slow hardware improved (ACAD 12 for Windows on Win 3.11 on a 16M RAM 386-class machine), improved as hardware got faster, until ACAD added additional tools that try to anticipate command entry somewhere in the early 2000's.  Apparently better tools come with a loss of keyboard responsiveness.

 

Today for example, if I quickly type "SCR" <enter>, I might get the SCRIPT command, or I might get the SCALE command.  Sometimes ACAD ignores the "R" I type if I hit the enter key too quickly.

 

Turning of AUTOCOMPLETE entirely seems to help most these days, but then I have to remember to turn it back on if I want to have it remember some command name for me, which can be convenient.  No big deal, just not ideal.

 

If anyone can tell me a way to change ACAD's priorities to  pay attention to exactly what is typed first, and then do whatever else it's going to do, I would really appreciate it.  I've been looking for years, and nothing quite does the trick.  Then again, it might just be something I have to tweak in the OS for a faster keyboard buffer...?  All I can do is slow down, often cancelling and re-entering commands, and sometimes it's a torment.

 

0 Me gusta