I have a fix for the scale of the presets on the pre-4.2 code locally, but haven’t tested it yet. I haven’t looked into updating this here yet. I’ll keep you posted.
@sw-tya, It looks like you have a good handle on this. I look forward to seeing your PR for it.
Modifying the inputs to include an angle as one of the inputs was part of a larger change I was working on, but turned out to be more involved, so I hadn't planned on backporting that part. I…
The preset values that are stored in the folder /addons/presets/operator/mesh.bolt_add are inputting values into the dialog box using mm rather than m. This means that the change presented…
This is a great reference, and I may actually use it in further enhancements I began working on.
I do think we should definitely support up to M160 or 160 mm, but I am hesitant to make this a…
I searched for all props that already had division by GLOBAL_SCALE somewhere in the file with the following regex:
bf_(12_Point_(HeadPractically 250 would be a better limit as that would cover anything that I have seen in agriculture.
Looking at the drivel on Wikipedia I got a bit bored and resorted to ChatGPT which said…
@lichtwerk, yes, I saw #84782, agreed it would be included in fix-set, but somehow let it fall on the floor. My mistake. Good catch.
Been a busy week here, possibly won’t get to review this…
@nickberckley suggested that this should be considered for #LTS36
(@brecht, ChatGPT seems to think that you’re Primary Person Responsible for 3.6 LTS maintenance, so I’m tagging you in this…
I didn’t even think of 3.6… good catch… I was just wanting to address the overall issue count. Who is the 3.6 LTS maintainer so we can bring this to their attention?
@nickberckley, what should happen to these two issues now that they are addressed in the other repo?