Command line invisible with SendCommand ?

[Anonymous]

Hello everybody,

Is there a way to make invisible the command lines sent by 'SendCommand' ?

'CMDECHO' variable works only on the results of a command.

Thank you

Driss.

[Anonymous]

Hi Driss,

I have a vague memory of a process whereby you effectively back spaced to
the start of the command line and then wrote blanks over the text sent by
Send command. I've just spent an hour with a Google search of the NG
without finding it though.

A system variable NOMUTT showed up, but all it seems to do is hide the word
"Command" in the command line.

I (and many others) want this capability as well- so where are the experts ?

--


Laurie Comerford
CADApps
www.cadapps.com.au


"Driss" wrote in message
news:8A3F0FDC3870F10FF3514C257DEF3813@in.WebX.maYIadrTaRb...
> Hello everybody,
>
> Is there a way to make invisible the command lines sent by 'SendCommand' ?
>
> 'CMDECHO' variable works only on the results of a command.
>
> Thank you
>
> Driss.
>
>
>
>

[Anonymous]

Well I'm not sure how high up in the expert category I fall, but lets
see...

First off, you don't want NOMUTT. It is used as a debugger - I find it
particularly useful with lisp. Second, you could try experimenting with
EXPERT. It runs from 0 to 5 and eliminates lots of the command prompts
for commands. Can't remember off hand which turns off the most, 0 or 5.
But, I would highly doubt that it'll produce what you want.

To play devil's advocate, if you are using 2000+ I'd recommend
revisiting your code. I've never had to resort to the sendcommand since
the R14 days. Usually it is as a last resort because you can't figure
any other way around what you are trying to do. Maybe try posting a
question, and/or a snippet of code, and see if we can help you avoid the
sendcommand altogether. If nothing else, email me your code directly and
I'll see what I can do to help you.

Mike

===============================
Mike Tuersley
PhD @ CADalyst's AutoCAD Clinic
http://www.cadonline.com

> Hi Driss,
>
> I have a vague memory of a process whereby you effectively back spaced to
> the start of the command line and then wrote blanks over the text sent by
> Send command. I've just spent an hour with a Google search of the NG
> without finding it though.
>
> A system variable NOMUTT showed up, but all it seems to do is hide the word
> "Command" in the command line.
>
> I (and many others) want this capability as well- so where are the experts ?
>
> --
>
>
> Laurie Comerford
> CADApps
> www.cadapps.com.au
>
>
> "Driss" wrote in message
> news:8A3F0FDC3870F10FF3514C257DEF3813@in.WebX.maYIadrTaRb...
> > Hello everybody,
> >
> > Is there a way to make invisible the command lines sent by 'SendCommand' ?
> >
> > 'CMDECHO' variable works only on the results of a command.
> >
> > Thank you
> >
> > Driss.
> >
> >
> >
> >
>
>
>

[Anonymous]

Hi Mike,

Thanks for the offer.

My situation is that I'm providing an interface to an existing VLX code for
which I don't have the source.

The intention is to use the interface to ensure the user goes through the
licensing system i.e. we do not want the user to be able to see the calls to
the VLX program and bypass the VBA code which provides the security.

In general terms we have both lots of code in place and it's only a couple
of hours c.f. rewriting the lisp in VBA, or writing the VBA in lisp.

I don't think I can call the Lisp functions from VBA without Sendcommand.

Is there a way to do that ?

--


Laurie Comerford
CADApps
www.cadapps.com.au




"Mike Tuersley" wrote in message
news:MPG.1822792bd89812e09896a4@discussion.autodesk.com...
> Well I'm not sure how high up in the expert category I fall, but lets
> see...
>
> First off, you don't want NOMUTT. It is used as a debugger - I find it
> particularly useful with lisp. Second, you could try experimenting with
> EXPERT. It runs from 0 to 5 and eliminates lots of the command prompts
> for commands. Can't remember off hand which turns off the most, 0 or 5.
> But, I would highly doubt that it'll produce what you want.
>
> To play devil's advocate, if you are using 2000+ I'd recommend
> revisiting your code. I've never had to resort to the sendcommand since
> the R14 days. Usually it is as a last resort because you can't figure
> any other way around what you are trying to do. Maybe try posting a
> question, and/or a snippet of code, and see if we can help you avoid the
> sendcommand altogether. If nothing else, email me your code directly and
> I'll see what I can do to help you.
>
> Mike
>
> ===============================
> Mike Tuersley
> PhD @ CADalyst's AutoCAD Clinic
> http://www.cadonline.com
>
> > Hi Driss,
> >
> > I have a vague memory of a process whereby you effectively back spaced
to
> > the start of the command line and then wrote blanks over the text sent
by
> > Send command. I've just spent an hour with a Google search of the NG
> > without finding it though.
> >
> > A system variable NOMUTT showed up, but all it seems to do is hide the
word
> > "Command" in the command line.
> >
> > I (and many others) want this capability as well- so where are the
experts ?
> >
> > --
> >
> >
> > Laurie Comerford
> > CADApps
> > www.cadapps.com.au
> >
> >
> > "Driss" wrote in message
> > news:8A3F0FDC3870F10FF3514C257DEF3813@in.WebX.maYIadrTaRb...
> > > Hello everybody,
> > >
> > > Is there a way to make invisible the command lines sent by
'SendCommand' ?
> > >
> > > 'CMDECHO' variable works only on the results of a command.
> > >
> > > Thank you
> > >
> > > Driss.
> > >
> > >
> > >
> > >
> >
> >
> >

