Autosave during Edit Array Source

[Anonymous]

John,

I am having a similar issue when editing an array.  In the past I traced down the command to any "auto-invoked" command not checking to see if it can run before it attempts to do so.  Case in point: Using the auto-save feature as expected causes this error when editing an array.  Question, if using the block editor or the refedit command allows a background save to execute properly, then why would an array edit source (which is similar to refedit) prohibit a save operation?  My guess is in the file locking.  Using the arrayEdit command locks the state of the drawing such that a save operation can not access the data that has been locked.  My suggestion is to disable autosave while editing an array or any other command that can cause this problem to arise.  (Autodesk has a list of things/command to defend against regarding this bug)

Also, if the error message would state "Hit [enter] to cancel or R to retry..." instead of the default response being [Retry] which uses an 'ENTER' key...What?

Foolishness!  There is NO WAY to Hit enter!

Finally, how about a clue as to what command is in operation and what command is attempting to run in the message as well.

I just had to trash the last 15 mins. of work...and I get a lot done in 15 mins...

TANX.Rob

My suggestion to the developers to solve this problem, in this case...do not ask the user to bail you out of a problem in your code if they are unable to generate any response that will SOLVE the issue.  Just terminate the interrupting command attempt and wait for the next idle state of the program and ask the user if they want to retry later.  This way the loop will exit and the user will leave the "locked" state and when the queued task is ready it can be run again.  I know there is a handler for this scenario as it works in the Block Editor and REFEDIT.

This thread was split from here.

[john.vellek]

Hi @Anonymous,

Can you give me the exact steps you are using to get this error message? In AutoCAD 2017 when I create an array, Edit Source and then try to save, I receive a message indicating ** QSAVE command not allowed during array editing **

I am not able to get that exact message you are showing. Does an ESC work to get out of the situation?

[Anonymous]

John...

in Autodesk Mechanical 2015 if you have the autosave feature enabled and you are within the ArrayEdit command (editing source components of an array) when AutoCAD attempts to perform the autosave function.  Instead of queuing the save command until AutoCAD is "able" to save, It just locks into the infamous loop mentioned in this post...Hit enter to cancel or [Retry]...
Hitting ESC might get you out, but most times you just have to kill AutoCAD and hope for the best.

So my guess to reproduce...Set your autosave to a relatively short time (say two minutes)...Create an Array...Edit the Source of that array and wait...

Note: we have upgraded to 2018, but are still using 2015 and earlier because of the file format change and as such have not tested this in that version...

TANX.Rob

[john.vellek]

Hi Rob,

I don't have Mechanical installed but I will reach out to another Specialist this morning to see if we can reproduce this behavior. Thanks for your contribution and patience.

[cheryl.buck]

Hi Rob, 

Thank you for your detailed description, I am very sorry for the inconvenience. Our development/QA Team is aware of this issue.

A couple things can be done to help reduce the chances of an autosave occurring during a key point during an active command are increasing the time between autosaves and if autosave is not needed, turning it off should eliminate the issue. Additionally, increasing RAM may also reduce the occurrence.

Thank you very much, 

[Anonymous]

Hello,

Knowing this is an unsolved problem...I purposely verified that the autosave was disabled before attempting to edit the source of an array.  Still locked up on the same issue.  Telling your userbase that is a know issue doesn't solve anything if nothing is done about it.  If you could reveal what command AutoCAD is attempting to execute, but can't, then I would make sure (the best I could) to prohibit that command somehow. 

I really need a work-around for this problem...do I need to "old-school" the way I deal with arrays and explode my source - modify - and regroup - FRUSTRADA!?

This bug should simply not exist on a program as mature as AutoCAD!  IMHO, If a company is going to do a complete rewrite of the code base, then the first items to be addressed should be bugs that cause a loss of data...which is what this does!  I disabled the autosave feature to avoid this problem, and I still lose data!?!  If I ever released a product that behaved like this then I would be put out of business.  Please stop costing me lost time and missed deadlines by not completing proper QA before you release!  We as professionals entrust your professionals not to allow such rudimentary errors to be released in your code.

I am sorry if I am coming off a bit rough, but it is no different than I hear from the clients I have to explain your errors to!  So please deal with any bug that is known to lose data.  This should be considered unacceptable by Management.

BTW, the work done for v2018 improved this a little by allowing the users to save up until the last command was good.  Not a fix, but a start...

P.S. Again sorry for the abrasiveness, I've been feeling sick all morning...

TANX.Rob

[cheryl.buck]

Hi Rob,

Thank you for posting about this issue in the forums, it has been logged with the development team for further investigation. If you would like to contact the product team directly, please use the Product Feedback page. 

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 autocad.beta@autodesk.com or autocad.lt.council@autodesk.com

Best Regards,