Combine Paper & Model Space

Feature Overview

The ability to combine AutoCAD model space and paper space when reading DWG^? files.

Feature Description:

Currently, the PowerDWG Translator has unofficial support for combining AutoCAD Model Space and Paper Space entities with translating a file as noted in this article. We'd like to see support for that unofficial feature formalized and automatically combine Model Space and Paper Space entities (or give us the choice) when reading (opening) a DWG file.

On the surface the feature request may seem simple. However, among the various technical hurdles this request has, one of the biggest issues we can see is what happens when there are multiple view ports in the AutoCAD DWG file, where each one might contain distinct Paper Space elements? How should the PowerDWG Translator handle that condition?

• Should it it create one new PowerCADD file for each viewport?
• Should each view port become a distinct sheet setup in PowerCADD, thereby allowing the common Model Space data to be used and a distinct layer (or layers) be made for the Paper Spaceentities?
• Are there other practical alternatives?

Cast your vote using the link below

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

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

Support for AutoCAD Xrefs

Feature Overview

The ability for the PowerDWG Translator to automatically bind AutoCAD Xrefs when translating a file

Feature Description:

Currently, the PowerDWG Translator External provides a warning dialog if the DWG file being translated contains Xref's. While this is a helpful warning, advising us that the translation will be incomplete, it requires translating each referenced drawing separately. The resulting individual files have to manually reassembled which can be difficult, or in some cases impossible due to a lack of common reference points in each file.

The only current work around is to have the original AutoCAD drawing author use the Bind Xref to make a single file for translation. In some cases, particularly on large scale projects with multiple consultants, this level of coordination is difficult as it requires additional steps by the coordinating consultant.

The fact PowerCADD knows which Xref drawing is missing is a big steps and tells us it knows the content exists... now the next logical step is to just include in the translation. A simple thing to say and we're sure quite a difficult thing to achieve but one that would be a significant step in cross platform coordination on large and small projects.

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