Programatically setting DWGUNITS
Giles is correct. I checked with tech support some time ago and there is no api to do what you want. Notice that you entered DWGUNITS ad the "command" prompt. It is just a command that does a bunch of stuff behind the scene.
Ed
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
How to post your code.
If INSUNITS is not correctly set in both source and target drawings, you should set the INSUNUTSDEFSOURCE and/or the INSUNITSDEFTARGET system variables.
INSUNITSDEFSOURCE and INSUNITSDEFTARGET have to be used if INSUNITS is equal to 0 respectively in the source and in the target file.
In the cas you describe you do not have to set INSUNITSDEFSOURCE as INSUNITS is equal to 1, and you should set INSUNITS to 2 in the taget file so that you won't have to set INSUNITSDEFTARGET anymore.
If this does not work (due to some issue with Civil 3d), you can use the Database.Insert() overload method which take a Matrix3d as argument passing it the following scaling matrix.
Matrix3d.Scaling(1.0 / 12.0, Point3d.Origin);
As said in the first replies, you have to call the -DWGUNITS command.
But if the issue is related to insertion, this is managed by the INSUNITS system variable, read this topic.
-DWGUNITS command also adds some AEC content to the file, which I suspect is where the units definition is stored. It's also the source of rogue AEC data that some have spent a *lot* of time trying to eliminate.
----------------------------------
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.
@dgorsman wrote:
-DWGUNITS command also adds some AEC content to the file, which I suspect is where the units definition is stored. It's also the source of rogue AEC data that some have spent a *lot* of time trying to eliminate.
Yes, running -DWGUNITS in Vanilla AutoCAD creates a new AEC_VARS dictionary in the NOD which contains an AecDbVarsDwgSetup object.
@Anonymous wrote:
Ok I have an update. I found an error in AutoCAD Text Window that could be related to the whole problem:
Unit-scaling inserted database...Duplicate definition of block _ClosedBlank ignored.
This has nothing to do with your scaling issue. This is an information message which just means that the source file contains a block definiton name "_ClosedBlank" which already exists in the target block table that it will be ignored.
@Anonymous wrote:
I did a search on this an it mentions that (Just had Gilles had mentioned) INSUNITS should match. I checked the source and destination and both have it set to 0. These are the settings for both files:
INSUNITS 0
INSUNITSDEFTARGET 1
INSUNITSDEFSOURCE 1
MEASUREINIT 0
MEASUREMENT 0
As said iupper and in the provided links to the AutoCAD documentation, the INSUNITS system variable is used to automatically scale the inserted files (as external references or block references) if both values in source and target files are different from 0 (No units).
The INSUNITSDEFSOURCE and INSUNITSDEFTARGET are to be used (in the target file) to emulate the INSUNITS values in respectiveley source and target files.
So, if INSUNITS equals 0 in source file, you can set, in the target file, the INSUNITSDEFSOURCE to the expected value for the source file, this won't change the source file INSUNITS system variable value but let the insertion process act if it was.
If INSUNITS equals 0 in the target file, you could also set the INSUNITSDEFTARGET to the expected value, but it should be better to directly set the INSUNITS value.
It looks like you're missing some AutoCAD basics which are absolutely required if you want to be able to customize AutoCAD by programming.
