Increase skirt_loops max value to 1000000

[ANTONIOPSD]

Increased the maximum allowed value for skirt_loops from 10 to 1000000 to serve as an outer brim replacement in scenarios where Brim does not work.

Brim not working with Tree Slim supports:

Skirt works:

But sometimes you need more skirt loops, whether for personal reasons or specific scenarios you encounter, and you can't do it due to a software limitation:

[ianalexis]

Why? this eliminates the goal of having a cap.
Honest question.
Is there any purpose for a 10000 skirt loops besides wasting filament?

[ANTONIOPSD]

Why? this eliminates the goal of having a cap. Honest question. Is there any purpose for a 10000 skirt loops besides wasting filament?

Brim does not appear when using certain support configurations, and the only similar feature is the skirt, which can at least be used as an outer brim. You can already achieve something similar by adjusting the skirt distance, but this makes the skirt width vary depending on the object's size. With this method, you always get the same number of lines without having to calculate the skirt distance manually and sometimes 10 loops is not enought.

[ianalexis]

It would be nice to make the brim work but I don't see this as a bad option. I still wouldn't leave it at such a high value. Maybe 15 or 20 is more than enough.

[ANTONIOPSD]

It would be nice to make the brim work but I don't see this as a bad option. I still wouldn't leave it at such a high value. Maybe 15 or 20 is more than enough.

Yeah, but why impose a low limit at all? There are people out there who like to experiment with crazy values or have ultra thin "exotic" nozzles, and a high limit like 1000000 wouldn't cause any harm. Users can still select 15 if that's what they want.

Consider these two scenarios:

1. Limit at 10:

People need 10 loops → ✅

People need 1520 loops → ❌

2. Limit at 1000000:

People need 10 loops → ✅

People need 1520 loops → ✅

So, why choose scenario 1 over scenario 2? Is there any practical reason to do so?

[ianalexis]

Limits are not a bad thing.
In software development, many limits are placed to guide the user or help them avoid really unnecessary “excesses”.
I don't agree with giving a false sense of individual freedom in a generalist software which can generate problems or misuses.
For example OrcaSlicer is used a lot in school environments, can you imagine how much filament wasted by students covering the hot bed of material either trying in a wrong way to avoid a piece to peel off or some malicious reason?
Still my main point is that to place a 10000 limit we should directly remove or ignore the limit. For example it occurs to me as an improvement to make an option under Developer Mode that ignores all minimum and maximum limits.

[igiannakas]

I'd vote for keeping the limit but increasing it to a reasonable number - 10 perimeters gives a "brim" wide around 4mm. That is indeed borderline low if you're intending to use the skirt as a brim. Going to a at most 10cm wide -> 25 perimeter maximum equivalent should be plenty for any practical purpose I feel.

[Noisyfox]

Why not just use this option instead?

[SoftFever]

Why not just use this option instead?

This is the way :)

@ANTONIOPSD does this solve your use case? 
Increasing the limit to a very large number effectively makes the cap useless, so generally, we won't do that.