We have implemented the generation of PDF files from .dwg files.
However, in some cases, some layers are missing.
We are using the version 23.6.0
and the conversion is done as followed :
using (var cadImage = (CadImage)Aspose.CAD.Image.Load(msSource))
{
var layers = new List<string>();
foreach (CadLayerTable layer in cadImage.Layers)
{
layers.Add(layer.Name);
}
var rasterizationOptions = new Aspose.CAD.ImageOptions.CadRasterizationOptions()
{
DrawType = CadDrawTypeMode.UseObjectColor,
PageWidth = cadImage.Width,
PageHeight = cadImage.Height,
UnitType = cadImage.UnitType != Aspose.CAD.ImageOptions.UnitType.Unitless ? cadImage.UnitType : cadImage.UnitlessDefaultUnitType,
};
cadImage.Save(msTarget, new Aspose.CAD.ImageOptions.PdfOptions()
{
VectorRasterizationOptions = rasterizationOptions,
Layers = layers.ToArray(),
});
}
Could you tell me what is missing ?
Thanks.
You’ll find attached an example file where the layer “*LayerNameForDynamicConstraint” is missing.
mechanical_example-imperial.zip (46.1 KB)
@pvanloo,
we checked this case and saw that mentioned layer is not missing at export. But it contains only entities (dynamic dimensional constraints) that were not designed to be plottable. The file does not contain enough information to plot them properly. So it seems the only way to export them is to convert to regular dimensions.
Thank you Oleskii for your answer.
Therefore, could you tell how it is possible to export such layer.
In fact, if I open this document with other tools, such as All in pdf or ShareCAD, this layer is correctly displayed.
Kind regards,
Patrick
@pvanloo
We will consider the implementation of support for these entities, but AutoCAD, ODA Viewer, DWGSee don’t plot them too Please share the file with the expected result from any other tool.
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): CADNET-9371
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
The issues you have found earlier (filed as CADNET-9371) have been fixed in this Aspose.CAD for .NET 23.10 update. This message was posted using Bugs notification tool by oleksii.gorokhovatskyi