Itoo Software Forum

RailClone => RailClone Pro (*) => Topic started by: QE2393 on August 11, 2015, 01:59:06 AM

Title: How to create basic 2D array - distributed using pivot
Post by: QE2393 on August 11, 2015, 01:59:06 AM
I want to create a simple 2d array which distributes an object in both X and Y at a fixed interval based on the object's pivot.  I know I can do this using X evenly using the Distance rule.  The distance rule uses the pivot for it's calculations.  However I only set the distance this way on one axis. 

To create spacing on the other axis, I have to use segment padding.  This works but it's not very elegant since it is based on the size of the object rather than distributing it based on its pivot like the old-fashioned max array tool.  How can I get a 2d array with distances based on the object pivot only?
Title: Re: How to create basic 2D array - distributed using pivot
Post by: Rokas on August 11, 2015, 04:53:12 AM
You have option for x and y axis to use evenly distance parameter:
(http://i.imgur.com/pyaWVwk.png)
Title: Re: How to create basic 2D array - distributed using pivot
Post by: Paul Roberts on August 11, 2015, 06:20:35 AM
Hi,

If you'd like to control the distance from the pivot for the X and Y axis at the same time it is possible by setting the segment's X and Y Alignments to Pivot and then enter the smallest value you can in the Fixed Size property for the X and Y axis.

(http://i.imgur.com/Ej3xh4Y.png)

You can then use the Right and Top Padding values to simulate distance. I've attached an example that demonstrates how RailClone can be used as a parametrised version of Max's Array.

I hope that helps, please let me know if you have any further questions.

Many thanks,

Paul
Title: Re: How to create basic 2D array - distributed using pivot
Post by: QE2393 on August 11, 2015, 09:44:00 PM
Rokas; using x and y evenly together does not work for this application.  It does not create a simple 2d array like Max's built-in command. 

Paul -- your technique is exactly what I was looking for.  Thank you.  If this is not in the docs you should consider adding it -- it isn't an obvious solution. At least not for me.