topic Re: echo off in VB in VBA Forum

echo off in VB

Anonymous — Wed, 14 Mar 2007 21:44:13 GMT

In lisp when "command" function is used "cmdecho" variable turns on or off
the command line "messages". In VBA, however, this variable does nothing.
I'm using SendCommand method in VBA and setting up the "cmdecho" variable
does not affect the command line "echoes" anyway. Is there any other
"variable" that can be used in VBA for similar purpose?
Thanks,

Re: echo off in VB

Ed__Jobe — Wed, 14 Mar 2007 21:48:19 GMT

Probably because the SendCommand method is asyncrnous and will run after your vba finishes, thus, you don't see any effect. Try using ThisDrawing.SetVariable instead.

Re: echo off in VB

Anonymous — Wed, 14 Mar 2007 21:58:00 GMT

The only way not to see anything is to avoid the SendCommand function and use the object adding/modifying methods -- however, you can clean up what is written to the command line by getting rid of the prompts by setting NOMUTT to 1.

For Example:

Thisdrawing.SendCommand "line" & vbcr & "0,0,0" & vbcr & "999,999,0" & vbcr & vbcr

... will display as:

line
0,0,0
999,999,0

... just remember to turn it back on when done (kinda hard to use commands when you don't know what AutoCAD is asking).

HTH - Lanny

Re: echo off in VB

Anonymous — Wed, 14 Mar 2007 22:04:02 GMT

The best thing is to only use SendCommand as a last resort only when absolutely necessary.

Regards - Nathan

Re: echo off in VB

Anonymous — Fri, 16 Mar 2007 12:21:39 GMT

I've never done this before, but couldn't you set cmdecho to 0, then use SendCommand, but send it as a small lisp routine that does what you want?

Re: echo off in VB

Ed__Jobe — Fri, 16 Mar 2007 16:43:46 GMT

The problem is not what SendCommand sends, but using SendCommand. Your vba would execute and then when its done, cmdecho would toggle on/off.

Re: echo off in VB

Anonymous — Fri, 16 Mar 2007 16:47:13 GMT

So just to clarify, if it were to be toggled off before you did anything in vba, you wouldn't have a problem?

Re: echo off in VB

Anonymous — Fri, 16 Mar 2007 19:39:21 GMT

CMDECHO has no affect on echoing of prompts
and input from SendCommand(). It doesn't matter
when you turn it off.

--
http://www.caddzone.com

AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006/2007
http://www.acadxtabs.com

wrote in message news:5521205@discussion.autodesk.com...
So just to clarify, if it were to be toggled off before you did anything in vba, you wouldn't have a problem?

Re: echo off in VB

Anonymous — Mon, 19 Mar 2007 10:10:55 GMT

Well that's what i would have thought. I would relate SendCommand() to actually typing in the command manually.

Re: echo off in VB

Ed__Jobe — Mon, 19 Mar 2007 15:17:37 GMT

Sorry, my mind was on a single track. But even if cmdecho did affect echoing of SendCommand, because SendCommand is asyncronous, it would not have solved the original problem. The OP was apparently using SendCommand do do many things, not just set a sysvar. So this could be a lesson on using SendCommand to set any sysvar.

What should happen:
Turn sysvar off
process
Turn sysvar on

What was happening:
process
vba finishes
SendCommand begins
Turn sysvar off
Turn sysvar on

Lesson: use SetVariable(), not SendCommand

Re: echo off in VB

Anonymous — Wed, 06 Jun 2007 00:37:26 GMT

Thank you guys, I've got enough information I needed.

wrote in message news:5523057@discussion.autodesk.com...
Sorry, my mind was on a single track. But even if cmdecho did affect echoing
of SendCommand, because SendCommand is asyncronous, it would not have solved
the original problem. The OP was apparently using SendCommand do do many
things, not just set a sysvar. So this could be a lesson on using
SendCommand to set any sysvar.

What should happen:
Turn sysvar off
process
Turn sysvar on

What was happening:
process
vba finishes
SendCommand begins
Turn sysvar off
Turn sysvar on

Lesson: use SetVariable(), not SendCommand