Since I opened a github account today, I reported the issue.
Kind regards
Peter
Search found 76 matches
- Sat Apr 15, 2023 2:22 pm
- Forum: Draft, Arch & BIM
- Topic: Bug or feature? Folder may not be hidden by spacebar
- Replies: 9
- Views: 1746
- Sat Apr 15, 2023 7:59 am
- Forum: Draft, Arch & BIM
- Topic: PropertyPythonObject::toString(): failed for <class 'pFeatures.ViewProviderPypeLine'>
- Replies: 7
- Views: 1113
Re: PropertyPythonObject::toString(): failed for <class 'pFeatures.ViewProviderPypeLine'>
Thanks for the instructions!
I have proceeded as described.
Best regards
Peter
I have proceeded as described.
Best regards
Peter
- Wed Apr 12, 2023 7:58 pm
- Forum: Draft, Arch & BIM
- Topic: Arch/TechDraw: Strange behavior of marking/hovering in View
- Replies: 9
- Views: 1176
Re: Arch/TechDraw: Strange behavior of marking/hovering in View
I set it to 10 decimal places now. Note, when a value have the unit m, then 10 digits can be still to less for 10^(-7)mm, if it is on the edge. Right, I later had the thought that I could have added a few more zeros to it. Besides, there are much more preciser industries (5mm is for me very rough),...
- Wed Apr 12, 2023 6:05 pm
- Forum: Draft, Arch & BIM
- Topic: Arch/TechDraw: Strange behavior of marking/hovering in View
- Replies: 9
- Views: 1176
Re: Arch/TechDraw: Strange behavior of marking/hovering in View
I see only three decimal places. Then set it in the preferences higher. The OCCT kernel of FreeCAD need a minimum precision around 10^(-7)mm to work properly. I set it to 10 decimal places now. This has the advantage that deviations from the pattern of chains of zeros are easily noticed. So you can...
- Wed Apr 12, 2023 3:21 pm
- Forum: Draft, Arch & BIM
- Topic: Arch/TechDraw: Strange behavior of marking/hovering in View
- Replies: 9
- Views: 1176
Re: Arch/TechDraw: Strange behavior of marking/hovering in View
Thank you very much!
I have revised it again and now I can't find any inaccuracies. There might be some, though, because marking some walls and some surfaces does not work in View as expected.
I see only three decimal places.
Many greetings
Peter
I have revised it again and now I can't find any inaccuracies. There might be some, though, because marking some walls and some surfaces does not work in View as expected.
I see only three decimal places.
Many greetings
Peter
- Wed Apr 12, 2023 12:03 pm
- Forum: Draft, Arch & BIM
- Topic: Arch/TechDraw: Strange behavior of marking/hovering in View
- Replies: 9
- Views: 1176
Re: Arch/TechDraw: Strange behavior of marking/hovering in View
Thank you for the reply. I had also noticed the inaccuracies, which I have since eliminated as far as apparent. The marking of the vast majority of walls in View is now fine. Some things that are currently still "therapy resistant" (e.g.areas). I still have to get to the bottom. Many greet...
- Tue Apr 11, 2023 5:56 pm
- Forum: Draft, Arch & BIM
- Topic: Arch/TechDraw: Strange behavior of marking/hovering in View
- Replies: 9
- Views: 1176
Arch/TechDraw: Strange behavior of marking/hovering in View
OS: Debian GNU/Linux 11 (bullseye) (XFCE/xfce) Word size of FreeCAD: 64-bit Version: 0.20.1.29410 (Git) AppImage Build type: Release Branch: (HEAD detached at 0.20.1) Hash: f5d13554ecc7a456fb6e970568ae5c74ba727563 Python 3.10.5, Qt 5.15.4, Coin 4.0.0, Vtk 9.1.0, OCC 7.6.2 Locale: German/Germany (de...
- Mon Apr 10, 2023 4:50 pm
- Forum: Draft, Arch & BIM
- Topic: PropertyPythonObject::toString(): failed for <class 'pFeatures.ViewProviderPypeLine'>
- Replies: 7
- Views: 1113
Re: PropertyPythonObject::toString(): failed for <class 'pFeatures.ViewProviderPypeLine'>
Thank you very much! :D The error messages have disappeared! Because of one missing colon after (self, data), here the complete correct code of the region: class ViewProviderPypeLine: def __getstate__(self): return None def __setstate__(self, data): return None def __init__(self,vobj): vobj.Proxy = ...
- Mon Apr 10, 2023 3:05 pm
- Forum: Draft, Arch & BIM
- Topic: PropertyPythonObject::toString(): failed for <class 'pFeatures.ViewProviderPypeLine'>
- Replies: 7
- Views: 1113
Re: PropertyPythonObject::toString(): failed for <class 'pFeatures.ViewProviderPypeLine'>
Thank you very much for your answer! At what point do you get these errors? When trying to save the project (or when auto-saving is done)? Correct, when trying to save the project or when auto-saving is done. The string "ViewProviderPypeLine" occurs not in the Document.xml but five times i...
- Mon Apr 10, 2023 4:05 am
- Forum: Draft, Arch & BIM
- Topic: PropertyPythonObject::toString(): failed for <class 'pFeatures.ViewProviderPypeLine'>
- Replies: 7
- Views: 1113
PropertyPythonObject::toString(): failed for <class 'pFeatures.ViewProviderPypeLine'>
OS: Debian GNU/Linux 11 (bullseye) (XFCE/xfce) Word size of FreeCAD: 64-bit Version: 0.20.1.29410 (Git) AppImage Build type: Release Branch: (HEAD detached at 0.20.1) Hash: f5d13554ecc7a456fb6e970568ae5c74ba727563 Python 3.10.5, Qt 5.15.4, Coin 4.0.0, Vtk 9.1.0, OCC 7.6.2 Locale: German/Germany (de...