Collecting Input: Array Command

I've seen this in another program, and it would come in handy for sure......

I know we could just move the array, but I think it would be helpful to specify "left, right, up, down" from the starting point? Being able to do this with the arrow keys, perhaps?

This would be really useful for landscaping takeoffs, good for visualizing plant spacing layouts. One thing that could be added is the ability to apply this to a defined takeoff area, similar to how the Grid/Joist/Beam tool would probably work.

Thanks for the input. What is the highest realistic number of repeat X or repeat Y that would be needed? For example, if a user selects a point count and duplicates it 100x100 that's 10,000 points and that will take a while to save and hammer our servers pretty good. What max do you think is realistic?

Hi Heber,

I would not let users go anywhere near 100 × 100 by default.

For a construction takeoff workflow, a realistic max depends on what is being arrayed:

For most normal use

Linear repeat X or Y: cap at 200

Grid array: cap at 50 × 50 = 2,500 instances

That already covers almost all real-world estimating cases without being silly.

My practical recommendation

Set two limits:

Soft limit

Warn user once they go above:

100 in one direction

or 1,000 total instances

Hard limit

Do not allow more than:

250 in one direction

or 2,500 total instances

That feels like the sweet spot.

Why 2,500 total is realistic

In your type of work, users are usually arraying:

piers

pads

trench points

setout points

repetitive footing elements

grids for layout

Even large residential or light commercial jobs usually do not need 10,000 individually saved duplicated objects from one command. At that point it stops being normal user intent and starts becoming either:

accidental input

misuse

or a case better handled by a smarter pattern/reference object instead of raw duplication 

Best product rule

I would use this:

Hard cap:

Max 2,500 generated objects per array action

Warning zone:

Over 1,000 generated objects show warning:

“This array will create 1,248 objects and may be slow to save.”

Absolute emergency cap:

5,000 objects max only if you really want to be generous

But honestly I would still prefer 2,500. 

My honest recommendation

If this is v1, use:

Max Repeat X: 100

Max Repeat Y: 100

Max total generated objects: 2,500

Warning at: 1,000

That gives flexibility while protecting performance.

So even if someone enters 100 × 100, the system blocks it because it exceeds total object cap.

Even better for users

In the dialog, show live:

Selected objects: 12

Repeat X: 8

Repeat Y: 6

Total result: 576 objects

That will stop a lot of accidental server abuse before it happens.

My bottom-line answer: 2,500 total generated objects is the highest realistic hard cap, with a warning from 1,000 upward.

Would this be for a count only or could this also be applied to a segment line?

@Camille This could apply to areas, linears, segments, or almost any other type of object on the page (including if you have multiple selected at the same time).

Can I use the array based on an area so I can calculate roof sheet lengths. For a hip or raking roof

Can you add the option for a negative number in the repeat X and repeat Y fields? Right now you can only array to the right and/or down.

@Fred, I was able to use the "minus" key to make this happen.....

I tried that and it gives me an error message.

@Fred, I gave this a whirl again today. It is working for me when I use the array command from the "Spacebar" menu. Also, one of my estimators told me to just use the "arrow" key. I don't know why I haven't tried that, but it works well to. This made counting parking stall striping, and utilities slick today.

Good input guys. The next update will allow you to put negative values either in the "offset" or "repeat" inputs.

@Fred and @Brendon We also have a joist tool coming out in the next that will make what you're doing a lot easier as well.