Topic: Using the new command from the command line

[ML]

I am trying to start a new drawing by using a drawing template via the command line. I had to set filedia to 0 to suppress the dialog box (-new does not work) but I just can't seem to get to work

Anyone see what might be wrong?

Also, is it possible to set filedia back to 1 in the same macro?

Thank you

Mark


^C^Cfiledia;0;new;("K:\Path\to\Template\templatefile.dwt");

[PDJ]

Try _new instead of -new..

Can't help ya with the macro, I'd write it in lisp myself..

[dubb]

CTRL + N

CREATES A NEW DRAWING...USING THE HOT KEY

[ML]

I did try _new and it was still no go.
I agree with you on The LISP part except I used a vbastmt command instead.

The problem is I may need to share these macro with LT users and it is not VBA or LISP enabled

Mark

[MikePerry]

Hi

Try removing the opening and closing brackets from the Path ie.

^C^CFileDia;0;_.New;"K:\Path\to\Template\templatefile.dwt";

Have a good one, Mike

[ML]

Mike,

That is not working either
It seems like after new is entered, the macro stops. If you type new at the command line (with Filedia set to 0), then you can type in your template file but it is not working in a macro so far.

Mark

[VerticalMojo]

Try this...

^C^C_fileopen;K:\Path\to\Template\templatefile.dwt;

[ML]

It looks like that will only open a .dwg file, I am trying to start a new drawing using a .dwt file

Mark

[VerticalMojo]

I dont think that you can start a macro and have it finish in another drawing, that being said you wont be able to restore the filedia after opening the template becuase it only works in "Single drawing compatibility mode".

Here is a snip from Autodesk - Discussion Groups

>snip<

Reply From:  Klasson, Conny
Date: Aug/21/01 - 04:40 (GMT)

Don't think its your system, I have the same thing here.
Seems like the "New" command has trouble with reading "Enter"
from the macro. Have not seen this before. Maybe it's a new
"feature" of LT 2000i?
I let you know if I can get a solution to this.

This macro works, and it should be the same for New:
^C^C_fileopen;acltiso.dwt;

Note the trick to turn of Filedia and then put it
back on in transparent mode while opening the file.
If I put the filedia;1; at the end of the macro
it's ignored (don't know why).

However, after som trial & error I found that the new
command works in a macro in "Single drawing compatibility mode".
Maybe it's the MDI that makes the macro get lost when the
macro is launched in one dwg and supposed to land in another??

Conny

--------------------------------------------------

Reply From: D'Arcy, Gary
Date: Aug/21/01 - 04:56 (GMT)
   
Dear Conny,

You are correct regarding SDI v's MDI.
This is the same for lisp and ARX also.

Once the NEW command with MDI enabled communication with the current
session ceases.
A new stack is created for each new drawing and all of the starup
initialization
has to be carried out including loading up the *.fas files etc.

In most it is the intention to set say a system variable in the current
drawing but by the time the new command has been issued you are no
longer in that drawing.

Regards Gary.


>snip<

[Sitra]

Maybe a script might work....

[VerticalMojo]

Conrad is right.....

First create a script file "Template" with this

Code: [Select]

filedia
0
_new
K:/Path/to/Template/templatefile.dwt
filedia
1

then a macro....

^C^Cexpert;5;scr;Template.scr;

[ML]

That's an intesesting idea, but I am not sure it could be launched from the menu macro.

Vertico, thank you for the informative post, I now know that I am not going crazy  

Every thing that was happening to me is confirmed in your post.

I found that using a VBA expression does the trick.
Here is how it works if anyone is interested:

Note:If you have a support path to your template files, you only need to put the template file name, not the entire path

^C^Cvbastmt;Application.Documents.add ("K:\Path to template file")

After you run the macro, you will notice that a new drawing (.dwg) is created just as it would be with going to File-New-template file

Mark

[ML]

I'm, sorry Vertical, I didn't see your macro. That is a real cool idea.
I will remember that idea if I need to see the menu to a none VBAenabled user

Mark