Ryan Rutledge, CID+

I very strongly agree. For two-checkpoint merges, at least, sigmoid can give drastically better merges. I understand 3-ckpt merges may only be possible with weighted sum, but supporting 3-ckpt merges...

What @hentailord85ez said is accurate, so maybe it's a matter of training the users and adding some explanation in the merge tab. In reality this is just bending the curve...

Ultimately, sigmoid gives you more fine control of weighting at the extremes _for the slider's 0.05 step size_, and inverse sigmoid gives you more fine control of the weighting around...

I think you mean Batch _count_ not working, then. :) Normally I wouldn't nitpick but since there is also a "Batch size" parameter that you are _not_ referring to, I...

> For situations like this one, there will likely be some cases where users prefer a customized script which works slightly different from native functionality which could arguably supersede the...

Initial thoughts: If QuickSilk was used to place the text initially, then the autoposition location can be inferred from the text's current justification setting (Solution 1). That's the easy case....

Solution 1: - Pros: - Easy and likely to give good outcomes - Cons: - Relies on text justification to infer placement if the tool is to be single-click (otherwise...

@dsicon the way it would work with #1 is if you use QuickSilk to, say, place the silkscreen text in the "Left-Below" octant around the part, the positioned text would...

I think the results in the rightmost column below make the most sense: 

@dsicon the "autoposition" property in this context is how Altium's internal algorithm places the designator around the part. The key interaction between this and what QuickSilk does (and how I...