2016-06-10 12:32 AM
2016-06-15 01:37 AM
rob2218 wrote:Initial irony aside (totally in on a parasol joke)...
come on GS, please....
2016-06-15 01:43 AM
2016-06-15 01:44 AM
Anton wrote:rob2218 wrote:Initial irony aside (totally in on a parasol joke)...
come on GS, please....
Can you elaborate what is wrong?
Can we start with a simple one to get it going? What does bug you about pens?... not trying to start a flame war, just want to know what pens did or didn't do for you.
2016-06-15 02:27 AM
rob2218 wrote:Actually I can imagine. I actually looked at out-of-the-box linework issues with doors and windows recently... they are all wrong with cut lines in wrong places line weights messed up... etc., the issue here is not with pens that are very simple to use and set up, but with default ARCHICAD template (that is simply horrendous) and errors in pen assignments within window/door library parts.
I have a hard time understanding the "pen assinged" to objects rationale.
You can't imagine how many times I've been repremanded for having window sills read very boldly and the wall edges read too lightly.....
just should be easier to use all those 256 pens and pen combinations.
2016-06-15 05:00 AM
2016-06-15 05:19 PM
2016-06-15 05:53 PM
rob2218 wrote:I agree and I don't understand that ether.
..it's a nightmare where an OOTB software should come with some semblance of a good lineweight basic setup.
2016-06-16 06:26 PM
2016-06-16 07:05 PM
Ransom wrote:Than you for official input on this.
But we should also notice that different markets have different localization teams and different OOTB content.
For example, your screenshot might not reflect the American pen table and library that Rob and Jeff are seeing OOTB.
Ransom wrote:My pen table does not reflect any standard pen table. 🙂 It is the one I put together on a whim to test broken library parts/macros-related issues.
For example, your screenshot might not reflect the American pen table and library that Rob and Jeff are seeing OOTB.
Ransom wrote:Yes, they are complex and no, there should not be mistakes like that in a commercially available product. It took me an hour or two to trace and fix all errors in all door/window macros in the INT version. I think GS QA staff can do the same.
Windows are very complex and there are mistakes and unintended consequences.