[Anonymous]

Hi Laurie!

I didn't realize it was your post. To answer your question, have you
tried ACADX.COM? Frank O. has an extension called VLAX [I believe] that
allows communication from vb/a to lisp. There are some limitations but I
can't recall the specifics.

HTH
Mike

===============================
Mike Tuersley
PhD @ CADalyst's AutoCAD Clinic
http://www.cadonline.com

[Anonymous]

Hi Mike,

Richard Binning from the AUGI group obviously has an excellent indexing
system and James Chung deserves the credit for the original process.

--


Laurie Comerford
CADApps
www.cadapps.com.au


"Neither "Nomutt" nor "cmdecho" completely silence the command prompt.
An interesting message was posted on Autodesk's VBA NG from James Chung
about suppressing the SendCommand output:
You can silence the response by wrapping your desired function in a quick
and dirty lisp routine
and then call it using the following sequence:
ThisDrawing.SendCommand"(MyLispCommand)"
and define your lisp command itself like this:
(defun MyLispCommand (/n)
(setq n (strlen "COMMAND: (MyLispCommand) "))
(repeat n(prompt(chr 8)))
(repeat n(prompt(chr 32)))
(princ)
;;place your code here
)
This construct will quickly replace the output at the command line with
spaces long enough to cover the function name.
Use it as you see fit....
Thanks,
Richard Binning
CADD Coordinator
The Haskell Company
Haskell Building
Jacksonville, FL 32231-4100
(904) 357-4855
(904) 791-4697 Fax

[Anonymous]

Hi Laurie and Mike,

Thank's for your answers, i have found also an other way to have a shorter
Lisp line command, 'cleaner' than a very long line of lisp command :

1) Put your Lisp command in one of the USERS variable (for example : USERS1)
:

2) Thisdrawing.sendcommand "(EVAL (READ (GETVAR ""USERS1"")))" & chr(13)

-> Don't forget to change all """ character by " (chr 34)"
...

But i'm going to try what you have suggested.

Driss.


"Laurie Comerford" a écrit dans le message de news:
FFA5834CB074D6012D3744D05F459FD0@in.WebX.maYIadrTaRb...
> Hi Mike,
>
> Richard Binning from the AUGI group obviously has an excellent indexing
> system and James Chung deserves the credit for the original process.
>
> --
>
>
> Laurie Comerford
> CADApps
> www.cadapps.com.au
>
>
> "Neither "Nomutt" nor "cmdecho" completely silence the command prompt.
> An interesting message was posted on Autodesk's VBA NG from James Chung
> about suppressing the SendCommand output:
> You can silence the response by wrapping your desired function in a quick
> and dirty lisp routine
> and then call it using the following sequence:
> ThisDrawing.SendCommand"(MyLispCommand)"
> and define your lisp command itself like this:
> (defun MyLispCommand (/n)
> (setq n (strlen "COMMAND: (MyLispCommand) "))
> (repeat n(prompt(chr 8)))
> (repeat n(prompt(chr 32)))
> (princ)
> ;;place your code here
> )
> This construct will quickly replace the output at the command line with
> spaces long enough to cover the function name.
> Use it as you see fit....
> Thanks,
> Richard Binning
> CADD Coordinator
> The Haskell Company
> Haskell Building
> Jacksonville, FL 32231-4100
> (904) 357-4855
> (904) 791-4697 Fax
>
>
>
>

[Anonymous]

Hi Driss,

If you decide to do this, then keep in mind that other developers may have
done exactly the same thing and you will end up conflicting with their
intentions.

You may care to write you code to store the value of User1 and provide to
restore the previous value if you use poorly written add on software.

--


Laurie Comerford
CADApps
www.cadapps.com.au


