Topic: DBMOD = 5 when I start AutoCAD

[BlackBox]

I'm running/loading a few things in S::Startup but that's between the PUSH/POP... I didn't think that would make a difference.  Maybe it does??

... (S::STARTUP) loads AFTER the (acad-pop-dbmod) at the end of ACAD.lsp

Also, the list above neglects this, but any .SCR file launched by your icon's startup switch loads AFTER (S::STARTUP).

[Matt__W]

I'm running/loading a few things in S::Startup but that's between the PUSH/POP... I didn't think that would make a difference.  Maybe it does??

... (S::STARTUP) loads AFTER the (acad-pop-dbmod) at the end of ACAD.lsp

Also, the list above neglects this, but any .SCR file launched by your icon's startup switch loads AFTER (S::STARTUP).

Even though it's nestled snug between PUSH & POP?

*stands with hands on hips*  Well that makes no doggone sense.  Hmmpphh!!!

[Lee Mac]

Wait, so what does the push/pop do?

Effectively starts/stops the counter that records the number of modifications to the drawing:

acad-push-dbmod

Stores the current value of the DBMOD system variable

(acad-push-dbmod)

This function is used with acad-pop-dbmod to control the DBMOD system variable. You can use this function to change a drawing without changing the DBMOD system variable. The DBMOD system variable tracks changes to a drawing and triggers save-drawing queries.

This function is implemented in acapp.arx, which is loaded by default. This function pushes the current value of the DBMOD system variable onto an internal stack. To use acad-push-dbmod and acad-pop-dbmod, precede operations with acad-push-dbmod and then use acad-pop-dbmod to restore the original value of the DBMOD system variable.

Return Values

Always returns T.

acad-pop-dbmod

Restores the value of the DBMOD system variable to the value that was most recently stored with acad-push-dbmod

(acad-pop-dbmod)

This function is used with acad-push-dbmod to control the DBMOD system variable. The DBMOD system variable tracks changes to a drawing and triggers save-drawing queries.

This function is implemented in acapp.arx, which is loaded by default. This function pops the current value of the DBMOD system variable off an internal stack.

Return Values

Returns T if successful; otherwise, if the stack is empty, returns nil.

[alanjt]

Wait, so what does the push/pop do?

Effectively starts/stops the counter that records the number of modifications to the drawing:

acad-push-dbmod

Stores the current value of the DBMOD system variable

(acad-push-dbmod)

This function is used with acad-pop-dbmod to control the DBMOD system variable. You can use this function to change a drawing without changing the DBMOD system variable. The DBMOD system variable tracks changes to a drawing and triggers save-drawing queries.

This function is implemented in acapp.arx, which is loaded by default. This function pushes the current value of the DBMOD system variable onto an internal stack. To use acad-push-dbmod and acad-pop-dbmod, precede operations with acad-push-dbmod and then use acad-pop-dbmod to restore the original value of the DBMOD system variable.

Return Values

Always returns T.

acad-pop-dbmod

Restores the value of the DBMOD system variable to the value that was most recently stored with acad-push-dbmod

(acad-pop-dbmod)

This function is used with acad-push-dbmod to control the DBMOD system variable. The DBMOD system variable tracks changes to a drawing and triggers save-drawing queries.

This function is implemented in acapp.arx, which is loaded by default. This function pops the current value of the DBMOD system variable off an internal stack.

Return Values

Returns T if successful; otherwise, if the stack is empty, returns nil.

Well damn, I guess I could have been a little less lazy and looked it up myself. Thanks.

[BlackBox]

I'm running/loading a few things in S::Startup but that's between the PUSH/POP... I didn't think that would make a difference.  Maybe it does??

... (S::STARTUP) loads AFTER the (acad-pop-dbmod) at the end of ACAD.lsp

Also, the list above neglects this, but any .SCR file launched by your icon's startup switch loads AFTER (S::STARTUP).

Even though it's nestled snug between PUSH & POP?

*stands with hands on hips*  Well that makes no doggone sense.  Hmmpphh!!!

Correct, during ACAD.lsp you're simply adding items to BE loaded/executed during (S::STARTUP).

Instead, is it possible for you to simply load/execute the code in ACAD.lsp, or ACADDOC.lsp?

As I said, I also use both ACAD.lsp and ACADDOC.lsp at startup and open Drawing1 DBMOD = 0.

FWIW - You don't need to use Push/Pop to startup without a save prompt... you can use this instead:

Code: [Select]

(defun c:FOO ()
  "FOO")

(if (= 1 (getvar 'dwgtitled))
  (c:FOO))

(princ)

... That way, any DEFUNs you add are still able to be called, but will not cause Drawing1 to prompt for save. Just a thought.

[irneb]

You could of course simply place the pop at the end of the S::Startup to have it run as late as possible. Of course if anything else appends onto the S::Startup as well that will get run after the pop. The /b switch only runs once per session though, so if you open another DWG all the usual suspects gets run again, without running the script.

This is a particularly prickly nettle! Even going through stuff like reactors can but make for more headaches. The "best" solution is not to change stuff inside the DWG through your startup routines, rather fix your templates correctly and run a script on existing files once and for all.