General rotation function

[Anonymous]

Is there a simple way to rotate any object/wall/slab/geometry on any axis or combination of axes? I have been assuming there was and that I just hadn't located the button yet but I'm beginning to think that is an incorrect assumption.

I know you can rotate a beam by typing in a slope. Is there any common function or button that works on any geometry to rotate the item in the x, y and z axes?

[Dwight]

That is great!

Your move, even tho it is complex, combines so many things!

I never considered what SEO "intersection" might mean.

Ooo, baby!!!

[__archiben]

Dwight wrote:
Ooo, baby!!!

just don't be looking for a floor plan drawing at the same time though!

[Dwight]

Floor Plans are for minions.

[Laszlo Nagy]

~/archiben wrote:
definitely a wall - you can still put windows and doors in . . .

b

Good stuff!

[Anonymous]

WOW! Lot's of great responses. The pictures help so much on seeing what ArchiCAD is capable of in experienced hands. My goal was to use the circular slab at a 90 degree angle as an SEO operator to cut an arch in a wall and then save that shape as a GDL model. So far my work arounds to issues like this always fall back on "write the object with GDL".

Whenever I create an object just to use it in an SEO operation is it bad to delete the object once the operation is performed? I see alot of references on the forums to simply placing the object on a hidden layer.

Also, do more practiced users tend to use SEO's for alot of their needs or create objects with scripting/modeling? So far I find it easier to create the object through scripting. But it seems like I should be more comfortable with SEO's and that SEO's would work quicker than writing several lines of code to get a desired shape.

[Dwight]

My advice is that if an element exists in the library, you should use it.
Writing code is very time consuming.

In this case, the easiest solution if you aren't putting a window in your disk is the cylinder 11 object. It tilts to any angle without distorting.

Deleting an SEO operator eliminates the operation but it remains valid if hidden. I think. But SEO is inefficient from a 3D imaging POV since there are extra steps for the model.

As for writing the object, unless there is a productivity payback or a specific technical requirement, why would you bother?

[Laura Yanoviak]

To repeat Dwight's answers, phrased a little differently:

Seraphim wrote:
Whenever I create an object just to use it in an SEO operation is it bad to delete the object once the operation is performed? I see alot of references on the forums to simply placing the object on a hidden layer.

Do not delete the operator, it will void the SEO. We have a layer, A-Work-SEOs for operators we want to keep hidden, the layer is hidden in all output Layer Combinations.

Seraphim wrote:
Also, do more practiced users tend to use SEO's for alot of their needs or create objects with scripting/modeling? So far I find it easier to create the object through scripting. But it seems like I should be more comfortable with SEO's and that SEO's would work quicker than writing several lines of code to get a desired shape.

If it's a one-off situation, model the Object. If it's an Object you may get a lot of use out of in multiple Projects, or you need the Object to be parametric, definitely script it (if you know how).