acad_<true>colordlg compilation error

[kozmos]

While packaging .lsp into .vlx in VLISP, the function calls of acad_colordlg(2002) and acad_reuecolordlg(2004) will be regarded as "null function" while executing the compiled VLX file, is there anyone know the reason and the solution?

 

[John Uhden]

Somewhere near the beginning of your primary source code you need to add those function names to whatever else you need to import into your separate-namespace VLX... (foreach item '(ACAD_COLORDLG ACAD_STRLSORT INITDIA ACAD-POP-DBMOD ACAD-PUSH-DBMOD STARTAPP <etc><etc>) (vl-arx-import item)
)

Or, looking at it again for the first time in a long time... (mapcar 'vl-arx-import '(ACAD_COLORDLG ACAD_STRLSORT INITDIA ACAD-POP-DBMOD ACAD-PUSH-DBMOD STARTAPP))

While packaging .lsp into .vlx in VLISP, the function calls of

acad_colordlg(2002) and acad_reuecolordlg(2004) will be regarded as "null function" while executing the compiled VLX file, is there anyone know the reason and the solution?

 

[kozmos]

Thanks John for ur reply and i have fixed this problem

btw, what is the function of acad-pop-dbmod & acad-push-dbmod do?

 

[John Uhden]

acad-push-dbmod saves the current value of the DBMOD variable and suspends any record of its change. acad-pop-dbmod restores the previous DBMOD value and reenables its recording. A typical example of its use would be in your acaddoc.lsp file where you might want to force the setting of certain drawing variables without causing AutoCAD to retain any record of the drawings's modification. The benefit is that the user might just want to see the drawing or may have opened the wrong one, so unless he zooms/pans he can exit the drawing without being asked to save changes, which is OK 'cause if he doesn't, his variables can be fixed the next time it's opened.