Hi every one,
i have had this problem for years but recently its unbearable,
when i type a command ( say L to get a line) the command line says nil, this problem showed up after using a lisp that helps my in my work, i used to save the file and exit, and when i open ACAD again every thing turns back to normal, Well lately the problem showed up again but this time the saving and exiting trick didn't work, any suggestions ?
You loaded a 3.party poor programmed program,
you need to know which one is it to avoid them.
Start a new file, or the current one again, is it still a problem?
Sebastian
Sorry, i ignored some part of your post.
You know this tool, good!
Contact the programmer, tell about the issue, wait for an update 😄
Sebastian
Ok, isn't there any way i can unload this program ?i tried going to APP load and unload the program but there are no contents , the other problem is that i don't know the programmer. any suggestions ?
We are not sitting in front of your PC, we didn't load anything in your AutoCAD,
we do know NOTHING about this program.
But we should know what happen?
Tell us the Tool name, the file name,share the source (webpage?) of this tool,
share the tool, share whatever information you have!
Last "in the blue" try:
Start command _AppManager
Is it there?
Sebastian
@Anonymous wrote:
....i tried going to APP load and unload the program but there are no contents .... any suggestions ?
(findfile "acaddoc.lsp")
If that returns a filepath and that filename, open that and check for (load) or (autoload) functions.
Programmer Mahmoud Yazed (Payazed) incl. Mail adress
https://payazed.wordpress.com/2015/08/31/syn/
Unlike you, I will not start an unknown program to determine the problem.
Check both files (if present)
(findfile "ACAD.lsp")
and
(findfile "ACADDOC.lsp")
Sebastian
IF the program is an autolisp program, type VLIDE at the command prompt. In VLIDE, enable "Break on error"
and then activate AutoCAD (return to AutoCAD from VLIDE) and do whatever you are doing that returns an unexpected nil. If you are lucky, it will be a lisp error that "breaks" and returns you to VLIDE. If so, select Last Break Source under the Debug tab (or use [Ctrl+f9])
and on a good day the offending lisp file will be opened and the offending code will be highlighted and can be corrected to eliminate the problem.
Can't find what you're looking for? Ask the community or share your knowledge.