When will Autodesk fix the "problem with 'custom' profiles"?

[hencoop]

My interface never stays put.  It changes on its own.  This is a long standing problem that has been identified as "a problem with custom profiles".  My frustration is that Autodesk enables users to customize their profiles (set things the way the user wants them) but it refuses to provide any way to find "problems" they may have and fix them.

I spend far too much time resetting my interface to my preferences after opening a session because Autodesk always makes its preferred adjustments to my interface.  Some windows will be as expected except for their height and even their order when docked and stacked.

• It has been proven that switching between SDI=1 and SDI=0 will result in the command line presentation changing to AutoCAD's default setting when a new session is opened.  (If AutoCAD's default was its prior setting you won't notice this).
• The SSM will NEVER be open when new sessions are started, regardless of previous profile settings.
• The SSM window will change its height during a session w/o user action.  It has been observed incrementally growing to about 85% of the stack and shrinking to about 20% of the stack during sessions (The Properties Window is the other in my stack.  I prefer them to both be at about 50% of the space available.)

The 2019 'solution' is to reset these things and then navigate to the Profile.aws file and make it read only; however, that prevents ANYTHING being changed in the Profile.aws file.  Things like recent files still need to be saved to it and can't be with this 'solution'.

Autodesk needs to fix the "problems with custom profiles" so users are not wasting time resetting their interface every time Autodesk decides to change it unilaterally.

Here is the reference to the 2019 solution:

https://blogs.rand.com/support/2019/09/command-line-will-not-stay-docked.html 

[pendean]

---

@hencoop wrote:

...Autodesk needs to fix the "problems with custom profiles" so users are not wasting time resetting their interface every time Autodesk decides to change it unilaterally.

Here is the reference to the 2019 solution:

https://blogs.rand.com/support/2019/09/command-line-will-not-stay-docked.html 

---

Autodesk looks for user feedback over THERE, never in these forums. 

Also... Here is 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...

[Jason.Piercey]

While profiles controlled everything once upon a time, they don't any longer. Use a workspace for graphical items and a profile for non-graphical items.

[cadffm]

You are right, but that has nothing to do with the stated issues.

The initial post isn't going deep enough, it's more like a overview or a quick state, it also doesn't match to Autocad (in some points Yes - for example the Commandline issue, for some not - the SSM for example).

[hencoop]

If it is as you say, then "When will Autodesk fix the "problem with Workspaces"?

(I have been using workspaces for many years).  Apparently, they do NOT preserve graphical items (or else the display of the Command line and other open windows are NOT graphical items... or perhaps "Automatically save workspace changes" doesn't?

[Jason.Piercey]

I use profiles and workspaces and do not suffer from the issue you've described, but I'm using Vanilla AutoCAD, not a vertical version. 

[cadffm]

>>"I use profiles and workspaces"

Nobody can "not use" them 😄

>>"and do not suffer from the issue you've described"

>>"but I'm using Vanilla AutoCAD, not a vertical version"

In Autocad, you can reproduce the CMDL issue, and there are two version of this issue.

(your "saving workspace changes option is off, as senseful too)

You are running in mdi (sdi=0), one file open,  place the commandline in center of program window,

some line visible.

Turn SDI on(0) and close Acad**

Reopen Acad (without a workspace parameter)

By this test, you didn't changed the profile or your (unnamed) workspace, but the commandline appears as docked commandline.

(right?)

or the same test, but this time,  save your worspace before closing.

** the commandline appears at the ititial  standard default place as 1line.

(right?)

[hencoop]

No.

But then I'm not certain I understand your meaning.

also, turning SDI on is 1, not 0

[pendean]

---

@hencoop wrote:

...or perhaps "Automatically save workspace changes" doesn't?

---

If it is important to you, get in the total-control habit of using WSSAVE command (or -WSSAVE command): never assume a checked box is going be as good as your intentional deliberate actions.

Been using Profiles and Workspaces in our offices for a long time now across multiple variants of AutoCAD, not seeing anything like what you may be facing doing it all this way.

HTH

[hencoop]

Do you switch between SDI=1 to SDI=0 and back to SDI=1 during a session?

I switched between SDI=1 to SDI=0 and back to SDI=1 and the command line stayed the same... a surprise.  So, I did more precisely what I always do.  I switched to a layout and then repeated the process except I plotted the layout to PDF using the Publish dialog before switching back to SDI=1.  Once again the command line reverted to its default presentation.

I always work in SDI=1.  I only switch to SDI=0 to publish (because Publish requires it).  I even use code to force SDI=1 upon opening a new session.  It appears that Publish may be involved in the creation of my problem.

[hencoop]

I haven't had any problem with the workspace not saving automatically. 

I repeated the exercise and issued an explicit WSSAVE after setting SDI=1.   After which I closed the session (my command line was as I prefer when WSSAVE was issued).  Upon opening a new session the command line had reverted to its default presentation.

[pendean]

---

@hencoop wrote:

...I always work in SDI=1.  I only switch to SDI=0 to publish (because Publish requires it).  I even use code to force SDI=1 upon opening a new session.  It appears that Publish may be involved in the creation of my problem.

---

Never EVER had to do that just to PUBLISH since it was called BATCHPLOT. Why do you if I may ask (I can guess, but you'll need to state it)?

You'll need to refer back to message #2 above for reporting and exploring a resolution, your workflow is on the face of it very different / unique

https://forums.autodesk.com/t5/autocad-forum/when-will-autodesk-fix-the-quot-problem-with-custom-pro... 

[hencoop]

[cadffm]

---

@hencoop wrote:

"No."

No? what "No"? Please quote the part you replied to.

"But then I'm not certain I understand your meaning."

I replied to Jason, so I don't know where you struggle with my post.

"also, turning SDI on is 1, not 0"

Sure, otherwise ot doesn't make sense, thx for pointing to this typo.

---

cadffm: @Jason.Piercey 
>You are running in mdi (sdi=0), one file open, place the commandline in center of program window, some line visible.
>Turn SDI on(1) (0) and close Acad**

>>" I switched to a layout and then repeated the process except I plotted the layout to PDF using the Publish dialog before switching back to SDI=1. Once again the command line reverted to its default presentation."

Not on my side, please describe it detailed.

Which I tested based on this statement:

I am in Model tab, set SDI from 0 to 1 switched in a Layout (why? Doesn't make sense for me, what is your reason?), published 2 Layouts (tested with layouts of the current file and also with external files,

set SDI off, back to the Model <- or Model tab first and sdi on later.

Commandline staying all the time.

>>"Do you switch between SDI=1 to SDI=0 and back to SDI=1 during a session?"

During the same session, it isn't a problem on my side. I can't reproduce an issue in this case (but again: I tested in AutoCAD).

>>" I only switch to SDI=0 to publish"

And why do you leave a session with SDI=0 or why do you start another session while SDI=0 ?

Is that an oversight then?
or is that intentional? and if it is wanted, why is it wanted (I just want to understand it, because you can also publish in the session in which you set SDI to 0)