Support for FreeCAD 1.0 and later

[dprojects]

Note

Currently officially supported version is FreeCAD 1.0.1. However you still can use the fast and stable FreeCAD 0.21.2 version, I will try to keep backward compatibility as long as possible.

Caution

Currently unsolved known issues at FreeCAD 1.0.1:

• unsolved: units not works... for example if you change units "Edit -> Preferences -> General -> Default unit system -> Building" the units not change in the data object window... broken FreeCAD function Units.getSchema(), always return 10 but the last schema index is 9... workaround: change units via right bottom corner to get units working at once, without FreeCAD restart
• unsolved at FreeCAD 1.0.1, solved at FreeCAD 1.1.0devR41127: you can't select face, edge or vertex of Pad object inside LinkGroup container. If you have for example LinkGroup -> Part -> Body -> Pad and you click once the face, edge or vertex, the entire object will be highlighted. To highlight only the face, edge or vertex you have to hold left CTRL key and click twice but in this case FreeCADGui.Selection.getSelection() return empty list, so FreeCAD doesn't see this face, edge or vertex selected and tools not works. If you click many times, the selection jump between Pad, Body, Part, LinkGroup, and again Pad but not select the face, edge or vertex... there is no workaround for FreeCAD 1.0 but it is solved since FreeCAD 1.1.0dev.40971
  ( click here to see picture )

  
• unsolved: access to field .ViewObject for Measure::MeasureDistanceDetached object at scanObjects end up with FreeCAD 1.0 crash and core dump... this is related to access field .ViewObject.IV, workaround: not access this field
• unsolved: you can't move Sketch directly via magicMove, because they consider direct sketch move as bug...

Note

Currently solved known issues at FreeCAD 1.0.1:

• solved: there is problem with float precision for Transparency attribute at .ViewObject.ShapeAppearance[0].Transparency. If you assign float(83/100) the assigned value will be 0.8299999833106995 instead of 0.83. I fixed this in my code, to get it to work but if this problem is not only related to Transparency, it is extremely huge problem at FreeCAD 1.0.1...

Note

Currently solved known issues at FreeCAD 1.1 weekly:

• solved: at FreeCAD 1.1.0dev.40971 new PySide6 not allow to start GUI with QtGui.QComboBox: self.sMode.activated[str].connect(self.selectedOption), this impact almost all tools with it's own GUI
• solved: at FreeCAD 1.1.0devR41127 new PySide6 caused search filter at scanObjects tool to stop working
• solved: at FreeCAD 1.1.0devR41127 new PySide6 caused debugInfo tool to stop working
• solved: at FreeCAD weekly-builds-40655 also the transparent structure has been broken... for example during adding dowels the dowels are transparent, broken... this is strong issue because the green face at the dowels is telling about correct dowels rotation, for example if you want to replace them with screws later
  ( click here to see picture )

  
• solved: the TechDraw cut-list toPrint from getDimensions tool is too small...
• solved at FreeCAD 1.1.0devR41127: at FreeCAD 1.1.0dev.40971 removing empty LinkGroup container makes FreeCAD crash

Caution

Currently unsolved known issues at FreeCAD 1.0:

• unsolved at FreeCAD 1.0, solved at FreeCAD 1.1.0devR41127: you can't select face, edge or vertex of Pad object inside LinkGroup container. If you have for example LinkGroup -> Part -> Body -> Pad and you click once the face, edge or vertex, the entire object will be highlighted. To highlight only the face, edge or vertex you have to hold left CTRL key and click twice but in this case FreeCADGui.Selection.getSelection() return empty list, so FreeCAD doesn't see this face, edge or vertex selected and tools not works. If you click many times, the selection jump between Pad, Body, Part, LinkGroup, and again Pad but not select the face, edge or vertex... there is no workaround for FreeCAD 1.0 but it is solved since FreeCAD 1.1.0dev.40971
  ( click here to see picture )

  
• unsolved at FreeCAD 1.0, solved at FreeCAD 1.0.1: screws thread spike is broken at FreeCAD 1.0, the same example at FreeCAD 0.21.2 is fine, confirmed FreeCAD 1.0. bug and you can fix it manually only at weekly build
  ( click here to see picture )

  
