FreeCAD News

This week in FreeCAD development:

Topon­am­ing: bgb­sww fin­ished trans­fer­ring the code to solve the save/restore errors with objects with ele­ment maps, this did away with 3 release blockers.

BIM: hase­cilu, Roy_043, paullee0, and cjmayo fixed sev­er­al bugs, includ­ing one blocker.

FEM: marioalexis84 fixed a bug where the work­bench would spill red ink into the Report View about linked objects when mesh­ing, and fan­daL fixed a bug where the FemMesh2Mesh tool didn’t work with quad elements.

Assem­bly: Pad­dle­Stroke made it pos­si­ble to edit joints by dou­ble-click­ing them in the 3D view. He also reworked assem­bly prop­er­ties to store the full path to objects so that two iden­ti­cal objects could be dif­fer­en­ti­at­ed; this resolves anoth­er release blocker.

Mate­ri­als: dav­es­rock­et­shop fixed two block­ers relat­ed to set­ting cus­tom col­or to objects.

GUI:

• 3x380V added a workaround for miss­ing cus­tom cur­sors on Way­land when build­ing FreeCAD with Qt6.
• Syres916 synced ‘Pref­er­ences > Dis­play > UI’ page with actu­al defaults for new users: some check­box­es had incor­rect states, one check­box was missing.
• kadet1090 fixed var­i­ous small cos­met­ic issues with the Pref­er­ences dia­log, such as incor­rect padding, incon­sis­tent align­ment, hor­i­zon­tal scroll­bars that should not be present etc.

Among oth­er changes:

• NewJok­er added a miss­ing 2D mesh­ing algo­rithm, Qua­si-struc­tured Quad, to the Gmsh mesh­er in the Mesh WB.
• Wan­der­erFan fixed a loop in Tech­draw dur­ing the cal­cu­la­tion of the auto­mat­ic scale.
• Roy_043 fixed a snap-at-inter­sec­tion bug that would cause the infi­nite hang­ing of the program.
• pieter­hi­j­ma fixed the use of the ‘–sin­gle-instance’ com­mand line argu­ment on Win­dows so that new files would always be opened in the already run­ning instance of FreeCAD.

PR stats: since the pre­vi­ous report, 33 pull requests have been merged, 14 new pull requests have been opened.

Issue stats: 1839 issues are cur­rent­ly open, 20 issues up from last week. Of those, 35 issues still block the v1.0 release — 4 up from last week.