grichards

1) create a "dTools" block in a block library (drawingA)
2) verify the block has an object with layer: MY_LAYER and the color is set to 123
3) tie the block in drawingA to dTools productX
4) open a dTools aCad drawing (drawingB)
5) verify that drawingB has a layer: MY_LAYER and the color is set to 456
6) add productX to drawingB

what i would expect to happen:
drawingB retains color 456 for MY_LAYER

what happens instead:
drawingB adopts color 123 for MY_LAYER


When adding a block in autoCad, the matching layers of the added block should conform to that of the drawing. This may be modifiable as an autoCad setting, but dTools changes the drawing layer info when it shouldn't regardless of any autoCad settings. This bug appears in both autoCad 2008 and 2009.

additional note:
when adding a block directly from a library and THEN selecting a product, the layer color (and presumably other layer info) is retained correctly. THIS IS NOT AN ACCEPTABLE WORKAROUND, im simply stating it to point out that the dTools "add Product" routines are inconsistent. Layer information should be retained by the drawing and NOT adopted by blocks added to the drawing.

__________________
Systems Engineer Technician/Crestron Programmer
www.ccisolutions.com

Victorc

Richards,

Logged as a bug - We are going to work on it. Thanks for catching this.

__________________
Vic
D-sonic

fryeguy

While I'm no great programmer it sounds like you have code that actually affects the layer color when you should just leave it alone. Is that fair to say?

grichards

Originally Posted by Victorc

Logged as a bug

case number, please?

__________________
Systems Engineer Technician/Crestron Programmer
www.ccisolutions.com

NareshN

Richards,

Bug # 6197.

To keep you in the loop the fix in .Net code was not so simple so we deffered it till we had more time to test (next dev cycle).

When cloning blocks we have two options in the .Net API
1. DuplicateRecordCloning.Replace
2. DuplicateRecordCloning.Ignore

We use the first one which is basically a "deep clone" - which means that if the block exists in current drawing it will be replaced completely from source drawing. What this does as a side effect is that it also updates the color from the incoming drawing layer.

The other option (DuplicateRecordCloning.Ignore) fixes your issue - this would clone block if it did not already exist in the current drawing - otherwise not copy it over.

So we are thinking of adding a option to do this with a variable DTReplaceBlocks - possible values 1 and 0. 1 would completely replace the block as we do now and 0 would add block only if it did not exist.

This was not done as it came at the end of the SP2 cycle. We will look at this in the next cycle.