AutoCAD - Command Line refuses to stay docked/locked

[hencoop]

Hello all,

There was a discussion earlier about AutoCAD pallets changing size for which a solution was accepted (here): https://forums.autodesk.com/t5/autocad-forum/why-do-side-docked-palettes-change-height-between-sessi... 

That solution does not solve this problem.

There is only one solution I've found that keeps everything exactly as intended, but only AFTER the governing .xml file is edited and then made read-only (the solution discussion is here): https://resources.imaginit.com/support-blog/command-line-will-not-stay-docked 

This solution has one major downside.  ALL of the things that should be written to this .xml file can no longer be written to it because the file is read-only, e.g., recent file lists become static/stagnant (both .dst and .dwg).  That's a problem.

Does anyone have a clue to why the <CommandLineControl Workspace="<your workspace name>"> tag is either not written or written incorrectly to the .xml file (%appdata%\Autodesk\<your product version and year (i.e. AutoCAD 2020, C3D 2018, etc)>\R##.#\enu\Support\Profiles\<Profile Name from Options box>)?

It seems that if the cause of that failure/error were identified we could eliminate this docking problem.

[The subject line of this post has been edited for better findability by @handjonathan Original: Command Line refuses to stay docked/locked ]

[DeaconDave]

If you're still having this issue try this:  First: Make sure all of your palettes and command line are where you want them.  Second: Make sure that your Workspace Settings are set to "Automatically save workspace changes".  Finally:  Go to OPTIONS > AEC Editor tab > then section "Similar - Purpose Dialogs" and uncheck "Use Common Position".  (see image below) This has seemed to work for me so far.  Good Luck!

[hencoop]

I tested this a few times against my problem scenario of switching between SDI=1 and SDI=0 and back again. My command line now stays docked! Thank you so much!

Now, if I could just get Autodesk to make the "Display File Tabs" option available when SDI=1 so I can turn it off without switching to SDI=0 just to enable its checkbox, all of my SDI switching issues (well, the ones I can remember right now) will be resolved. For now my workaround is a little macro that executes .FILETABCLOSE before switching back to SDI=1.

[pendean]

---

@hencoop wrote:

Now, if I could just get Autodesk to make 

---

You can always ask for program enhancements and changes here https://www.autodesk.com/company/contact-us/product-feedback

[hencoop]

I don't have much confidence in that process but I'll give it a shot.

[pendean]

@hencoop it's the only thing on offer from Autodesk to us end users that are not part of their $1M client club, and they insist it is looked at by each developer lead regularly.

Or, obviously, spend a $1M plus per year with them and get your own contact deep inside the org 😉

[hencoop]

Alas!  The problem has returned... and these settings which briefly fixed it have not changed.

[DeaconDave]

Yea, mine just quit too.  This has been an issue for a few versions.  I don't understand how these little things can't be fixed.  It's really not that big of a deal but it's annoying.

[pendean]

@DeaconDave @hencoop changing or reloading workspaces?
Are you actively saving your workspaces with WSSAVE command after placement?

Works fine here in our offices full of AutoCAD users: If you've truly tried everything then start a support ticket through your subscription portal as explained here https://knowledge.autodesk.com/customer-service/account-management/users-software/support-options#:~....

[hencoop]

@pendean For me, I use the same workspace all the time.  I believe that this problem will never appear if you exclusively use SDI=0.  It seems to be caused by switching from SDI=1 to SDI=0 and then later switching back to SDI=1.

This sequence ALWAYS causes my docked command line to be changed to floating the next time I start AutoCAD (Civil 3D in my case... but I don't think its limited to Civil 3D).

[DeaconDave]

I too work in the same workspace everyday but I don't change my SDI value either.  I've had this issue since 2018 working with a different company than I am now.  

[Gunnar.lynch]

My command line was coming un-docked every time I restarted civil 3d 2022. I got it to stay put by editing the palette setting via the workspace. Open the CUI, highlight the currently used workspace, customize the workspace, expand palettes, select command line, where is says "allow docking" , change it to "do not change". Then hit done, then apply. My command line has stayed put ever since and this has worked for the couple other users at my office. Maybe this will work for some of you.  We only really use one workspace, but I would imagine this will need to be repeated for any workspaces that are used.

Forgive me if this has already been mentioned, I did not read all the threads linked to this topic.

***POST EDITED TO INCLUDE THE IMAGE IN THE BODY OF THE TEXT***

[hencoop]

I had high hopes for this fix but it has not kept my command line from being floated without my consent.

[Gunnar.lynch]

I did some more testing, and have some more info. We are in the process of transitioning to name users licenses. Which means I have access to an old style multi user license, for a few more days at least. As such, I'm able to use autodesk products without being signed into an autodesk account. If I sign out of my autodesk account, dock the command, close C3D. When I reopen the software, the command line stays docked every time I restart. It behaves as it should basically. As soon as I sign in to my Autodesk account, close c3d, then reopen, it will revert back to the default settings (un-docked and transparent) every start up. It doesn't matter how many times I dock it, if I'm signed in it won't stay put. I don’t know how to fix this, but wanted to mentioned what I found in my testing. Maybe it can help lead to a permanent solution.

[wil.marAtMasTec]

That's good information!

The issue is that C3D 2023 won't let the user sign off without closing the program.  Then, one can't open it without signing in.

I guess it's how Autodesk confirms a current license.
Any comments on that?

More importantly, I think I found a solution for this!
The 1st solutions here:

https://knowledge.autodesk.com/support/civil-3d/learn-explore/caas/sfdcarticles/sfdcarticles/command...

worked for me, but set the value for "LOCKUI" to 1, not 0.
I closed my session, reopened, and for the 1st time in a long time, the Command Bar was still locked.

I'll come back with updates if anything changes.

[pendean]

@wil.marAtMasTec Correct, signing out will always close the program: it cannot stay up, the whole purpose of signing is is to allow you to use the program.

[jcareyK8S9K]

Just wanted to say AutoCAD MAP 2024 the command was staying locked before an update just a few days ago, now I am having the same issue as above. The command line will not stay docked at the bottom

[pendean]

---

@jcareyK8S9K wrote:

Just wanted to say AutoCAD MAP 2024 the command was staying locked before an update just a few days ago, now I am having the same issue as above. The command line will not stay docked at the bottom

---

If the latest update is the reason, you'll need to report the issue to Autodesk (not here, we are all end users just like you). 

How to open a support case with Autodesk if you are on subscription to seek out Autodesk Support's help:
https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/How-to-find-my-sup... 

[jcareyK8S9K]

this has been a common recurrence every year when the new udpates come out. Drives me batty.

[tommcgtx]

I was just searching for a fix for this when I came across a Reddit post, and it worked for me. When you open AutoCAD, dock and position the command line where you want it and then immediately close the program without doing anything else. It's weird that it works, but it does. Edit: Nevermind! As soon as you open it and do anything, the next time you open it will revert to floating again. 

[hencoop]

@tommcgtx wrote:  "When you open AutoCAD, dock and position the command line where you want it and then immediately close the program without doing anything else."

---

That works for me as long as I do not set SDI=0 in my session; however, I must do that after every session in which I set SDI=0.

If I did set SDI=0 in my session,  upon starting a new session (opening AutoCAD) my Command Line is ALWAYS floated regardless of its position or the value of SDI when I closed the previous session.  I always set SDI=1 and make sure the position of my Command Line is as I want it.  My workspace is set to automatically save workspace changes... but setting SDI=0 makes it all useless.

I.E., setting SDI=0 at any point in a session will cause the Command Line to float the next time a new AutoCAD session is started no matter what is done to prevent it.

P.S.

My default setting for SDI is always 1.

Where I've used the word "AutoCAD" I am referring to "AutoCAD Civil 3D".