"Driss" wrote in message
news:F94DC613AAFB3211EA2490CB331A227C@in.WebX.maYIadrTaRb...
> Hi Laurie and Mike,
>
> Thank's for your answers, i have found also an other way to have a shorter
> Lisp line command, 'cleaner' than a very long line of lisp command :
>
> 1) Put your Lisp command in one of the USERS variable (for example :
USERS1)
> :
>
> 2) Thisdrawing.sendcommand "(EVAL (READ (GETVAR ""USERS1"")))" & chr(13)
>
> -> Don't forget to change all """ character by " (chr 34)"
> ...
>
> But i'm going to try what you have suggested.
>
> Driss.
>
>
> "Laurie Comerford" a écrit dans le message de
news:
> FFA5834CB074D6012D3744D05F459FD0@in.WebX.maYIadrTaRb...
> > Hi Mike,
> >
> > Richard Binning from the AUGI group obviously has an excellent indexing
> > system and James Chung deserves the credit for the original process.
> >
> > --
> >
> >
> > Laurie Comerford
> > CADApps
> > www.cadapps.com.au
> >
> >
> > "Neither "Nomutt" nor "cmdecho" completely silence the command prompt.
> > An interesting message was posted on Autodesk's VBA NG from James Chung
> > about suppressing the SendCommand output:
> > You can silence the response by wrapping your desired function in a
quick
> > and dirty lisp routine
> > and then call it using the following sequence:
> > ThisDrawing.SendCommand"(MyLispCommand)"
> > and define your lisp command itself like this:
> > (defun MyLispCommand (/n)
> > (setq n (strlen "COMMAND: (MyLispCommand) "))
> > (repeat n(prompt(chr 8)))
> > (repeat n(prompt(chr 32)))
> > (princ)
> > ;;place your code here
> > )
> > This construct will quickly replace the output at the command line with
> > spaces long enough to cover the function name.
> > Use it as you see fit....
> > Thanks,
> > Richard Binning
> > CADD Coordinator
> > The Haskell Company
> > Haskell Building
> > Jacksonville, FL 32231-4100
> > (904) 357-4855
> > (904) 791-4697 Fax
> >
> >
> >
> >
>
>

[Anonymous]

That's right ... 🙂

Thank's anyway

Driss.

"Laurie Comerford" a écrit dans le message de news:
16DF1320E1FFA33CB21FEC576BA4EA5F@in.WebX.maYIadrTaRb...
> Hi Driss,
>
> If you decide to do this, then keep in mind that other developers may have
> done exactly the same thing and you will end up conflicting with their
> intentions.
>
> You may care to write you code to store the value of User1 and provide to
> restore the previous value if you use poorly written add on software.
>
> --
>
>
> Laurie Comerford
> CADApps
> www.cadapps.com.au
>
>
> "Driss" wrote in message
> news:F94DC613AAFB3211EA2490CB331A227C@in.WebX.maYIadrTaRb...
> > Hi Laurie and Mike,
> >
> > Thank's for your answers, i have found also an other way to have a
shorter
> > Lisp line command, 'cleaner' than a very long line of lisp command :
> >
> > 1) Put your Lisp command in one of the USERS variable (for example :
> USERS1)
> > :
> >
> > 2) Thisdrawing.sendcommand "(EVAL (READ (GETVAR ""USERS1"")))" & chr(13)
> >
> > -> Don't forget to change all """ character by " (chr 34)"
> > ...
> >
> > But i'm going to try what you have suggested.
> >
> > Driss.
> >
> >
> > "Laurie Comerford" a écrit dans le message de
> news:
> > FFA5834CB074D6012D3744D05F459FD0@in.WebX.maYIadrTaRb...
> > > Hi Mike,
> > >
> > > Richard Binning from the AUGI group obviously has an excellent
indexing
> > > system and James Chung deserves the credit for the original process.
> > >
> > > --
> > >
> > >
> > > Laurie Comerford
> > > CADApps
> > > www.cadapps.com.au
> > >
> > >
> > > "Neither "Nomutt" nor "cmdecho" completely silence the command prompt.
> > > An interesting message was posted on Autodesk's VBA NG from James
Chung
> > > about suppressing the SendCommand output:
> > > You can silence the response by wrapping your desired function in a
> quick
> > > and dirty lisp routine
> > > and then call it using the following sequence:
> > > ThisDrawing.SendCommand"(MyLispCommand)"
> > > and define your lisp command itself like this:
> > > (defun MyLispCommand (/n)
> > > (setq n (strlen "COMMAND: (MyLispCommand) "))
> > > (repeat n(prompt(chr 8)))
> > > (repeat n(prompt(chr 32)))
> > > (princ)
> > > ;;place your code here
> > > )
> > > This construct will quickly replace the output at the command line
with
> > > spaces long enough to cover the function name.
> > > Use it as you see fit....
> > > Thanks,
> > > Richard Binning
> > > CADD Coordinator
> > > The Haskell Company
> > > Haskell Building
> > > Jacksonville, FL 32231-4100
> > > (904) 357-4855
> > > (904) 791-4697 Fax
> > >
> > >
> > >
> > >
> >
> >
>
>