Search found 214 matches

Go to advanced search

by rynn
Tue Nov 17, 2020 1:17 pm
Forum: Part Design module development
Topic: Hole dialog discussion
Replies: 123
Views: 5050

Re: Hole dialog discussion

- While implementing this, I found out that we did not support the sizes M4.5, M7 and M39, They are normed and you can buy screws in that size, e.g. here M39: https://schraube-mutter.de/schrauben/m39/ I added these sizes with the PR. Metric coarse threads are divided into 3 series/rows. One should ...
by rynn
Sat Nov 14, 2020 11:04 am
Forum: Part Design module development
Topic: Hole dialog discussion
Replies: 123
Views: 5050

Re: Hole dialog discussion

I had a look at the norms, and they only define screw heads, not how the holes for a countersink/bore must look. Please have a look at "DIN 74 countersinks for countersunk head screws" and including DIN ISO 20273. The problem is, these cost a fortune: DIN 74 (42,88 €) and DIN EN 20273 (30,23 €) Tha...
by rynn
Fri Nov 13, 2020 4:11 pm
Forum: Part Design module development
Topic: Hole dialog discussion
Replies: 123
Views: 5050

Re: Hole dialog discussion

chrisb wrote:
Fri Nov 13, 2020 3:54 pm
These translations are done via Crowdin.
These names are read on runtime from files. I don’t know enough about the freecad Enumeration classes, that are used here, to give a based opinion, but I doubt translation is possible here without major changes in the code.
by rynn
Wed Nov 11, 2020 8:45 pm
Forum: Part Design module development
Topic: Hole dialog discussion
Replies: 123
Views: 5050

Re: Hole dialog discussion

rynn wrote:
Wed Nov 11, 2020 1:46 pm
The problem is, that it’s not possible to have cut-profiles with the same name for different thread-types. (p.e. “DIN 912” for metric and “DIN 912” for metric fine.)
This is the result of an implementation-detail and should be fixed.
Fixed in PR #4041 (hopefully)
by rynn
Wed Nov 11, 2020 1:46 pm
Forum: Part Design module development
Topic: Hole dialog discussion
Replies: 123
Views: 5050

Re: Hole dialog discussion

Implementation-detail. This should be fixed. What exactly? I cannot see a problem so far. The problem is, that it’s not possible to have cut-profiles with the same name for different thread-types. (p.e. “DIN 912” for metric and “DIN 912” for metric fine.) This is the result of an implementation-det...
by rynn
Wed Nov 11, 2020 8:07 am
Forum: Part Design module development
Topic: Hole dialog discussion
Replies: 123
Views: 5050

Re: Hole dialog discussion

uwestoehr wrote:
Wed Nov 11, 2020 12:09 am
Why must this be unique?
Implementation-detail.
This should be fixed.
by rynn
Tue Nov 10, 2020 9:06 pm
Forum: Part Design module development
Topic: Hole dialog discussion
Replies: 123
Views: 5050

Re: Hole dialog discussion

uwestoehr wrote:
Tue Nov 10, 2020 2:54 am
I added with the PR 3 files with values for ISO fine type.
That’s not working. You gave the profiles the same name as the coarse versions but the names must be unique.
As far as I can see ISO 7462 has no fine threads that’s ISO 12474.
by rynn
Tue Nov 10, 2020 12:23 pm
Forum: Part Design module development
Topic: Hole dialog discussion
Replies: 123
Views: 5050

Re: Hole dialog discussion

There are CPP changes and I don't have a nice dev environment set up to test this. Once this is merged and ends up in the the freecad-daily PPA, I am happy to go through and add some more JSON definitions. It is merged and as far as I know it is in the 0.19_pre AppImages https://github.com/FreeCAD/...
by rynn
Tue Nov 10, 2020 12:16 pm
Forum: Part Design module development
Topic: Hole dialog discussion
Replies: 123
Views: 5050

Re: Hole dialog discussion

For a predefined cutting (screwtype), I think the user should be: | Type | able to change | able to change | able to change | | | diameter | depth | angle | |-------------+----------------+----------------+----------------| | counterbore | not usefull | usefull | does not apply | |-------------+----...
by rynn
Tue Nov 10, 2020 9:18 am
Forum: Part Design module development
Topic: Hole dialog discussion
Replies: 123
Views: 5050

Re: Hole dialog discussion

What is the purpose of the file "iso14583part.json". I thought it is only a part of the norm and you were lazy to add the larger sizes. Then I realized that it means partial depth. Can we therefore rename it? For example to "ISO 14583 (partial depth)". The json-files I provieded are more or less ex...

Go to advanced search