Insert Block Prompt and Autocomplete Woes

[tyler2sl]

As soon as I start typing a block name, AutoCAD assumes and autocompletes to my dismay (99% of the time the block is not the one I'm looking for). I would like to turn off the Autocomplete feature for this prompt, but it seems unaffected by the INPUTSEARCHOPTIONS command and the options found therein.

Any ideas?

[cadffm]

Why you display us the InsertDialog?
This Dialog show all named Blocks of your Drawing, INPUTSEARCHOPTIONS is for a shortcut function of commandline, a totally other part.

The default Blockname for Insert can set by InsName
http://help.autodesk.com/view/ACD/2018/DEU/?guid=GUID-1654B78D-A11A-44D6-9790-28C756929EFB

[tyler2sl]

---

@cadffm wrote:
Why you display us the InsertDialog?
This Dialog show all named Blocks of your Drawing, INPUTSEARCHOPTIONS is for a shortcut function of commandline, a totally other part.

The default Blockname for Insert can set by InsName
http://help.autodesk.com/view/ACD/2018/DEU/?guid=GUID-1654B78D-A11A-44D6-9790-28C756929EFB

---

Thanks for the response. My issue is AutoCAD autocompletes my block name. If I need to bring in block "AB" but "ABC" is already in session, AutoCAD autocompletes to "ABC". It's annoying and slows me down. I am hoping there is a system variable that I can shut off for the insert dialog's autocomplete.

[cadffm]

On my machine with 2018.1.1

If i type AB, both: Commandline and Insert-Dialog show my the right Block!

My test: 3 Blocks

"AB"

"ABC"

"ABCD"

all names works fine?

[tyler2sl]

Try it the other way around, larger names first.

-Insert ABCD.

-Insert AB (it autocompletes to ABCD) Hit enter and ABCD is brought in.

My wish is to stop the autocomplete in this dialogue. I assume its intent is to increase a user's speed, but it has only done the opposite for me.

[cadffm]

Ok, on my sytem it works very well, not like yours.

_insert abcd ...

_insert (abcd is preselected), i typ in AB and Acad NOT complete to another Blockname

LowerLeft Corner you see my Cursorprompt after "AB"

AutoCAD 2018.1.1 on Win8.1

[tyler2sl]

Any other ideas? Anyone?

[tyler2sl]

So, is there some setting I can change to get my program to behave differently?

[GrantsPirate]

Pick on the wrench icon to the left of the command line, pick input search options, uncheck Block.  See image.

[tyler2sl]

These are my current 'Input Search Options' settings:

It seems that AutoCAD disregards these settings for the InsertDialogue?

[tyler2sl]

I should specify that even though these are my settings, I am still having this issue.

[john.vellek · Accepted solution]

Hi @tyler2sl,

Since turning off AutoComplete entirely doesn't seem to have any affect, can you try logging onto your computer as a new user?  I am curious to see if the behavior continues.

You could also consider a Reset Settings to Default and then again adjust the Input Search Option settings.

Please add a post with how you decide to proceed and the results.

I just received confirmation from the QA team that this behavior in a dialogue is as designed and is not controlled by the Input Search Options.

You are also welcome to contact the product team directly. If you have additional comments specific to the software or its functionality for future consideration, please use the Product Feedback page. How to provide feedback on Autodesk products goes into more detail.

Another great option is to participate in the AutoCAD Customer Council. This is an opportunity for our customers to partner with the AutoCAD development team to improve future releases of AutoCAD by giving continuous feedback on ideas, designs, and early builds.
In order to get involved email [email protected] or [email protected]

Please select the Accept as Solution button if my post solves your issue or answers your question.

[tyler2sl · Accepted solution]

So, to put it plainly, there is no way to turn this behavior off?

Thanks very much for your response.

edit: I'm going back to ACAD 2016 as this behavior did not occur with that release. I've contacted the product team directly, pleading they allow the autocomplete behavior to be toggled off in future releases!

[john.vellek · Accepted solution]

Hi @tyler2sl,

Yes, sadly that is the answer but at least we both have one!

Thanks for your patience on this question and I apologize that I didn't see it earlier.

Have a great weekend

[cadffm]

Hello tyler2sl,

as said it works with me well. When I enter: A
and there is no block "A", then automatically supplemented to AB,
which is also useful if A is not a valid block name (block A does not exist).

When AB is entered, however, is not added to ABC or ABCD, because there is really a block AB available.

If it is really different with you would be very interesting to me why,
maybe @john.vellek writes or someone @Anonymous like it at his System works.

(please to all, please test it and write your experience - and tylor too )

The question is: Do I have a special system or you?
What is the standard, there are really different behavior
and if so, why?

Video is rec by AutoCAD 2018.1.1, Win8.1

[tyler2sl]

For the set you included, my acad works just as your video does.

However, the set of blocks that would induce the issue would be named like: abca, abcb, abcc, abcd. For example, if you need abcc, but one of those other blocks are in session already, then autocomplete finishes to the wrong block name, the block seemingly loads into memory, and then you can adjust the text further.

I think it has a bit to do with how large my blocks are, because it really slows down.

EDIT: I should add that I am bringing my blocks in from a directory. That directory has been added to the support and working search path (in options) and has been moved up to be the first place autocad looks to bring in blocks.

[cadffm]

ah OK,

if we talk about unknown Blocks and you type in the name of a non-defined Block for searching for a DWG with that Name within the SupportPathes , thats right.

Than we need [< -Backspace] if Acad auto-completed the input to the next valid (known) Blockname and hit <enter>.

For me from the previous description was not right, perhaps a translation problem on my part, sorry.