Soften coplanar ?

jolran

@unknownuser said:

We have updated docs pending for release.

That's awesome news!

@unknownuser said:

entities.fill_faces_from_mesh(mesh, true, 2 |

Right. Will try that.

I persume you mean one can choose between 2 or 8, not apply expression in argument?

jolran

fill_faces_from_mesh ? Typo ?

jolran

2 | 8
Expression it is! Yei! It works.

Dan Rathbun

| is the Integer BITWISE OR operator (really method name.)
Both subclasses ( Fixnum & Bignum) have this method.
see:
http://www.ruby-doc.org/core-1.8.6/Fixnum.html#method-i-7C

Dan Rathbun

Also there are many API methods that allow bit mask Integer arguments, where you can combine different bit flags using **|**.

Some are not documented, like the 2nd arg to UI.messagebox can also (in addition to the button flag,) be OR'd with an icon integer flag that sets which standard icon (or none,) is displayed in the messagebox.

jolran

ahh, nice info. I've used bitwise in JavaScript ( for performance reason ). Good to know they work in Ruby as well.

@unknownuser said:

Some are not documented, like the 2nd arg to UI.messagebox can also (in addition to the button flag,) be OR'd with an icon integer flag that sets which standard icon (or none,) is displayed in the messagebox.

How the heck do you guys know all this ?
Must spend a lot of time experimenting outside the docs..

tt_su

Heh! Docs? The docs where in a very poor state five/size years ago. Poking about was the way to go.
(Not saying that the docs now are "good" or anything though... ...just that they where a lot worse.)

tt_su

@jolran said:

fill_faces_from_mesh ? Typo ?

Yes - should be "fill_from_mesh". Just love the consistency of the Ruby API naming...

jolran

@unknownuser said:

Yes - should be "fill_from_mesh". Just love the consistency of the Ruby API naming...

I had to ask, thought there where some new hidden stuff

tt_su

Yes, you never know.

jolran

entities.fill_from_mesh(mesh, true, 2 | 8) is working nicelly, but a small gotcha..

%(#FF0000)[mesh.add_polygon(1,2,3)
mesh.add_polygon(2,3,4)]

Does gives hard edges, as expected.

%(#FF0000)[mesh.add_polygon(1,-2,3)
mesh.add_polygon(-2,3,4)]

gives hard soft edge between Points 2, as expected.

but so does this:

%(#FF0000)[mesh.add_polygon(1,2,3)
mesh.add_polygon(-2,3,4)]

or

%(#FF0000)[mesh.add_polygon(1,-2,3)
mesh.add_polygon(2,3,4)]

So I'm starting to see some trouble with this method. To be able to stear edge visibility one need to use 2 Points in comparison. For ex a Collection of edge.start and end positions.
For a triangulated quad this works but not if the face has innerloops,
Or faces where triangulation is splitting the face without hitting innerloops.

Was to fast here..
The docs actually explains this behavior, "value of [-1, 2, 3] indicates that the edge from 1 to 2 is hidden"