Support for AutoCAD Associative Hatches

Feature Overview

The ability for the PowerDWG Translator to automatically translate Associative Hatches from AutoCAD into PowerCADD Hatch patterns..

Feature Description:

Currently, the PowerDWG Translator shipping with PowerCADD v7 does not translate Associative Hatch patterns from AutoCAD. If the objects in AutoCAD have an Associative Hatch assigned, the resulting object in PowerCADD has no hatch pattern at all. The feature request is essentially broken into two parts:

Part 1: Minimum Requested Functionality
At a minimum, the PowerDWG Translator should translate the AutoCAD Associative Hatch into basic PowerCADD Objects. Currently the Associative Hatches from AutoCAD are simply ignored increasing editing time to recreate the drawing look and feel.

Part 2: Ideal Functionality
In a perfect world the AutoCAD Associative Hatches should be translated into PowerCADD Associative Hatches. The new (AutoCAD) hatch pattern would be appended to the PowerCADD Document's Hatch Palette. These Hatch patterns should be translatable round trip; they would be maintained when saving PowerCADD drawings as DWG and when importing DWG drawings from AutoCAD.

Current Work Arounds
In order to have AutoCAD DWG file Associative Hatches translate into PowerCADD:

  1. Open the drawing in AutoCAD
  2. Explode the Associative Hatches
  3. Save a copy of the AutoCAD DWG file
  4. Open the file from (3) in PowerCADD
  5. Result: the AutoCAD hatch pattern becomes basic objects in PowerCADD

The work around can be time consuming and does require additional steps which can only be carried out in AutoCAD. However, in those cases where it's important to maintain the same look and feel between AutoCAD and PowerCADD, the fix works and may be worth the additional effort.

Cast your vote using the link below
Don't see the voting link? Log in to vote.

Poll Choices are:

  • Very Important Feature: you think the feature is a big deal and has a big impact to your workflow
  • Important Feature: not critical to your workflow but something you'd find useful or would explore more deeply if it was there
  • Not an Important Feature: this feature wouldn't impact your workflow at all and you're not interested or don't see value in exploring it

If you found this article or the website in general to be helpful, educational or a time and money saver you can show your support. Thank you ~ Brian (huc) Huculak

No votes yet