• unsolved: access to field .ViewObject for Measure::MeasureDistanceDetached object at scanObjects end up with FreeCAD 1.0 crash and core dump... this is related to access field .ViewObject.IV, workaround: not access this field
• unsolved: you can't move Sketch directly via magicMove, because they consider direct sketch move as bug...

Note

Currently solved known issues at FreeCAD 1.0:

• solved, About solution: I added new button to get furniture color reference from face, I guess it is the only way to solve this issue if the FreeCAD no longer provide object color. Issue: for the example below, the white chipboard with black edgeband (edge around) the FreeCAD 1.0 returns black colors, so the getDimensions tool is not able to create cut-list with edgeband determined automatically because there is no white color reference anywhere at object, read more about this bug
  ( click here to see picture )

  
• solved, solved, About solution: PartDesign objects will be moved by default via Body container, the same solution is to move PartDesign objects via arrows. Issue: you can't move Pad by selecting Pad or Sketch at magicMove, because they consider direct sketch move as bug... you can move the Pad via magicMove only by selecting higher container, for example Body... however you still can move Pad via arrows...
• solved, solved About solution: colorManager tool has been replaced with new magicColors tool, also I made new color functions to communicate with FreeCAD 0.21.2 and FreeCAD 1.0+ color structure and changed all instances to color change... Issue: at FreeCAD 1.0 the colors are stored at .ViewObject.ShapeAppearance, so this change requires redesign of colorManager, MagicPanels copyColors functions and all Woodworking workbench color references...
• solved: they changed Sketch object field .Support to .AttachmentSupport, this stopped working all the Cube to Pad conversions...
• solved: they changed App::MeasureDistance object fields .P1 to .Position1, .P2 to .Position2 and also removed field .DistFactor
• solved: they also changed measurement objects type from App::MeasureDistance into Measure::MeasureDistanceDetached so the getDimensions cut-list tool is not able to list the custom measurement...
• solved: new colors impact scanObjects tool, so you can't preview colors per face because they are hidden behind Material structure...
  ( click here to see picture )

  
• solved: in magicMeasure at preselection mode the FreeCAD 1.0 crashes with core dump, for example, if you want to measure twice horizontal edge... this issue is related to FreeCAD automatic labeling bug, if you add the same label twice the FreeCAD 1.0 is not able to add next number to the label and crash, it has been solved at FreeCAD 1.1.0dev.40971 but I also fixed this for FreeCAD 1.0 to avoid crash.
• personal experience only: personally I don't like this new kind of dimension drawing, it's nice that a background was added, which makes the text more visible, but the removed guide lines were better in my opinion
  ( click here to see picture )

  
• working in a different way: you can't set alpha channel for face like it was in FreeCAD 0.21.2. Since new FreeCAD 1.0+ color structure you can set only Transparency attribute to make the face transparent. Read more about this FreeCAD new color structure here: Alpha channel for colors has not been implemented yet?
  ( click here to see picture )

  

[SnowBeaver]

Sorry to hear that. However, I have been using magicmMove with version 1.0 without problem. Anyway, I was writing about a bug with magicMeasure, as the tool do not measure a all and keeps generating Distance element in the TreeView.

If magicMove works with Freecad 1.0, will you consider supporting it?

Michel Belanger, Canada

[dprojects]

Anyway, I was writing about a bug with magicMeasure, as the tool do not measure a all and keeps generating Distance element in the TreeView.

I didn't test all features so carefully because I saw I can't move Sketch at FreeCAD 1.0 what makes the FreeCAD 1.0 useless for me. Please open new issue and describe it, maybe this bug is also at FreeCAD 0.21.2.

However, I have been using magicmMove with version 1.0 without problem.

At FreeCAD 1.0 you can't move Sketch by selecting it, or move Pad by selecting Pad. You can only move Sketch or Pad inside container, for example by selecting Body. But the bigger problem is their politics, they consider Sketch move as bug, so probably there will not be setGlobalPlacement() function for Sketch object.

If magicMove works with Freecad 1.0, will you consider supporting it?

If someone find it working, it is fine to me. But I can't recommend FreeCAD 1.0.
FreeCAD is released with AppImage so you can have more than one version of FreeCAD at your system.

Sorry to hear that.

