Window objects section attributes and SEO's bug

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2005-12-29
10:23 AM
- last edited on
2023-05-24
12:47 PM
by
Rubia Torres
2005-12-29
10:23 AM
I just now realized the walls that were ignoring SECT_FILL all used SEO's to define roof gables shapes. Deleting the SEO operation on the wall restored the correct section attributes to the window.
Has anyone else run up against this? The only solution I could find was to use Trim to Roof instead of SEO's, which doesn't interfere with the window object section attributes.
David Collins
Win10 64bit Intel i7 6700 3.40 Ghz, 32 Gb RAM, GeForce RTX 3070
AC 27.0 (4001 INT FULL)
Win10 64bit Intel i7 6700 3.40 Ghz, 32 Gb RAM, GeForce RTX 3070
AC 27.0 (4001 INT FULL)
1 REPLY 1
Anonymous
Not applicable
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2006-01-05 01:47 AM
2006-01-05
01:47 AM
David,
I run into this behavior all the time.
I had not noticed the consistency you note when windows
are in walls that are participating in an SEO.
I encounter this behavior in many contexts and find no patterns.
One recent example is a "Beam" object's Sect_Fill
command is ignored but if the section line is given a small jog
the problem goes away. Or, another example, a solid object
made with the Prism_ command has it's Sect_Fill command ignored
but if the the object's settings dialogue is opened and without changing
anything click OK the object behaves itself for a while, sometimes.
There was an issue for a while about Sect_Fill commands being
ignored after a "Call" is issued in the script but this has been fixed.
Peter Devlin
I run into this behavior all the time.
I had not noticed the consistency you note when windows
are in walls that are participating in an SEO.
I encounter this behavior in many contexts and find no patterns.
One recent example is a "Beam" object's Sect_Fill
command is ignored but if the section line is given a small jog
the problem goes away. Or, another example, a solid object
made with the Prism_ command has it's Sect_Fill command ignored
but if the the object's settings dialogue is opened and without changing
anything click OK the object behaves itself for a while, sometimes.
There was an issue for a while about Sect_Fill commands being
ignored after a "Call" is issued in the script but this has been fixed.
Peter Devlin