2010-04-16 03:01 AM
2010-04-16 12:19 PM
2010-04-17 04:27 AM
2010-04-19 04:44 AM
2010-04-19 04:52 AM
Piotr wrote:It's not the assignment of elements to storeys that is the issue. It's that the "Edit Story Levels" process changes the elevation of the adjusted storey's elements, so they remain in the same position, relative to the adjusted level.
Change the story of the element from "automatic" and hardlink it to the story You need.
2010-04-19 08:12 PM
peter_h wrote:An hour spent cleaning up multiple stories of incorrectly placed elements does not seem excessive to me. It also seems that the auto-adjustment would not work with elements that were incorrectly assigned. Elements on the wrong story would get the wrong delta.
Matthew: In my case, as I described in my first post, it hasn't been "trivial": 5 storeys, all with different heights relative to each other and all different from the project I pulled it from. Plus finding and adjusting the elements that were incorrectly assigned to the wrong storey, and hence were caught in the "select all on this storey" process but shouldn't have been. Plus the post-process cross-checking to make sure everything was as it was, in relation to each other.
I spent atleastan hour on doing this, so I wouldn't call it trivial.
And by comparison, I'd argue - having a good deal of programming experience - that the programming to include this option is a rather trivial matter. Particularly, if you compare it against the sum of all the time that all users have to spend doing adjusting elements after such a shift in storey levels.If it is truly trivial to implement then it might well be worthwhile, but I also have a fair amount of programming experience and I wouldn't presume to know how much difficulty there would be in writing back a change in elevation to all the elements on each of the altered stories, nor what complex ramifications this might have. For example, if this were implemented would there also be a restriction to apply the change only to the current selection/marquee?
The trade off of one-time "programming resources spent" vs. multiple "users productivity gained" would make this a no-brainer, in my opinion.
2010-04-20 07:07 PM
Matthew wrote:It's one of my biggest issues with ArchiCAD too, and I think it's going to be a staple of BIM tool simply because the concept of BIM is all about making changes to large collections of data in arbitrary ways, and with a heavy focus on GUI tools many of these functions will be invisible to the end user.
I generally distrust automatic functions that act invisibly on large numbers of elements. The potential for inadvertent errors seems too high. This is one of my biggest issues with Revit.
2010-04-30 05:12 AM
2010-04-30 05:13 AM
2010-04-30 05:14 AM