TheSwamp

Code Red => AutoLISP (Vanilla / Visual) => Topic started by: MSTG007 on October 17, 2016, 09:26:27 AM

Title: Qaflags or initcommandversion
Post by: MSTG007 on October 17, 2016, 09:26:27 AM

Just trying to get a better understanding of these two commands. Qaflags and initcommandversion. I have noticed that Qaflags effect the whole CAD environment where the initcommandversion, just effects the command its currently in?

We were playing around with exploding previous within macros, scripts, and lisp.

Thanks for the feedback.

Title: Re: Qaflags or initcommandversion
Post by: ribarm on January 20, 2018, 05:37:37 AM

I want to revive this question as it has never got a decent answer...

Maybe now there is better situation for discussion...

I was about to ask the same as OP, but I saw this post and decided to reply...

From help I saw that (initcommandversion -1) is default and is for the most recent version of command, but then I saw that also that meaning have (initcommandversion 2)... (initcommandversion 1) is automatically set when routine operates - that's how I understood what was written in help...

QAFLAGS I often turn to 1 and then immediately after I used it I put it back to 0... But still it is mystery for me and I believe for others too...

Thanks for reply, M.R.

Title: Re: Qaflags or initcommandversion
Post by: rkmcswain on January 22, 2018, 07:54:10 AM

More info on QAFLAGS here (http://www.manusoft.com/resources/acadexposed/sysvars.html).