A new user.cfg is written in any case if you close FreeCAD. That vanilla user.cfg is the problem. If you restart FreeCAD using that user.cfg you still have the same issue. Yes. Just found that it needs to be set by ok-ing preferences. After that the user.cfg contains the precision preference set to...

The author of the DraftGui.py must have intended that the number of decimals would be governed by some parameter "precision": self.xValue.setDecimals(Draft.getParam("precision")) Not the same precision as the dimensions it seems. Trying to figure out how this works. The Draft.py reads "precision" as...

I agree with Roy_043 that the scale factor should not be affected by the precision settings for dimensions at all. The best thing would be to enable expressions in the scale factor input (eg. to write 1/3). I did change the code in my copy (DraftGui.py line 2296, 2303, 2310) to always use 6 decimals...

It takes almost 1/3 of my screen

Not mine. Might be that I am not logged in to the bug tracker. I just googled the problem and found the bug report.

I have reopened the ticket.

Good.

Thanks!

1 No it does not work. Works as it should. You probably have set the number of decimals wrong. This is then a problem with the default settings. I have not changed any setting. Just downloaded and installed the latest version on a computer with no previous version installed. 2 I did not submit the b...

Just found this bug issue #0003691 using version 0.18.15780 of FreeCAD.
So I start a discussion here as directed.

microelly2 wrote: ↑

Wed Jun 01, 2016 9:55 am

Is there still some activity and newer results on this image2 wb?

Otherwise I would "merge" it into my reconstruction wb

No no activity...
Made a small bugfix as I revisited the WB yesterday. Thats it for the last 2 years...

Separating organizing tools from creation tools in the tool bar would be a good thing. I also thought that floor was for creating floors when I first used Arch.

Thanks! Hello, In your case I think it is best to create your object directly from DocumentObject. Than you just add a Placement property to your object directly. In your viewprovider you watch for changes of the pacement property, and if one happens you simply update a Transform node you have added...