Very nice update Michael, as always. I guess V1.0 is coming really soon !!!

Hehe new powerful function!
Speed of releasing betas is like Bip Bip and the wolf coyote :D

Update french version for perfectionnist!
Just one accent replaced :D
Unzip it and replace FrenchString in folder C:..\Program Files\MoI beta Mar-9-2007\ui

Woaw ! Just terrific !
I've been playing with it for an hour now and it's sooo incredible. So easy to create complex objects. And FUN ! ;-))
A major update in my opinion.

Hi,

great new beta. I like the new boolean possibilities.

As far as i can see there are no new text string to translate?

MfG
sk2k

> As far as i can see there are no new text string to translate?

Nope, no text changes for this version.

- Michael

Just a precision about all combinaisons between "2 solides" using the Boolean Intersection "merge" :)

Little test of functions of Mr George B 1814-1875 :)

Hi Pilou, looks like you are having fun with booleans!

One interesting thing is that history will work for the case of boolean intersection between auto-extruded curves, so if you turn on control points and edit the curves for your intersection case, you should see the object update.

This is because this particular case does not delete any input objects, it only creates new objects. Deletion of the input objects is what normally breaks history right now.

- Michael

Hi Pilou, here is an example.

2 Circles, 90 degrees from one another:



Select one of them, then run Boolean intersection, then select the other one and push Done to generate this result by auto-extrude:




Because the original curves are still around and have not been deleted, you can turn on control points for either one and edit it and the intersection will update:



- Michael

Ah ! I have made that with a curve and a solid and not with 2 curves !

Yes, the solid as an input doesn't work with history right now, because that original solid gets deleted.

But with 2 curves none of the inputs are deleted - this is the case that works with history right now.

- Michael

This is a very cool trick. I have so much to learn about nurbs...

Hi Joe, that is not about mystery of NURBS, but rather about Michael's astonishing skills! -Petr

Some quick notes...

-Now, when comming boolean curves, it proved to be very useful that Invert command works from within other running command like Trim or Boolean.

-Updated/fixed "gizmo" for rotating background image looks good and works fine.

-Thanks for implementing a way to turn off points by pushing Esc key. Priceless!

Petr

Trivial question but...

As the first choice for a boolean Intersection seems give different results :)
why with a same "first start"
order for choice of the "second set" give a same result!
Star / Circle / Polygon = Star / Polygon / Circle : is that normal?
Anxious rationalist :D

For intersection, multiple objects within a single set are first unioned together into a single object, and then those 2 unioned results are then intersected with each other.

Does that explain what you are seeing there?

For intersecting 3 objects in that way you may want to do that with 2 separate runs of the boolean intersection command, or possibly use merge mode instead.

- Michael

:)
Not posted the following so there

I have 3 objects, but in reality we can put any numbers of object for "the second set"!
So that I ask if the order of selection of objects has or has not importance for end intersection (first being selected) :)

> So that I ask if the order of selection of objects has or has not importance
> for end intersection (first being selected) :)

I don't think it should make any difference.

The thing that makes a difference is what set you put the "extra" object in.

For instance if the 2 sets are ( 1 2 ) isect ( 3 ) or ( 1 ) iset ( 2 3 ), that can make a difference.

- Michael