Yes it is little sad but I guess the Woodworking workbench should be rather considered as new different product dedicated for woodworking but based on FreeCAD kernel. Woodworking workbench has too much features to be always up-to-date with any FreeCAD changes.

But maybe someday the FreeCAD kernel will be upgraded from 0.21.2 into something above 1.0.
Currently I want to focus on make the Woodworking workbench stable with FreeCAD 0.21.2 kernel and create maybe some more useful features. I think chasing all FreeCAD changes is not good approach.

[SnowBeaver]

I understand your position, Woodworking is a tool for yourself and it does not really matter which Freecad version you are using.

As for the problem using magicMeasure, it is easy to reproduce in FC 1.0 as it does not work at all. I simply click on the tool and the mearements keep showing 0,000.

Michel

[dprojects]

Woodworking is a tool for yourself and it does not really matter which Freecad version you are using.

It is natural process, more features you have, more problematic is to keep all the features in sync with other dependent software, especially if they don't care about backward compatibility. So maybe it is time to go with my own way...

As for the problem using magicMeasure, it is easy to reproduce in FC 1.0 as it does not work at all. I simply click on the tool and the mearements keep showing 0,000.

Currently I am going to add new feature "Mirror Copy" to magicMove to be able to copy part of the furniture with Edge selection... Also I want to add possibility to create drawers in series.

However, I don't say no to FreeCAD 1.0 fixes. They change Sketch.Support into Sketch.AttachmentSupport so the Cube ->Pad conversion wasn't possible at FreeCAD 1.0 but I made small fix and now this working in FreeCAD 0.21.2 and also in FreeCAD 1.0. If the same will be possible with magicMeasure I will do it.

[SnowBeaver]

I started using your workbench once FC 1.0 was released. Before FC 1.0, FC was too buggy and I did not bothered to seriously try workbenches. I imagine other users will do the same. The video you made help a lot. The doc itself is harder to follow. Anyway, for me the video made a difference. Excelent tool overall.

I am building a cabinet (3 meters x 2 meters) for my daughter, and one new feature I would appreciate is the ability to copy a cabinet section and change one of its dimension. At the moment, I can copy a cabinet section, but to change the cabinet dimension requires to modify each panel one by one. May be it can be already done with one of your tools but reading through the docs, that function did not appear to be available?

I tried to update your workbench but nothing was avalable. Your update have not been publish yet I assume?

Michel

[dprojects]

I started using your workbench once FC 1.0 was released. Before FC 1.0, FC was too buggy and I did not bothered to seriously try workbenches.

There is no code without bug. Bug can be opportunity for nice useful feature, like for example direct Sketch move.

I imagine other users will do the same.

If they only looking for FreeCAD version number, not for doing something useful, probably yes.

I am building a cabinet (3 meters x 2 meters) for my daughter, and one new feature I would appreciate is the ability to copy a cabinet section and change one of its dimension.

You can share your project file at FreeCAD forum so maybe I will be to look at it and maybe improve the Woodworking workbench to make it more easier to do. This issue is related only for FreeCAD 1.0. However you can also open new issue and share your file there.

to change the cabinet dimension requires to modify each panel one by one

It is FreeCAD feature, yOu can hold left-CTRL to select more panels and change the dimensions in FreeCAD Data window. You don't need special tool for that.

I tried to update your workbench but nothing was avalable. Your update have not been publish yet I assume?

Currently I am during magicMove improve, it is not submitted yet. I don't know when it will be available.

[dprojects]

As for the problem using magicMeasure, it is easy to reproduce in FC 1.0 as it does not work at all.

Because they changed measurement objects fields from .P1 into .Position1 and the .P2 into Position2. I have already added support measurement for FreeCAD 1.0 and now it is working in hover off mode. But personally I like the FreeCAD 0.21.2 version much more because at FreeCAD 1.0 there is no lines above, it is flat at the object, harder visible at edge...

I simply click on the tool and the mearements keep showing 0,000.

However, you are the lucky one because for me in hover on mode the FreeCAD 1.0 crashes, probably adding and removing objects in Tree is changed as well... as I mentioned before, they also changed Sketch.Support to Sketch.AttachmentSupport.

