Marionette Script runs differently if it's a wrapper or not

[Xavi1]

Hi Everybody. The Problem is that, if the Marionette Script isn't a Wrapper, it works right. If it is a Wrapper, it does something totally different. very strange. I added the file

Thanks for helping me

[SBarrettWalker]

Hello - I checked this file out and the issue seems to come from the offset poly. you have two different operations performed on this single object - planar boolean and extrude. Because of this the definition will react differently within a wrapper. A wrapper changes the hierarchy of operations within a definition - it can't hold off performing operations til the end of a definition. For example, using the delete node within a wrapper can cause a problem - its best to create an output for the object to be deleted and attach the delete node outside of the wrapper.

For this definition, if you make a copy of the offset poly and use one for the boolean and one for the extrude you should be fine.

Let me know if that works!

-Sarah

[Xavi1]

Hello, It works better and allmost right but not at all. I think the new Problem is the Planar Boolean. After the substraction, within a wrapper, i have two surfaces to extrude instead of one. Is There no possibility to delete only one of them?

Sorry for my terrible English.

-Xavi

[SBarrettWalker]

I am not sure why the boolean node is keeping the rectangles when it is in the wrapper, but I added a few nodes to isolate and delete them within the wrapper.

[Xavi1]

Thank you very much!

Xavi

[ScottBFM]

Has anybody encountered a situation in which the script works the same when it's in a wrapper, but differently when the wrapper is converted into an object node?

I'm testing out marionette and trying to put together a very rudimentary tool for 2d window elevations, and when I wrap this script and then convert to an object node, it starts to behave differently. I think it has something to do with the origin input in the very beginning but am not sure.

[Marissa Farrell]

@ScottBFM:

The problem isn't with the origin input, it appears to be with the "move" command. I'm not sure why this doesn't work well with Marionette Objects, but I have attached a revised network that when you convert to an object node looks as expected.

In order to accomplish this, I added to the initial origin to offset the following rectangles. Take a look and let me know if you have any questions.

Thanks!

Marissa

[ScottBFM]

Thanks for your help Marissa!

In the revision you've attached, the object node works except when you try to change the frame and sash. I'm assuming the dim nodes titled Frame and Sash need to be connected to the origin in order to center under the original rectangle, or perhaps by somehow using the center point output of the getRectangle node.

This is why I had posted on the other thread about centering/aligning etc., it seems like there would be some unnecessary scripting involved in getting the rectangles to align responsively.

[Marissa Farrell]

So in this case, the "origin" refers to one of the corners of the rectangle - with this file, it is the bottom left of the rectangles.

In order to have everything grow together, we need to create more relationships.

Let me put together another example (I should have it ready and posted by tomorrow, latest).

I would not have taken the center point approach, personally, but I can mock up an example using that method as well.

Thanks for your patience!

Marissa

[Marissa Farrell]

Tried to upload this yesterday... But this one behaves better.

[ScottBFM]

Marissa, this is fantastic. Thanks again!

[drfoulk@gmail.com]

Can you wrap a network inside a wrapper to create a hierarchy of operations, or???

Edited April 11, 2021 by drfoulk@gmail.com