Don't get me wrong, but I don't recommend anyone to use FreeCAD 1.0... it's really ridiculous, it seems like they've never heard of backward compatibility...

[SnowBeaver]

I can understand the despair feeling seeing your work ruined by unconsidered development rules. Where can I get your recommended FC version?

…

On Sun, Jan 19, 2025, 09:07 Darek L ***@***.***> wrote: As for the problem using magicMeasure, it is easy to reproduce in FC 1.0 as it does not work at all. Because they changed measurement objects fields from .P1 into .Position1 and the .P2 into Position2. I have already add support measurement for FreeCAD 1.0 <10c971b> and now it is working in hover off mode. I simply click on the tool and the mearements keep showing 0,000. However, you are the lucky one because for me in hover on mode the FreeCAD 1.0 crashes, probably adding and removing objects in Tree is changed as well... as I mentioned before, they also changed Sketch.Support to Sketch.AttachmentSupport. Don't get me wrong, but I don't recommend anyone to use FreeCAD 1.0... it's really ridiculous, it seems like they've never heard of backward compatibility... — Reply to this email directly, view it on GitHub <#49 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADQ3R6QW2KHQ35UTORHPKH32LOWQZAVCNFSM6AAAAABTV7DUPKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBQHA3TMNBZHE> . You are receiving this because you commented.Message ID: ***@***.***>

[dprojects]

I can understand the despair feeling seeing your work ruined by
unconsidered development rules.

They ruined many workbenches and macros for sure, not only my work, by creating new objects fields without linking the old names to the new one. But looks like they don't care about it. It is little strange because why they allow for python scripting? and making macros and workbenches if they "just changing" fields names? I don't understand their politics... sounds like joke to me...

Where can I get your recommended FC version?

It is described at main page... FreeCAD 0.21.2 but maybe I should release my own product because you never know what they have in mind and who paid them...

[txtinman]

I use FC only for woodworking projects. The woodworking workbench makes it much easier for me to design my projects. I don't care what version of FC you use. If you create a separate application then I will use it.

[dprojects]

I use FC only for woodworking projects. The woodworking workbench makes it much easier for me to design my projects. I don't care what version of FC you use. If you create a separate application then I will use it.

It's no problem to have version AppImage 0.21.2 for Woodworking workbench purposes and version AppImage weekly for other purposes. I personally have several versions of AppImage under the Xubuntu operating system and there are no problems with it. However, I don't see anything interesting in the new version of FreeCAD 1.1 that would somehow enhance furniture creation.

Support for higher versions of FreeCAD 1.1+ will be considered, but first I would like to do some more functionalities that are useful in practice and improve the documentation a bit, so that it is all at a stage that I consider cool and worthy of a new stable version. Then I will release another version 0.23 based on the FreeCAD 0.21.2 kernel and then I will start thinking about support for newer versions of FreeCAD.

However, the problem of supporting FreeCAD 1.0 has highlighted the problem of the FreeCAD team's politics that has been there for a long time since I started creating any macros. I don't want to go into details here and accuse anyone... but sometimes I have the impression that the FreeCAD team feels great injustice and even hatred towards anyone who creates some valuable macro or workbench just on the basis of "because it's not ours"...

That's why I don't know if it wouldn't be better to completely cut myself off from these people... and run my own project... I'm still thinking about it, but for now I'm doing what I like the most, which is programming, creating new functionalities, inventing new solutions, making work easier for myself and others...

Perhaps it would be better if Woodworking workbench attracted only people who are looking to do something practical in the real world, design and make some furniture, than those who install Woodworking workbench just for the version number...

BTW: I used Google Translate to make it faster, because I have to go and finish a new feature...

[awschult002]

I don't know if this falls into the bucket of 1.0 support or not; but for my workflow, I really really need assemblies. Is there anyway to get the containers for pre-made furniture into a freeCad Assembly structure? This would allow super fast work of TechDraw blueprints and exploded views.

[dprojects]

I don't know if this falls into the bucket of 1.0 support or not; but for my workflow, I really really need assemblies. Is there anyway to get the containers for pre-made furniture into a freeCad Assembly structure? This would allow super fast work of TechDraw blueprints and exploded views.

This is not related to supporting a new version of the FreeCAD kernel, just new functionality. So, I created new issue and I will answer there.