View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4793 [FreeCAD] Bug crash always 2021-11-28 16:25 2022-02-14 15:09
Reporter: will1 Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 0.19  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
FreeCAD Information: OS: void (Sway)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.2.2_voidlinux
Build type: Release
Python version: 3.10.0
Qt version: 5.15.2
Coin version: 4.0.0
OCC version: 7.4.0
Locale: English/United States (en_US)
Summary: FreeCAD crashes when trying to create a new file in sway wm
Description: when using sway window manager in linux I get a crash when I do `File > New` with the output:

FreeCAD 0.19.2, Libs: 0.19.2R2_voidlinux
© Juergen Riegel, Werner Mayer, Yorik van Havre and others 2001-2021
FreeCAD is free and open-source software licensed under the terms of LGPL2+ license.
FreeCAD wouldn't be possible without FreeCAD community.
  #####                 ####  ###   ####  
  #                    #      # #   #   # 
  #     ##  #### ####  #     #   #  #   # 
  ####  # # #  # #  #  #     #####  #   # 
  #     #   #### ####  #    #     # #   # 
  #     #   #    #     #    #     # #   #  ##  ##  ##
  #     #   #### ####   ### #     # ####   ##  ##  ##

connect failed: No such file or directory
Program received signal SIGSEGV, Segmentation fault.
#0  /usr/lib/libc.so.6(+0x3d000) [0x7ff4af357000]
#1  /usr/lib/libX11.so.6(XDefaultScreenOfDisplay+0) [0x7ff4acf552e0]
0000002  /usr/lib/libCoin.so.80(+0x458c2e) [0x7ff4aeeb3c2e]
0000003  /usr/lib/libCoin.so.80(glxglue_init+0x3c) [0x7ff4aeeb44dc]
0000004  /usr/lib/libCoin.so.80(cc_glglue_instance+0x122) [0x7ff4aeead002]
0000005  0x7ff4aed3dbe8 in SoGLRenderActionP::isDirectRendering(SoState const*) const from /usr/lib/libCoin.so.80+0x48
0000006  0x7ff4aed3ff53 in SoGLRenderActionP::render(SoNode*) from /usr/lib/libCoin.so.80+0xc3
0000007  0x7ff4aed395c2 in SoAction::apply(SoNode*) from /usr/lib/libCoin.so.80+0x2d2
0000008  0x7ff4b1c1e5f9 in Gui::SoBoxSelectionRenderAction::apply(SoNode*) from /usr/lib/freecad/lib64/libFreeCADGui.so+0x29
0000009  0x7ff4b1cc2833 in Gui::View3DInventorViewer::renderScene() from /usr/lib/freecad/lib64/libFreeCADGui.so+0x143
0000010  0x7ff4b1c8a415 in SIM::Coin3D::Quarter::QuarterWidget::paintEvent(QPaintEvent*) from /usr/lib/freecad/lib64/libFreeCADGui.so+0x275
0000011  0x7ff4b1c90282 in SIM::Coin3D::Quarter::SoQTQuarterAdaptor::paintEvent(QPaintEvent*) from /usr/lib/freecad/lib64/libFreeCADGui.so+0x42
0000012  0x7ff4b057c03e in QWidget::event(QEvent*) from /usr/lib/libQt5Widgets.so.5+0x1ce
0000013  0x7ff4b06244de in QFrame::event(QEvent*) from /usr/lib/libQt5Widgets.so.5+0x1e
0000014  0x7ff4afa11f03 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) from /usr/lib/libQt5Core.so.5+0x93
0000015  0x7ff4b053c16e in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /usr/lib/libQt5Widgets.so.5+0x6e
0000016  0x7ff4b1a05328 in Gui::GUIApplication::notify(QObject*, QEvent*) from /usr/lib/freecad/lib64/libFreeCADGui.so+0x88
0000017  0x7ff4afa1219a in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /usr/lib/libQt5Core.so.5+0x12a
0000018  0x7ff4b0574166 in QWidgetPrivate::sendPaintEvent(QRegion const&) from /usr/lib/libQt5Widgets.so.5+0x36
0000019  0x7ff4b05749b2 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags<QWidgetPrivate::DrawWidgetFlag>, QPainter*, QWidgetRepaintManager*) from /usr/lib/libQt5Widgets.so.5+0x7f2
0000020  0x7ff4b0575d03 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, QFlags<QWidgetPrivate::DrawWidgetFlag>, QPainter*, QWidgetRepaintManager*) from /usr/lib/libQt5Widgets.so.5+0x503
0000021  0x7ff4b05746cc in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags<QWidgetPrivate::DrawWidgetFlag>, QPainter*, QWidgetRepaintManager*) from /usr/lib/libQt5Widgets.so.5+0x50c
0000022  0x7ff4b0575d03 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, QFlags<QWidgetPrivate::DrawWidgetFlag>, QPainter*, QWidgetRepaintManager*) from /usr/lib/libQt5Widgets.so.5+0x503
0000023  0x7ff4b05746cc in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags<QWidgetPrivate::DrawWidgetFlag>, QPainter*, QWidgetRepaintManager*) from /usr/lib/libQt5Widgets.so.5+0x50c
0000024  0x7ff4b0575d03 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, QFlags<QWidgetPrivate::DrawWidgetFlag>, QPainter*, QWidgetRepaintManager*) from /usr/lib/libQt5Widgets.so.5+0x503
0000025  0x7ff4b05746cc in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags<QWidgetPrivate::DrawWidgetFlag>, QPainter*, QWidgetRepaintManager*) from /usr/lib/libQt5Widgets.so.5+0x50c
0000026  0x7ff4b0575d03 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, QFlags<QWidgetPrivate::DrawWidgetFlag>, QPainter*, QWidgetRepaintManager*) from /usr/lib/libQt5Widgets.so.5+0x503
0000027  0x7ff4b05746cc in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags<QWidgetPrivate::DrawWidgetFlag>, QPainter*, QWidgetRepaintManager*) from /usr/lib/libQt5Widgets.so.5+0x50c
0000028  /usr/lib/libQt5Widgets.so.5(+0x173810) [0x7ff4b054c810]
0000029  0x7ff4b057c767 in QWidget::event(QEvent*) from /usr/lib/libQt5Widgets.so.5+0x8f7
0000030  0x7ff4b053c17f in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /usr/lib/libQt5Widgets.so.5+0x7f
0000031  0x7ff4b1a05328 in Gui::GUIApplication::notify(QObject*, QEvent*) from /usr/lib/freecad/lib64/libFreeCADGui.so+0x88
0000032  0x7ff4afa1219a in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /usr/lib/libQt5Core.so.5+0x12a
0000033  0x7ff4afa14bd1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) from /usr/lib/libQt5Core.so.5+0x171
0000034  /usr/lib/libQt5Widgets.so.5(+0x475933) [0x7ff4b084e933]
0000035  0x7ff4afa3e1c1 in QObject::event(QEvent*) from /usr/lib/libQt5Core.so.5+0x291
0000036  0x7ff4b053c17f in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /usr/lib/libQt5Widgets.so.5+0x7f
0000037  0x7ff4b1a05328 in Gui::GUIApplication::notify(QObject*, QEvent*) from /usr/lib/freecad/lib64/libFreeCADGui.so+0x88
0000038  0x7ff4afa1219a in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /usr/lib/libQt5Core.so.5+0x12a
#39  0x7ff4afa14bd1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) from /usr/lib/libQt5Core.so.5+0x171
#40  /usr/lib/libQt5Core.so.5(+0x306ef3) [0x7ff4afa69ef3]
0000041  /usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x25b) [0x7ff4ad54ec0b]
0000042  /usr/lib/libglib-2.0.so.0(+0x53eb8) [0x7ff4ad54eeb8]
0000043  /usr/lib/libglib-2.0.so.0(g_main_context_iteration+0x2f) [0x7ff4ad54ef6f]
0000044  0x7ff4afa6957f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /usr/lib/libQt5Core.so.5+0x5f
0000045  0x7ff4afa10b4b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) from /usr/lib/libQt5Core.so.5+0x12b
0000046  0x7ff4afa18dd0 in QCoreApplication::exec() from /usr/lib/libQt5Core.so.5+0x90
0000047  0x7ff4b197af68 in Gui::Application::runApplication() from /usr/lib/freecad/lib64/libFreeCADGui.so+0x1978
0000048  FreeCAD(+0x4954) [0x55bdd297a954]
0000049  /usr/lib/libc.so.6(__libc_start_main+0xea) [0x7ff4af341e0a]
0000050  FreeCAD(+0x4c4a) [0x55bdd297ac4a]
Tags:
Steps To Reproduce: Install FreeCAD from the void repository, open it in sway window manager, create a new file
Additional Information:
Attached Files:
Notes
(0017119)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6288.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4450 [FreeCAD] Bug major always 2020-10-03 19:29 2022-02-07 03:44
Reporter: mozarelo Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: feedback Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 0.20  
FreeCAD Information: OS: Windows 7 SP 1 (6.1)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.22522 (Git)
Build type: Release
Branch: master
Hash: d8e476ef428017900dfe0f9359ba448503c216f9
Python version: 3.8.5
Qt version: 5.12.6
Coin version: 4.0.0
OCC version: 7.4.0
Locale: Russian/Russia (ru_RU)
Summary: When running FC 0.19 on Windows 7, it returns errors in the Report window
Description: Each time it starts, it outputs:

23:00:50 OpenGL version is: 4.5 (4.5.0 NVIDIA 347.52)
23:00:50 Run Gui init script
23:00:51 Init: Running FreeCADGuiInit.py start script...
23:00:51 Init: Searching modules...
23:00:51 Init: Initializing C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\AddonManager... done
23:00:51 Init: Initializing C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\Arch... done
23:00:51 Init: Initializing C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\Complete... done
23:00:51 Init: Initializing C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\Draft... done
23:00:51 Init: Initializing C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\Drawing... done
23:00:51 Init: Initializing C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\Fem... done
23:00:51 Init: Initializing C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\Idf(InitGui.py not found)... ignore
23:00:51 Init: Initializing C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\Image... done
23:00:52 Init: Initializing C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\Import... done
23:00:52 Init: Initializing C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\Inspection... done
23:00:52 Init: Initializing C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\Material... done
23:00:52 Init: Initializing C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\Measure(InitGui.py not found)... ignore
23:00:52 Init: Initializing C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\Mesh... done
23:00:52 Init: Initializing C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\MeshPart... done
23:00:52 Init: Initializing C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\OpenSCAD... done
23:00:52 Init: Initializing C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\Part... done
23:00:52 Init: Initializing C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\PartDesign... done
23:00:52 Init: Initializing C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\Path... done
23:00:52 Init: Initializing C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\Points... done
23:00:52 Init: Initializing C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\Raytracing... done
23:00:52 Init: Initializing C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\ReverseEngineering... done
23:00:52 Init: Initializing C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\Robot... done
23:00:52 Init: Initializing C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\Show(InitGui.py not found)... ignore
23:00:52 Init: Initializing C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\Sketcher... done
23:00:52 Init: Initializing C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\Spreadsheet... done
23:00:52 Init: Initializing C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\Start... done
23:00:52 Init: Initializing C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\Surface... done
23:00:53 Init: Initializing C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\TechDraw... done
23:00:53 Init: Initializing C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\Test... done
23:00:53 Init: Initializing C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\Tux... done
23:00:53 Init: Initializing C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\Web... done
23:00:53 Module: Part
23:00:53 Loading Part module... done
23:00:53 Init: Initializing C:\Users\Ultranemo\AppData\Roaming\FreeCAD\Mod\A2plus... failed
23:00:53 ----------------------------------------------------------------------------------------------------
23:00:53 Traceback (most recent call last):
  File "<string>", line 127, in InitApplications
  File "<string>", line 233, in <module>
  File "<string>", line 47, in __init__
  File "C:\Users\Ultranemo\AppData\Roaming\FreeCAD\Mod\A2plus\a2plib.py", line 35, in <module>
    import numpy
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\site-packages\numpy\__init__.py", line 140, in <module>
    from . import core
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\site-packages\numpy\core\__init__.py", line 101, in <module>
    from . import _internal
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\site-packages\numpy\core\_internal.py", line 14, in <module>
    import ctypes
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\ctypes\__init__.py", line 468, in <module>
    GetLastError = windll.kernel32.GetLastError
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\ctypes\__init__.py", line 443, in __getattr__
    dll = self._dlltype(name)
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\ctypes\__init__.py", line 373, in __init__
    self._handle = _dlopen(self._name, mode)
OSError: [WinError 87] Параметр задан неверно
23:00:53 ----------------------------------------------------------------------------------------------------

23:00:53 During initialization the error "[WinError 87] Параметр задан неверно" occurred in C:\Users\Ultranemo\AppData\Roaming\FreeCAD\Mod\A2plus\InitGui.py
23:00:53 Please look into the log file for further information

23:00:53 Init: Initializing freecad.asm3
23:00:54 During initialization the error "[WinError 87] Параметр задан неверно" occurred in freecad.asm3
23:00:54 --------------------------------------------------------------------------------
23:00:54 Traceback (most recent call last):
  File "<string>", line 152, in InitApplications
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\importlib\__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
  File "<frozen importlib._bootstrap>", line 991, in _find_and_load
  File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 671, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 783, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\site-packages\freecad\asm3\init_gui.py", line 3, in <module>
    from .utils import mainlogger as logger
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\site-packages\freecad\asm3\utils.py", line 11, in <module>
    import numpy as np
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\site-packages\numpy\__init__.py", line 140, in <module>
    from . import core
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\site-packages\numpy\core\__init__.py", line 101, in <module>
    from . import _internal
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\site-packages\numpy\core\_internal.py", line 14, in <module>
    import ctypes
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\ctypes\__init__.py", line 468, in <module>
    GetLastError = windll.kernel32.GetLastError
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\ctypes\__init__.py", line 443, in __getattr__
    dll = self._dlltype(name)
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\ctypes\__init__.py", line 373, in __init__
    self._handle = _dlopen(self._name, mode)
OSError: [WinError 87] Параметр задан неверно
23:00:54 --------------------------------------------------------------------------------

23:00:54 Init: Initializing freecad.asm3... failed
23:00:54 --------------------------------------------------------------------------------
23:00:54 Traceback (most recent call last):
  File "<string>", line 152, in InitApplications
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\importlib\__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
  File "<frozen importlib._bootstrap>", line 991, in _find_and_load
  File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 671, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 783, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\site-packages\freecad\asm3\init_gui.py", line 3, in <module>
    from .utils import mainlogger as logger
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\site-packages\freecad\asm3\utils.py", line 11, in <module>
    import numpy as np
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\site-packages\numpy\__init__.py", line 140, in <module>
    from . import core
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\site-packages\numpy\core\__init__.py", line 101, in <module>
    from . import _internal
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\site-packages\numpy\core\_internal.py", line 14, in <module>
    import ctypes
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\ctypes\__init__.py", line 468, in <module>
    GetLastError = windll.kernel32.GetLastError
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\ctypes\__init__.py", line 443, in __getattr__
    dll = self._dlltype(name)
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\ctypes\__init__.py", line 373, in __init__
    self._handle = _dlopen(self._name, mode)
OSError: [WinError 87] Параметр задан неверно
23:00:54 --------------------------------------------------------------------------------
23:00:54 Init: Loading FreeCAD GUI
23:00:54 Init: Running FreeCADGuiInit.py start script... done
23:00:56 Init: Activating default workbench StartWorkbench
23:00:56 Loading GUI of Web module... done
23:00:56 Loading GUI of Start module... done
23:00:56 Loading Start module... done
23:00:56 Installed Qt WebEngine locales directory not found at location C:/FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64/translations\qtwebengine_locales. Trying application directory...
23:00:56 Qt WebEngine locales directory not found at location C:/FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64/bin\qtwebengine_locales. Trying fallback directory... Translations MAY NOT not be correct.
23:00:56 Init: Showing main window
23:00:56 Main window restored
23:00:56 Show main window
23:00:56 Toolbars restored
23:00:56 3Dconnexion device not attached.
23:00:56 Init: Entering event loop
23:00:56 Init: Processing command line files


The Part Design and Path workbenches do not work and also give errors. And Part Design at each choice, and Path only the first time, then it writes that the workbench Path activated, but also does not work.

This gives out Part Design:

23:04:22 Hide main window
23:04:41 Show main window
23:04:51 Hide main window
23:05:11 Show main window
23:05:15 Hide main window
23:05:51 Show main window
23:06:01 Hide main window
23:06:31 Show main window
23:10:44 Loading Sketcher module... done
23:10:44 Loading PartDesign module... done

23:10:44 [WinError 87] Параметр задан неверно
23:10:44 Traceback (most recent call last):
  File "<string>", line 42, in Initialize
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\PartDesign\WizardShaft\WizardShaft.py", line 27, in <module>
    from .Shaft import Shaft
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\PartDesign\WizardShaft\Shaft.py", line 25, in <module>
    from .SegmentFunction import SegmentFunction, IntervalFunction, StressFunction, TranslationFunction
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\PartDesign\WizardShaft\SegmentFunction.py", line 25, in <module>
    import numpy as np
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\site-packages\numpy\__init__.py", line 140, in <module>
    from . import core
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\site-packages\numpy\core\__init__.py", line 101, in <module>
    from . import _internal
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\site-packages\numpy\core\_internal.py", line 14, in <module>
    import ctypes
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\ctypes\__init__.py", line 468, in <module>
    GetLastError = windll.kernel32.GetLastError
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\ctypes\__init__.py", line 443, in __getattr__
    dll = self._dlltype(name)
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\ctypes\__init__.py", line 373, in __init__
    self._handle = _dlopen(self._name, mode)


This outputs Path for the first time:

23:14:17 Loading Path module... done
23:14:17 Loading PathStock... done
23:14:17 Loading GUI of Part module... done
23:14:17 Loading GUI of Path module... done
23:14:17 Loading PathToolControllerGui... done
23:14:17 Loading PathToolController... done
23:14:17 Loading PathJobCmd... done
23:14:17 Loading PathToolBitCmd... done
23:14:17 Loading PathToolBitLibraryCmd... done

23:14:17 [WinError 87] Параметр задан неверно
23:14:17 Traceback (most recent call last):
  File "<string>", line 86, in Initialize
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\Path\PathCommands.py", line 29, in <module>
    from PathScripts.PathUtils import loopdetect
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\Mod\Path\PathScripts\PathUtils.py", line 30, in <module>
    import numpy
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\site-packages\numpy\__init__.py", line 140, in <module>
    from . import core
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\site-packages\numpy\core\__init__.py", line 101, in <module>
    from . import _internal
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\site-packages\numpy\core\_internal.py", line 14, in <module>
    import ctypes
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\ctypes\__init__.py", line 468, in <module>
    GetLastError = windll.kernel32.GetLastError
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\ctypes\__init__.py", line 443, in __getattr__
    dll = self._dlltype(name)
  File "C:\FreeCAD_0.19.22522-Win-Conda_vc14.x-x86_64\bin\lib\ctypes\__init__.py", line 373, in __init__
    self._handle = _dlopen(self._name, mode)


And then when you re-enable it, Path returns:

23:15:12 Path workbench activated

In addition, there is a debug.log file in the Bin folder. Each time i run FC, two identical lines appear there:

[1003/221915.977:WARNING:resource_bundle_qt.cpp(116)] locale_file_path.empty() for locale
[1003/221916.618:WARNING:resource_bundle_qt.cpp(116)] locale_file_path.empty() for locale
Tags: #pending-forum
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0014807)
openBrain   
2020-10-09 21:15   
@mozarelo : please address your issue according our reporting guidelines by opening a new topic on our forum. Thx
Also consider using 'code' tags to insert tracebacks.
(0014860)
Kunda1   
2020-10-15 14:12   
@mozarelo can you still reproduce this on latest 0.19 ?
(0014861)
Kunda1   
2020-10-15 14:13   
Discussion thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=51188
(0014867)
Kunda1   
2020-10-15 16:01   
@mozarelo please follow this advice: https://forum.freecadweb.org/viewtopic.php?f=8&t=51188#p439657
(0014876)
Kunda1   
2020-10-15 18:43   
@mozarelo please make sure all your addons are up to date and try again. This includes A2+
(0015566)
Kunda1   
2021-03-28 16:24   
@mozarelo ping
(0015567)
Kunda1   
2021-03-28 16:27   
Looks like these issues occur for @mozarelo on win-conda and not on Win-LP
https://forum.freecadweb.org/viewtopic.php?f=8&t=51188#p439902
(0016943)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6110.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4839 [FreeCAD] Bug minor always 2022-02-06 16:45 2022-02-07 03:40
Reporter: mdkus Platform: Desktop  
Assigned To: OS: Windows  
Priority: normal OS Version: 7,11  
Status: new Product Version: 0.20  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
FreeCAD Information: <!--ATTENTION:
COMPLETELY ERASE THIS AFTER PASTING YOUR
Help > About FreeCAD > Copy to clipboard
NOTE: just the snippet alone will do without anything else included.
The ticket will not be submitted without it.
-->
Summary: Tools: workbench icon error when envoking pure python test module
Description: The location of the workbench icon for pure python modules should be the recommended resource directory as described under chapter 6.2.2 in the developpers guide, and not the location of users app data. I generated a PR to solve this.
Tags: #pending-PR
Steps To Reproduce: 1. Generate a pure python module with the fcbt-Tool (CP option)
2. Generate build files with CMake
3. Compile the build files
4. Start FC: The python test modul will be envoked with an error when searching the workbench icon under the users app data
Additional Information:
Attached Files:
Notes
(0016370)
Kunda1   
2022-02-07 03:39   
PR https://github.com/FreeCAD/FreeCAD/pull/5507
(0017145)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6314.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4264 [Draft] Bug minor always 2020-02-12 13:15 2022-02-06 23:16
Reporter: louisgag Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 0.20  
FreeCAD Information: OS: Ubuntu 18.04.4 LTS (ubuntu:GNOME/ubuntu)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.Unknown
Build type: Unknown
Python version: 2.7.17
Qt version: 4.8.7
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: C/Default (C)
Summary: Constructor from the makeArray Function in the Draft Workbench does not Allow Polar Array
Description: Yes, I have not created a thread because I think the bug is quite obvious.
I verified it on 0.19 and 0.18.4 but it probably also affects other earlier versions.

When in Python mode, trying to construct an array with a name using for example
Draft.makeArray(App.getDocument('Unnamed').getObject('Cylinder'),App.Vector(0,0,0),360,4,"testArray")
from the function (line 1249 from Draft.py) does not allow to directly make a polar array with a name.

Indeed, the instructions in the code say
makeArray(object,center,totalangle,totalnum,[name]) for polar array

but because of this part from the code:

    elif arg4:
        obj.ArrayType = "ortho"
it forces any call with a non-null "arg4" argument (in this case the name of the array) to make an Orthogonal array, or when the arguments for are polar array are given to simply return an error about wrong argument type.
Tags: #pending-forum
Steps To Reproduce: This is just an example:
Make a new document, go to Part workbench, make a cylinder, go to python console, type:
import Draft
Draft.makeArray(App.getDocument('Unnamed').getObject('Cylinder'),App.Vector(0,0,0),360,4,"testArray")
Additional Information:
Attached Files:
Notes
(0014162)
openBrain   
2020-02-19 13:06   
@louisgag : according guidelines (big yellow bow on top of the page), could you please open a topic on the forum (Draft subforum) so it can be more widely discussed ?
Please cross-post ticket number in forum, and forum thread in this ticket. Thanks.
(0014163)
louisgag   
2020-02-19 15:53   
thanks for having a look at my report, here is the Forum thread I just opened.
(0016864)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6030.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
3206 [Project Tools & Websites] General feature N/A 2017-10-01 12:29 2022-02-06 23:10
Reporter: Kunda1 Platform:  
Assigned To: Kunda1 OS:  
Priority: low OS Version:  
Status: assigned Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 0.20  
FreeCAD Information:
Summary: TravisCI to run code linting to report trailing whitespace/tabs + LF line endings
Description: Recently @wmayer expressed a way to remove trailing whitespaces and tabs in FC code. We could also think about avoiding more of them from being introduced in to source via testing when a PR is submitted.

Tags: #pending, TravisCI, unit-test
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0010262)
berndhahnebach   
2017-10-08 07:16   
(Last edited: 2017-10-08 07:17)
How did he do this?


AFAIK FEM is be free of trailing whitespaces and tabs. I remove them manually. For tabs I use:

grep -rl --exclude=\*.{qm,fcstd,png} $'\t' ./src/Mod/Fem/

Would be cool if we could include this in travis and step by step add any clean source directory of FreeCAD to it.

From my point it should be before any start of compiling on travis.

bernd

(0010274)
Kunda1   
2017-10-09 19:27   
Here's a tut on Howto Automatically fix PEP-8 issues using Travis-CI
Just can show us how to implement something in to travis
(0010297)
Kunda1   
2017-10-14 18:41   
Cause TravisCI to fail on any trailing whitespace
https://coderwall.com/p/h988xa/cause-travis-to-fail-on-trailing-whitespace
Add this to the script: section of .travis.yml
- "! git grep ' $' -- \\*.rb \\*.js \\*.other-file-types | grep -v -e 'FILE_TO_IGNORE' -e 'OTHER_FILE_TO_IGNORE"
(0010301)
Kunda1   
2017-10-16 14:27   
@wmayer what do you think would be a good outcome if a PR is found to have trailing whitespace? Should it kill the build process and report to the user where the whitespace is?
(0010311)
wmayer   
2017-10-17 18:12   
> what do you think would be a good outcome if a PR is found to have trailing whitespace?
Detecting a trailing whitespace would be good but it should not abort the build process.
(0010405)
Kunda1   
2017-11-10 14:25   
FFmpeg has a cool script that checks patches:
https://github.com/FFmpeg/FFmpeg/blob/master/tools/patcheck
(0016109)
chennes   
2021-12-17 03:54   
This can probably be handled via GitHub Actions now.
(0016270)
Kunda1   
2022-01-24 18:04   
A volunteer is working on this now
(0016369)
Kunda1   
2022-02-06 23:10   
'Floriansimmer' https://github.com/FreeCAD/FreeCAD/pull/5314#issuecomment-1019503744
(0016566)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 5731.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4840 [FEM] Bug minor always 2022-02-06 17:11 2022-02-06 18:55
Reporter: StefanBruens Platform:  
Assigned To: keithsloan52 OS:  
Priority: normal OS Version:  
Status: assigned Product Version: 0.19  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
FreeCAD Information: OS: openSUSE Tumbleweed (KDE//usr/share/xsessions/plasma5)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.Unknown
Build type: Release
Python version: 3.8.12
Qt version: 5.15.2
Coin version: 3.1.3
OCC version: 7.5.3
Locale: English/United States (en_US)
Summary: parsetab.py not created as part of installation
Description: FreeCAD uses ply.yacc in two places:


Mod/Fem/femtools/tokrules.py:yacc.yacc()
Mod/OpenSCAD/importCSG.py:    parser = yacc.yacc(debug=0)

According to https://www.skenz.it/compilers/ply
> Since table construction is relatively expensive (especially for large grammars), the resulting parsing table is written to a file called parsetab.py. In addition, a debugging file called parser.out is created.

When FreeCAD has been installed to a write-protected (not writable by regular user) path, the parsetab.py can not be created.
Tags:
Steps To Reproduce: This is e.g. visible when running the "TestFemApp" unit test:

....WARNING: Couldn't open 'parser.out'. [Errno 13] Permission denied: '/usr/lib64/FreeCAD/Mod/Fem/femtools/parser.out'
WARNING: Token 'COMMENT' defined, but not used
WARNING: There is 1 unused token
Generating LALR tables
WARNING: Couldn't create 'femtools.parsetab'. [Errno 13] Permission denied: '/usr/lib64/FreeCAD/Mod/Fem/femtools/parsetab.py'
Additional Information: This was already mentioned in:

https://forum.freecadweb.org/viewtopic.php?style=1&p=369267#p369267
Attached Files:
Notes
(0016364)
StefanBruens   
2022-02-06 17:41   
As the relevant code is unchanged in master, this also applies to 0.20
(0016368)
Kunda1   
2022-02-06 18:50   
(Last edited: 2022-02-06 18:55)
@StefanBruens thanks. Next time please open a forum thread. my bad, there was a forum thread attached
@keithsloan52 this is openscad related. Care to weigh-in?

Edit: forum thread exists
(0017146)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6315.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4397 [FreeCAD] Bug minor always 2020-07-02 14:31 2022-02-06 17:50
Reporter: Fizik Platform:  
Assigned To: OS: Windows 10  
Priority: low OS Version: Build 19041.329  
Status: resolved Product Version: 0.18  
Product Build: Resolution: reopened  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 0.20  
FreeCAD Information: OS: Windows 10
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.18.4 (GitTag)
Build type: Release
Branch: releases/FreeCAD-0-18
Hash: 980bf9060e28555fecd9e3462f68ca74007b70f8
Python version: 3.6.6
Qt version: 5.6.2
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: German/Germany (de_DE)
Summary: Extensions module directory lacking from module paths on startup
Description: Modules installed (by the Extension Manager) in the user Python modules directory %appdata%\FreeCAD\Mod are not accessible by means of the Python console (nor are they available to macros loaded into the workbench) when FreeCAD is started without command line options (e.g. from the start menu after a fresh install).

Things work fine when starting with the --module-path option, like

> path\to\FreeCAD.exe -M %appdata%\FreeCAD\Mod
Tags:
Steps To Reproduce: This description is pretty arbitrary, but it is what I stumbled across.

  1. Get a fresh install of FreeCAD 0.18.4 on Windows 10.
  2. Install, by means of the Extension Manager, A2+. This drops a Python module directory A2plus in your %appdata%\FreeCAD\Mod directory.
  3. Start FreeCAD (from the Windows Menu, i.e. without command line options).
  4. In the Python console, type
  5.    
    
       >>> import A2plus
       

       The interpreter reports ModuleNotFoundError on A2plus for the line entered.
  6. Quit FreeCAD, and restart with the extension modules directory passed as an additional Python module path, e.g.
  7. 
    > & "$env:ProgramFiles\FreeCAD 0.18\bin\FreeCAD.exe" -M "$env:AppData\FreeCAD\Mod"
    
  8. In FreeCAD, try accessing A2+ from the Python Console again,
  9. 
    >>> import A2plus
    
    The module is now accessible (and can be listed, e.g. dir(A2plus)).
Additional Information:
Attached Files:
Notes
(0014612)
Fizik   
2020-07-02 15:13   
Please delete this. I learned what I did wrong.
(0014625)
openBrain   
2020-07-07 16:22   
@Fizik : please tell us what you did wrong so everybody will take advantage of this. I'll close ticket when done. Thx.
(0014633)
Fizik   
2020-07-07 21:37   
(Last edited: 2020-07-07 21:38)
@openBrain The module is accessible by the name FreeCAD.A2plus (instead of A2plus without the prefix), and hence is imported by

import FreeCAD.A2plus

(I got myself fooled by the — apparently outdated — example file [A2p_animation-example-script.py](https://forum.freecadweb.org/download/file.php?id=97981) from the [A2+ documentation wiki](https://wiki.freecadweb.org/A2plus_Workbench).)
(0016350)
Kunda1   
2022-02-04 18:45   
@openBrain where should we document this?
(0016366)
openBrain   
2022-02-06 17:48   
@Kunda1 : It's purely related to A2plus so we don't really have room for that. At least the information is here. ;)
(0016919)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6086.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
3849 [Sketcher] Feature minor always 2019-02-18 23:12 2022-02-06 17:45
Reporter: sopwith Platform: x64  
Assigned To: OS: Windows  
Priority: normal OS Version: 10  
Status: new Product Version: 0.18  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 0.20  
FreeCAD Information:
Summary: Cursor info in Sketcher doesn't use proper units
Description: When drawing a shape in Sketcher, e.g. a line or a rectangle, the units displayed in blue next to the cursor are always mm, even if I've selected another units system in Preferences -> General -> Units.
Tags: #tobeclosed, units
Steps To Reproduce: Hopefully the above is self-explanatory.
Additional Information: OS: Windows 10
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.18.15860 (Git)
Build type: Release
Branch: master
Hash: 3b708c7f84b0425076b520e1d95627b20fd75fe0
Python version: 2.7.14
Qt version: 4.8.7
Coin version: 4.0.0a
OCC version: 7.2.0
Locale: English/UnitedStates (en_US)
Attached Files:
Notes
(0012691)
wmayer   
2019-02-19 12:58   
Check ViewProviderSketch::setPositionText
Check all occurrences of setPositionText in CommandCreateGeo.cpp
(0016355)
Kunda1   
2022-02-04 19:20   
(Last edited: 2022-02-04 19:21)
@openBrain we can close this, right?
(0016365)
openBrain   
2022-02-06 17:45   
@Kunda1 : Nope. It's still a valid bug.
(0016719)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 5884.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4263 [FreeCAD] Bug minor always 2020-02-10 09:40 2022-02-05 02:07
Reporter: jylandry Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 0.18  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 0.20  
FreeCAD Information: OS: Ubuntu 18.04.4 LTS
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.18.4.
Build type: Release
Python version: 3.6.8
Qt version: 5.9.5
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: English/UnitedStates (en_US)
Summary: Problem with negative offset "Placement" when the preference are "Building US" units
Description: https://forum.freecadweb.org/viewtopic.php?f=8&t=42766

When using "Placement" for an object and working with the unit in "Building US(ft-in/sqft/cuft)"

You can't work with negative number. For example, «-1.5"» or «-1+1/2"» will translate to «-1/2»

The same for «-13'6"» that will become «-12'6"»
Tags: #pending-forum, #ready-for-migration, units
Steps To Reproduce: 1) Put your preference in "Building US(ft-in/sqft/cuft)"

2) Create an empty document with an object like a cube (or anything will do)

3) try to change the "placement" (Translation) -- any of X: Y: or Z: -- Enter «-1.5"» or «-1+1/2"» or «-13'6"»

if you return in placement, the entry «-1.5"» should have been change to «-1/2"»
the entry «-13'6"» shall have been change by «-12'6"»
Additional Information:
Attached Files:
Notes
(0014144)
openBrain   
2020-02-10 11:00   
Could that be a duplicate of 0003925 ?
(0014149)
jylandry   
2020-02-11 02:16   
I look at it. Some aspect of 0003925 might exhibit the same symptom.

However, their is additional problem with the Building US unit related to the interpretation of the fraction.

a) When you enter -10+1/8" and click OK on the "Placement box"... you get -9+7/8". This might be similar to 0003925.

b) When you re-enter the "Placement Box", it does display -8+1/8". I don't think it is the same.
(0014150)
jylandry   
2020-02-11 02:17   
if you look at the post https://forum.freecadweb.org/viewtopic.php?f=8&t=42766

I have documented several cases scenario... including one that is not flagged as a bug.
(0014744)
pablito   
2020-09-12 15:07   
Independently observed again in 0.19.22366 and discussed in thread : https://forum.freecadweb.org/viewtopic.php?p=429940#p429940
(0016249)
Kunda1   
2022-01-23 00:02   
@openBrain since you've been tackling 'units' do you want to assign yourself to these tickets tagged as 'units' ?
(0016295)
openBrain   
2022-01-25 15:34   
@Kunda1 : certainly not. This ticket implies dealing with lexers and parsers, that I'm not totally not capable. ;)
(0016863)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6029.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2721 [Part] Bug major random 2016-10-04 15:41 2022-02-05 02:00
Reporter: DeepSOIC Platform:  
Assigned To: realthunder OS:  
Priority: normal OS Version:  
Status: assigned Product Version: 0.17  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 0.20  
FreeCAD Information:
Summary: Face order instability with Part Extrude and friends
Description: Sorting inside facemaker can cause order of faces to shuffle based on subtolerance differences if extruding multiple profiles of same size (e.g. a face with a few equally sized holes).
Tags: #pending, #tobeclosed, toponaming
Steps To Reproduce: 1. New Sketch. Draw two circles, constrain them equal radius.
2. Part Extrude.
3. add a fillet to one of the cylinders
4. open the sketch, and drag the circles so that their radii change.
-> fillet jumps from one cylinder to another,
Additional Information: OS: Windows 10
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.17.8361 (Git)
Build type: Release
Branch: DeepSOIC10
Hash: 4ac7673e543274bcae856872033a114c7b60481b
Python version: 2.7.8
Qt version: 4.8.7
Coin version: 4.0.0a
OCC version: 7.0.0
Attached Files: facemaker toponaming.FCStd (5,791 bytes) 2016-10-04 15:41
https://tracker.freecad.org/file_download.php?file_id=1343&type=bug
facemaker toponaming-2.FCStd (5,791 bytes) 2017-12-17 12:50
https://tracker.freecad.org/file_download.php?file_id=1772&type=bug
Notes
(0010575)
Kunda1   
2017-12-11 20:31   
@DeepSOIC do you mind re-upping the attachment again?
(0010611)
DeepSOIC   
2017-12-17 12:50   
Sure!
(0011713)
DeepSOIC   
2018-09-11 21:41   
If it wasn't yet fixed by realthunder already, it should be done in his branch, or in master after his toponaming is merged.
(0015386)
Kunda1   
2021-02-20 14:07   
@realthunder is this fixed in your branch ?
(0016314)
realthunder   
2022-01-25 21:47   
Yes, topo naming fixes this problem.
(0016501)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 5666.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4408 [FEM] Bug major always 2020-07-21 00:05 2022-02-05 01:55
Reporter: lsoltmann Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: confirmed Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 0.20  
FreeCAD Information: OS: macOS Mojave (10.14)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.21938 (Git)
Build type: Release
Branch: master
Hash: 5666598a6be219830a992610243fe23144a61453
Python version: 3.8.2
Qt version: 5.12.5
Coin version: 4.0.0
OCC version: 7.4.0
Locale: C/Default (C)
Summary: FEM constraints not on part design workbench object when moved using placement
Description: The FEM constraints (only tested force and fixed) graphics do not show up in the selected location if an object created with the part workbench was moved using placement. The graphics show up in the location of the part as if it were at the global origin. Running the FEM confirms that the constraints are not on the object. It was noted by the user thschrader that this only happens in the part design workbench and not the part workbench. Moderator bernd said this is a known problem that the FEM does not play well with the part design workbench.

Issue was posted about here: https://forum.freecadweb.org/viewtopic.php?f=18&t=48750
Tags: #pending, #pending-forum, FEM, Part Design, Placement
Steps To Reproduce: 1. Create a new file and select the part design workbench.
2. Create a new body and a sketch on the XY plane.
3. Sketch a square that is 1in by 1in.
4. Pad the sketch 1in in +z direction.
5. Using the placement property in the model view, set y = 2.0in.
6. Open the FEM workbench and create a new analysis.
7. Add a fixed constraint to any side of the cube using Model > Mechanical Constraints > Constraint fixed.
8. Observe that the constraint graphics are not on the object, but would be if the object had not been moved from the global origin. The same issue occurs with the force constraint as well. Those are the only two constraints that were tested.
Additional Information:
Attached Files:
Notes
(0014690)
berndhahnebach   
2020-07-26 21:54   
confirmed by Bernd
(0014691)
berndhahnebach   
2020-07-26 21:55   
Workaround. Create Simple Copy of the body with Part workbench.
(0015371)
wmayer   
2021-02-20 11:00   
(Last edited: 2022-01-22 21:59)
In Constraint::getPoints
the line can be added before accessing the sub-elements:

  toposhape.setPlacement(feat->globalPlacement());
(0016243)
Kunda1   
2022-01-22 21:58   
@jnxd can you take a look at this?
(0016299)
jnxd   
2022-01-25 17:41   
https://forum.freecadweb.org/viewtopic.php?f=18&t=48750&p=564856#p564856
(0016348)
jnxd   
2022-02-04 18:14   
@berndhahnebach @wmayer do you have any comments on this, especially the forum post? I am trying to make the PD feature also include the body's transformation/placement when it's own transformation/placement or coordinates are asked. I expect this, however, to have some side effect elsewhere in PD.
(0016926)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6093.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4115 [FreeCAD] Feature feature N/A 2019-09-05 20:22 2022-02-04 23:15
Reporter: Kunda1 Platform:  
Assigned To: OS:  
Priority: low OS Version:  
Status: resolved Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 0.20  
    Target Version: 0.20  
FreeCAD Information:
Summary: [Feature Request] Ability to change the Crosshair color
Description: Referencing 2 older threads:
2016: Crosshair color & size - update? (https://forum.freecadweb.org/viewtopic.php?t=14597)
2013: Setup for Crosshair (http://forum.freecadweb.org/viewtopic.php?t=3722)

This would be a nice customization option.
 
Usecase: if the user has setup their background to be a lighter neutral color it's difficult to see the crosshair

Case in point:
(see screenshot below)

Workaround: obviously to change the background color (but this is not an ideal solution hence the Feature Request)
Tags: #tobeclosed, mouse
Steps To Reproduce:
Additional Information: Forum thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=39099

OS: Manjaro Linux (XFCE/xfce)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.18009 (Git) AppImage
Build type: Release
Branch: master
Hash: 0641ca0d1e020d18f23d2adb49959195266f04f7
Python version: 3.7.3
Qt version: 5.12.1
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: English/United States (en_US)
Attached Files: FreeCAD-Coincedent-Constraint.gif (191,735 bytes) 2019-09-05 20:23
https://tracker.freecad.org/file_download.php?file_id=2311&type=bug
Notes
(0013538)
Kunda1   
2019-09-05 20:23   
Screenshot shows the usecase for changing the crosshair color
(0016347)
Kunda1   
2022-02-04 16:35   
@realthunder is this possible in Link branch?
(0016357)
realthunder   
2022-02-04 22:50   
This has already implemented in upstream, by setting parameter User parameter:BaseApp/Preferences/View/CursorCrosshairColor
(0016358)
Kunda1   
2022-02-04 23:12   
(Last edited: 2022-02-04 23:14)
@realthunder Oh wow...! Had no idea.
hmmm...i don't see this mentioned in https://wiki.freecad.org/Fine-tuning

What are the colors one can choose?


Edit: here's the commit: https://github.com/FreeCAD/FreeCAD/commit/0e9b8ef4d44ac0d3ed438d00abb29b38ef881157
(0016816)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 5982.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4315 [FreeCAD] Feature minor have not tried 2020-04-15 16:23 2022-02-04 19:49
Reporter: fc_tofu Platform:  
Assigned To: OS:  
Priority: low OS Version:  
Status: acknowledged Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 0.20  
FreeCAD Information: OS: Windows 10 (10.0)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.20514 (Git)
Build type: Release
Branch: master
Hash: a05ffd499366ab12fa1b43f37db73f4f1e9c332d
Python version: 3.8.2
Qt version: 5.12.5
Coin version: 4.0.0
OCC version: 7.4.0
Locale: Chinese/China (zh_CN)
Summary: FEM WB, WarpVector widget default position from Right to Left
Description:
By default pref, NaviCube shows on TopRight corner of viewport, and WarpVector bar widget (FEM WB) cannot be moved.
NaviCube and WarpVector bar widget overlay at TopRight corner in every new installed FreeCAD.
A known workgound is to move NaviCube away to the left.
But right side of viewport is more "stable" and preferable. By "stable", I mean that cannot be affected by frequent ajustment of neighboring ComboView border position. Since NaviCube is far more used than WarpVector bar, so I hope the NaviCube can stay at right, and WarpVector bar moved to left as future default position.

To prevent new conflict with other/potential widgets, a "Alighment = Left/Right" option can be added to view properties of WarpVector.
Tags: #ready-for-migration
Steps To Reproduce: Open stock example file "FemCalculixCantilever3D.FCStd", then
WarpVector bar widget appear on right of viewport with NaviCube overlayed on TopRight corner.
Additional Information:
Forum discussion
Attached Files:
Notes
(0016343)
Kunda1   
2022-02-03 13:47   
@jnxd can you take a look at this ?
(0016345)
Kunda1   
2022-02-03 21:40   


If I get it well, it's not trivial to move as the color bar actually lies in the "foreground" provided by Inventor View Provider : https://github.com/FreeCAD/FreeCAD/blob/8492cfb9eb49f6d882ceefb60440acd2a30fccfd/src/Mod/Fem/Gui/ViewProviderFemPostObject.cpp#L194

OpenBrain
(0016356)
jnxd   
2022-02-04 19:49   
Thanks for locating the exact place where the colorbar is implemented. Unfortunately there's no clear parameter in Gui::SoFCColorBar to just set it's position (I'd be happy to be proven wrong), so I'll need to dig in a bit.

While this bug itself should be fixed, I don't know how much of the post-processing we would want to handle locally within FreeCAD. There are other programs that are built for exactly this purpose (looking mainly at ParaView), and I believe it'd be kind of a duplication of effort to support more complex behavior.
(0016881)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6047.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4431 [FreeCAD] Bug crash always 2020-09-09 19:05 2022-02-04 19:00
Reporter: Gregory son of Carl Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: confirmed Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 0.20  
FreeCAD Information: OS: Debian GNU/Linux 10 (buster) (KDE/default)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.22284 (Git) AppImage
Build type: Release
Branch: master
Hash: bf1e8e48389f5e9e25bd77b67fe98da4213e797c
Python version: 3.8.5
Qt version: 5.12.5
Coin version: 4.0.0
OCC version: 7.4.0
Locale: English/United States (en_US)
Summary: Crash after editing Part Design feature links with DAGView active
Description: Link to forum thread

When the DAGView panel is active, FreeCAD will crash after editing App:Link objects that reference Part Design features such as Pads, Revolves, Sweeps, and Sketches.
Tags: #pending-forum, crash, DAG, Part Design
Steps To Reproduce:
  1. Download both attached files into the same folder (Assembly3Test.FCStd, Assembly3TestCube2.FCStd)
  2. Activate DAG view. (Tools> Edit Parameters...> BaseApp> Preferences> DockWindows> DAGView> Enabled=True)
  3. Restart FreeCAD
  4. Open Assembly3Test.FCStd
  5. Double-click the Pad feature in Assembly3Test
  6. Click Cancel or OK in the task window.
The crash happens immediately after releasing the mouse button
Additional Information:
FreeCAD 0.19, Libs: 0.19R22284 (Git)
© Juergen Riegel, Werner Mayer, Yorik van Havre and others 2001-2020
FreeCAD is free and open-source software licensed under the terms of LGPL2+ license.
FreeCAD wouldn't be possible without FreeCAD community.
  #####                 ####  ###   ####  
  #                    #      # #   #   # 
  #     ##  #### ####  #     #   #  #   # 
  ####  # # #  # #  #  #     #####  #   # 
  #     #   #### ####  #    #     # #   # 
  #     #   #    #     #    #     # #   #  ##  ##  ##
  #     #   #### ####   ### #     # ####   ##  ##  ##

Loading Assembly4 WorkBench
Sheet Metal workbench loaded
During initialization the error "'backend.qt4 is not a valid rc parameter (see rcParams.keys() for a list of valid parameters)'" occurred in /home/gregory/.FreeCAD/Mod/animation/InitGui.py
Please look into the log file for further information
During initialization the error "inconsistent use of tabs and spaces in indentation (<string>, line 48)" occurred in /home/gregory/.FreeCAD/Mod/GDT/InitGui.py
Please look into the log file for further information
Program received signal SIGSEGV, Segmentation fault.
#0  /lib/x86_64-linux-gnu/libc.so.6(+0x37840) [0x7fd13613f840]
#1  0x7fd138ba2f54 in Gui::DAG::Model::slotResetEdit(Gui::ViewProviderDocumentObject const&) from /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libFreeCADGui.so+0x44
0000002  /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libFreeCADGui.so(+0x382d1c) [0x7fd13892ad1c]
0000003  0x7fd138981c35 in Gui::Document::_resetEdit() from /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libFreeCADGui.so+0x1f5
0000004  0x7fd13891022a in Gui::Application::setEditDocument(Gui::Document*) from /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libFreeCADGui.so+0x3a
0000005  0x7fd13899177c in Gui::DocumentPy::resetEdit(_object*) from /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libFreeCADGui.so+0x2c
0000006  0x7fd1389917c4 in Gui::DocumentPy::staticCallback_resetEdit(_object*, _object*) from /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libFreeCADGui.so+0x24
0000007  /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libpython3.8.so.1.0(PyCFunction_Call+0xf7) [0x7fd138393d87]
0000008  /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libpython3.8.so.1.0(_PyObject_MakeTpCall+0x250) [0x7fd138348850]
0000009  /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libpython3.8.so.1.0(_PyEval_EvalFrameDefault+0x4e36) [0x7fd1383d77d6]
0000010  /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libpython3.8.so.1.0(_PyEval_EvalCodeWithName+0x2e2) [0x7fd138344f92]
0000011  /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libpython3.8.so.1.0(PyEval_EvalCodeEx+0x44) [0x7fd138345d54]
0000012  /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libpython3.8.so.1.0(PyEval_EvalCode+0x1c) [0x7fd1383fb6ac]
0000013  /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libpython3.8.so.1.0(+0x219ecf) [0x7fd138419ecf]
0000014  /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libpython3.8.so.1.0(+0x252b84) [0x7fd138452b84]
0000015  /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libpython3.8.so.1.0(PyRun_StringFlags+0x7d) [0x7fd138452c1d]
0000016  0x7fd137c4d2ba in Base::InterpreterSingleton::runString[abi:cxx11](char const*) from /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libFreeCADBase.so+0x6a
0000017  0x7fd1389ec3b8 in Gui::Command::_runCommand(char const*, int, Gui::Command::DoCmd_Type, char const*) from /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libFreeCADGui.so+0x98
0000018  0x7fd1389ec5a2 in Gui::Command::_doCommand(char const*, int, Gui::Command::DoCmd_Type, char const*, ...) from /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libFreeCADGui.so+0x102
0000019  0x7fd04a7a9e35 in PartDesignGui::TaskDlgFeatureParameters::reject() from /tmp/.mount_FreeCAbs6iBc/usr/lib/PartDesignGui.so+0x105
0000020  0x7fd04a7aeaa1 in PartDesignGui::TaskDlgSketchBasedParameters::reject() from /tmp/.mount_FreeCAbs6iBc/usr/lib/PartDesignGui.so+0x31
0000021  0x7fd138c85819 in Gui::TaskView::TaskView::reject() from /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libFreeCADGui.so+0x59
0000022  0x7fd1366867b8 in QMetaObject::activate(QObject*, int, int, void**) from /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libQt5Core.so.5+0x780
0000023  /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libQt5Widgets.so.5(+0x274bbb) [0x7fd136f9cbbb]
0000024  0x7fd1366867b8 in QMetaObject::activate(QObject*, int, int, void**) from /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libQt5Core.so.5+0x780
0000025  0x7fd136f351fe in QAbstractButton::clicked(bool) from /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libQt5Widgets.so.5+0x32
0000026  /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libQt5Widgets.so.5(+0x20d8b7) [0x7fd136f358b7]
0000027  /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libQt5Widgets.so.5(+0x20e14c) [0x7fd136f3614c]
0000028  0x7fd136f361e8 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) from /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libQt5Widgets.so.5+0x88
0000029  0x7fd136ec7c3e in QWidget::event(QEvent*) from /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libQt5Widgets.so.5+0xce
0000030  0x7fd136e9c82a in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libQt5Widgets.so.5+0xde
0000031  0x7fd136ea1095 in QApplication::notify(QObject*, QEvent*) from /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libQt5Widgets.so.5+0x79d
0000032  0x7fd1389baab9 in Gui::GUIApplication::notify(QObject*, QEvent*) from /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libFreeCADGui.so+0x89
0000033  0x7fd136670186 in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libQt5Core.so.5+0x88
0000034  0x7fd136ea053f in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool, bool) from /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libQt5Widgets.so.5+0x283
0000035  /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libQt5Widgets.so.5(+0x1af554) [0x7fd136ed7554]
0000036  /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libQt5Widgets.so.5(+0x1b03a6) [0x7fd136ed83a6]
0000037  0x7fd136e9c82a in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libQt5Widgets.so.5+0xde
0000038  0x7fd136ea23f1 in QApplication::notify(QObject*, QEvent*) from /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libQt5Widgets.so.5+0x1af9
#39  0x7fd1389baab9 in Gui::GUIApplication::notify(QObject*, QEvent*) from /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libFreeCADGui.so+0x89
#40  0x7fd136670186 in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libQt5Core.so.5+0x88
0000041  0x7fd136a1640b in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) from /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libQt5Gui.so.5+0x6d3
0000042  0x7fd136a16ff7 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) from /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libQt5Gui.so.5+0x175
0000043  0x7fd136a03dd4 in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libQt5Gui.so.5+0x64
0000044  /tmp/.mount_FreeCAbs6iBc/usr/plugins/platforms/../../lib/libQt5XcbQpa.so.5(+0x5af0e) [0x7fd132402f0e]
0000045  /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/./libglib-2.0.so.0(g_main_context_dispatch+0x2cb) [0x7fd13364cb3b]
0000046  /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/./libglib-2.0.so.0(+0x54d81) [0x7fd13364cd81]
0000047  /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/./libglib-2.0.so.0(g_main_context_iteration+0x2e) [0x7fd13364ce0e]
0000048  0x7fd13669f42b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libQt5Core.so.5+0x63
0000049  0x7fd13666cbc1 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) from /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libQt5Core.so.5+0x187
0000050  0x7fd136670a39 in QCoreApplication::exec() from /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libQt5Core.so.5+0x105
0000051  0x7fd138932ca2 in Gui::Application::runApplication() from /tmp/.mount_FreeCAbs6iBc/usr/bin/../lib/libFreeCADGui.so+0x15a2
0000052  /tmp/.mount_FreeCAbs6iBc/usr/bin/freecad(+0x37cd) [0x560a04df97cd]
0000053  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7fd13612c09b]
0000054  /tmp/.mount_FreeCAbs6iBc/usr/bin/freecad(+0x4521) [0x560a04dfa521]
Attached Files: Assembly3TestCube2.FCStd (10,796 bytes) 2020-09-09 19:05
https://tracker.freecad.org/file_download.php?file_id=2521&type=bug
Assembly3Test.FCStd (2,771 bytes) 2020-09-09 19:05
https://tracker.freecad.org/file_download.php?file_id=2522&type=bug
Notes
(0014731)
Kunda1   
2020-09-10 14:49   
Confirmed by chrisb on the thread
(0015074)
Kunda1   
2020-12-04 02:51   
@chennes responded in https://forum.freecadweb.org/viewtopic.php?f=20&t=49982#p454170
(0016353)
Kunda1   
2022-02-04 19:00   
bumped forum thread
(0016936)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6103.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4452 [FreeCAD] Bug feature always 2020-10-07 18:33 2022-02-04 18:56
Reporter: Kryptal Platform: PC  
Assigned To: Kunda1 OS: Manjaro Linux  
Priority: normal OS Version: 20.1.1  
Status: feedback Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 0.20  
FreeCAD Information: OS: Manjaro Linux (KDE//usr/share/xsessions/plasma)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.22656 (Git)
Build type: Release
Branch: master
Hash: 1816a71d270c21e9657c99ed376138efb01f85b1
Python version: 3.8.5
Qt version: 5.15.1
Coin version: 4.0.0
OCC version: 7.4.0
Locale: French/France (fr_FR)
Summary: Zoom with mouse wheel is broken
Description: When working on any document (even a new one) the zoom functionality doesn't work when using the mouse wheel with any navigation style.
However, zooming is still possible using Ctrl + Wheel click and moving the mouse forward and backward with the following navigation styles : OpenInventor, Revit and Blender.
Tags: #pending-forum, 0.19, linux, mouse, UI, zoom
Steps To Reproduce: Use the mouse wheel to zoom on any document (a new one or one you already have. It doesn't change anything)
Additional Information:
Attached Files:
Notes
(0014791)
Kunda1   
2020-10-08 01:13   
Forum thread, per the guidelines, please?
(0014804)
openBrain   
2020-10-09 21:08   
Forum thread
(0016351)
Kunda1   
2022-02-04 18:55   
(Last edited: 2022-02-04 18:56)
@Kryptal can you recheck this on latest v0.20dev ?
The forum thread mentions that the issues may be fixed. See https://forum.freecadweb.org/viewtopic.php?p=568306#p568306


Edit:
Commit associated with this ticket: https://github.com/FreeCAD/FreeCAD/commit/c9923ab15
(0016944)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6111.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4499 [FEM] Bug major always 2020-11-22 02:12 2022-02-04 18:48
Reporter: johnwang Platform:  
Assigned To: OS: Windows 10  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 0.20  
FreeCAD Information: OS: Windows 10 (10.0)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.22900 (Git)
Build type: Release
Branch: master
Hash: b7b4250b7fe5e98bcdbe2a7c7be256132b35cd3d
Python version: 3.6.8
Qt version: 5.12.1
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: English/United States (en_US)
Summary: Can't save color
Description: Talked in the post:
https://forum.freecadweb.org/viewtopic.php?f=3&t=52341

Using this code to generate a FemMesh object with two triangle elements. Then changed the color of one element. But after saving and reopen, the color is lost.
Tags:
Steps To Reproduce: Use this code to create the file, then save and reopen.
import Fem

a = Fem.FemMesh()

a.addNode(0,    0,    0,    1)
a.addNode(10,    0,    0,    2)
a.addNode(5,    10,    0,    3)
a.addNode(15,    15,    0,    4)

a.addFace([1,2,3], 1)
a.addFace([2,4,3], 2)
obj = FreeCAD.ActiveDocument.addObject("Fem::FemMeshObject")
#obj.Placement.Base = FreeCAD.Vector(2, 0, 0)
obj.FemMesh = a

obj.ViewObject.ElementColor = {1:(1,0,0)}
Additional Information:
Attached Files:
Notes
(0016964)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6131.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4832 [FreeCAD] Bug major always 2022-01-16 20:05 2022-02-04 16:32
Reporter: chrisdepalma Platform:  
Assigned To: Kunda1 OS:  
Priority: normal OS Version:  
Status: assigned Product Version: 0.20  
Product Build: Resolution: reopened  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
FreeCAD Information: OS: Windows 10 Version 2009
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.24267 +99 (Git)
Build type: Release
Branch: Branch_0.19.3
Hash: 6530e364184ce05ccff39501e175cf2237e6ee4b
Python version: 3.8.6+
Qt version: 5.15.2
Coin version: 4.0.1
OCC version: 7.5.3
Locale: English/United States (en_US)
Summary: Freecad hangs when trying to import a step file
Description: I am using latest freecad dev version from 1/16/2022

Freecad hangs when trying to load the step file. It does this on the .19.3 version also.

Freecad starts to render but when clicking on the UI even after an hour after starting import, the ui is unresponsive.
Tags: #pending-forum
Steps To Reproduce: Select file import step.

Select step file located here: https://github.com/ZeroGDesign/Mercury/blob/main/CAD/Zero%20G%20-%20Mercury%20One.step

Freecad will never finish import.

This step was i believe generated by Fusion 360.
Additional Information: PC is a I7 5820K with 40 GB of ram.
Attached Files:
Notes
(0016221)
openBrain   
2022-01-17 16:52   
@chrisdepalma : please report your issues according our reporting guidelines by creating a new topic in our forum. Thx
(0016227)
Kunda1   
2022-01-19 16:50   
Closing since no forum thread was opened. Re-open if needed.
(0016323)
chrisdepalma   
2022-01-30 00:12   
I added a post on forum as requested. If anybody cares that step files don't load, then you should try the simple repro steps.



(0016324)
chrisdepalma   
2022-01-30 00:13   
post title: Freecad hangs loading step file.
(0016325)
Kunda1   
2022-01-30 00:51   
Y u no add URL ?
(0016326)
chrisdepalma   
2022-01-30 03:49   
@Kunda1 Url to github is in the issue.
(0016327)
adrianinsaval   
2022-01-31 20:39   
url to the forum thread
here it is: https://forum.freecadweb.org/viewtopic.php?f=3&t=65799
OP please read and follow guidelines when doing a bug report
(0017142)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6311.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1240 [FreeCAD] Feature feature have not tried 2013-09-11 07:19 2022-02-03 22:35
Reporter: nikospap Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 0.12  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 0.20  
FreeCAD Information:
Summary: Welding WB (which also includes Technical drawing symbols)
Description: Think of iron welding, hot glue, silicon sealer...

Because the welding material is an object of its own, and its volume is not insignificant.

Like "fillet" or "chamfer", but where two elements meet.

And by elements I mean, a point, a line, a surface.

We would select two of the above and we would apply "weld".

We would determine the thickness of the weld material,
and the allowed, maximum, possible gap between them.
Because these two elements might cross each other,
or there might be a little space between them (for example 1mm).

The weld would be applied on the "free" areas.

It must be graphically clear that this is a weld.



Useful for both the design and the construction of a project.
Tags: #ready-for-migration
Steps To Reproduce:
Additional Information: I 've made two pictures, showing how weld might look like.

And there is a third picture.
I can't imagine how Freecad would calculate the welding, for this case.
Attached Files: weld_001.jpg (24,285 bytes) 2013-11-04 13:48
https://tracker.freecad.org/file_download.php?file_id=605&type=bug
weld_002.jpg (27,269 bytes) 2013-11-04 13:48
https://tracker.freecad.org/file_download.php?file_id=606&type=bug
weld_003.jpg (25,644 bytes) 2013-11-04 13:48
https://tracker.freecad.org/file_download.php?file_id=607&type=bug
weld_001-2.jpg (24,285 bytes) 2017-07-21 08:11
https://tracker.freecad.org/file_download.php?file_id=1678&type=bug
weld_002-2.jpg (27,269 bytes) 2017-07-21 08:11
https://tracker.freecad.org/file_download.php?file_id=1679&type=bug
weld_003-2.jpg (25,644 bytes) 2017-07-21 08:11
https://tracker.freecad.org/file_download.php?file_id=1680&type=bug
weld_004_weld_symbol.jpg (46,821 bytes) 2017-07-21 08:42
https://tracker.freecad.org/file_download.php?file_id=1681&type=bug
Notes
(0009782)
Kunda1   
2017-07-19 11:06   
@yorik perhaps you still have these attachments somewhere (fingers crossed) ?
(0009783)
Kunda1   
2017-07-19 11:16   
@nikospap perhaps you could find them? 0001240:0009782
(0009789)
nikospap   
2017-07-21 08:11   
re-uploading attachments
(0009790)
nikospap   
2017-07-21 08:42   
After a long time, I found out that there are actually "weld symbols" used in drawings.
See...
https://yandex.com/images/search?text=weld%20symbols

I attach a properties dialog from WeldCAD
(a program that is no longer supported, but still available in http://arcworks.lincolnsupport.com/files/wcad3b_inst.exe , according to http://www.weldingdata.com/weldcad/weldcad.html ).
Just to get an idea.

Of course this is not the same as my initial request. I think that these symbols are "official" and more advanced, used in professional drawings. My suggestion seems to be more suitable for amateur users.
(0009791)
Kunda1   
2017-07-21 09:25   
(Last edited: 2017-08-04 14:47)
Appropriate forum threads:

(0009873)
normandc   
2017-08-04 21:51   
Adding welding symbols to the TechDraw workbench (TechDraw will replace the Drawing workbench which is no longer developed) is a matter for a different but linked report. Linked because the weld symbols would need to extract data from the actual weld objects on the 3D model.
(0009877)
Kunda1   
2017-08-05 13:08   
Thanks @normandc for your comment. Do you mind opening and linking said report?
(0010995)
Kunda1   
2018-03-03 18:15   
Related: 'Simulated Weld' in the FC User Showcase subforum
(0012199)
Kunda1   
2018-11-16 02:34   
@wandererfan should I move this to Techdraw based on what NormandC wrote in 0001240:0009873 ? (and rename the issue?)
(0012200)
wandererfan   
2018-11-16 14:45   
@Kunda1 symbols on drawings would be TD, but if the welds are to be modelled then that would not be TD.

Ultimate solution probably needs both, so I would leave things as they are.

caveat: IANAW (I Am Not a Welder)
(0012204)
nikospap   
2018-11-17 09:57   
But if you had to choose between the two methods, you should choose the professional symbols. Simply because they must be more well though, and more thoroughly tested.
(0012975)
Kunda1   
2019-03-29 01:35   
@reox writes in https://forum.freecadweb.org/viewtopic.php?f=35&t=34990&p=297616#p294888

I had a quick look around, but it looks like they are not defined in unicode.
But someone created a glyph font: https://www.fontspace.com/micronus/y145m-2009/13390/charmap

reox
(0013425)
Kunda1   
2019-08-14 19:04   
Welding Symbol Testing Help - https://forum.freecadweb.org/viewtopic.php?f=35&t=38560
(0016406)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 5571.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
3744 [FreeCAD] Bug major always 2018-12-21 20:14 2022-02-03 22:35
Reporter: sbisbip Platform: macbook pro  
Assigned To: OS: macOS Mojave  
Priority: normal OS Version: 10.14.2  
Status: confirmed Product Version: 0.17  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 0.20  
FreeCAD Information:
Summary: Open file dialog freezes the laptop for several minutes (approx. 2 min) <-- Due to missing Code Signing
Description: Each time I use Freecad app the open file dialog freezes the machine for at least 2 min...
Please note at the beginning the open file is small like a rendering problem and after the frozen delay it has a normal scale.
If I browse the filesystem I have the same kind of freezes :(
Tags: #ready-for-migration, macOS
Steps To Reproduce: How to reproduce:
1. Launch freecad app (wait at least 30 sec before the app is opened)
2. open file dialog
=> the open file dialog is small
=> the machine is not usable only the mouse cursor is visible, a keyboard action has no effects
3. wait about 2 minutes
=> the app is available
3.b browse the file system
=> same behavior as step 3
Additional Information: my freedcad
OS: Mac OS X
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.17.13541 (Git)
Build type: Release
Branch: releases/FreeCAD-0-17
Hash: 9948ee4f1570df9216862a79705afb367b2c6ffb
Python version: 2.7.14
Qt version: 5.10.1
Coin version: 4.0.0a
OCC version: 7.2.0
Locale: English/UnitedStates (en_US)
Attached Files:
Notes
(0012336)
Kunda1   
2018-12-24 12:28   
Currently FC's MacOS maintainers haven't been active. Please post this issues to the forums to generate further discussion.
Also can you reproduce this on 0.18_pre?
(0012341)
sbisbip   
2018-12-25 11:37   
Hi Kunda1,

Thanks a lot for your message.
I have tested the dev version as you advised in your previous message.

With this following version the delay is shorter about 5 seconds, it is not friendly but it is acceptable.
I propose to decrease the severity.

Tested on:
OS: macOS 10.14
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.18.15310 (Git)
Build type: Release
Branch: (HEAD detached at c88a64e8e)
Hash: c88a64e8e7a3bb66a23b965b655b5a5040dfa4d2
Python version: 2.7.15
Qt version: 5.11.2
Coin version: 4.0.0a
OCC version: 7.2.0
Locale: English/UnitedStates (en_US)
(0012564)
martijnthe   
2019-01-31 10:07   
I think it has something to do with the binary release not being code signed.
If I use codesign to sign the FreeCAD.app and all the executables in it, the freezing goes away.

Perhaps it's a good idea to sign the binary releases for macOS (by the CI build machine).

See my forum post here: https://forum.freecadweb.org/viewtopic.php?f=4&t=31343&p=283600#p283600
(0012607)
Kunda1   
2019-02-10 15:44   
(Last edited: 2019-02-10 15:44)
CC @blacey @peterl94

(0013821)
michaelhund   
2019-11-12 20:09   
I can report this issue continues with FreeCAD-0.19-18644 running on MacOS 10.14.6 on a MacBook Pro mid 2014 model. The delay affects all file operations, and last about 45 seconds.
(0013883)
Kunda1   
2019-12-09 14:00   
@michaelhund thanks for the note. Please continue discussion on the forum https://forum.freecadweb.org/viewtopic.php?f=4&t=31343&p=283600#p283600 to find a solution with the community
(0016688)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 5853.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2869 [FreeCAD] Feature feature N/A 2017-01-21 22:31 2022-02-03 22:33
Reporter: Kunda1 Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 0.20  
FreeCAD Information:
Summary: IPython / Jupyter support
Description: This is a placeholder ticket for IPython / Jupyter. It has been listed as a potential GSOC project (https://www.freecadweb.org/wiki/index.php?title=Google_Summer_of_Code#Implementation_Ideas) and mentored by ickby (though this year ickby may not be able to mentor it (as per https://forum.freecadweb.org/viewtopic.php?t=20063#p154833)

Nevertheless, for those interested, discussion on this topic have occurred in the FreeCAD forums:
* IPython notebook integration https://forum.freecadweb.org/viewtopic.php?t=14740
* Ipython Qt Console https://forum.freecadweb.org/viewtopic.php?f=10&t=14166
* [SOLVED] Embedding FreeCAD in ipython https://forum.freecadweb.org/viewtopic.php?t=13620

Please continue the conversation in https://forum.freecadweb.org/viewtopic.php?t=14740
Tags: #ready-for-migration
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0013498)
Kunda1   
2019-08-31 13:33   
(Last edited: 2019-08-31 13:33)
@looo made a proof of concept some time ago:
screencast: https://vimeo.com/159119041
https://github.com/looooo/jupyter_freecad_kernel

(0013499)
Kunda1   
2019-08-31 13:35   
(Last edited: 2019-09-01 13:40)
A user "Bayesian" created a forum thread: How to use Jupyter Notebook with FreeCad [Guide]

@keithsloan posts thread called Exciting possibilities with jupyter and FreeCAD

(0016514)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 5679.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
3304 [FreeCAD] Feature feature N/A 2018-01-08 20:04 2022-02-03 21:57
Reporter: Kunda1 Platform:  
Assigned To: OS:  
Priority: low OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 0.20  
FreeCAD Information:
Summary: Integrate Inkscape in to FreeCAD
Description: Relevant threads:
Tags: #ready-for-migration
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0016592)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 5757.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4238 [FreeCAD] Feature trivial N/A 2020-01-02 14:23 2022-02-03 13:45
Reporter: Kunda1 Platform:  
Assigned To: OS:  
Priority: low OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 0.20  
FreeCAD Information: FreeCAD 0.19
Summary: Decide on the function of system.cfg
Description: Right now ~/.FreeCAD/system.cfg doesn't serve a purpose. See forum thread https://forum.freecadweb.org/viewtopic.php?f=8&t=40517
Tags: #ready-for-migration
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0016853)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6019.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4675 [FreeCAD] Bug minor sometimes 2021-06-04 14:31 2022-02-03 12:11
Reporter: drmacro Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: confirmed Product Version: 0.20  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
FreeCAD Information: OS: Ubuntu 20.04.2 LTS (XFCE/ubuntustudio)
Word size of FreeCAD: 64-bit
Version: 0.20.25024 (Git)
Build type: Release
Branch: master
Hash: 1fb45a0c5ee88ddd31c1e17b2b3efc83fc9106f6
Python version: 3.8.5
Qt version: 5.12.8
Coin version: 4.0.0
OCC version: 7.5.1
Locale: English/United States (en_US)
Summary: Programmatically building sketch geometry and constraints displays error, but creates valid geometry and constraints
Description: Adding this as requested by @abdullah

When programmatically building geometry the following error is displayed, but, only with certain sets of valid input data.

Updating geometry: Error build geometry(6): gp_Circ::SetRadius() - radius should be positive number
Invalid solution from DogLeg solver.

It appears to only happen with certain sets of data in the Python scripts available here:
https://github.com/macdroid53/FreeCADScripts
(put the files in the macro directory and execute the .py file with no _ui in the name.

Forum discussion.
Tags: #pending-forum, python, sketcher
Steps To Reproduce: Using certain set of data input to the linked Python scripts produces the error shown.

Sometimes all values appear to work. Sometimes not. And at other times the same values produce no error.

I have been unable to discern a pattern.

Sometimes the error mentions multiple solvers.
Additional Information:
Attached Files:
Notes
(0017057)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6226.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4448 [TechDraw] Bug major always 2020-10-03 02:21 2022-02-02 20:21
Reporter: CrashedAgain Platform: All  
Assigned To: OS:  
Priority: high OS Version:  
Status: resolved Product Version:  
Product Build: Resolution: won't fix  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 0.20  
FreeCAD Information: Forum link
[quote=CrashedAgain post_id=435450 time=1601481254 user_id=29187]
Test file created in 0.18.16146.
All Tech Draw views were deliberately moved from their default locations because "locations" is where the problem lies.
Screenshot 1 is the original as created in 0.18. Note the rotated section view.
Screenshot 2 is the same file as opened by 0.19.22522. Note the Data sidebar indicates -90 rotation but the section view is not actually rotated and the dimensions are (0.00) because the reference points are now in line.
File was then saved (without making any changes) by 0.19 and then reopened in 0.18. (Screenshot3) All the views are piled together in the corner because 18 is now reading all the the x-y locations and the rotation value as 0.
But....if the file is now reopened in 19, the display is the same as screenshot 2, therefore the stored rotation data has not been changed and 19 can read the x-y data correctly but 18 can not. Neither version can read the rotation data correctly.
If the file is now re-saved by version 18, all the location values will actually be changed to "0".
[/quote]
Summary: 0.19 Tech Draw does not correctly open files from previous versions.
Description: 0.19 Tech Draw does not correctly interpret the rotation angle of any rotated views created by previous versions. For example, if the page contains a view that has been rotated -90 degrees, 0.19 displays the view as being rotated 0 degrees. This causes any dimensions in the view to be incorrect (usually to "0.00") because the anchor points are shifted.
Tags: 0.18, 0.19, TechDraw
Steps To Reproduce: Step 1: Create a object in an earlier version (eg 0.18) and insert views of it into a Tech Draw page.
Step 2: Either rotate one (or more) of the views or create a section view and rotate it. Angle does not matter but it should be obvious. Add some x and y dimensions to the rotated view.
Step 3:Save and close.
Step 4: Open the file in 0.19. You will find that (even though the angle in the data box is unchanged), the rotated view is displayed at a different angle and consequently the dimensions have changed.
Obviously, this corrupted file cannot be used, therefore I have marked this bug as severe. The file can be repaired by editing the rotation data in the properties box until the orientation is correct.
Sample file attached...
Additional Information: The only additional information I have is that a file originally rotated -90 degrees becomes correct when the rotation angle is set to 0; and a file originally rotated 30 degrees becomes correct when the rotation angle is reset to 60. Maybe 0.18 is measuring the angles from horizontal while 0.19 is measuring from vertical????

Attached Files: TestFileCreatedin0.18.FCStd (13,215 bytes) 2020-10-03 02:21
https://tracker.freecad.org/file_download.php?file_id=2532&type=bug
Notes
(0016340)
wandererfan   
2022-02-02 20:20   
V018 had issues with direction of rotation and section views. Note that the -90 rotation in the sample file is counter clockwise in v018, but clockwise (as it should be) in v019.

Also note the inconsistency between section direction (looking down) and section normal ((0,0,-1) which indicates looking up).

It is unfortunate, but I don't think we can duplicate errors in order to maintain backwards compatibility.
(0016942)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6109.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4838 [TechDraw] Feature minor N/A 2022-01-31 19:19 2022-02-02 17:29
Reporter: bensay Platform:  
Assigned To: OS:  
Priority: low OS Version:  
Status: feedback Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
FreeCAD Information: OS: Ubuntu 20.04.3 LTS (ubuntu:GNOME/ubuntu)
Word size of FreeCAD: 64-bit
Version: 0.20.
Build type: Release
Branch: unknown
Hash: 3a4100d656182667ac4efd8d4b127ad03f7edf46
Python version: 3.8.10
Qt version: 5.12.8
Coin version: 4.0.0
OCC version: 7.5.2
Locale: English/United States (en_US)
Summary: Mouse-over Info in Task: Edit welding symbols
Description: Detailed information on forum: Add Weld Tool - thoughts and suggestions
Tags: #pending
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0016338)
Kunda1   
2022-02-02 17:11   
PR https://github.com/FreeCAD/FreeCAD/pull/5477
Commit https://github.com/FreeCAD/FreeCAD/commit/8506453c933110f124dcb0033ca5f71cfe1b0975

@bensay what is left?
(0017144)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6313.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
3575 [TechDraw] Feature feature N/A 2018-08-31 13:12 2022-02-02 17:07
Reporter: Kunda1 Platform:  
Assigned To: OS:  
Priority: none OS Version:  
Status: new Product Version: 0.18  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 0.20  
FreeCAD Information:
Summary: TechDraw: Don't recompute on text changes
Description: Reference: https://forum.freecadweb.org/viewtopic.php?f=3&t=30524&p=253695#p253670
Tags: #pending
Steps To Reproduce:
Additional Information:
Attached Files: ssRecompute.FCStd (20,581 bytes) 2019-03-04 13:55
https://tracker.freecad.org/file_download.php?file_id=2148&type=bug
Notes
(0011929)
wandererfan   
2018-10-05 12:46   
I don't understand this one. What text is being changed? Is Page KeepUpToDate property set to false to avoid recompute/redraw?
(0012709)
jango   
2019-02-21 04:39   
The problem is the following: when we're making a technical draw of some machine, we need to specify a lot of components characteristics and names in order to make it easily understandable; in example the table of components, welding type, surface finishing and so forth; in the designing process we change continuously those characteristics and text, in this sense is annoying have to recompute a whole text if you only need to change a section of it: an incorrect letter or number, recompute a whole 50 components table for only one incorrect part. Try to make those texts individual boxes, like Inventor.
(0012730)
wandererfan   
2019-02-23 13:36   
(Last edited: 2019-03-03 14:10)
This may be a SpreadsheetWB issue. See forum post

(0012829)
Kunda1   
2019-03-03 14:09   
@wmayer can you weigh in ?
(0012845)
wmayer   
2019-03-04 09:24   
Is there an example project available to test the behaviour?
(0012848)
wandererfan   
2019-03-04 13:55   
Here is the one I've been using. Still don't know what text the OP is changing.
(0013367)
wandererfan   
2019-07-19 15:26   
How can this be "confirmed" if we don't know what the OP is talking about?
(0013368)
Kunda1   
2019-07-19 19:56   
@wandererfan hmm, looks like I did that. Not sure what my rationale was at the time. Apologies.
(0013369)
Kunda1   
2019-07-19 19:57   
@wandererfan though, instead as marking it as 'new' better to mark as 'feedback' because we are awaiting feedback from OP in that case
(0013370)
wandererfan   
2019-07-20 00:16   
@kunda1 - thought I did make it "feedback". getting old.
(0016230)
Kunda1   
2022-01-19 17:46   
@jango ping
(0016337)
wandererfan   
2022-02-02 17:07   
The forum discussion is marked as "Solved". Can we close this ticket?
(0016638)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 5803.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4820 [Arch] Bug crash always 2022-01-07 20:39 2022-02-01 07:59
Reporter: thomas-neemann Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 0.20  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
FreeCAD Information: OS: Ubuntu 20.04.1 LTS (XFCE/xubuntu)
Word size of FreeCAD: 64-bit
Version: 0.20.26720 (Git) AppImage
Build type: Release
Branch: (HEAD detached at 7bca26e)
Hash: 7bca26e7c14d4d43374ff7e0c8582735b249cbfd
Python version: 3.9.9
Qt version: 5.12.9
Coin version: 4.0.0
OCC version: 7.5.3
Locale: German/Germany (de_DE)
Summary: some self-created ifc files and many external ifc files cause frecad to crash when importing
Description:

https://forum.freecadweb.org/viewtopic.php?f=39&t=65016
Tags:
Steps To Reproduce: file import
Additional Information:
Attached Files: 923.ifc (25,164 bytes) 2022-01-07 20:39
https://tracker.freecad.org/file_download.php?file_id=2748&type=bug
Notes
(0016328)
thomas-neemann   
2022-02-01 07:59   
Thanks for the fix, it's working now


how can you change the status "new"?

OS: Ubuntu 20.04.1 LTS (XFCE/xubuntu)
Word size of FreeCAD: 64-bit
Version: 0.20.27078 (Git) AppImage
Build type: Release
Branch: (HEAD detached at bcdd926)
Hash: bcdd926686f2245fe60baface1cce1ab3dff7a5b
Python version: 3.9.9
Qt version: 5.12.9
Coin version: 4.0.0
OCC version: 7.5.3
Locale: German/Germany (de_DE)
(0017135)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6304.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4313 [FreeCAD] Feature tweak always 2020-04-12 19:01 2022-01-29 17:22
Reporter: freedman Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: feedback Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 0.20  
FreeCAD Information: OS: Windows 7
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.18.16085 (Git)
Build type: Release
Branch: master
Hash: 6323069cbbda5ac71dff073f15cc632d8a1f3ea3
Python version: 2.7.14
Qt version: 4.8.7
Coin version: 4.0.0a
OCC version: 7.2.0
Locale: English/UnitedStates (en_US)
Summary: Set "Maximum number of backup files" default to a larger number
Description: Please set the default maximum number of backup files to a larger number, it is currently set at 1. I suggest a setting of 20, this is what it used to be set to. I can think of no down-side to doing this.
Tags: #pending-PR
Steps To Reproduce: Look in Preferences-Document-Maximum number of backup files.
Additional Information: 1 backup could easily be over-written if there is model problem. The user might restart FreeCAD a couple times trying to figure out what's wrong and could possibly lose their good version of the model.

I see the value of 1 set in 0.18.16 and in (just downloaded) 19.204.
Thanks
Attached Files:
Notes
(0014340)
openBrain   
2020-04-13 07:35   
@freedman : beyond following our reporting guidelines, this kind of changes shall absolutely be discussed in the forum so we have a community consensus. Please open a topic and post link here. Thx
(0014345)
openBrain   
2020-04-14 08:09   
Forum discussion
(0016319)
Kunda1   
2022-01-27 15:16   
PR https://github.com/FreeCAD/FreeCAD/pull/5451
(0016322)
Kunda1   
2022-01-29 17:22   
I think OP means minimum here...not maximum
(0016879)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6045.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4837 [TechDraw] Feature minor have not tried 2022-01-27 18:00 2022-01-27 18:00
Reporter: NewJoker Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
FreeCAD Information: OS: Windows 10 Version 2009
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.24276 (Git)
Build type: Release
Branch: releases/FreeCAD-0-19
Hash: a88db11e0a908f6e38f92bfc5187b13ebe470438
Python version: 3.8.6+
Qt version: 5.15.1
Coin version: 4.0.1
OCC version: 7.5.0
Locale: Polish/Poland (pl_PL)
Summary: Built-in symbols
Description: It would be great to have a list of built-in symbols (standards, such as diameter, angle and geometric tolerances) accessible when creating a dimension or annotation.

Forum discussion
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0017143)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6312.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4009 [Path] Bug crash always 2019-06-06 21:44 2022-01-26 15:38
Reporter: freman Platform:  
Assigned To: mlampert OS:  
Priority: normal OS Version:  
Status: confirmed Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 0.20  
FreeCAD Information:
Summary: Dogbone locks up on path with two surface elements
Description: As discussed here, if two sufraces are selected to for a milling path and dog-bone is applied it locks up totally. This does not seem to happen with a single geometry.

https://forum.freecadweb.org/viewtopic.php?f=15&t=36832


Freecad file demonstating problem.
https://forum.freecadweb.org/download/file.php?id=85053
Tags: #tobeclosed, dogbone
Steps To Reproduce: select two surfaces
add face mill path
add dog bone dress-up
kill FreeCAD process
rince and repeat. ;)
Additional Information: OS: Linux (LXDE/LXDE)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.16854 (Git)
Build type: Release
Branch: master
Hash: fe0fd5512ba9a8a9c729cdc47af35bbe965050ac
Python version: 2.7.15
Qt version: 4.8.7
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: English/UnitedKingdom (en_GB)
Attached Files: negtest3.FCStd (38,370 bytes) 2019-06-11 01:51
https://tracker.freecad.org/file_download.php?file_id=2237&type=bug
Notes
(0013176)
sliptonic   
2019-06-11 01:51   
(Last edited: 2019-06-11 01:54)
The description is not quite accurate. A dogbone dressup works fine with two separate faces. The problem is unique to this shape.

Increasing the radius of the circular middle tier so that it overlaps the lower square resolves the error. (see attached negtest3 file)

(0014022)
Kunda1   
2020-01-08 18:24   
Any conclusions on this ticket?
(0016246)
Kunda1   
2022-01-22 22:09   
@sliptonic I've tagged this #tobeclosed
Can you let me know if anything needs to happen before closing this ticket?
(0016291)
sliptonic   
2022-01-25 15:00   
Good to close.
(0016316)
fremen   
2022-01-26 07:09   
What is the motivation to close this before the bug is fixed ?
Of course there a specific set of conditions which triggers the bug.That is the case with most bugs which don't get caught in initial testing.
Dogbone is fine mostly.

I cannot re-examine the FCStd file attached because the link no longer works but from the description it a work around. It is not showing that the original geometry was invalid in some way or that it will not be reproduced in the future.

The whole point of this test piece ( based on on ISO standard for testing CNC machine accuracy ) is that the circle diameter is identical to the side of the square. So the proposed "solution" negates the point of the part. Maybe the ISO standards should be changed so we don't need to fix FreeCAD ?
(0016317)
sliptonic   
2022-01-26 15:27   
Lots of reasons to close an issue. Lack of interest is one. If the issue isn't getting attention, even by the original poster, then it's not likely to be taken seriously by a developer.

If this is still an issue for you, we can leave it open
(0016318)
fremen   
2022-01-26 15:38   
The bug seems legitimate and not disputed. It should stay open until it gets fixed, o/w not much point in having a bug tracker and taking the trouble to report defects.

It's unfortunate that the internal changes in FC mean the original file no longer works. But the cause seems clearly identified.
(0016778)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 5944.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4443 [FreeCAD] Feature feature N/A 2020-09-25 00:44 2022-01-25 22:53
Reporter: Kunda1 Platform:  
Assigned To: OS:  
Priority: none OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 0.20  
FreeCAD Information: n/a
Summary: Safe Mode (ala LibreOffice) that offers comprehensive options to deal with user config files
Description: Apparently LO has a cool feature that helps users deal with corrupt profile/config files. It's called Safe Mode. It backs up the current config files and uses a vanilla copy. This would be mean: No more asking users to back up their ~/.FreeCAD/ and ~/.config/FreeCAD directories (well at least the majority of usecases).

Forum thread
Tags: #ready-for-migration, UI
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0015337)
Kunda1   
2021-02-13 15:05   
Helpful findConfigFiles macro by @TheMarkster that may be useful when creating this feature
https://forum.freecadweb.org/viewtopic.php?f=22&t=29888
(0015497)
Kunda1   
2021-03-09 00:16   
https://github.com/furti/FreeCAD-PreferencesPresets
(0016939)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6106.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4761 [OpenSCAD] Bug major always 2021-10-09 13:12 2022-01-25 21:59
Reporter: ozzee Platform:  
Assigned To: chennes OS:  
Priority: normal OS Version:  
Status: confirmed Product Version: 0.20  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: CSG file from OpenSCAD does not load. Part.OCCError
Description:
Log shows:
00:02:29 End processing CSG file
00:02:33 Traceback (most recent call last):
  File "C:\Users\gianni\Downloads\FreeCAD_0.20.25645_Win-LPv12.5.4_vc17.x-x86-64\Mod\OpenSCAD\OpenSCADFeatures.py", line 406, in execute
    self.createGeometry(fp)
  File "C:\Users\gianni\Downloads\FreeCAD_0.20.25645_Win-LPv12.5.4_vc17.x-x86-64\Mod\OpenSCAD\OpenSCADFeatures.py", line 448, in createGeometry
    pipe_shell.build()
<class 'Part.OCCError'>: Approx_CurvlinFunc::GetUParameter
Tags: #post-to-forum, OpenSCAD
Steps To Reproduce: Import attached CSG file.
Additional Information:
Attached Files: anchorcad_FilterFunnel_default_example.csg (21,983 bytes) 2021-10-09 13:12
https://tracker.freecad.org/file_download.php?file_id=2713&type=bug
anchorcad_FilterFunnel_default_example.scad (37,806 bytes) 2021-10-09 13:12
https://tracker.freecad.org/file_download.php?file_id=2714&type=bug
Image 25-01-2022 at 21.56.jpeg (157,378 bytes) 2022-01-25 21:59
https://tracker.freecad.org/file_download.php?file_id=2754&type=bug
linearExtrude.FCStd (31,751 bytes) 2022-01-25 21:59
https://tracker.freecad.org/file_download.php?file_id=2755&type=bug
Notes
(0015972)
openBrain   
2021-10-13 14:15   
@ozzee : could you please open a new thread in our forum (per our reporting guidelines) and add link here ? Thx
(0016134)
chennes   
2021-12-29 03:08   
The actual bit of failing code is the part that connects the circular part of the funnel to the highly-elongated part:

// 'inner'
          linear_extrude(height=25.002, twist=0.0, scale=[0.3, 2.85], $fn=128) {
            polygon(points=[[0.0, 10.0], [-0.4906767432741801, 9.987954562051724], [-0.9801714032956065, 9.95184726672197], [-1.4673047445536165, 9.89176509964781], [-1.950903220161282, 9.807852804032304], [-2.4298017990326386, 9.700312531945439], [-2.9028467725446214, 9.56940335732209], [-3.3688985339221995, 9.415440651830208], [-3.826834323650897, 9.238795325112868], [-4.275550934302819, 9.039892931234434], [-4.713967368259977, 8.819212643483551], [-5.1410274419322155, 8.577286100002722], [-5.55570233019602, 8.314696123025453], [-5.956993044924333, 8.03207531480645], [-6.3439328416364535, 7.730104533627371], [-6.715589548470184, 7.40951125354959], [-7.071067811865475, 7.0710678118654755], [-7.409511253549589, 6.715589548470185], [-7.73010453362737, 6.343932841636455], [-8.032075314806448, 5.956993044924335], [-8.314696123025453, 5.555702330196022], [-8.57728610000272, 5.141027441932218], [-8.81921264348355, 4.713967368259978], [-9.039892931234432, 4.275550934302824], [-9.238795325112868, 3.826834323650899], [-9.415440651830208, 3.3688985339221986], [-9.569403357322088, 2.902846772544624], [-9.700312531945439, 2.429801799032641], [-9.807852804032304, 1.9509032201612861], [-9.89176509964781, 1.467304744553618], [-9.951847266721968, 0.9801714032956083], [-9.987954562051724, 0.49067674327417965], [-10.0, 1.2246467991473533e-15], [-9.987954562051724, -0.4906767432741772], [-9.95184726672197, -0.9801714032956059], [-9.89176509964781, -1.4673047445536158], [-9.807852804032304, -1.9509032201612837], [-9.700312531945439, -2.429801799032638], [-9.56940335732209, -2.902846772544621], [-9.41544065183021, -3.368898533922197], [-9.238795325112868, -3.8268343236508966], [-9.039892931234434, -4.275550934302818], [-8.819212643483551, -4.7139673682599765], [-8.577286100002722, -5.1410274419322155], [-8.314696123025454, -5.55570233019602], [-8.03207531480645, -5.9569930449243325], [-7.730104533627371, -6.343932841636453], [-7.409511253549591, -6.715589548470184], [-7.071067811865477, -7.071067811865475], [-6.715589548470186, -7.409511253549589], [-6.343932841636452, -7.730104533627372], [-5.956993044924332, -8.03207531480645], [-5.555702330196022, -8.314696123025453], [-5.141027441932218, -8.57728610000272], [-4.713967368259978, -8.81921264348355], [-4.275550934302824, -9.039892931234432], [-3.8268343236509033, -9.238795325112864], [-3.3688985339222075, -9.415440651830204], [-2.9028467725446245, -9.569403357322088], [-2.4298017990326413, -9.700312531945439], [-1.9509032201612866, -9.807852804032303], [-1.4673047445536145, -9.89176509964781], [-0.9801714032956045, -9.95184726672197], [-0.4906767432741803, -9.987954562051724], [-1.8369701987210296e-15, -10.0], [0.4906767432741766, -9.987954562051724], [0.9801714032956009, -9.95184726672197], [1.4673047445536107, -9.891765099647811], [1.950903220161283, -9.807852804032304], [2.4298017990326377, -9.700312531945439], [2.9028467725446205, -9.56940335732209], [3.3688985339222044, -9.415440651830206], [3.8268343236509, -9.238795325112866], [4.275550934302822, -9.039892931234434], [4.713967368259976, -8.819212643483551], [5.1410274419322155, -8.577286100002722], [5.555702330196018, -8.314696123025454], [5.956993044924328, -8.032075314806452], [6.343932841636449, -7.730104533627374], [6.7155895484701835, -7.409511253549591], [7.071067811865474, -7.071067811865477], [7.409511253549589, -6.715589548470186], [7.730104533627365, -6.343932841636459], [8.03207531480645, -5.9569930449243325], [8.314696123025453, -5.555702330196022], [8.57728610000272, -5.141027441932219], [8.819212643483548, -4.713967368259979], [9.039892931234432, -4.275550934302825], [9.238795325112864, -3.826834323650904], [9.415440651830208, -3.3688985339222], [9.569403357322088, -2.902846772544625], [9.700312531945439, -2.4298017990326417], [9.807852804032303, -1.9509032201612873], [9.89176509964781, -1.4673047445536238], [9.95184726672197, -0.980171403295605], [9.987954562051724, -0.4906767432741809], [10.0, -2.4492935982947065e-15], [9.987954562051724, 0.490676743274176], [9.95184726672197, 0.9801714032956002], [9.89176509964781, 1.467304744553619], [9.807852804032304, 1.9509032201612824], [9.70031253194544, 2.429801799032637], [9.56940335732209, 2.90284677254462], [9.41544065183021, 3.3688985339221955], [9.238795325112868, 3.8268343236508997], [9.039892931234434, 4.275550934302821], [8.819212643483551, 4.713967368259976], [8.577286100002722, 5.141027441932215], [8.314696123025456, 5.555702330196018], [8.032075314806452, 5.956993044924328], [7.730104533627369, 6.343932841636455], [7.409511253549592, 6.7155895484701835], [7.071067811865477, 7.071067811865474], [6.715589548470186, 7.409511253549588], [6.343932841636459, 7.730104533627365], [5.9569930449243325, 8.03207531480645], [5.555702330196023, 8.314696123025453], [5.141027441932219, 8.57728610000272], [4.71396736825998, 8.819212643483548], [4.275550934302826, 9.039892931234432], [3.8268343236509046, 9.238795325112864], [3.3688985339222004, 9.415440651830208], [2.9028467725446254, 9.569403357322088], [2.429801799032642, 9.700312531945439], [1.9509032201612877, 9.807852804032303], [1.4673047445536245, 9.89176509964781], [0.9801714032956057, 9.95184726672197], [0.49067674327418154, 9.987954562051724], [3.061616997868383e-15, 10.0]]);
          }
For some reason a slight twist (approximately 10 degrees) is being applied when this transform is occurring in FreeCAD. (Note to self: that polygon is really just a circle, radius=10 I think -- no idea why it's defined as a polygon here).
(0016244)
Kunda1   
2022-01-22 22:02   
CC'ing @keithsloan52 on this too
(0016312)
keithsloan52   
2022-01-25 21:37   
Chris @chennes have you been able to create a simpler test case that shows the same error, as I am not having much luck importing with the csg or scad file just seem to be spinning.
(0016313)
chennes   
2022-01-25 21:41   
Did you try that snippet I posted just above? My recollection is that was enough to get the failure: it turned out to be pretty easy to reproduce, but I did not have a chance to debug it.
(0016315)
keithsloan52   
2022-01-25 21:59   
Not seeing any problem with Cut and paste of linear_extrude.
(0017101)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6270.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4508 [FreeCAD] Bug minor always 2020-12-09 19:41 2022-01-25 18:57
Reporter: hardrock Platform: x86  
Assigned To: OS: Ubuntu  
Priority: normal OS Version: 18.04  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 0.20  
FreeCAD Information:
OS: Ubuntu 18.04.4 LTS (Unity:Unity7:ubuntu/unity)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.
Build type: Release
Branch: unknown
Hash: 983e513704a659c1008fbaf95da6a34975cc37ac
Python version: 3.6.9
Qt version: 5.9.5
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: Russian/Russia (ru_RU)
Summary: Grouping problem (object disappearing after drag drop into group)
Description: If group and object has same prefix, then when putting object into this group, or pulling out, object may dissapear :)
After close / open project, dissapeared object will be on place before grouping operation, even if project was saved after object disappearing.
Tags: #tobeclosed
Steps To Reproduce: 1. Create a new group for example with name "Test_Group".
2. Create any kind of object, for example cube with name "Test_Cube". Name start should be the same with name start of the group.
3. Drop in / Drop out box into / from group untill it dissapear from project tree.

Object may dissapear after first drop, or may be after few.
Additional Information: https://forum.freecadweb.org/viewtopic.php?t=51344
Attached Files: grouping_bug.FCStd (4,016 bytes) 2020-12-09 19:41
https://tracker.freecad.org/file_download.php?file_id=2571&type=bug
Notes
(0015123)
hardrock   
2020-12-10 08:50   
(Last edited: 2020-12-10 08:50)
Seems like it happens not only when names have same prefix. In fact name doesn't matter.
(0015284)
chennes   
2021-02-07 03:56   
I could not reproduce on:
OS: Windows 10 Version 2004
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.23935 (Git)
Build type: Debug
Branch: master
Hash: d5b68febbb4989b290b9af36bb2cb21d61a87a2e
Python version: 3.8.6+
Qt version: 5.15.1
Coin version: 4.0.1
OCC version: 7.5.0
Locale: English/United States (en_US)
(0015375)
Kunda1   
2021-02-20 13:37   
(Last edited: 2021-02-20 13:40)
@hardrock please retest on latest v0.19_pre

Edit:
Can't reproduce on
OS: Manjaro Linux (KDE//usr/share/xsessions/plasma)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.24054 (Git) AppImage
Build type: Release
Branch: master
Hash: ed873038025277f220dfaa058599a0dfbb435835
Python version: 3.8.6
Qt version: 5.12.5
Coin version: 4.0.0
OCC version: 7.4.0
Locale: English/United States (en_US)
(0015417)
hardrock   
2021-02-21 15:40   
New video.

https://gofile.io/d/zL8ZUN

Try to drop in drop out multiple times. Problem appears not always, but frequently.

OS: Ubuntu 18.04.4 LTS (Unity:Unity7:ubuntu/unity)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.
Build type: Release
Branch: unknown
Hash: 3d227cf7179c00e57f2733f947b4b1b0368d219a
Python version: 3.6.9
Qt version: 5.9.5
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: Russian/Russia (ru_RU)
(0016306)
Kunda1   
2022-01-25 18:57   
@hardrock the clip is missing. Can you re-upload?
(0016969)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6136.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4696 [FreeCAD] Bug minor always 2021-07-02 16:50 2022-01-25 18:26
Reporter: mcgiwer Platform: amd64  
Assigned To: chennes OS: Debian  
Priority: normal OS Version: 10  
Status: assigned Product Version: 0.19  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
FreeCAD Information:
Summary: Problems with startup from command line (attached logs)
Description: When I attempt to start a fresh (just downloaded from the freecad.org website) FreeCAD from the console and add an " & " char at the end (to run it in background), I get a following error message thrown out in the terminal window:


/tmp/.mount_freecazyi6sl/AppRun: line 41: 21741 Aborted                 ${MAIN} "$@"
Tags: 0.19
Steps To Reproduce: Attempt to start FreeCAD from the console, adding after the command a space and the & character
Additional Information: For security reasons, I had replaced in the attached debug log the path to the home folder
Attached Files:
Notes
(0015735)
mcgiwer   
2021-07-14 18:28   
[UPDATE]

I had discovered that the issue was caused because xcb couldn't become loaded. I got able to fix this by typing in the console following command:

sudo xhost +si:localuser:$USER
(0015737)
mcgiwer   
2021-07-18 19:30   
(Last edited: 2021-07-18 20:44)
[UPDATE]

Note: The path where freeCAD is placed has been truncated for security reasons

After updating python to the version 3.9, it stopped to work with following errors:

`
Python path configuration:
  PYTHONHOME = '/usr/lib/python3.9' (set manually)
  PYTHONPATH = (not set)
  program name = 'bin/freecad'
  isolated = 0
  environment = 1
  user site = 1
  import site = 1
  sys._base_executable = 'bin/freecad'
  sys.base_prefix = '/usr'
  sys.base_exec_prefix = '/usr'
  sys.executable = 'bin/freecad'
  sys.prefix = '/usr'
  sys.exec_prefix = '/usr'
  sys.path = [
    '/usr/lib/python38.zip',
    '/usr/lib/python3.8',
    '/usr/lib/python3.8/lib-dynload',
  ]
Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding
Python runtime state: core initialized
ModuleNotFoundError: No module named 'encodings'

Current thread 0x00007fd8b4507800 (most recent call first):
<no Python frame>
`
Additionally, I don't know why the "PYTHONPATH" variable is displayed as not beeing set, even if it's has been exported.

Enviromental informations:

  • System: Debian 10 (64-bit Linux)
  • FreeCAD version: 0.19.2
  • Installed Python versions: 2.7 (for copatibility reasons to be able to run some extensions), 3.9

Hopefully it helps
(0015806)
chennes   
2021-08-11 17:20   
It looks like this is two different bugs, and that the first one has been resolved -- is that correct?
(0016136)
chennes   
2021-12-29 03:26   
@mcgiwer Your original bug report appears to have been resolved and was related to your system configuration. My read is that your later post here is a totally separate bug, so I plan to close this one shortly. If that is not the case, please let me know.
(0016301)
Kunda1   
2022-01-25 18:17   
@mcgiwer ping
(0016304)
mcgiwer   
2022-01-25 18:23   
@Kunda1 pong ;-p
(0016305)
mcgiwer   
2022-01-25 18:26   
@chennes The both bugs are related to each other and I'm not sure why they are becomming thrown out. To add it, this issue has appeared suddenly because in not long time earlier, the FreeCAD was working correcly. I hope it's only a temporary problem
(0017068)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6237.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
857 [FreeCAD] Feature minor have not tried 2012-10-28 08:01 2022-01-25 15:55
Reporter: wmayer Platform:  
Assigned To: wmayer OS:  
Priority: low OS Version:  
Status: assigned Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 0.20  
FreeCAD Information:
Summary: Split package into smaller ones.
Description: A meta package freecad can be offered which installs all other packages.

First mentioned: http://forum.freecadweb.org/viewtopic.php?f=10&t=3132#p24310
Formal discussion: https://forum.freecadweb.org/viewtopic.php?f=10&t=22691
Tags: #ready-for-migration, addon-manager, packaging
Steps To Reproduce:
Additional Information: https://wiki.debian.org/PkgSplit
Attached Files: freecad_0.12.5284-dfsg-5ubuntu1.debian.tar.gz (24,781 bytes) 2017-03-09 02:54
https://tracker.freecad.org/file_download.php?file_id=1543&type=bug
Notes
(0006049)
wmayer   
2015-04-19 15:04   
The steps to split FreeCAD into smaller packages:
1. Add a new package name to the control file (e.g. freecad-fem)
2. Write a file freecad-<PACKAGE>.install (e.g. freecad-fem.install)
Add there the files which should go to this package, e.g.:
usr/lib/freecad/Mod/Fem
usr/lib/freecad/lib/Fem.so
usr/lib/freecad/lib/FemGui.so
usr/share/freecad/Mod/Fem

3. Adjust the file freecad.install to avoid that the files appear in two packages. Instead of
usr/lib/freecad/Mod
usr/lib/freecad/lib
a more concrete list of files must be set.
(0006050)
wmayer   
2015-04-19 16:03   
Use "fakeroot debian/rules binary" to avoid to build from scratch.
(0008581)
normandc   
2017-03-09 02:54   
Rather than using this method, maybe look at the old freecad 0.12.5284 package from the Ubuntu 12.04 repository which didn't use any .install file but did it from the rules makefile. Attaching the debian folder for future reference as Ubuntu 12.04 will soon reach EOL and it may disappear from the packages.ubuntu.com site.
(0008935)
Kunda1   
2017-05-10 12:36   
Relevant: prerequisite checker https://forum.freecadweb.org/viewtopic.php?f=18&t=21576&p=173596#p173596
(0009178)
Kunda1   
2017-05-28 12:11   
Opened a dedicated Formal discussion: https://forum.freecadweb.org/viewtopic.php?f=10&t=22691
(0016394)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 5559.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4120 [FreeCAD] Feature minor have not tried 2019-09-09 12:53 2022-01-25 15:47
Reporter: Kunda1 Platform:  
Assigned To: Kunda1 OS:  
Priority: normal OS Version:  
Status: assigned Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 0.20  
FreeCAD Information:
Summary: Improve tooltips for the FC preference panel (make them more verbose) using the content from the wiki
Description: Relevant wiki page: https://www.freecadweb.org/wiki/Preferences_Editor
source code: /src/Gui/Dlg*.ui
Tags: #ready-for-migration, tooltips
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0016818)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 5984.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4810 [Path] General minor sometimes 2021-12-23 15:48 2022-01-25 15:14
Reporter: eldstal Platform: Linux  
Assigned To: sliptonic OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 0.20  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
FreeCAD Information: OS: Arch Linux (i3/i3)
Word size of FreeCAD: 64-bit
Version: 0.20.26683 (Git) AppImage
Build type: Release
Branch: (HEAD detached at 0388fbc)
Hash: 0388fbc98d49d874fb341b9037a743bc691d501f
Python version: 3.9.7
Qt version: 5.12.9
Coin version: 4.0.0
OCC version: 7.5.3
Locale: English/United States (en_US)
Summary: Security Vulnerability in PathSanity.py
Description: An external command execution by the PathSanity script is vulnerable to OS command injection when applied to a crafted input file.

This allows an attacker to execute arbitrary commands on the victim's system.
Tags: Path, security
Steps To Reproduce: Attacker:
1. Start with an FCStd document with some content
2. Open the Path workbench
3. Create a new Path Job object using the toolbar, assign it to any model.
4. Edit the new Path Job, in the [i]Output[i] tab, set [i]Output File[i] to ./$(galculator)
5. Save the document

Victim
1. Open the evil document
2. Open the Path workbench
3. Run the Sanity check on the evil Path Job

Result: galculator is launched by FreeCAD.
Additional Information: Impact
Arbitrary Code Execution

Caveats
The exploit sequence described above is somewhat unreliable. After working once, the PathSanity script tends to fail entirely until a new path is created. This appears to be a problem with the script itself, not related to the security vulnerability.

Cause
The invocation of asciidoctor at PathSanity.py:467 contains unsanitized text taken from the input file. Since the command is invoked using os.system(), there is no separation between command and parameter. Furthermore, the command is passed through the OS shell, which allows for more ways of injecting commands.

Proposed Mitigation
Use subprocess.Popen() instead of os.system(). This allows the command to be separated from its parameters, and prevents injection of shell commands using substitution methods (such as the $(galculator) trick demonstrated above.
Attached Files:
Notes
(0016287)
eldstal   
2022-01-25 12:58   
This vulnerability has been assigned CVE-2021-45845
(0016292)
sliptonic   
2022-01-25 15:07   
This was corrected with PR #5306. I think I used the 'fixes' tag wrong.

https://github.com/FreeCAD/FreeCAD/pull/5306
(0016293)
sliptonic   
2022-01-25 15:09   
https://github.com/FreeCAD/FreeCAD/pull/5306
(0016294)
Kunda1   
2022-01-25 15:14   
@eldstal that appimage is now dated btw
(0017129)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6298.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4527 [TechDraw] Bug minor always 2021-01-02 14:44 2022-01-25 12:53
Reporter: Roeland Huys Platform: macOS  
Assigned To: OS:  
Priority: normal OS Version: Big Sur  
Status: feedback Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 0.20  
FreeCAD Information: <!--ATTENTION:
COMPLETELY ERASE THIS AFTER PASTING YOUR
Help > About FreeCAD > Copy to clipboard
NOTE: just the snippet alone will do without anything else included.
The ticket will not be submitted without it.
-->
Summary: TechDraw page layout screwing up
Description: After deleting a dimension, the layout of the drawing page screws up.
I use MacOS Big Sur.
Tags: #pending-forum, #tobeclosed, macOS
Steps To Reproduce: Create a new page using TechDraw toolbox
Insert Multiple linked views of drawable objects
Set scale to 0.5
Arrange the views in a convenient way
Add dimensions
Delete dimension
-> Message: "These items are linked to items selected for deletion and might break. Page"
Click OK
Observe how all views are messed up.
Additional Information:
Attached Files: image.png (165,613 bytes) 2021-01-02 14:44
https://tracker.freecad.org/file_download.php?file_id=2592&type=bug
image-2.png (132,850 bytes) 2021-01-02 14:44
https://tracker.freecad.org/file_download.php?file_id=2593&type=bug
image-3.png (135,987 bytes) 2021-01-02 14:44
https://tracker.freecad.org/file_download.php?file_id=2594&type=bug
Notes
(0015241)
Kunda1   
2021-01-31 12:05   
Please post to the forum next time. Please paste your full About info in the FreeCAD Information field next time. Please open a forum thread to discuss this issue.
(0016282)
Kunda1   
2022-01-24 20:36   
Forum thread: https://forum.freecadweb.org/viewtopic.php?f=35&t=65637
(0016286)
Kunda1   
2022-01-25 12:52   
no file was attached or full version info. OP please respond or we will close ticket very soon
(0016978)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6146.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4826 [FreeCAD] Bug tweak always 2022-01-12 05:01 2022-01-25 08:29
Reporter: DustinH Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 0.19  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
FreeCAD Information: <!--ATTENTION:
COMPLETELY ERASE THIS AFTER PASTING YOUR
Help > About FreeCAD > Copy to clipboard
NOTE: just the snippet alone will do without anything else included.
The ticket will not be submitted without it.
-->
Summary: UI Rotation box can be drug out of view
Description: Sorry I don't know the name of the rotation widget in the upper right corner of the design screen, but I just accidentally drug it out of view when I tried to rotate the part with it. I can see the bottom arrow, but can't seem to drag it back onto the screen.

I of course recommend it be confined to the boundaries of the design view.
Tags: #lowhangingfruit
Steps To Reproduce: Click on whatever part drags the widget, and move the mouse up before releasing the mouse.
Additional Information:
Attached Files:
Notes
(0016204)
df1990   
2022-01-14 11:48   
Hi
This is my first comment in FreeCAD bug tracker so excuse any lack of knowledge.
I think widget @DustinH mentioned is called NaviCube and we need to modify NaviCubeImplementation::mouseMoved method.
Luckily there are already m_PrevWidth and m_PrevHeight set by NaviCubeImplementation::handleResize, so adding constraints to fit inside 0 ~ m_PrevWidth and 0 ~ m_PrevHeight should be fairly easy.
If no one has already started working on this issue I'll gladly do it.
(0016205)
DustinH   
2022-01-14 18:57   
(Last edited: 2022-01-14 18:58)
Thank you @df1990 for the addition. Its good to know what the tool is called. It slips into a feature request, but the reason I accidentally moved the NaviCube off screen is because I am coming from Fusion360 where the view can be rotated by dragging over the NaviCube. I feel like that would be a much more useful behavior than dragging the tool around the screen.
(0016217)
openBrain   
2022-01-17 16:43   
@DustinH : you should always report (potential) issues according our reporting guidelines by creating a new topic in our forum.

NaviCube position is reset on each view creation, so to recover you just have to create a new view of your document and close the previous one.
Not a big issue so, but I'll let ticket open because it can be a low hanging fruit improvement.
(0016234)
DustinH   
2022-01-19 18:56   
@openBrain Thank you for the input. I'll look at those guidelines before I post next time. For myself, I ended up reinstalling FreeCAD because I couldn't figure out how to reset the Navi Cube position. As a new user I am discovering how powerful this program it is, but also thinking about going back to Fusion because the it is not intuitive.
(0016285)
openBrain   
2022-01-25 08:29   
@DustinH : I'll be honest, FreeCAD isn't a commercial program so roughly we don't really care about users leaving. However we greatly appreciate unhappy users that take time to describe transparently in a forum topic what they don't like and how they would propose to improve FreeCAD.
On the forum, you can find several threads written by Fusion refugees that may help you transitioning (mainly people valuing owning their data :p).
(0017137)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6306.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
3803 [Sketcher] Feature tweak always 2019-01-27 11:17 2022-01-24 20:57
Reporter: markus51 Platform:  
Assigned To: OS: Win7  
Priority: low OS Version:  
Status: feedback Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 0.20  
FreeCAD Information:
Summary: Improvement of "Constraints" list in the Sketch task of the "Combo view"
Description: Some features to improve the "Constraints" list.

1.) Add a "Hide all constraints" to the "Constraints" listbox
2.) Add a "Show all constraints" to the "Constraints" listbox
3.) Add a shortcut Cltr+A to select all item in the "Constraints" listbox
4.) Add a shortcut Cltr+A to select all item in the "Elements" listbox
Tags: #post-to-forum, UI
Steps To Reproduce: 1.) Create a new sketch
2.) Draw some elemnts
3.) Goto the "Combo view" (in "Sketcher")
4.) Open the task tab
Additional Information:
Attached Files:
Notes
(0012558)
Kunda1   
2019-01-29 18:30   
(Last edited: 2019-01-29 18:30)
Where is the forum thread?
JFYI, tickets like this will get lost if they aren't discussed in the forum. The community decides if a ticket should be opened. Thank you for your comprehension.

(0013004)
Kunda1   
2019-04-06 19:05   
@abdullah Can I move this to 'Sketcher' ?
(0013024)
abdullah   
2019-04-12 17:16   
@kunda1

Sure. It is sketcher. I have just moved it.
(0013290)
abdullah   
2019-06-22 05:58   
@kunda1
@markus51

There are a couple of aspects that would benefit from community discussion:

1) Selection of all elements via language dependent shortcut (e.g. ctrl+A)

normal list shortcuts are disabled, as the lists are intended to interact with the keyboard commands of the sketcher.

The checkbox in the constraints is specific to visibility, not selection. This has to be taken into account.

However, it may be possible to add a button to select all items. Maybe a context menu entry. Here I think UI experts, which I am not, could have interesting ideas/alternatives.

2)If by "constraints listbox" the context menu of the constraints is intended, it is very easy to add. Again, maybe UI experts come with a better usability solution.

It would not be the first time I propose a UI and people come with great enriching ideas. I have learnt to leverage the knowledge of the community in this cases. I think it is important it gets discussed.
(0016712)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 5877.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4754 [FreeCAD] Bug major always 2021-09-27 14:02 2022-01-24 20:18
Reporter: basnijholt Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: feedback Product Version: 0.19  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
FreeCAD Information: OS: macOS 10.16
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.24291 (Git)
Build type: Release
Branch: (HEAD detached at 0.19.2)
Hash: 7b5e18a0759de778b74d3a5c17eba9cb815035ac
Python version: 3.8.8
Qt version: 5.12.9
Coin version: 4.0.0
OCC version: 7.4.0
Locale: C/Default (C)
Summary: recompute undos removeSplitter
Description: When calling `move`, the object moves, then I call `obj.Shape.removeSplitter()` and `doc.recompute` and the shifted box is unmoved.
Tags: #pending-forum
Steps To Reproduce: Execute the following in the Python console:

from freecad import app as FreeCAD

import Draft

doc = FreeCAD.newDocument("testDoc")
box1 = doc.addObject("Part::Box", "Box1")
doc.recompute()
box2 = Draft.move(box1, FreeCAD.Vector(1, 0, 0), copy=True)
box2.Shape = box2.Shape.removeSplitter()

doc.recompute()
Additional Information:
Attached Files:
Notes
(0015967)
openBrain   
2021-10-13 13:52   
@basnijholt : the problem is that you're not authorized to override a Shape property. You should use a new object.
I tested and there seems to me that there are 2 problem though : 1) the rendered shape is temporarily overridden (before change is rejected) + 2) trying to assign a new shape resets the Placement property -- this is what you see --

Could you please open a new thread in our forum according our reporting guidelines and post the link here ? Thx
(0016281)
Kunda1   
2022-01-24 20:16   
Forum thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=65635
(0017097)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6266.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4373 [FEM] Bug crash always 2020-06-15 06:22 2022-01-24 20:10
Reporter: david9991 Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: feedback Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 0.20  
FreeCAD Information: OS: macOS 10.15
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.21514 (Git)
Build type: Release
Branch: master
Hash: 89ddab33f692a9bd739171689f9ab0eb58d64b35
Python version: 3.8.2
Qt version: 5.12.5
Coin version: 4.0.0
OCC version: 7.4.0
Locale: C/Default (C)
Summary: Crash when create FEM pipeline
Description: Crash when create FEM pipeline
Tags: #pending-forum
Steps To Reproduce: 1. Select a FEM result
2. Click the 'Create post processing pipeline from a result object' on toolbar.
3. Crash.
Additional Information: See backtrace in attached log3.txt
Attached Files: log3.txt (5,623 bytes) 2021-12-15 09:46
https://tracker.freecad.org/file_download.php?file_id=2739&type=bug
Notes
(0014582)
berndhahnebach   
2020-06-22 13:36   
Would you try if it works for you with the FemCalculixCantilever3D example from StartWB?

This one works great for me on Linux and Windows. I can not test on OSX.

bernd

BTW: It would be better to post on the forum first before creating a bugreport. See HUGE letters Attention on top of every FreeCAD mantis page.
(0014586)
Kunda1   
2020-06-26 17:05   
@david9991 please follow up + next time please post to the forum before opening a ticket.
(0014830)
Kunda1   
2020-10-10 21:11   
@david9991 ping
please use latest v0.19 update
(0014845)
Kunda1   
2020-10-14 02:30   
@bernd who on the FEM subforum runs macOS and can test these FEM macOS-related tickets ?
(0014846)
Kunda1   
2020-10-14 02:30   
@berndhahnebach ^
(0014858)
Kunda1   
2020-10-15 14:08   
Discussion thread: https://forum.freecadweb.org/viewtopic.php?f=18&t=51186
(0016096)
yorik   
2021-12-15 09:46   
Putting the backtrace in OP in an attached txt file to workaround export issues
(0016278)
Kunda1   
2022-01-24 20:08   
bumped forum thread again
(0016279)
Kunda1   
2022-01-24 20:10   
@chrisb, could you please try to recreate on macOS ?
(0016908)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6075.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4749 [FreeCAD] Bug minor always 2021-09-23 06:57 2022-01-24 19:21
Reporter: GoodFeat Platform: PC  
Assigned To: Kunda1 OS: Windows  
Priority: high OS Version: 10  
Status: feedback Product Version: 0.19  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
FreeCAD Information: OS: Windows 10 Version 2009
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.24291 (Git)
Build type: Release
Branch: releases/FreeCAD-0-19
Hash: 7b5e18a0759de778b74d3a5c17eba9cb815035ac
Python version: 3.8.6+
Qt version: 5.15.2
Coin version: 4.0.1
OCC version: 7.5.0
Locale: Russian/Russia (ru_RU)
Summary: automatic dogumentation is not generated
Description: Hello, I am trying to go to python auto-generated documentation, but the documentation does not appear.
Instead of documentation, the error "connection interrupted" occurs

ERR_CONNECTION_RESET

Tags: #tobeclosed
Steps To Reproduce: 1) run the fricad program
2) go to the help section
3) load the automatic documentation python module
4) there is a transition to the address http://localhost: 7465/
Additional Information: if you write any characters after the address, then the documentation gives an error, for example "http://localhost:7465/ab"
Attached Files: image.png (106,053 bytes) 2021-09-23 06:57
https://tracker.freecad.org/file_download.php?file_id=2699&type=bug
image-2.png (42,903 bytes) 2021-09-23 06:57
https://tracker.freecad.org/file_download.php?file_id=2700&type=bug
image-3.png (43,976 bytes) 2021-09-23 06:57
https://tracker.freecad.org/file_download.php?file_id=2701&type=bug
Notes
(0016276)
Kunda1   
2022-01-24 19:20   
@GoodFeat I can't reproduce on
OS: Ubuntu Core 20 (KDE/plasma)
Word size of FreeCAD: 64-bit
Version: 0.20.27191 (Git)
Build type: Release
Branch: master
Hash: c4c81e6e697ec69adefccd44b9645d622ce61426
Python version: 3.8.10
Qt version: 5.15.3
Coin version: 4.0.0
OCC version: 7.5.2
Locale: English/United States (en_US)


Can you try reproducing on v0.20dev https://github.com/FreeCAD/FreeCAD-Bundle/releases/tag/weekly-builds
(0017093)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6262.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4661 [FreeCAD] Bug crash always 2021-05-19 01:18 2022-01-24 19:16
Reporter: BruceL Platform:  
Assigned To: chennes OS:  
Priority: low OS Version:  
Status: assigned Product Version: 0.19  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
FreeCAD Information:
Summary: FreeCAD crashes on spreadsheet update Due to Fillet
Description: Forum Post

FreeCAD crashes on spreadsheet update Due to Fillet
Tags: #ready-for-migration, fillet, OCC 7.6, OCC Bug, upstream
Steps To Reproduce: On the attached file, open the spreadsheet.

Change the formula in cell B6 from

=board_depth + 2 * (wall_width + part_clearance)

to

=board_depth + 2 * (thin_wall_width + part_clearance)

FreeCAD will crash with the output attached below.

I'm attempting to change the depth of the "case" pad by changing the formula as listed above.
Additional Information: Program received signal SIGSEGV, Segmentation fault.
#0 /lib/x86_64-linux-gnu/libc.so.6(+0x3bd60) [0x7f6b54484d60]
#1 0x7f6b2b362b98 in Geom2d_Curve::Value(double) const from /tmp/.mount_FreeCA0weYfg/usr/lib/./libTKG2d.so.7+0x18
0000002 0x7f6b2d505b46 in ChFi3d_Builder::PerformMoreThreeCorner(int, int) from /tmp/.mount_FreeCA0weYfg/usr/lib/./libTKFillet.so.7+0xa936
0000003 0x7f6b2d4e701e in ChFi3d_Builder::PerformIntersectionAtEnd(int) from /tmp/.mount_FreeCA0weYfg/usr/lib/./libTKFillet.so.7+0x7cfe
0000004 0x7f6b2d4eae1a in ChFi3d_Builder::PerformOneCorner(int, bool) from /tmp/.mount_FreeCA0weYfg/usr/lib/./libTKFillet.so.7+0x10ba
0000005 0x7f6b2d4874fe in ChFi3d_Builder::PerformFilletOnVertex(int) from /tmp/.mount_FreeCA0weYfg/usr/lib/./libTKFillet.so.7+0x51e
0000006 0x7f6b2d4884fc in ChFi3d_Builder::Compute() from /tmp/.mount_FreeCA0weYfg/usr/lib/./libTKFillet.so.7+0xe5c
0000007 0x7f6b2d64d504 in BRepFilletAPI_MakeFillet::Build() from /tmp/.mount_FreeCA0weYfg/usr/lib/./libTKFillet.so.7+0x34
0000008 0x7f6af984bbb1 in PartDesign::Fillet::execute() from /tmp/.mount_FreeCA0weYfg/usr/lib/_PartDesign.so+0x4b1
0000009 0x7f6b56269ec2 in App::DocumentObject::recompute() from /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libFreeCADApp.so+0x122
0000010 0x7f6b2e48962a in Part::Feature::recompute() from /tmp/.mount_FreeCA0weYfg/usr/lib/Part.so+0xa
0000011 0x7f6b561fa81d in App::Document::_recomputeFeature(App::DocumentObject*) from /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libFreeCADApp.so+0x2fd
0000012 0x7f6b56255dd6 in App::Document::recompute(std::vector<App::DocumentObject*, std::allocator<App::DocumentObject*> > const&, bool, bool*, int) from /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libFreeCADApp.so+0x5c6
0000013 0x7f6b562b557f in App::DocumentPy::recompute(_object*) from /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libFreeCADApp.so+0x2df
0000014 0x7f6b562b5749 in App::DocumentPy::staticCallback_recompute(_object*, _object*) from /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libFreeCADApp.so+0x29
0000015 /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libpython3.8.so.1.0(PyCFunction_Call+0xf5) [0x7f6b566b7725]
0000016 /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libpython3.8.so.1.0(_PyObject_MakeTpCall+0x230) [0x7f6b5665f550]
0000017 /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libpython3.8.so.1.0(_PyEval_EvalFrameDefault+0x4ddd) [0x7f6b566c928d]
0000018 /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libpython3.8.so.1.0(_PyEval_EvalCodeWithName+0x2ea) [0x7f6b56660d9a]
0000019 /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libpython3.8.so.1.0(PyEval_EvalCodeEx+0x3a) [0x7f6b566ee40a]
0000020 /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libpython3.8.so.1.0(PyEval_EvalCode+0x1c) [0x7f6b566ee42c]
0000021 /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libpython3.8.so.1.0(+0x1e05aa) [0x7f6b567135aa]
0000022 /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libpython3.8.so.1.0(+0x224225) [0x7f6b56757225]
0000023 /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libpython3.8.so.1.0(PyRun_StringFlags+0x80) [0x7f6b567572c0]
0000024 0x7f6b55f542cc in Base::InterpreterSingleton::runString[abi:cxx11](char const*) from /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libFreeCADBase.so+0x6c
0000025 0x7f6b56d6e091 in Gui::Command::_runCommand(char const*, int, Gui::Command::DoCmd_Type, char const*) from /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libFreeCADGui.so+0x91
0000026 0x7f6b56d6e231 in Gui::Command::_doCommand(char const*, int, Gui::Command::DoCmd_Type, char const*, ...) from /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libFreeCADGui.so+0x101
0000027 0x7f6af8961365 in SpreadsheetGui::SheetModel::setData(QModelIndex const&, QVariant const&, int) from /tmp/.mount_FreeCA0weYfg/usr/lib/SpreadsheetGui.so+0x105
0000028 0x7f6af8955e30 in SpreadsheetGui::SheetView::editingFinished() from /tmp/.mount_FreeCA0weYfg/usr/lib/SpreadsheetGui.so+0x140
0000029 0x7f6b5497ca18 in QMetaObject::activate(QObject*, int, int, void**) from /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libQt5Core.so.5+0x6c0
0000030 0x7f6af89478f7 in SpreadsheetGui::LineEdit::event(QEvent*) from /tmp/.mount_FreeCA0weYfg/usr/lib/SpreadsheetGui.so+0x127
0000031 0x7f6b5518c7f2 in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libQt5Widgets.so.5+0xdc
0000032 0x7f6b55190cbb in QApplication::notify(QObject*, QEvent*) from /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libQt5Widgets.so.5+0x467
0000033 0x7f6b56d3cdf9 in Gui::GUIApplication::notify(QObject*, QEvent*) from /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libFreeCADGui.so+0x89
0000034 0x7f6b54966606 in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libQt5Core.so.5+0x86
0000035 /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libQt5Widgets.so.5(+0x1aff6c) [0x7f6b551c7f6c]
0000036 0x7f6b5518c7f2 in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libQt5Widgets.so.5+0xdc
0000037 0x7f6b5519231d in QApplication::notify(QObject*, QEvent*) from /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libQt5Widgets.so.5+0x1ac9
0000038 0x7f6b56d3cdf9 in Gui::GUIApplication::notify(QObject*, QEvent*) from /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libFreeCADGui.so+0x89
#39 0x7f6b54966606 in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libQt5Core.so.5+0x86
#40 0x7f6b54d08eaa in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) from /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libQt5Gui.so.5+0xca
0000041 0x7f6b54d0b939 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) from /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libQt5Gui.so.5+0x79
0000042 0x7f6b54cf8c65 in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libQt5Gui.so.5+0x63
0000043 /tmp/.mount_FreeCA0weYfg/usr/plugins/platforms/../../lib/libQt5XcbQpa.so.5(+0x5b010) [0x7f6b501b2010]
0000044 /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/./libglib-2.0.so.0(g_main_context_dispatch+0x27d) [0x7f6b518e123d]
0000045 /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/./libglib-2.0.so.0(+0x554d1) [0x7f6b518e14d1]
0000046 /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/./libglib-2.0.so.0(g_main_context_iteration+0x31) [0x7f6b518e1571]
0000047 0x7f6b549950e8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libQt5Core.so.5+0x5e
0000048 0x7f6b54963019 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) from /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libQt5Core.so.5+0x187
0000049 0x7f6b54966e8f in QCoreApplication::exec() from /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libQt5Core.so.5+0xfd
0000050 0x7f6b56cc6926 in Gui::Application::runApplication() from /tmp/.mount_FreeCA0weYfg/usr/bin/../lib/libFreeCADGui.so+0x15f6
0000051 /tmp/.mount_FreeCA0weYfg/usr/bin/freecad(+0x44bf) [0x55a8337464bf]
0000052 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea) [0x7f6b5446fd0a]
0000053 /tmp/.mount_FreeCA0weYfg/usr/bin/freecad(+0x47d9) [0x55a8337467d9]
Attached Files:
Notes
(0015664)
BruceL   
2021-05-19 01:22   
Trying again to upload the file, I'm informed that there's no space on the webserver.
(0015665)
BruceL   
2021-05-19 01:23   
I'm not able to upload the file to the bug tracker. It's available on the forum here
(0015825)
chennes   
2021-08-17 16:57   
Can you still reproduce this on the latest HEAD? I am not getting a crash right now.
(0015829)
BruceL   
2021-08-19 21:22   
I can report that the crash still occurs on the latest weekly Appimage (25429).

I'll see what's involved in running the latest HEAD version.
(0015842)
chennes   
2021-08-20 15:13   
If the AppImage is compiled against the official OpenCASCADE libraries, rather than the "blobfish" patched version, then we'll just have to wait for OCCT 7.6 to be released to fix this.
(0015844)
BruceL   
2021-08-20 21:03   
I suspect that's the case, the current Appimage shows it using the OCC 7.5.2 libraries.
(0017050)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6219.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4648 [FreeCAD] Bug minor always 2021-04-29 17:11 2022-01-24 19:16
Reporter: Spindoctor Platform: AMD x64  
Assigned To: OS: Debian  
Priority: normal OS Version: Bullseye (AppIma  
Status: new Product Version: 0.20  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
FreeCAD Information: OS: Debian GNU/Linux bullseye/sid (GNOME/gnome-xorg)
Word size of FreeCAD: 64-bit
Version: 0.20.24693 (Git) AppImage
Build type: Release
Branch: master
Hash: e01f0d25d5f3ef9ceb66aa087212121e9f2f2e8b
Python version: 3.9.2
Qt version: 5.12.9
Coin version: 4.0.0
OCC version: 7.5.1
Locale: German/Austria (de_AT)
Summary: Polar Pattern of Loft does not work on certain objects
Description: The rotate pattern features does not work for a loft on a specified object.



It does work, when the clones generated by the Polar pattern overlap, but it fails when they don't.

The behaviour is described in this forum thread:
https://forum.freecadweb.org/viewtopic.php?f=3&t=58097

Please find a file that contains an object with this problem attached to this bug report.
Tags: #ready-for-migration, OCC Bug, Part Design, PolarPattern, Sketch
Steps To Reproduce: To illustrate the behaviour, I added an octagon to Sketch001 in the file attached.



When you drag the vertical line inside of the octagon, the clones will overlap - the polar pattern then works as expected.

When you drag it back outside of the octagon, the polar pattern would fail again.
Additional Information:
Attached Files: Rotate Loft Problem 2.FCStd (212,849 bytes) 2021-04-29 17:11
https://tracker.freecad.org/file_download.php?file_id=2682&type=bug
Notes
(0017042)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6210.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4639 [TechDraw] Bug minor always 2021-04-20 21:56 2022-01-24 19:16
Reporter: run_the_race Platform: PC  
Assigned To: OS: Windows 10  
Priority: normal OS Version: 2004  
Status: feedback Product Version: 0.19  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
FreeCAD Information: OS: Windows 10 Version 2004
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.24276 (Git)
Build type: Release
Branch: releases/FreeCAD-0-19
Hash: a88db11e0a908f6e38f92bfc5187b13ebe470438
Python version: 3.8.6+
Qt version: 5.15.1
Coin version: 4.0.1
OCC version: 7.5.0
Locale: English/United Kingdom (en_GB)
Summary: TechDraw not drawing all lines in view
Description: TechDraw is missing some lines in the isometric view
Tags: #pending-forum, #ready-for-migration, OCC Bug
Steps To Reproduce: 1. Open the attached file raspberry_pi_4b.FCStd
2. Open "Page" item in the tree browser
3. Look at the isometric view.
4. Notice some of the 40way header pins are missing vertical lines, as shown by the attached images.
Additional Information:
Attached Files: raspberry_pi_4b.FCStd (319,189 bytes) 2021-04-20 21:56
https://tracker.freecad.org/file_download.php?file_id=2675&type=bug
missing vertical lines - ub tech draw.png (101,081 bytes) 2021-04-20 21:56
https://tracker.freecad.org/file_download.php?file_id=2676&type=bug
missing vertical lines - printed.png (83,512 bytes) 2021-04-20 21:56
https://tracker.freecad.org/file_download.php?file_id=2677&type=bug
Notes
(0015634)
Kunda1   
2021-04-21 18:26   
it's 'TechDraw' not 'tech draw'. Edited ticket.
I'll start a discussion for you on the forum.
(0015635)
Kunda1   
2021-04-21 18:27   
Discussion at https://forum.freecadweb.org/viewtopic.php?f=35&t=57994
(0016172)
wandererfan   
2021-12-30 20:35   
Some of the overlapping vertical lines for the pins are being treated as "hard hidden" instead of "hard visible". Only part of the edge is hidden - does OCC not split the edge into visible and invisible portions before classifying??
(0016181)
wandererfan   
2022-01-02 17:18   
is there a connection with 4564 short and/or overlapping lines not drawn??
(0016195)
wandererfan   
2022-01-06 18:26   
using the perspective projector with a long focal length shows all the lines (also gives a better result for 4564).

this has come up before, but I can't find an upstream ticket.
(0017035)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6203.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4350 [FreeCAD] Bug minor always 2020-05-28 05:37 2022-01-24 19:16
Reporter: TedM Platform: Windows  
Assigned To: OS: Windows 10 Home  
Priority: normal OS Version: 1909 18363.836  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 0.20  
FreeCAD Information: OS: Windows 10 (10.0)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.21125 (Git)
Build type: Release
Branch: master
Hash: 40600a55c2fe71ff589be677f6e427ccc937d003
Python version: 3.8.2
Qt version: 5.12.5
Coin version: 4.0.0
OCC version: 7.4.0
Locale: English/United States (en_US)
Summary: Pad or Pocket of ShapeString in Part Design causes BOPcheck to abort (OCC bug)
Description: Forum link

After successfully making a pocket or pad of a ShapeString within a Part Design body, BOP Check fails with "Solid1 : Solid : BOPAlgo OperationAborted".
Tags: #ready-for-migration, 0.19, OCC Bug, OCC NotOnRoadmap, Part Design, shapestring, upstream
Steps To Reproduce:
  1. Create new document.
  2. Go to Part Design workbench and create a body.
  3. Create a sketch of a fully constrained rectangle and pad it.
  4. Go to Draft workbench and create a ShapeString, small enough to fit in the rectangle.
  5. Go back to Part Design workbench.
  6. Move the ShapeString into the body and position so it is sitting on the surface of the pad.
  7. Using the shapeString, either make a pocket into (but not through) the solid or make a pad onto the surface of the solid.
  8. Go to Part workbench.
  9. Select the body and select "Analyzes Geometry for Errors".
  10. Check "Run BOP Check" and, under "Individual BOP Checks", check "Self-Intersect".
  11. Click "Run Check".
  12. Error result is "... Solid : BOPAlgo OperationAborted".
Additional Information: Also tested under release 0.18.4 and "Analyzes Geometry for Errors" with BOPCheck enabled simply causes FreeCAD to crash (program closes).

The examples use an open-source font from Google for portability. My original encounter was using a native Windows font.

Note: It has been suggested that this may be related to an upstream OCC bug: https://tracker.dev.opencascade.org/view.php?id=31522

Note: Tracking this ticket and upstream in OCC bugs in FreeCAD forum thread
Attached Files: Roboto-Bold.ttf (170,348 bytes) 2020-05-28 05:37
https://tracker.freecad.org/file_download.php?file_id=2469&type=bug
shapestringcut.FCStd (75,091 bytes) 2020-05-28 05:37
https://tracker.freecad.org/file_download.php?file_id=2470&type=bug
shapestringpad.FCStd (106,140 bytes) 2020-05-28 05:37
https://tracker.freecad.org/file_download.php?file_id=2471&type=bug
Notes
(0014442)
TedM   
2020-05-30 07:21   
When reading through the forum thread, please ignore early replies disputing the problem. There was confusion from some of the posters where they were looking at a suggested workaround file instead of my original.

Further testing reported on the forum thread show these results:
  • Lone ShapeString => No error
  • ShapeString with Part/Extrude => Error
  • ShapeString with PartDesign/Pad => Error
  • ShapeString with PartDesign/Pocket => Error
  • Any failing case above exported as STEP then reimported => No error
  • ShapeString converted to sketch then Extrude/Pad/Pocket => No error
  • Error only occurs if the text/font includes curves. Text without curves, for example "TTTTkkkk" in a sans-serif font => No error

It has been suggested that this may be a duplicate of https://tracker.dev.opencascade.org/view.php?id=31522

@chrisb reports that the problem also occurs under MacOS:
OS: macOS High Sierra (10.13)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.21125 (Git)
Build type: Release
Branch: master
Hash: 40600a55c2fe71ff589be677f6e427ccc937d003
Python version: 3.8.2
Qt version: 5.12.5
Coin version: 4.0.0
OCC version: 7.4.0
Locale: C/Default (C)
(0014446)
Kunda1   
2020-05-30 15:20   
Updated ticket to reflect it may be an upstream bug. Please notate ticket if in fact it is an I will track both this ticket and upstream via a forum thread that tracks OCC bugs in FreeCAD: https://forum.freecadweb.org/viewtopic.php?t=20264
(0015184)
Kunda1   
2020-12-31 12:20   
(Last edited: 2020-12-31 12:21)
Can someone bump the upstream ticket, please ? (and also confirm this exists on OCC 7.5.0?)
This ticket is being tracked from OCC Bugs in the Bugtracker forum thread.
(0016898)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6065.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4311 [FreeCAD] Bug crash always 2020-04-11 23:47 2022-01-24 19:16
Reporter: BruceL Platform:  
Assigned To: OS: Debian GNU/Linux bullseye/sid  
Priority: low OS Version:  
Status: acknowledged Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 0.20  
FreeCAD Information: OS: Debian GNU/Linux bullseye/sid (GNOME/gnome)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.20406 (Git) AppImage
Build type: Release
Branch: master
Hash: bb45a2b01f9aafeae00cdf60c87b43fc36ad28ad
Python version: 3.8.2
Qt version: 5.12.5
Coin version: 4.0.0
OCC version: 7.4.0
Locale: English/Canada (en_CA)
Summary: Crash on a loft command with incorrect input (OCC bug)
Description: I'm experience a crash on 0.19-20406 Appimage. But with an admittedly wrong user input, but I would think that the program should complain to me instead of crashing. Lofting and adding the section that was used to start the loft will crash FreeCAD.

Thank you in advance for you time.

Forum post: https://forum.freecadweb.org/viewtopic.php?f=8&t=45013&p=386183#p386183

Note: this ticket is be tracked via OCC bugs in the bugtracker forum thread
Tags: #ready-for-migration, OCC 7.5, OCC Bug, OCC NotOnRoadmap, upstream
Steps To Reproduce: 1. Create a new file
2. Go to part design workbench
3. Draw a simple sketch on XY plane, ie a rectangle
4. Draw another simple sketch either on a different plane, or on a parallel plane
5. select one sketch
6. click additive loft
7. Click add section
8. click on the first sketch (yes, this is wrong).
9. Click add section
10. click on the second sketch.
11. Crash.
Additional Information: Reading failed from embedded file: PartShape.bin (0 bytes, 2 bytes compressed)
6.79e-07 <App> Document.cpp(3715): Failed to recompute crash#AdditiveLoft: Loft: At least one section is needed
Recompute failed! Please check report view.
0.0035612 <App> Document.cpp(3715): Failed to recompute crash#AdditiveLoft: Loft: At least one section is needed
Recompute failed! Please check report view.
3.67836 <App> Document.cpp(3715): Failed to recompute crash#AdditiveLoft: Loft could not be built
3.7744 Tree.cpp(293): [TreeView] duplicate child item crash#AdditiveLoft.Sketch
3.77562 Tree.cpp(293): [ComboView] duplicate child item crash#AdditiveLoft.Sketch
Program received signal SIGSEGV, Segmentation fault.
#0 /lib/x86_64-linux-gnu/libc.so.6(+0x3b7e0) [0x7f5d0350e7e0]
#1 /tmp/.mount_FreeCAhwE8MW/usr/lib/./libTKTopAlgo.so.7(+0x17a177) [0x7f5cdbfcd177]
0000002 0x7f5cdbfcdb72 in BRepLib::EncodeRegularity(TopoDS_Shape const&, double) from /tmp/.mount_FreeCAhwE8MW/usr/lib/./libTKTopAlgo.so.7+0x152
0000003 0x7f5cdd607c26 in BRepOffsetAPI_ThruSections::Build() from /tmp/.mount_FreeCAhwE8MW/usr/lib/./libTKOffset.so.7+0xd16
0000004 0x7f5c6afae337 in PartDesign::Loft::execute() from /tmp/.mount_FreeCAhwE8MW/usr/lib/_PartDesign.so+0x7f7
0000005 0x7f5d0529956e in App::DocumentObject::recompute() from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libFreeCADApp.so+0x9e
0000006 0x7f5cddd6818c in Part::Feature::recompute() from /tmp/.mount_FreeCAhwE8MW/usr/lib/Part.so+0xc
0000007 0x7f5d0522fded in App::Document::_recomputeFeature(App::DocumentObject*) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libFreeCADApp.so+0x2fd
0000008 0x7f5d0528904c in App::Document::recomputeFeature(App::DocumentObject*, bool) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libFreeCADApp.so+0xdc
0000009 0x7f5c6a4cd2b2 in PartDesignGui::TaskLoftParameters::onSelectionChanged(Gui::SelectionChanges const&) from /tmp/.mount_FreeCAhwE8MW/usr/lib/PartDesignGui.so+0x122
0000010 0x7f5d0618286e in Gui::SelectionObserver::_onSelectionChanged(Gui::SelectionChanges const&) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libFreeCADGui.so+0x4e
0000011 /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libFreeCADGui.so(+0x5cc47c) [0x7f5d05ede47c]
0000012 0x7f5d06190917 in Gui::SelectionSingleton::slotSelectionChanged(Gui::SelectionChanges const&) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libFreeCADGui.so+0x2b7
0000013 /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libFreeCADGui.so(+0x5cc47c) [0x7f5d05ede47c]
0000014 0x7f5d06191566 in Gui::SelectionSingleton::notify(Gui::SelectionChanges&&) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libFreeCADGui.so+0xf6
0000015 0x7f5d0619a762 in Gui::SelectionSingleton::addSelection(char const*, char const*, char const*, float, float, float, std::vector<Gui::SelectionSingleton::SelObj, std::allocator<Gui::SelectionSingleton::SelObj> > const*, bool) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libFreeCADGui.so+0x7e2
0000016 0x7f5d05f74891 in Gui::SoFCUnifiedSelection::setSelection(std::vector<Gui::SoFCUnifiedSelection::PickedInfo, std::allocator<Gui::SoFCUnifiedSelection::PickedInfo> > const&, bool) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libFreeCADGui.so+0x8f1
0000017 0x7f5d05f75dd1 in Gui::SoFCUnifiedSelection::handleEvent(SoHandleEventAction*) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libFreeCADGui.so+0x141
0000018 0x7f5d048a923a in SoAction::traverse(SoNode*) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libCoin.so.80+0x6a
0000019 0x7f5d04a9384b in SoChildList::traverse(SoAction*, int, int) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libCoin.so.80+0xeb
0000020 0x7f5d04aeb378 in SoGroup::doAction(SoAction*) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libCoin.so.80+0x58
0000021 0x7f5d04b08b3a in SoSeparator::doAction(SoAction*) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libCoin.so.80+0x2a
0000022 0x7f5d048a923a in SoAction::traverse(SoNode*) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libCoin.so.80+0x6a
0000023 0x7f5d048b3960 in SoHandleEventAction::beginTraversal(SoNode*) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libCoin.so.80+0x70
0000024 0x7f5d048aa0a2 in SoAction::apply(SoNode*) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libCoin.so.80+0x442
0000025 0x7f5d04ab379b in SoEventManager::processEvent(SoEvent const*) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libCoin.so.80+0x15b
0000026 0x7f5d05ff8fee in SIM::Coin3D::Quarter::QuarterWidget::processSoEvent(SoEvent const*) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libFreeCADGui.so+0x1e
0000027 0x7f5d06001d6a in SIM::Coin3D::Quarter::SoQTQuarterAdaptor::processSoEvent(SoEvent const*) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libFreeCADGui.so+0x5a
0000028 0x7f5d0603bf3a in Gui::View3DInventorViewer::processSoEventBase(SoEvent const*) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libFreeCADGui.so+0xa
0000029 0x7f5d060118ca in Gui::BlenderNavigationStyle::processSoEvent(SoEvent const*) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libFreeCADGui.so+0x22a
0000030 0x7f5d0600cea8 in Gui::NavigationStyle::processEvent(SoEvent const*) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libFreeCADGui.so+0xf8
0000031 0x7f5d0603bea5 in Gui::View3DInventorViewer::processSoEvent(SoEvent const*) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libFreeCADGui.so+0x65
0000032 0x7f5d05fefe05 in SIM::Coin3D::Quarter::EventFilter::eventFilter(QObject*, QEvent*) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libFreeCADGui.so+0x185
0000033 0x7f5d039ebb6d in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libQt5Core.so.5+0xd1
0000034 0x7f5d0421781a in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libQt5Widgets.so.5+0xce
0000035 0x7f5d0421c095 in QApplication::notify(QObject*, QEvent*) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libQt5Widgets.so.5+0x79d
0000036 0x7f5d05d1bae9 in Gui::GUIApplication::notify(QObject*, QEvent*) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libFreeCADGui.so+0x89
0000037 0x7f5d039ee186 in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libQt5Core.so.5+0x88
0000038 0x7f5d0421b53f in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool, bool) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libQt5Widgets.so.5+0x283
#39 /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libQt5Widgets.so.5(+0x1af554) [0x7f5d04252554]
#40 /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libQt5Widgets.so.5(+0x1b03a6) [0x7f5d042533a6]
0000041 0x7f5d0421782a in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libQt5Widgets.so.5+0xde
0000042 0x7f5d0421d3f1 in QApplication::notify(QObject*, QEvent*) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libQt5Widgets.so.5+0x1af9
0000043 0x7f5d05d1bae9 in Gui::GUIApplication::notify(QObject*, QEvent*) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libFreeCADGui.so+0x89
0000044 0x7f5d039ee186 in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libQt5Core.so.5+0x88
0000045 0x7f5d03d9440b in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libQt5Gui.so.5+0x6d3
0000046 0x7f5d03d94ff7 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libQt5Gui.so.5+0x175
0000047 0x7f5d03d81dd4 in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libQt5Gui.so.5+0x64
0000048 /tmp/.mount_FreeCAhwE8MW/usr/plugins/platforms/../../lib/libQt5XcbQpa.so.5(+0x5af0e) [0x7f5cff8cbf0e]
0000049 /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/./libglib-2.0.so.0(g_main_context_dispatch+0x2e8) [0x7f5d00ac39d8]
0000050 /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/./libglib-2.0.so.0(+0x51c21) [0x7f5d00ac3c21]
0000051 /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/./libglib-2.0.so.0(g_main_context_iteration+0x2e) [0x7f5d00ac3cae]
0000052 0x7f5d03a1d42b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libQt5Core.so.5+0x63
0000053 0x7f5d039eabc1 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libQt5Core.so.5+0x187
0000054 0x7f5d039eea39 in QCoreApplication::exec() from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libQt5Core.so.5+0x105
0000055 0x7f5d05c944ea in Gui::Application::runApplication() from /tmp/.mount_FreeCAhwE8MW/usr/bin/../lib/libFreeCADGui.so+0x155a
0000056 /tmp/.mount_FreeCAhwE8MW/usr/bin/freecad(main+0x74d) [0x561431e1e7cd]
0000057 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7f5d034f9e0b]
0000058 /tmp/.mount_FreeCAhwE8MW/usr/bin/freecad(+0x451f) [0x561431e1f51f]
Attached Files:
Notes
(0014978)
chennes   
2020-11-12 04:16   
(Last edited: 2020-11-12 04:16)
The bug is really in OCC (https://forum.freecadweb.org/viewtopic.php?f=8&t=45013&p=447258#p447258) -- do we want to try to work around it, at least this exact incarnation, by preventing the original profile from being selected as a section?
(0015185)
Kunda1   
2020-12-31 12:25   
Tracking this via OCC bugs in the bugtracker forum thread
(0016213)
Kunda1   
2022-01-15 13:51   
This needs an upstream ticket
(0016878)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6044.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4275 [FreeCAD] Bug major always 2020-03-01 10:17 2022-01-24 19:16
Reporter: Hakanseven12 Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: confirmed Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 0.20  
FreeCAD Information: OS: Windows 10 (10.0)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.19697 (Git)
Build type: Release
Branch: master
Hash: 8832356802011bf5d70e9d6f0efa89c47bc70a91
Python version: 3.7.3
Qt version: 5.12.5
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: Turkish/Turkey (tr_TR)
Summary: [OCC/Coin] Rendering issue with large coordinate values
Description: When I created an object(wire,point,mesh etc.) at large coordinate values(eight or nine orders of magnitude), object look vawy. When zoom in or zoom out objects change their positions.

I think OCC uses 32bit float variables and it dont work properly at large coordinates. FreeCAD need a general solution that works for every workbench at large coordinates.

In the script below, I create a list with several points with the larger values, then re-reference those points w.r.t the start to 'normalize' them and get the values into a smaller range. The difference is obvious when it gets rendered.
Tags: #ready-for-migration, Coin3d, OCC Bug
Steps To Reproduce: Run this macro

from FreeCAD import Vector
import Part

points = [
    Vector (4275011518.128912, 507510589.4751387, 0.0),
    Vector (4275011717.0043764, 507511569.4996429, 0.0),
    Vector (4275011913.4291606, 507512550.0182727, 0.0),
    Vector (4275012107.4020367, 507513531.0248998, 0.0),
    Vector (4275012298.921793, 507514512.5133929, 0.0),
    Vector (4275012487.987232, 507515494.4776178, 0.0),
    Vector (4275012674.5971723, 507516476.91143715, 0.0),
    Vector (4275012858.7504473, 507517459.80871075, 0.0),
    Vector (4275013040.445906, 507518443.1632955, 0.0),
    Vector (4275013219.6824136, 507519426.96904546, 0.0),
    Vector (4275013396.4588485, 507520411.21981186, 0.0),
    Vector (4275013570.774107, 507521395.9094431, 0.0),
    Vector (4275013742.6270995, 507522381.0317848, 0.0),
    Vector (4275013912.0167513, 507523366.5806801, 0.0),
    Vector (4275014078.942004, 507524352.5499692, 0.0),
    Vector (4275014243.401815, 507525338.93348986, 0.0),
    Vector (4275014405.3951554, 507526325.72507715, 0.0),
    Vector (4275014564.9210134, 507527312.9185637, 0.0),
    Vector (4275014721.9783916, 507528300.5077795, 0.0),
    Vector (4275014876.5663085, 507529288.48655206, 0.0),
    Vector (4275015028.6837983, 507530276.8487066, 0.0),
    Vector (4275015178.3299093, 507531265.58806586, 0.0),
    Vector (4275015325.5037074, 507532254.6984502, 0.0),
    Vector (4275015470.204272, 507533244.1736777, 0.0),
    Vector (4275015612.430699, 507534234.00756407, 0.0),
    Vector (4275015752.1820993, 507535224.19392294, 0.0),
    Vector (4275015889.4575996, 507536214.7265656, 0.0),
    Vector (4275016024.256342, 507537205.5993012, 0.0),
    Vector (4275016156.5774837, 507538196.80593693, 0.0),
    Vector (4275016286.420198, 507539188.3402776, 0.0),
    Vector (4275016413.783673, 507540180.19612616, 0.0),
    Vector (4275016538.6671133, 507541172.3672835, 0.0),
    Vector (4275016661.069738, 507542164.84754866, 0.0),
    Vector (4275016780.990782, 507543157.6307185, 0.0),
    Vector (4275016898.429496, 507544150.7105882, 0.0),
    Vector (4275017013.3851457, 507545144.08095104, 0.0),
    Vector (4275017125.857013, 507546137.7355984, 0.0),
    Vector (4275017235.8443947, 507547131.66832, 0.0),
    Vector (4275017343.346604, 507548125.8729037, 0.0),
    Vector (4275017448.362968, 507549120.3431357, 0.0),
    Vector (4275017550.892831, 507550115.0728007, 0.0),
    Vector (4275017650.9355516, 507551110.0556815, 0.0),
    Vector (4275017748.4905057, 507552105.2855596, 0.0),
    Vector (4275017843.557082, 507553100.7562147, 0.0),
    Vector (4275017936.134688, 507554096.4614251, 0.0),
    Vector (4275018026.222744, 507555092.39496773, 0.0),
    Vector (4275018113.820687, 507556088.550618, 0.0),
    Vector (4275018198.92797, 507557084.9221499, 0.0),
    Vector (4275018281.5440607, 507558081.50333613, 0.0),
    Vector (4275018361.6684427, 507559078.287948, 0.0),
    Vector (4275018439.3006153, 507560075.2697558, 0.0),
    Vector (4275018514.4400935, 507561072.4425281, 0.0),
    Vector (4275018587.0864077, 507562069.80003285, 0.0),
    Vector (4275018657.239104, 507563067.3360364, 0.0),
    Vector (4275018724.897743, 507564065.04430425, 0.0),
    Vector (4275018790.061903, 507565062.9186007, 0.0),
    Vector (4275018852.731176, 507566060.95268893, 0.0),
    Vector (4275018912.905171, 507567059.1403314, 0.0),
    Vector (4275018970.583511, 507568057.47528934, 0.0),
    Vector (4275019025.765836, 507569055.95132315, 0.0),
    Vector (4275019078.451801, 507570054.56219244, 0.0),
    Vector (4275019128.6410766, 507571053.3016559, 0.0),
    Vector (4275019176.3333497, 507572052.1634713, 0.0),
    Vector (4275019221.5283217, 507573051.14139575, 0.0),
    Vector (4275019264.2257104, 507574050.2291858, 0.0),
    Vector (4275019304.4252486, 507575049.420597, 0.0),
    Vector (4275019342.1266856, 507576048.70938456, 0.0),
    Vector (4275019377.329785, 507577048.0893028, 0.0),
    Vector (4275019410.0343275, 507578047.5541056, 0.0),
    Vector (4275019440.240108, 507579047.09754634, 0.0),
    Vector (4275019467.9469385, 507580046.7133779, 0.0),
    Vector (4275019493.1546454, 507581046.39535266, 0.0),
    Vector (4275019515.863071, 507582046.13722265, 0.0),
    Vector (4275019536.072074, 507583045.93273944, 0.0),
    Vector (4275019553.781527, 507584045.7756543, 0.0),
    Vector (4275019568.9913206, 507585045.6597183, 0.0),
    Vector (4275019581.701359, 507586045.578682, 0.0),
    Vector (4275019591.9115624, 507587045.52629614, 0.0),
    Vector (4275019599.6218677, 507588045.49631083, 0.0),
    Vector (4275019604.8322268, 507589045.4824764, 0.0),
    Vector (4275019607.5426064, 507590045.4785429, 0.0),
    Vector (4275019607.7529902, 507591045.47826034, 0.0),
    Vector (4275019605.4633765, 507592045.47537875, 0.0),
    Vector (4275019600.67378, 507593045.46364814, 0.0),
    Vector (4275019593.3842306, 507594045.4368186, 0.0),
    Vector (4275019583.5947733, 507595045.3886403, 0.0),
    Vector (4275019571.3054695, 507596045.3128635, 0.0),
    Vector (4275019556.5163965, 507597045.2032388, 0.0),
    Vector (4275019539.2276464, 507598045.0535167, 0.0),
    Vector (4275019519.439327, 507599044.8574483, 0.0),
    Vector (4275019497.151562, 507600044.60878474, 0.0),
    Vector (4275019472.3644915, 507601044.3012776, 0.0),
    Vector (4275019445.0782695, 507602043.9286788, 0.0),
    Vector (4275019415.293067, 507603043.4847407, 0.0),
    Vector (4275019402.2241297, 507603457.47993255, 0.0)
]

points_2 = []

for _pt in points:
    points_2.append(_pt.sub(points[0]))

curve_1 = Part.makePolygon(points)
curve_2 = Part.makePolygon(points_2)

curve_1.Placement.Base = Vector(points[0]).multiply(-1.0)
curve_1.Placement.Base.x += 1000.0

Part.show(curve_1)
Part.show(curve_2)
Additional Information: Tracking this via OCC bugs in the bugtracker forum thread
Attached Files: OCC Bug.png (9,239 bytes) 2020-03-01 10:17
https://tracker.freecad.org/file_download.php?file_id=2434&type=bug
Notes
(0014191)
wmayer   
2020-03-01 11:49   
The problem is that the internal view and model matrices of Coin3d causes quite big round-off errors when multiplying with huge coordinate values.
(0014192)
Kunda1   
2020-03-01 12:17   
OP, please link back to forum thread discussions when you open a ticket, it makes tracking convenient for devs and triaging, thanks!

https://forum.freecadweb.org/viewtopic.php?f=10&t=35935
https://forum.freecadweb.org/viewtopic.php?f=3&t=36362
(0014193)
Kunda1   
2020-03-01 12:18   
Is anyone going to check and if need be open a ticket on the coin3d bugtracker ?
https://github.com/coin3d/coin
(0014196)
Hakanseven12   
2020-03-02 10:07   
(Last edited: 2020-03-02 10:08)
I opened a ticket and got this answer:
https://github.com/coin3d/coin/issues/371
(0014203)
Hakanseven12   
2020-03-03 20:19   
(Last edited: 2020-03-03 20:20)
I think core implementation of this Coin class can solve problem
https://coin3d.github.io/Coin/html/classSoGeoOrigin.html#details
(0014319)
Hakanseven12   
2020-04-04 23:52   
Is there any interest for this or is it postponed to 0.20?
(0014322)
Kunda1   
2020-04-05 13:15   
(Last edited: 2020-04-05 13:15)
@Hakanseven12 Can you write-up a proposal, perhaps a dev will read it and take it on ?
(0014415)
Hakanseven12   
2020-05-11 21:46   
(Last edited: 2020-05-11 21:49)
We are start to working on something. https://forum.freecadweb.org/viewtopic.php?f=8&t=22277&start=980#p395784

Also I created a guide to use SoGeo classes. https://forum.freecadweb.org/viewtopic.php?f=3&t=36362

I hope the other FreeCAD workbenches will be start to integrate SoGeo objects.
(0015186)
Kunda1   
2020-12-31 12:28   
@Hakanseven12 is this also an upstream OCC bug ?
(0015193)
Kunda1   
2020-12-31 13:07   
Tracking this via OCC bugs in the bugtracker forum thread
(0016870)
yorik   
2022-03-03 13:55   
This ticket has been migrated to GitHub as issue 6036.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4247 [Part] Bug block always 2020-01-13 13:50 2022-01-24 19:16
Reporter: CyrilWaechter Platform: Gnu/Linux 64-bits  
Assigned To: OS: Manjaro Linux (GNOME/gnome)  
Priority: normal OS Version: 5.4.6  
Status: resolved Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 0.20  
FreeCAD Information: OS: Manjaro Linux (GNOME/gnome)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19 (Git)
Build type: Release
Branch: master
Hash: 49e4e45ff38b0459f0f9a76df634f6da4995b731
Python version: 3.8.1
Qt version: 5.14.0
Coin version: 4.0.0a
OCC version: 7.4.0
Locale: French/Switzerland (fr_CH)
Summary: GeometryCurvePy::intersect / GeometryCurvePy::intersectCC Segmentation Fault with OCC 7.4 (Fixed in OCC 7.5)
Description: Calling function intersect / intersectCC with 2 colinear lines crash FreeCAD with OCC 7.4.
Forum post : https://forum.freecadweb.org/viewtopic.php?f=19&t=42361

  • Error message :
  • Program received signal SIGSEGV, Segmentation fault.
    #0  /usr/lib/libc.so.6(+0x3bfb0) [0x7f1718865fb0]
    #1  0x7f168e3003a4 in Extrema_ExtCC::Points(int, Extrema_POnCurv&, Extrema_POnCurv&) const from /usr/lib/libTKGeomBase.so.7+0x54
    0000002  0x7f168eae20d7 in GeomAPI_ExtremaCurveCurve::Points(int, gp_Pnt&, gp_Pnt&) const from /usr/lib/libTKGeomAlgo.so.7+0x57
    0000003  0x7f1690dbe550 in Part::GeomCurve::intersect(opencascade::handle<Geom_Curve>, opencascade::handle<Geom_Curve>, std::vector<std::pair<Base::Vector3<double>, Base::Vector3<double> >, std::allocator<std::pair<Base::Vector3<double>, Base::Vector3<double> > > >&, double) from /usr/lib/freecad/lib/Part.so+0x3e0
    0000004  0x7f1690dbeb2e in Part::GeomCurve::intersect(Part::GeomCurve*, std::vector<std::pair<Base::Vector3<double>, Base::Vector3<double> >, std::allocator<std::pair<Base::Vector3<double>, Base::Vector3<double> > > >&, double) const from /usr/lib/freecad/lib/Part.so+0xfe
    0000005  0x7f1690cacfbe in Part::GeometryCurvePy::intersectCC(_object*) from /usr/lib/freecad/lib/Part.so+0x9e
    0000006  0x7f1690cad1af in Part::GeometryCurvePy::staticCallback_intersectCC(_object*, _object*) from /usr/lib/freecad/lib/Part.so+0x1f
    0000007  /usr/lib/libpython3.8.so.1.0(PyCFunction_Call+0xf3) [0x7f1719ffa5d3]
    0000008  /usr/lib/libpython3.8.so.1.0(_PyObject_MakeTpCall+0x230) [0x7f1719fa3220]
    0000009  /usr/lib/libpython3.8.so.1.0(_PyEval_EvalFrameDefault+0x4c9a) [0x7f171a00c97a]
    0000010  /usr/lib/libpython3.8.so.1.0(_PyEval_EvalCodeWithName+0x2fa) [0x7f1719fd809a]
    0000011  /usr/lib/libpython3.8.so.1.0(PyEval_EvalCodeEx+0x3a) [0x7f1719fd8cca]
    0000012  /usr/lib/libpython3.8.so.1.0(PyEval_EvalCode+0x1c) [0x7f171a06473c]
    0000013  0x7f171affbce6 in Gui::InteractiveInterpreter::runCode(PyCodeObject*) const from /usr/lib/freecad/lib/libFreeCADGui.so+0x66
    0000014  0x7f171affc54c in Gui::InteractiveInterpreter::runSource(char const*) const from /usr/lib/freecad/lib/libFreeCADGui.so+0xac
    0000015  0x7f171affc62d in Gui::InteractiveInterpreter::push(char const*) from /usr/lib/freecad/lib/libFreeCADGui.so+0xbd
    0000016  0x7f171affc834 in Gui::PythonConsole::runSource(QString const&) from /usr/lib/freecad/lib/libFreeCADGui.so+0xf4
    0000017  0x7f171affd107 in Gui::PythonConsole::runSourceFromMimeData(QString const&) from /usr/lib/freecad/lib/libFreeCADGui.so+0x737
    0000018  0x7f171affeeac in Gui::PythonConsole::insertFromMimeData(QMimeData const*) from /usr/lib/freecad/lib/libFreeCADGui.so+0x1cc
    0000019  /usr/lib/libQt5Widgets.so.5(+0x356664) [0x7f1719b2d664]
    0000020  0x7f1719b32a13 in QWidgetTextControl::processEvent(QEvent*, QMatrix const&, QWidget*) from /usr/lib/libQt5Widgets.so.5+0x193
    0000021  0x7f1719b28b1c in QWidgetTextControl::processEvent(QEvent*, QPointF const&, QWidget*) from /usr/lib/libQt5Widgets.so.5+0x5c
    0000022  0x7f1719b03aa4 in QPlainTextEdit::keyPressEvent(QKeyEvent*) from /usr/lib/libQt5Widgets.so.5+0x254
    0000023  0x7f171b029653 in Gui::TextEdit::keyPressEvent(QKeyEvent*) from /usr/lib/freecad/lib/libFreeCADGui.so+0x23
    0000024  0x7f171affe097 in Gui::PythonConsole::keyPressEvent(QKeyEvent*) from /usr/lib/freecad/lib/libFreeCADGui.so+0x277
    0000025  0x7f1719976e1b in QWidget::event(QEvent*) from /usr/lib/libQt5Widgets.so.5+0x88b
    0000026  0x7f1719a2822f in QFrame::event(QEvent*) from /usr/lib/libQt5Widgets.so.5+0x1f
    0000027  0x7f1719a2af7a in QAbstractScrollArea::event(QEvent*) from /usr/lib/libQt5Widgets.so.5+0x26a
    0000028  0x7f1719b032b9 in QPlainTextEdit::event(QEvent*) from /usr/lib/libQt5Widgets.so.5+0xc9
    0000029  0x7f1719932472 in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /usr/lib/libQt5Widgets.so.5+0x82
    0000030  0x7f171993c3c4 in QApplication::notify(QObject*, QEvent*) from /usr/lib/libQt5Widgets.so.5+0xa74
    0000031  0x7f171ae1f069 in Gui::GUIApplication::notify(QObject*, QEvent*) from /usr/lib/freecad/lib/libFreeCADGui.so+0x89
    0000032  0x7f1718e99832 in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /usr/lib/libQt5Core.so.5+0x182
    0000033  /usr/lib/libQt5Widgets.so.5(+0x1bdf3e) [0x7f1719994f3e]
    0000034  0x7f1719932472 in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /usr/lib/libQt5Widgets.so.5+0x82
    0000035  0x7f171993bc89 in QApplication::notify(QObject*, QEvent*) from /usr/lib/libQt5Widgets.so.5+0x339
    0000036  0x7f171ae1f069 in Gui::GUIApplication::notify(QObject*, QEvent*) from /usr/lib/freecad/lib/libFreeCADGui.so+0x89
    0000037  0x7f1718e99832 in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /usr/lib/libQt5Core.so.5+0x182
    0000038  0x7f171925e66d in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) from /usr/lib/libQt5Gui.so.5+0x16d
    #39  0x7f17192639ba in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) from /usr/lib/libQt5Gui.so.5+0x26a
    #40  0x7f171923cc2c in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /usr/lib/libQt5Gui.so.5+0xbc
    0000041  /usr/lib/libQt5XcbQpa.so.5(+0x66a2c) [0x7f17133aba2c]
    0000042  /usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x27e) [0x7f17169d239e]
    0000043  /usr/lib/libglib-2.0.so.0(+0x6c1b1) [0x7f17169d41b1]
    0000044  /usr/lib/libglib-2.0.so.0(g_main_context_iteration+0x31) [0x7f17169d41f1]
    0000045  0x7f1718ef1cc0 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /usr/lib/libQt5Core.so.5+0x60
    0000046  0x7f1718e9839c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) from /usr/lib/libQt5Core.so.5+0x12c
    0000047  0x7f1718ea03a6 in QCoreApplication::exec() from /usr/lib/libQt5Core.so.5+0x96
    0000048  0x7f171ad93222 in Gui::Application::runApplication() from /usr/lib/freecad/lib/libFreeCADGui.so+0x15e2
    0000049  freecad(main+0x759) [0x5562249605d9]
    0000050  /usr/lib/libc.so.6(__libc_start_main+0xf3) [0x7f1718851153]
    0000051  freecad(_start+0x2e) [0x5562249608fe]
    
    Tags: #ready-for-migration, OCC 7.4, OCC 7.5, OCC Bug, regression, upstream
    Steps To Reproduce:
    1. Open FreeCAD
    2. Run following code in python console :
    import Part
    
    doc = FreeCAD.newDocument()
    v = FreeCAD.Vector
    w1 = Part.makePolygon([v(0,0,0), v(0,10,0), v(-5, 5, 0), v(0,0,0)])
    w2 = Part.makePolygon([v(0,2,0), v(0,8,0), v(5, 5, 0), v(0,2,0)])
    Part.show(w1)
    Part.show(w2)
    e1 = w1.Edges[0]
    e2 = w2.Edges[0]
    e1.Curve.intersectCC(e2.Curve)
    
    Additional Information: Bug confirmed by looo.
    Tracking this via OCC bugs in the bugtracker forum thread
    Attached Files:
    Notes
    (0014819)
    Kunda1   
    2020-10-10 13:07   
    Someone volunteer to make an upstream ticket? (https://forum.freecadweb.org/viewtopic.php?f=19&t=42361&p=438189#p438189)
    (0014977)
    chennes   
    2020-11-11 20:21   
    I cannot reproduce using OCCT 7.5.0, so this may have already been fixed upstream. The output I get is:
    
    >>> e1.Curve.intersectCC(e2.Curve)
    Traceback (most recent call last):
      File "<input>", line 1, in <module>
    RuntimeError: NCollection_Sequence::Value
    
    (0015070)
    Kunda1   
    2020-12-03 22:55   
    Thanks @chennes!
    @CyrilWaechter can you reproduce with OCC 7.5 ?
    (0015079)
    CyrilWaechter   
    2020-12-04 14:46   
    Thanks @chennes for testing !
    @Kunda1 I waited a bit to update to OCCT 7.5.0 but I confirm that it is solved in OCCT 7.5.0. Should we close this issue keep it for a while until OCCT 7.4 «vanish» from most distros ?
    (0015089)
    Kunda1   
    2020-12-06 00:24   
    Good point. Lets resolve it but not close it. That way we can keep an eye on it.
    (0016856)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6022.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3938 [PartDesign] Bug major always 2019-04-19 06:34 2022-01-24 19:16
    Reporter: Sembazuru Platform: Windows 64-bit  
    Assigned To: OS: 10 Pro  
    Priority: normal OS Version: 1809  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 10
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16110 (Git)
    Build type: Release
    Branch: (HEAD detached at upstream/releases/FreeCAD-0-18)
    Hash: f7dccfaa909e5b9da26bf50c4a22ccca9bb10c40
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    Summary: Polar Pattern "transformed shapes do not intersect support" (upstream OCC bug)
    Description: As discussed on the forum here, there is a bug when using polar pattern if features are lined up just wrong. I tried using polar pattern of Grooves on a Revolved solid and get "transformed shapes do not intersect support". Selecting different numbers of occurrences get different array elements working, but never all of them.

    As mentioned by forum member kisolre,

    We again hit some OCC coplanar/colinear/co_something issue. Moving the center of the arc some distance away from the edge of the base coin fixes the issue (see the 0.1mm dimension).

    kisolre

    kisolre provides a good screenshot of the "fix" to get around the bug in the forum thread.
    Tags: #ready-for-migration, OCC 7.4, OCC Bug, OCC NotOnRoadmap
    Steps To Reproduce:
    • Open the attached file.
    • Edit the ScallopPolarPattern and see the preview. (Also see my screenshot on my forum OP.)
    • Change the number of Occurrences and see the preview.
    • To get around this:
      • Open the ScallopSketch to edit.
      • On the horizontal construction line remove the horizontal constraint.
      • Add a vertical distance constraint between the two endpoints of the horizontal construction line.
      • Set that vertical distance constraint to a non-zero number.
      • Close the sketch and see on the object that all the Grooves are now properly patterned around the disk.
    Additional Information: This ticket is being tracked via OCC Bugs in the Bugtracker forum thread
    Attached Files: ScallopedEdgeCoin.FCStd (153,677 bytes) 2020-12-22 12:42
    https://tracker.freecad.org/file_download.php?file_id=2586&type=bug
    Notes
    (0013043)
    Kunda1   
    2019-04-24 11:38   
    Putting this on the 0.19 roadmap so that it gets some attention.
    (0015177)
    Kunda1   
    2020-12-22 12:42   
    Re-uploaded broken attachment (used file from forum thread)
    (0015856)
    chennes   
    2021-08-25 03:43   
    This is still failing, as of:

    OS: Windows 10 Version 2009
    Word size of FreeCAD: 64-bit
    Version: 0.20.25541 (Git)
    Build type: Debug
    Branch: master
    Hash: ca043dcb6d20d70b8e24d75e810683214eecc5d4
    Python version: 3.8.6+
    Qt version: 5.15.1
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: English/United States (en_US)
    (0016214)
    Kunda1   
    2022-01-15 13:52   
    This needs an upstream ticket
    (0016751)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5917.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3670 [Part] Bug minor always 2018-11-05 08:02 2022-01-24 19:16
    Reporter: 0kko Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Thickness operation for part fails (upstream OCC bug)
    Description: Thickness operation in Part and Part Design -workbences fails with: "BRep_API: command not done."
    Tags: #ready-for-migration, OCC Bug, OCC NotOnRoadmap, upstream
    Steps To Reproduce: Select "face 8" in "case.fcstd".
    Try to do "Thickness"
    Additional Information: Binaries tested with "case.fcstd"

    FreeCAD-0.17.13541.9948ee4.glibc2.17-x86_64.AppImage
    FreeCAD-0.17.13541.9948ee4.glibc2.17-x86_64.AppImage

    Note: Issue is reproducible on latest v0.19 since the bug is with upstream OCCT
    This ticket is being tracked via OCC Bugs in the Bugtracker forum thread
    Attached Files: case.fcstd (203,881 bytes) 2020-12-22 12:15
    https://tracker.freecad.org/file_download.php?file_id=2585&type=bug
    Notes
    (0012137)
    Kunda1   
    2018-11-05 18:37   
    @0kko Please check with 0.18_pre appImage to see if you can recreate. https://github.com/FreeCAD/FreeCAD/releases/tag/0.18_pre
    (make sure you backup you file before doing so as 0.18 is not backward compatible if you open said file in 0.17 again)

    BTW, your ticket does not follow our guidelines stated in the enormous banner at the top of this page. We ask for people to report their issues on the forum first, many times they don't even make it to the tracker because they either get solved, or there is an open ticket already (there are exceptions). You also tested this on 0.17 yet you labeled this 0.18. + we have no idea what OS or OS version you are running. Guidelines are there for a reason, thank you.
    (0012171)
    normandc   
    2018-11-11 05:58   
    (Last edited: 2018-11-11 06:01)
    It is no surprise that the Thickness operation fails - look at the corners at the joint between the wedge and the box. The fillet created a deep cavity at the four corners.

    While this may look like a separate and legitimate bug (a fillet causing a crease between slanted corners), fixing it does not solve the thickness issue. The thickness command is notoriously weak. It is most probably an upstream (OCC) issue over which the FreeCAD team has no control.

    It is indeed exasperating that some people are completely blind to the f***ing huge yellow banner at the top. IMO we should start ruthlessly closing reports that do not comply with rules. Enough with this.

    (0015166)
    chrisb   
    2020-12-22 00:33   
    File is lost, and it was as Normand guessed most probably an OCC issue anyway.
    (0015173)
    wmayer   
    2020-12-22 11:53   
    https://forum.freecadweb.org/viewtopic.php?f=8&t=53514&p=460091#p460091
    (0015174)
    Kunda1   
    2020-12-22 12:13   
    Reopening and tracking via OCC Bugs in the Bugtracker forum thread
    (0015175)
    Kunda1   
    2020-12-22 12:15   
    Re-uploaded attachment since previous one was broken. Thanks wmayer ;)
    (0016253)
    Kunda1   
    2022-01-23 00:34   
    I can't find face8 in the attached file ???
    @chrisb care to check?
    (0016664)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5829.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3655 [Sketcher] Bug minor have not tried 2018-10-28 09:26 2022-01-24 19:16
    Reporter: Kunda1 Platform:  
    Assigned To: abdullah OS:  
    Priority: low OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: GeomAPI_ExtremaCurveCurve fails to detect intersection (upstream OCCT bug)
    Description: This ticket is for tracking https://tracker.dev.opencascade.org/view.php?id=30316
    Original forum thread: https://forum.freecadweb.org/viewtopic.php?p=265166#p265166
    Tags: #ready-for-migration, OCC Bug, OCC NotOnRoadmap, upstream
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016659)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5824.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3458 [Part] Bug minor always 2018-05-04 12:31 2022-01-24 19:16
    Reporter: chrisb Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Recompute does not create a solid containing a complex shaped hole (upstream OCC bug)
    Description: When a solid contains a very complex hole it is not displayed correctly.
    See forum discussion

    UR_ has found a fix: https://forum.freecadweb.org/viewtopic.php?f=3&t=28487&start=10#p231534

    and some code:

    obj = App.getDocument("kuggkuggkugg_ur").getObject("Offset")
    obj.ViewObject.update()
    Tags: #ready-for-migration, OCC 7.3, OCC Bug, upstream
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0011287)
    wmayer   
    2018-05-27 16:39   
    It's a 100% OCCT bug. With v7.2 it at least can create the missing face but must perform the meshing twice.
    (0011316)
    Kunda1   
    2018-05-30 23:39   
    @wmayer should a bug be submitted upstream ?
    (0016211)
    Kunda1   
    2022-01-15 13:25   
    @user1234 writes in https://forum.freecadweb.org/viewtopic.php?p=534396#p534396

    Pads without issues, well, it the padding works a few seconds since the insane amount of segments, but the geometry check takes a few minutes. But it works out of the box and the shape is valid. The padded file is too big to attach.

    OS: Debian GNU/Linux 11 (bullseye) (X-Cinnamon/lightdm-xsession)
    Word size of FreeCAD: 64-bit
    Version: 0.20.25751 (Git)
    Build type: Release
    Branch: master
    Hash: ef0e303235c03811eb29bc17e71f22ebdce95356
    Python version: 3.9.2
    Qt version: 5.15.2
    Coin version: 4.0.0
    OCC version: 7.5.3
    Locale: English/United States (en_US)

    user1234
    (0016622)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5787.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3435 [File formats] Bug crash always 2018-04-19 15:45 2022-01-24 19:16
    Reporter: fhackenberger Platform: Linux  
    Assigned To: OS: Ubuntu  
    Priority: normal OS Version: 16.04  
    Status: confirmed Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: Tracking this via OCC bugs in the bugtracker forum thread
    Summary: Crash with STEP export (Upstream OCC bug)
    Description: Freecad crashes when exporting the (only) part in the attached project as a .step file.

    OS: Ubuntu 16.04.4 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.13515 (Git)
    Build type: None
    Branch: releases/FreeCAD-0-17
    Hash: e17b340949b75a226cc7d89989b0aa238ccfc75f
    Python version: 2.7.12
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.2.0
    Locale: English/UnitedKingdom (en_GB)
    Tags: #pending, #ready-for-migration, OCC 7.6, OCC Bug, STEP, upstream
    Steps To Reproduce:
    1. Open the attached project
    2. Select the only part
    3. Click File->Export
    4. Choose 'STEP with colors' as File format
    5. Click save
    6. Freecad crashes with a segfault
    Additional Information: I exported the part as an IGES, re-imported it and then everything is fine.

    $ freecad --log-file -
    FreeCAD 0.17, Libs: 0.17R13515 (Git)
    © Juergen Riegel, Werner Mayer, Yorik van Havre 2001-2018
      ##### #### ### ####
      # # # # # #
      # ## #### #### # # # # #
      #### # # # # # # # ##### # #
      # # #### #### # # # # #
      # # # # # # # # # ## ## ##
      # # #### #### ### # # #### ## ## ##

    Mod pluginloader InitGui.py starting ...
    pluginmanager config file /home/fhackenberger/.FreeCAD//Mod/plugins/pluginloaderconfig.yaml
    pluginmanager userconfig file /usr/lib/freecad/Mod/plugins/myconfig.yaml
    userconfigfile not available
    IOError: [Errno 2] No such file or directory: '/usr/lib/freecad/Mod/plugins/myconfig.yaml'

    pluginmanager userconfig file /usr/lib/freecad/Mod/plugins/myconfig.yaml
    userconfigfile not available and cannot be created
    IOError: [Errno 2] No such file or directory: '/usr/lib/freecad/Mod/plugins/myconfig.yaml'

    Mod pluginloader InitGui.py done
    gentoolbars ...
    My Macros done
    My Workbenches done
    Program received signal SIGSEGV, Segmentation fault.
    #0 /lib/x86_64-linux-gnu/libc.so.6(+0x354b0) [0x7f190abe04b0]
    #1 0x7f18e3ac65ff in TopoDSToStep_MakeStepFace::Init(TopoDS_Face const&, TopoDSToStep_Tool&, opencascade::handle<Transfer_FinderProcess> const&) from /usr/lib/x86_64-linux-gnu/libTKSTEP.so.7+0x1a7f
    0000002 0x7f18e3ab8573 in TopoDSToStep_Builder::Init(TopoDS_Shape const&, TopoDSToStep_Tool&, opencascade::handle<Transfer_FinderProcess> const&) from /usr/lib/x86_64-linux-gnu/libTKSTEP.so.7+0x503
    0000003 0x7f18e3ab8fe8 in TopoDSToStep_Builder::TopoDSToStep_Builder(TopoDS_Shape const&, TopoDSToStep_Tool&, opencascade::handle<Transfer_FinderProcess> const&) from /usr/lib/x86_64-linux-gnu/libTKSTEP.so.7+0x38
    0000004 /usr/lib/x86_64-linux-gnu/libTKSTEP.so.7(+0x260cfc) [0x7f18e3abecfc]
    0000005 0x7f18e3abf60f in TopoDSToStep_MakeManifoldSolidBrep::TopoDSToStep_MakeManifoldSolidBrep(TopoDS_Solid const&, opencascade::handle<Transfer_FinderProcess> const&) from /usr/lib/x86_64-linux-gnu/libTKSTEP.so.7+0x5f
    0000006 0x7f18e3adfe1c in STEPControl_ActorWrite::TransferShape(opencascade::handle<Transfer_Finder> const&, opencascade::handle<StepShape_ShapeDefinitionRepresentation> const&, opencascade::handle<Transfer_FinderProcess> const&, opencascade::handle<TopTools_HSequenceOfShape> const&, bool) from /usr/lib/x86_64-linux-gnu/libTKSTEP.so.7+0x1e7c
    0000007 0x7f18e3ae5057 in STEPControl_ActorWrite::Transfer(opencascade::handle<Transfer_Finder> const&, opencascade::handle<Transfer_FinderProcess> const&) from /usr/lib/x86_64-linux-gnu/libTKSTEP.so.7+0x2e7
    0000008 0x7f18e6406317 in Transfer_ActorOfFinderProcess::Transferring(opencascade::handle<Transfer_Finder> const&, opencascade::handle<Transfer_ProcessForFinder> const&) from /usr/lib/x86_64-linux-gnu/libTKXSBase.so.7+0x67
    0000009 0x7f18e6411696 in Transfer_ProcessForFinder::TransferProduct(opencascade::handle<Transfer_Finder> const&) from /usr/lib/x86_64-linux-gnu/libTKXSBase.so.7+0xc6
    0000010 0x7f18e641357c in Transfer_ProcessForFinder::Transferring(opencascade::handle<Transfer_Finder> const&) from /usr/lib/x86_64-linux-gnu/libTKXSBase.so.7+0x1cc
    0000011 0x7f18e6413da6 in Transfer_ProcessForFinder::Transfer(opencascade::handle<Transfer_Finder> const&) from /usr/lib/x86_64-linux-gnu/libTKXSBase.so.7+0x26
    0000012 /usr/lib/x86_64-linux-gnu/libTKXSBase.so.7(+0x177c53) [0x7f18e6497c53]
    0000013 0x7f18e6498758 in XSControl_Controller::TransferWriteShape(TopoDS_Shape const&, opencascade::handle<Transfer_FinderProcess> const&, opencascade::handle<Interface_InterfaceModel> const&, int) const from /usr/lib/x86_64-linux-gnu/libTKXSBase.so.7+0x78
    0000014 0x7f18e3ae68b4 in STEPControl_Controller::TransferWriteShape(TopoDS_Shape const&, opencascade::handle<Transfer_FinderProcess> const&, opencascade::handle<Interface_InterfaceModel> const&, int) const from /usr/lib/x86_64-linux-gnu/libTKSTEP.so.7+0xc4
    0000015 0x7f18e64b22fa in XSControl_TransferWriter::TransferWriteShape(opencascade::handle<Interface_InterfaceModel> const&, TopoDS_Shape const&) from /usr/lib/x86_64-linux-gnu/libTKXSBase.so.7+0x15a
    0000016 0x7f18e64b9c0e in XSControl_WorkSession::TransferWriteShape(TopoDS_Shape const&, bool) from /usr/lib/x86_64-linux-gnu/libTKXSBase.so.7+0x3e
    0000017 0x7f18e3aef501 in STEPControl_Writer::Transfer(TopoDS_Shape const&, STEPControl_StepModelType, bool) from /usr/lib/x86_64-linux-gnu/libTKSTEP.so.7+0x1c1
    0000018 0x7f18c6386030 in STEPCAFControl_Writer::Transfer(STEPControl_Writer&, NCollection_Sequence<TDF_Label> const&, STEPControl_StepModelType, char const*, bool) from /usr/lib/x86_64-linux-gnu/libTKXDESTEP.so.7+0xa70
    0000019 0x7f18c63867b6 in STEPCAFControl_Writer::Transfer(opencascade::handle<TDocStd_Document> const&, STEPControl_StepModelType, char const*) from /usr/lib/x86_64-linux-gnu/libTKXDESTEP.so.7+0xa6
    0000020 0x7f18d8178c0a in ImportGui::Module::exporter(Py::Tuple const&) from /usr/lib/freecad/lib/ImportGui.so+0xdca
    0000021 0x7f18d817209a in Py::ExtensionModule<ImportGui::Module>::invoke_method_varargs(void*, Py::Tuple const&) from /usr/lib/freecad/lib/ImportGui.so+0x3a
    0000022 /usr/lib/freecad/lib/libFreeCADBase.so(method_varargs_call_handler+0x16c) [0x7f190ccfe62c]
    0000023 /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x8a51) [0x7f190c7a6971]
    0000024 /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x85c) [0x7f190c8dc05c]
    0000025 /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCode+0x19) [0x7f190c79dda9]
    0000026 /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyRun_StringFlags+0x76) [0x7f190c8181f6]
    0000027 0x7f190cd2e916 in Base::InterpreterSingleton::runString[abi:cxx11](char const*) from /usr/lib/freecad/lib/libFreeCADBase.so+0x66
    0000028 0x7f190d84c3fd in Gui::Command::runCommand(Gui::Command::DoCmd_Type, char const*) from /usr/lib/freecad/lib/libFreeCADGui.so+0x4d
    0000029 0x7f190d7dee96 in Gui::Application::exportTo(char const*, char const*, char const*) from /usr/lib/freecad/lib/libFreeCADGui.so+0x3a6
    0000030 0x7f190d857ef0 in StdCmdExport::activated(int) from /usr/lib/freecad/lib/libFreeCADGui.so+0x530
    0000031 0x7f190d85063c in Gui::Command::invoke(int) from /usr/lib/freecad/lib/libFreeCADGui.so+0x7c
    0000032 0x7f190b6ac010 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) from /usr/lib/x86_64-linux-gnu/libQtCore.so.4+0x4d0
    0000033 0x7f190bbbed62 in QAction::triggered(bool) from /usr/lib/x86_64-linux-gnu/libQtGui.so.4+0x42
    0000034 0x7f190bbc00b3 in QAction::activate(QAction::ActionEvent) from /usr/lib/x86_64-linux-gnu/libQtGui.so.4+0x83
    0000035 /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x6219fd) [0x7f190c0219fd]
    0000036 /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x625de9) [0x7f190c025de9]
    0000037 0x7f190bc1b8d0 in QWidget::event(QEvent*) from /usr/lib/x86_64-linux-gnu/libQtGui.so.4+0x2a0
    0000038 0x7f190c029ffb in QMenu::event(QEvent*) from /usr/lib/x86_64-linux-gnu/libQtGui.so.4+0x6b
    #39 0x7f190bbc4fdc in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /usr/lib/x86_64-linux-gnu/libQtGui.so.4+0x8c
    #40 0x7f190bbcc0d6 in QApplication::notify(QObject*, QEvent*) from /usr/lib/x86_64-linux-gnu/libQtGui.so.4+0x476
    0000041 0x7f190d82b464 in Gui::GUIApplication::notify(QObject*, QEvent*) from /usr/lib/freecad/lib/libFreeCADGui.so+0x54
    0000042 0x7f190b69790d in QCoreApplication::notifyInternal(QObject*, QEvent*) from /usr/lib/x86_64-linux-gnu/libQtCore.so.4+0x8d
    0000043 0x7f190bbcb6dd in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) from /usr/lib/x86_64-linux-gnu/libQtGui.so.4+0x14d
    0000044 /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x249d7c) [0x7f190bc49d7c]
    0000045 0x7f190bc48c83 in QApplication::x11ProcessEvent(_XEvent*) from /usr/lib/x86_64-linux-gnu/libQtGui.so.4+0x16b3
    0000046 /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x272542) [0x7f190bc72542]
    0000047 /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x2a7) [0x7f1904300197]
    0000048 /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4a3f0) [0x7f19043003f0]
    0000049 /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f190430049c]
    0000050 0x7f190b6c82ae in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /usr/lib/x86_64-linux-gnu/libQtCore.so.4+0x7e
    0000051 /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x272616) [0x7f190bc72616]
    0000052 0x7f190b69618f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /usr/lib/x86_64-linux-gnu/libQtCore.so.4+0x3f
    0000053 0x7f190b6964f5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) from /usr/lib/x86_64-linux-gnu/libQtCore.so.4+0x1b5
    0000054 0x7f190b69c4b9 in QCoreApplication::exec() from /usr/lib/x86_64-linux-gnu/libQtCore.so.4+0x99
    0000055 0x7f190d7e4240 in Gui::Application::runApplication() from /usr/lib/freecad/lib/libFreeCADGui.so+0x15b0
    0000056 freecad(main+0x8b4) [0x403804]
    0000057 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f190abcb830]
    0000058 freecad(_start+0x29) [0x404a49]
    Attached Files: crash-step-export.fcstd (34,985 bytes) 2018-04-19 15:45
    https://tracker.freecad.org/file_download.php?file_id=1898&type=bug
    crash-step-export.fcstd1 (35,001 bytes) 2018-04-19 15:45
    https://tracker.freecad.org/file_download.php?file_id=1899&type=bug
    Notes
    (0011172)
    Kunda1   
    2018-04-20 21:47   
    Please open a forum thread in the help section of the forum and link this ticket to it + vice versa
    (0011192)
    fhackenberger   
    2018-04-25 07:44   
    Confirmed by bejant on the forum. Could you please change the status of this bug?
    (0011864)
    wmayer   
    2018-09-27 21:13   
    (Last edited: 2018-09-27 21:14)
    This is a bug in TopoDSToStep_MakeStepFace::Init:

    
          else { // Copy the Curve2d which might be changed
        //C2d = CA.CurveOnSurface().GetCurve().Curve();
        //C2d = Handle(Geom2d_Curve)::DownCast(C2d->Copy());
        C2d = Handle(Geom2d_Curve)::DownCast(C2d->Copy());
          }
    

    The handle C2d is null and dereferencing it causes a segfault.

    (0012792)
    Kunda1   
    2019-02-27 21:39   
    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=3&t=28341
    (0015092)
    chennes   
    2020-12-06 01:08   
    In that forum thread, @easyw-fc posted a workaround: the crash only occurs if "Write out curves in parametric space of surface" is selected in Preferences->Import-Export->Step. If this is disabled the crash does not occur. I have tested and verified that the crash a) still occurs, so has not been fixed upstream as of OCC 7.5.0, and b) Unchecking that preference does eliminate the crash. If we want to "fix" this on our end, it seems that we could change the default for the curves in parametric space option to false. @easyw-fc's post says that "p-curves are sort of 'abandoned' by OCC".

    OS: Windows 10 Version 2004
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.23237 (Git)
    Build type: Debug
    Branch: master
    Hash: 71726a11d0844f263dad636fb98bb996a479e007
    Python version: 3.8.6+
    Qt version: 5.15.1
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: English/United States (en_US)
    (0015189)
    Kunda1   
    2020-12-31 12:44   
    Tracking this via OCC bugs in the bugtracker forum thread
    (0016210)
    Kunda1   
    2022-01-15 13:21   
    (Last edited: 2022-01-15 13:21)
    @user1234 writes in https://forum.freecadweb.org/viewtopic.php?p=534386#p534386


    When i open the file crash-step-export.fcstd and make a geometry check, the geometry is invalid. This is a common error of many exporters, i get that regularly from many manufacturers.

    With the Defeaturing of the Part Workbench, i deleted the round surface, that was invalid and then the area is fine (with the bore, means no area is missing). Then the checks are good and exports and imports fine.

    user1234
    (0016618)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5783.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3425 [PartDesign] Bug major always 2018-04-09 22:07 2022-01-24 19:16
    Reporter: nikisteen Platform:  
    Assigned To: OS: Windows  
    Priority: normal OS Version: 10  
    Status: confirmed Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Boolean operation in PDN fails depending on placement of one of the parts
    Description: When creating a boolean fuse between a cylinder and sphere (as shown in the attached project), the sphere disappear when its placement is adjusted to certain values, although the sphere still intersects the cylinder.
    Tags: #ready-for-migration, boolean, OCC 7.4, OCC Bug, OCC NotOnRoadmap, Part Design NEXT, upstream
    Steps To Reproduce: In the attached project, adjust the Y-axis placement of the sphere to 8mm. The sphere will be offset as expected. Now adjust the Y-axis placement to 9mm and the sphere disappears.
    Additional Information: Refer to forum thread

    Freecad version information:
    OS: Windows 10
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.13488 (Git)
    Build type: Release
    Branch: master
    Hash: 2891173923bcecaace64e0544f5773facbdef436
    Python version: 2.7.14
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.1.0
    Locale: English/SouthAfrica (en_ZA)

    It was also confirmed to occur on the newest stable release (0.17.13509) - see forum thread.
    Attached Files: BoolTest.FCStd (16,453 bytes) 2018-04-09 22:07
    https://tracker.freecad.org/file_download.php?file_id=1888&type=bug
    8mm_offset.PNG (53,838 bytes) 2018-04-09 22:07
    https://tracker.freecad.org/file_download.php?file_id=1889&type=bug
    9mm_offset.PNG (34,988 bytes) 2018-04-09 22:07
    https://tracker.freecad.org/file_download.php?file_id=1890&type=bug
    Notes
    (0011362)
    Kunda1   
    2018-06-07 16:57   
    @wmayer
    @DeepSOIC thinks this is a OCC bug. Please weigh in. Thanks!
    (0011849)
    wmayer   
    2018-09-26 09:35   
    Seems to be related to a different behaviour between OCC 7.2 and older versions. With 7.2 I can confirm the behaviour but with 7.0 it works as expected.
    (0011852)
    Kunda1   
    2018-09-26 13:24   
    @wmayer what about OCC 7.3?
    (0012705)
    wmayer   
    2019-02-20 15:44   
    There is a different behaviour in 7.2. For some reason the fusion of the sphere with the fused cylinder and box creates a compound with two solids.

    
    cyl=App.ActiveDocument.Cylinder.Shape
    sphere=App.ActiveDocument.Body002.Shape
    cube=App.ActiveDocument.Body001.Shape
    fuse=cyl.fuse(cube)
    fuse.Solids
    # shows one solid
    fuse=fuse.fuse(sphere)
    fuse.Solids
    # shows two solids => error
    

    If the y value of the placement of the sphere is <= 8 then the second fusion correctly creates a single solid.
    (0012743)
    normandc   
    2019-02-24 15:45   
    Same issue with OCC 7.3.

    OS: Ubuntu 18.04.2 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.15972 (Git)
    Build type: Release
    Branch: master
    Hash: 4e973324ae03c6db9188c08483232fa059c1c9ae
    Python version: 3.6.7
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: French/Canada (fr_CA)
    (0013236)
    Kunda1   
    2019-06-17 07:54   
    Added to "OCC Bugs in the Bugtracker" thread
    (0016209)
    Kunda1   
    2022-01-15 13:17   
    (Last edited: 2022-01-15 13:18)
    @user1234 writes in https://forum.freecadweb.org/viewtopic.php?p=534379#p534379

    I think this bug is solved (and was not OCCT related). When i switch the visibility to Tools and then to Result back, the file is fine. Also when i delete the boolean operation and redo it, it works fine.

    user1234
    (0016252)
    Kunda1   
    2022-01-23 00:21   
    See responses:
    https://forum.freecadweb.org/viewtopic.php?p=561983#p561983
    https://forum.freecadweb.org/viewtopic.php?p=562493#p562493
    (0016617)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5782.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2961 [FreeCAD] Bug minor always 2017-03-10 14:03 2022-01-24 19:16
    Reporter: Kunda1 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: BRepOffsetAPI_MakePipeShellPy.setAuxiliarySpine problems
    Description: See forum thread for details: https://forum.freecadweb.org/viewtopic.php?f=22&t=21193

    Upstream OCC ticket: https://tracker.dev.opencascade.org/view.php?id=26295 created by @ickby

    Tags: #ready-for-migration, bump, OCC Bug, OCC NotOnRoadmap, upstream
    Steps To Reproduce:
    Additional Information: ATM this bug is not on the OCC roadmap.
    Attached Files:
    Notes
    (0010059)
    wmayer   
    2017-09-02 11:13   
    Still crashes with occ 7.2
    (0016522)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5687.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2732 [File formats] General minor always 2016-10-10 21:51 2022-01-24 19:16
    Reporter: vern.zimm Platform: Intel Core i5 64-bit  
    Assigned To: OS: Windows  
    Priority: low OS Version: 7 SP1  
    Status: new Product Version: 0.16  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: IGES and STEP export compatibility
    Description: Greetings,

    Disclaimer : I do understand that the Import/Export is part of OCC and you do not have control over that, and also understand that you have no control over the CMM software, but I would appreciate any help you can give me. It does appear that there are some settings for OCC that are variable on your end.

    I am using CMM software called PC-DMIS, and it has some very strange results from attempts to import both .step and .iges from FreeCAD. It is a bit finicky with .iges, but .step has always been the better format and I can't think of the last time I had an issue with it.

    .step files fail to import completely. Luckily there is a translate log and it shows errors "building bounds of Face". That and the exported .step are attached.

    .iges files have mixed results depending on "144" or "186" type.

    The "144" type will import all curves, but only some faces.
    The "186" type will import all faces, and some huge lines that are clearly related to the missing curves.
    (File and screenshots of results attached for both)

    I am able to merge the two, then delete huge lines and duplicate faces, so it does work to do that. The settings for the .iges importer are attached as well. Perhaps you can make some sense of them, but no combination seems to give better results.
    Tags: #ready-for-migration, file format, IGES, OCC Bug, STEP, units
    Steps To Reproduce: Create part (including curves of some sort for the IGES issue)
    Export using either File menu, or Part Workbench export
    Additional Information: OS: Windows 7
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.16.6706 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-16
    Hash: f86a4e411ff7848dea98d7242f43b7774bee8fa0
    Python version: 2.7.8
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 6.8.0.oce-0.17
    Attached Files: Export Test.zip (222,054 bytes) 2016-10-10 21:51
    https://tracker.freecad.org/file_download.php?file_id=1349&type=bug
    Inch to MM compare.zip (17,330 bytes) 2016-10-14 17:13
    https://tracker.freecad.org/file_download.php?file_id=1355&type=bug
    Notes
    (0007357)
    normandc   
    2016-10-12 11:29   
    Creating a post on the forum first would have been more appropriate. This looks like a help request, not like a bug report. As it is, this bug report is much too vague.

    Please read the "Please read before reporting" link. http://forum.freecadweb.org/viewtopic.php?f=3&t=5236
    (0007362)
    vern.zimm   
    2016-10-14 17:21   
    There would appear to be a bug in either FreeCAD or OCC with the Inch export vs. MM export. In the preferences for Import/Export, one can set the export units. I set this to MM and suddenly my .step files come in perfectly. The "186" .iges files still have the lines, but do pull in complete otherwise. I suspect there may be a conversion error somewhere, for instance, in the MM .iges I find this "-0.E+000", but in the Inch .iges, I find "-1.928577636E-017". I don't know if that's the issue, but it is one difference I found. See the "502" line from each file in the attached MM to Inch Compare.txt (with the inch equivalent converted for the other numbers).
    (0007813)
    Kunda1   
    2017-01-16 08:58   
    Forum thread to continue discussion: http://forum.freecadweb.org/viewtopic.php?f=10&t=19941
    (0008895)
    Kunda1   
    2017-05-06 11:07   
    Forum thread updated
    (0016503)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5668.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2715 [FreeCAD] Feature minor always 2016-09-30 05:29 2022-01-24 19:16
    Reporter: caijulong Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.16  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: The result for fillet of the union of cube and sphere is wrong
    Description: I made an union of cube and sphere, and then made a fillet on one edge(closed to sphere) of the union.The result is not right.
    Tags: #ready-for-migration, OCC Bug, upstream
    Steps To Reproduce: Use the attached project
    Additional Information:
    Attached Files: Fillet.7z (16,513 bytes) 2016-09-30 05:29
    https://tracker.freecad.org/file_download.php?file_id=1338&type=bug
    Fillet.FCStd (9,846 bytes) 2018-02-22 04:04
    https://tracker.freecad.org/file_download.php?file_id=1838&type=bug
    Fillet_normandc1.FCStd (16,803 bytes) 2018-02-22 04:22
    https://tracker.freecad.org/file_download.php?file_id=1839&type=bug
    Notes
    (0007375)
    normandc   
    2016-10-15 20:44   
    I can reproduce on
    OS: Ubuntu 14.04.5 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.16.6703 (Git)
    Build type: None
    Branch: releases/FreeCAD-0-16
    Hash: 2ce5c8d2e3020d05005ed71f710e09e9aa561f40
    Python version: 2.7.6
    Qt version: 4.8.6
    Coin version: 4.0.0a
    OCC version: 6.8.0.oce-0.17

    To devs: am I right in believing this is an OCC issue FreeCAD has no control on? Or would it be a FreeCAD issue somewhat?

    If the former, then this would need to be reported upstream to the OCCT bug tracker by someone with an account and knowledge of DRAWEXE.
    (0007376)
    normandc   
    2016-10-15 20:46   
    That being said caijulong, you should have first reported this in the FreeCAD forum, as explained in the "Please read first before reporting" link. That link is just over the "Report issue" link in the Issues menu. You couldn't have missed it...

    It is very simple to work around this bug. Simply apply the fillet on the cube *before* fusing to the sphere.
    (0007776)
    Kunda1   
    2017-01-15 02:14   
    I've seen @shoogen report upstream OCC bugs.
    @normandc please advise how to proceed with this ticket?
    (0010061)
    wmayer   
    2017-09-02 12:25   
    In OCC 6.8 the result is always broken when doing a fillet on an edge (there are three of them) that hits the seam edge of the sphere.

    In 7.2 the result is even worse. For two of the edges (where the sphere intersects the box) the output shape is completely empty (BRep_API: command not done) and for the third edge several faces are missing.
    When using one of the other edges that intersect the sphere the CPU load goes to 100% and doesn't end in a reasonable time (in case it even does since I stopped the process after a minute).

    So compared to older occ versions this is a great regression!
    (0010790)
    Kunda1   
    2018-01-18 14:27   
    @caijulong could you possibly re-upload Fillet.7z ?
    (0010964)
    Kunda1   
    2018-02-18 12:46   
    @caijulong ping
    (0010969)
    caijulong   
    2018-02-22 04:04   
    @Kunda1,sorry about the late reply.
    I can't find the old file.
    Just reproduce one.
    (0010970)
    normandc   
    2018-02-22 04:22   
    Thanks for providing a new file. For future reference to rebuild the example file:

    1. Create Part Cube with default parameters.
    2. Create Part Sphere with default parameters.
    3. Fuse them.
    4. Select Edge5 (the vertical edge on the cube centred to the origin).
    5. Create Part Fillet of 1mm.

    There is another workaround than creating the fillet before the fuse: just rotate the sphere so that its seam does not intersect the edge to be filleted. Set sphere's axis to (1, 0, 0) and set angle to 90º. This repairs the model. See attached.
    (0011903)
    wmayer   
    2018-10-03 17:59   
    The actual problems seems to be related to older OCCT versions. At some point the tolerances of the model are broken leading to huge values like 363.5 (instead of 1e-7).
    This makes then the fillet to fail.

    With OCCT 7.0 or later the tolerances are not broken any more and thus no error occurs. But one needs to start from scratch because the broken tolerance values are saved into the BRep files.
    (0011906)
    Kunda1   
    2018-10-03 20:06   
    @wmayer how to proceed with this ticket then?
    (0011909)
    wmayer   
    2018-10-03 21:37   
    What we need are some shape healing functions and therefore the file can be used for testing purposes.

    I changed the category from bug to feature request.
    (0016500)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5665.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2497 [PartDesign] Bug minor always 2016-04-06 15:22 2022-01-24 19:16
    Reporter: otto Platform: Windows  
    Assigned To: OS: Windows 7  
    Priority: normal OS Version: WIndows 7 64bits  
    Status: new Product Version: 0.16  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Changing dimension 40.001 to a value <= 40 (and > 30) gets the expected behavior. More than 40 gets the the buggy one
    Description: possible bug: FreeCAD>>Part Design>> Draft tool
    Tags: #ready-for-migration, OCC Bug, upstream
    Steps To Reproduce: Sketch001: Changing dimension 40.001 to a value less or equal to 40 (and greater than 30) gets the expected behavior. More than 40 gets the buggy one.
    Additional Information: About FreeCAD

    OS: Windows 7
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.16.6689 (Git)
    Build type: Release
    Branch: master
    Hash: 3003f1638949a018596a16e9e8eea7f237e1d94d
    Python version: 2.7.8
    Qt version: 4.8.6
    Coin version: 4.0.0a
    OCC version: 6.8.0.oce-0.17
    Attached Files: Bug in Draft tool.FCStd (281,099 bytes) 2016-04-06 15:22
    https://tracker.freecad.org/file_download.php?file_id=1232&type=bug
    2497.fcstd (211,873 bytes) 2021-09-15 19:02
    https://tracker.freecad.org/file_download.php?file_id=2694&type=bug
    Notes
    (0008006)
    Kunda1   
    2017-01-26 22:20   
    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=10&t=20261
    (0015927)
    chennes   
    2021-09-15 19:02   
    In testing with:
    OS: Windows 10 Version 2009
    Word size of FreeCAD: 64-bit
    Version: 0.20.25558 +5 (Git)
    Build type: Release
    Branch: pr/4996
    Hash: 8633270b2acffd2cf26c88be2cad8aea8b068988
    Python version: 3.8.6+
    Qt version: 5.15.1
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: English/United States (en_US)

    The problem appears to have reversed itself: I get good results for 40.0 and higher, and garbage for less than 40. I'm re-attaching the file from the forums since the above attachment isn't currently working for me.
    (0015952)
    jnxd   
    2021-09-22 05:25   
    Possibly related forum post: https://forum.freecadweb.org/viewtopic.php?f=10&t=3209&start=10#p25341
    (0015964)
    jnxd   
    2021-10-11 00:45   
    Problem appears to be upstream in OCC. See https://forum.freecadweb.org/viewtopic.php?p=539132#p539132
    (0016484)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5649.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2461 [PartDesign] Bug minor always 2016-03-02 11:10 2022-01-24 19:16
    Reporter: taiyo_uk Platform: x86_64  
    Assigned To: OS: Windows  
    Priority: normal OS Version: Windows 7 64 bit  
    Status: confirmed Product Version: 0.15  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Crash when creating loft between two sketches
    Description: Crating a loft between two sketches causes FreeCAD to segfault in Fedora 23 x86_64, and to produce this error in Windows 7 64-bit: "ACCESS VIOLATION at address 0x00000010 during 'READ' operation"

    This only happens for certain sketches such as those included in the attached file.
    Tags: #ready-for-migration, OCC 7.3, OCC Bug, upstream
    Steps To Reproduce: 1. Open the attached file in FreeCAD
    2. Create a loft using the two sketches
    3. The crash happens when clicking the OK button in the loft dialog.
    Additional Information: Changing the order of the two sketches has no effect. Selecting the closed option produces a different error in Windows: "TCollection_DataMap::ChangeFind"
    Attached Files: loft-test-1.FCStd (5,156 bytes) 2016-03-02 11:10
    https://tracker.freecad.org/file_download.php?file_id=1215&type=bug
    loft-test_normandc1.FCStd (14,260 bytes) 2016-03-06 20:05
    https://tracker.freecad.org/file_download.php?file_id=1217&type=bug
    loft-sigsegv.fcstd (13,153 bytes) 2018-06-08 23:53
    https://tracker.freecad.org/file_download.php?file_id=1937&type=bug
    Notes
    (0006877)
    taiyo_uk   
    2016-03-02 11:20   
    Version information:

    OS: Windows 7
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.15.4671 (Git)
    Branch: releases/FreeCAD-0-15
    Hash: 244b3aef360841646cbfe80a1b225c8b39c8380c
    Python version: 2.7.8
    Qt version: 4.8.6
    Coin version: 4.0.0a
    OCC version: 6.8.0.oce-0.17
    (0006879)
    taiyo_uk   
    2016-03-03 07:22   
    The same problem happens on the latest (at the time of writing) git build, this is what happens on Fedora:

    *** Abort *** an exception was raised, but no catch was found.
        ... The exception is:SIGSEGV 'segmentation violation' detected. Address 0

    Version information:

    OS: Linux
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.16.6538 (Git)
    Build type: Release
    Branch: master
    Hash: 57c783e5b0f4da8611f5b1f26dc7499a5979e574
    Python version: 2.7.10
    Qt version: 4.8.7
    Coin version: 3.1.3
    (0006888)
    normandc   
    2016-03-06 20:04   
    (Last edited: 2016-03-06 20:05)
    I can confirm the problem here.

    OS: Ubuntu 14.04.4 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.16.6557 (Git)
    Build type: None
    Branch: master
    Hash: 948ccac021b15aff3c7a3b033c508e7ec9b123d6
    Python version: 2.7.6
    Qt version: 4.8.6
    Coin version: 4.0.0a
    OCC version: 6.8.0.oce-0.17

    But I suspect this is due to your sketches having a different number of segments - this is bound for trouble when creating lofts. This is probably an OCC issue (the geometric kernel FreeCAD uses) that the FreeCAD devs have no control of.

    A workaround is to add very short line segments to the second sketch so it has the same number of segments as the first sketch. Then the loft succeeds (see attached "loft-test_normandc1.fcstd" file). Another would be to create this model in two separate operations: first create a prism of the outer volume with a Pad, then create a loft representing the volume you want to be cut from the prism, and apply a boolean cut. This way the model will have planar faces rather than BSpline ones on which sketches cannot be mapped.

    Next time, please report modeling issues to the FreeCAD forum first, so to determine if it's a FreeCAD bug, or a bug in OCC which the devs can't do anything about. http://forum.freecadweb.org/viewtopic.php?f=3&t=5236

    I wonder if the crash can be avoided, and an error thrown instead.

    (0008002)
    Kunda1   
    2017-01-26 21:55   
    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=10&t=20258
    (0010608)
    Kunda1   
    2017-12-15 20:36   
    @taiyo_uk do you still have the attachment for this ticket? Bugtracker shows it's missing.
    (0010789)
    Kunda1   
    2018-01-18 14:25   
    @taiyo_uk ping
    (0011373)
    hirnsalat   
    2018-06-08 23:53   
    (Last edited: 2018-06-08 23:53)
    Ran into the same problem, apparently it still exists in 0.17. How to reproduce: Go to Part Design workbench, load attached file, create an additive loft, add sections from top to bottom. FreeCAD should crash with a segmentation fault.

    OS: "Manjaro Linux"
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.13522 (Git) AppImage
    Build type: None
    Branch: releases/FreeCAD-0-17
    Hash: 3bb5ff4e70c0c526f2d9dd69b1004155b2f527f2
    Python version: 2.7.6
    Qt version: 4.8.6
    Coin version: 4.0.0a
    OCC version: 7.2.0
    Locale: English/UnitedKingdom (en_GB)

    Also tested on a friend's Mac, which crasches too:

    OS: Mac OS X
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.13519 (Git)
    Build type: Release
    Branch: (HEAD detached at 1a8b868)
    Hash: 1a8b868018f45ea486c0023fdbfeb06febc1fb89
    Python version: 2.7.14
    Qt version: 5.10.1
    Coin version: 4.0.0a
    OCC version: 7.2.0
    Locale: English/Austria (en_AT)

    (0011374)
    Kunda1   
    2018-06-08 23:58   
    @hirnsalat Thanks for testing. Can you also test with OCC7.3 when it becomes available ?
    Also please also report your findings to the dedicated forum thread
    (0011876)
    wmayer   
    2018-09-30 15:27   
    That's a regression in OCCT 7.2. When using OCCT 7.0 it doesn't create a loft but reports an appropriate error message and does not crash.
    (0012473)
    maiden   
    2019-01-20 20:04   
    Is this issue resolved now? or is there another "exceptions in occt" ticket that can replace this?
    (0012474)
    wmayer   
    2019-01-20 21:01   
    It was hirnsalat you said that it crashes with OCCT 7.2. But I've just tested it and I get it working when I also select the Ruled surface option. Without it an error message pops up but I don't get a crash. I have tested this with OCCT 7.0 and 7.2.
    (0012598)
    normandc   
    2019-02-09 20:16   
    I get a crash when I add the third section with the version below using OCC 7.3.0.

    Program received signal SIGSEGV, Segmentation fault.
    #0  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20) [0x7f7bc5f14f20]
    #1  /usr/lib/x86_64-linux-gnu/libTKTopAlgo.so.7(+0x17bcb5) [0x7f7b7e043cb5]
    0000002  0x7f7b7e04477e in BRepLib::EncodeRegularity(TopoDS_Shape const&, double) from /usr/lib/x86_64-linux-gnu/libTKTopAlgo.so.7+0x14e
    0000003  0x7f7b7cd22da8 in BRepOffsetAPI_ThruSections::Build() from /usr/lib/x86_64-linux-gnu/libTKOffset.so.7+0xd28
    0000004  0x7f7b1e4a3c2b in PartDesign::Loft::execute() from /home/normand2/compilation/FreeCAD/freecad-build2/Mod/PartDesign/_PartDesign.so+0x7db
    0000005  0x7f7bc83c3265 in App::DocumentObject::recompute() from /home/normand2/compilation/FreeCAD/freecad-build2/lib/libFreeCADApp.so+0x155
    0000006  0x7f7b827aabdb in Part::Feature::recompute() from /home/normand2/compilation/FreeCAD/freecad-build2/Mod/Part/Part.so+0xb
    0000007  0x7f7bc8377544 in App::Document::_recomputeFeature(App::DocumentObject*) from /home/normand2/compilation/FreeCAD/freecad-build2/lib/libFreeCADApp.so+0xb4
    0000008  0x7f7bc837f013 in App::Document::recomputeFeature(App::DocumentObject*) from /home/normand2/compilation/FreeCAD/freecad-build2/lib/libFreeCADApp.so+0x83
    0000009  0x7f7b1e0691d0 in PartDesignGui::TaskLoftParameters::onSelectionChanged(Gui::SelectionChanges const&) from /home/normand2/compilation/FreeCAD/freecad-build2/Mod/PartDesign/PartDesignGui.so+0x120
    0000010  0x7f7bc8ed09c6 in Gui::SelectionObserver::_onSelectionChanged(Gui::SelectionChanges const&) from /home/normand2/compilation/FreeCAD/freecad-build2/lib/libFreeCADGui.so+0x56
    0000011  0x7f7bc8edebbf in boost::signals2::detail::signal_impl<void (Gui::SelectionChanges const&), boost::signals2::optional_last_value<void>, int, std::less<int>, boost::function<void (Gui::SelectionChanges const&)>, boost::function<void (boost::signals2::connection const&, Gui::SelectionChanges const&)>, boost::signals2::mutex>::operator()(Gui::SelectionChanges const&) from /home/normand2/compilation/FreeCAD/freecad-build2/lib/libFreeCADGui.so+0x20f
    0000012  0x7f7bc8ed8f81 in Gui::SelectionSingleton::addSelection(char const*, char const*, char const*, float, float, float) from /home/normand2/compilation/FreeCAD/freecad-build2/lib/libFreeCADGui.so+0x281
    0000013  0x7f7bc8d4237a in Gui::SoFCUnifiedSelection::handleEvent(SoHandleEventAction*) from /home/normand2/compilation/FreeCAD/freecad-build2/lib/libFreeCADGui.so+0xd3a
    0000014  0x7f7bc5722504 in SoAction::traverse(SoNode*) from /usr/lib/x86_64-linux-gnu/libCoin.so.80c+0x64
    0000015  0x7f7bc58c2008 in SoChildList::traverse(SoAction*, int, int) from /usr/lib/x86_64-linux-gnu/libCoin.so.80c+0xd8
    0000016  0x7f7bc59114e6 in SoGroup::doAction(SoAction*) from /usr/lib/x86_64-linux-gnu/libCoin.so.80c+0x56
    0000017  0x7f7bc592b967 in SoSeparator::doAction(SoAction*) from /usr/lib/x86_64-linux-gnu/libCoin.so.80c+0x27
    0000018  0x7f7bc5722504 in SoAction::traverse(SoNode*) from /usr/lib/x86_64-linux-gnu/libCoin.so.80c+0x64
    0000019  0x7f7bc572be48 in SoHandleEventAction::beginTraversal(SoNode*) from /usr/lib/x86_64-linux-gnu/libCoin.so.80c+0x68
    0000020  0x7f7bc5722a82 in SoAction::apply(SoNode*) from /usr/lib/x86_64-linux-gnu/libCoin.so.80c+0x372
    0000021  0x7f7bc58de8a0 in SoEventManager::actuallyProcessEvent(SoEvent const*) from /usr/lib/x86_64-linux-gnu/libCoin.so.80c+0x60
    0000022  0x7f7bc8db590e in SIM::Coin3D::Quarter::QuarterWidget::processSoEvent(SoEvent const*) from /home/normand2/compilation/FreeCAD/freecad-build2/lib/libFreeCADGui.so+0x1e
    0000023  0x7f7bc8dbe5c6 in SIM::Coin3D::Quarter::SoQTQuarterAdaptor::processSoEvent(SoEvent const*) from /home/normand2/compilation/FreeCAD/freecad-build2/lib/libFreeCADGui.so+0x56
    0000024  0x7f7bc8de8179 in Gui::View3DInventorViewer::processSoEventBase(SoEvent const*) from /home/normand2/compilation/FreeCAD/freecad-build2/lib/libFreeCADGui.so+0x9
    0000025  0x7f7bc8dd118e in Gui::GestureNavigationStyle::processSoEvent(SoEvent const*) from /home/normand2/compilation/FreeCAD/freecad-build2/lib/libFreeCADGui.so+0xabe
    0000026  0x7f7bc8dc8418 in Gui::NavigationStyle::processEvent(SoEvent const*) from /home/normand2/compilation/FreeCAD/freecad-build2/lib/libFreeCADGui.so+0xf8
    0000027  0x7f7bc8de80f3 in Gui::View3DInventorViewer::processSoEvent(SoEvent const*) from /home/normand2/compilation/FreeCAD/freecad-build2/lib/libFreeCADGui.so+0x63
    0000028  0x7f7bc8dacd45 in SIM::Coin3D::Quarter::EventFilter::eventFilter(QObject*, QEvent*) from /home/normand2/compilation/FreeCAD/freecad-build2/lib/libFreeCADGui.so+0x185
    0000029  0x7f7bc6af268c in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x7c
    0000030  0x7f7bc7107805 in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x75
    0000031  0x7f7bc710f64f in QApplication::notify(QObject*, QEvent*) from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x7ff
    0000032  0x7f7bc8b88a48 in Gui::GUIApplication::notify(QObject*, QEvent*) from /home/normand2/compilation/FreeCAD/freecad-build2/lib/libFreeCADGui.so+0x88
    0000033  0x7f7bc6af29a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x118
    0000034  0x7f7bc710e622 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x1d2
    0000035  /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5(+0x1ae14b) [0x7f7bc716114b]
    0000036  /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5(+0x1b07ba) [0x7f7bc71637ba]
    0000037  0x7f7bc710782c in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x9c
    0000038  0x7f7bc710f0f4 in QApplication::notify(QObject*, QEvent*) from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x2a4
    #39  0x7f7bc8b88a48 in Gui::GUIApplication::notify(QObject*, QEvent*) from /home/normand2/compilation/FreeCAD/freecad-build2/lib/libFreeCADGui.so+0x88
    #40  0x7f7bc6af29a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x118
    0000041  0x7f7bc2a1d523 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5+0x6f3
    0000042  0x7f7bc2a1eff5 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5+0x135
    0000043  0x7f7bc29f62eb in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5+0xab
    0000044  /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5(+0x9d1c0) [0x7f7bb615a1c0]
    0000045  /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x2e7) [0x7f7bc0d74387]
    0000046  /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c5c0) [0x7f7bc0d745c0]
    0000047  /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f7bc0d7464c]
    0000048  0x7f7bc6b4b8ef in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x5f
    0000049  0x7f7bc6af09ea in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x13a
    0000050  0x7f7bc6af9a84 in QCoreApplication::exec() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x94
    0000051  0x7f7bc8b0dfab in Gui::Application::runApplication() from /home/normand2/compilation/FreeCAD/freecad-build2/lib/libFreeCADGui.so+0x133b
    0000052  ./FreeCAD(main+0x6ad) [0x5588702ee48d]
    0000053  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f7bc5ef7b97]
    0000054  ./FreeCAD(_start+0x2a) [0x5588702ef1ea]
    
    OS: Ubuntu 18.04.1 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.15816 (Git)
    Build type: Release
    Branch: master
    Hash: 7ee0e4d43909ec688299b8498b240cccf8362c47
    Python version: 3.6.7
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: French/Canada (fr_CA)
    (0012599)
    normandc   
    2019-02-09 20:21   
    No crash with OCC 7.1.0 with this version. An error message appears in a pop up when pressing OK:
    BRepFill :: profiles are inconsistent

    OS: Ubuntu 18.04.1 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.13509 (Git) AppImage
    Build type: None
    Branch: master
    Hash: 0258808ccb6ba3bd5ea9312f79cd023f1a8671b7
    Python version: 2.7.6
    Qt version: 4.8.6
    Coin version: 4.0.0a
    OCC version: 7.1.0
    Locale: French/Canada (fr_CA)
    (0012734)
    wmayer   
    2019-02-23 20:29   
    I don't have OCCT 7.3 to this but according to the call stack this anyway must be a bug in OCCT, then.
    (0016477)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5642.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2325 [PartDesign] Bug crash always 2015-11-01 21:56 2022-01-24 19:16
    Reporter: joostn Platform: Mac  
    Assigned To: abdullah OS: 10.11  
    Priority: normal OS Version: 10.11  
    Status: assigned Product Version: 0.15  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Pad -> Fillet -> Apply Thickness causes crash (upstream OCC bug)
    Description: See attached project and steps below:
    Tags: #ready-for-migration, OCC 7.2.1, OCC Bug, OCC NotOnRoadmap, upstream
    Steps To Reproduce: - Open test3.FCStd
    - Switch to Part workbench
    - highlight a face of the 'Fillet' solid (I tried the topmost flat face as displayed)
    - select the Apply Thickness tool

    Bang! crash.
    Additional Information: OS: Mac OS X
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.15.4671 (Git)
    Branch: releases/FreeCAD-0-15
    Hash: 244b3aef360841646cbfe80a1b225c8b39c8380c
    Python version: 2.7.9
    Qt version: 4.8.6
    Coin version: 4.0.0a

    I've also tried with a daily build:

    OS: Mac OS X
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.16.5846 (Git)
    Build type: Unknown
    Branch: master
    Hash: 71be79e09e293bd2ccb1470981f07807be4c04fb
    Python version: 2.7.10
    Qt version: 4.8.7
    Coin version: 3.1.3
    OCC version: 6.7.0
    Attached Files: test3.FCStd (9,368 bytes) 2015-11-01 21:56
    https://tracker.freecad.org/file_download.php?file_id=1131&type=bug
    test3-2.FCStd (9,368 bytes) 2017-05-12 13:21
    https://tracker.freecad.org/file_download.php?file_id=1594&type=bug
    bug_thickness.FCStd (22,731 bytes) 2020-11-17 10:34
    https://tracker.freecad.org/file_download.php?file_id=2561&type=bug
    USB Charger Housing.FCStd (175,570 bytes) 2020-11-18 13:40
    https://tracker.freecad.org/file_download.php?file_id=2562&type=bug
    Notes
    (0006859)
    wmayer   
    2016-02-28 20:47   
    TKG3dd.dll!Geom_TrimmedCurve::Geom_TrimmedCurve(const Handle_Geom_Curve & C={...}, const double U1=0.00000000000000000, const double U2=1.5707963267949001, const bool Sense=true) Line 80 + 0x1d bytes C++
    TKOffsetd.dll!BRepOffset_Tool::TryProject(const TopoDS_Face & F1={...}, const TopoDS_Face & F2={...}, const TopTools_ListOfShape & Edges={...}, TopTools_ListOfShape & LInt1={...}, TopTools_ListOfShape & LInt2={...}, const TopAbs_State Side=TopAbs_IN, const double TolConf=4.9999999999999998e-007) Line 1983 + 0x49 bytes C++
    TKOffsetd.dll!BRepOffset_Inter3d::ContextIntByArc(const TopTools_IndexedMapOfShape & ContextFaces={...}, const bool InSide=false, const BRepOffset_Analyse & Analyse={...}, const BRepAlgo_Image & InitOffsetFace={...}, BRepAlgo_Image & InitOffsetEdge={...}) Line 864 C++
    TKOffsetd.dll!BRepOffset_MakeOffset::Intersection3D(BRepOffset_Inter3d & Inter={...}) Line 2591 C++
    TKOffsetd.dll!BRepOffset_MakeOffset::MakeOffsetShape() Line 727 C++
    TKOffsetd.dll!BRepOffset_MakeOffset::MakeThickSolid() Line 792 C++
    TKOffsetd.dll!BRepOffsetAPI_MakeThickSolid::Build() Line 72 C++
    TKOffsetd.dll!BRepOffsetAPI_MakeThickSolid::BRepOffsetAPI_MakeThickSolid(const TopoDS_Shape & S={...}, const TopTools_ListOfShape & ClosingFaces={...}, const double Offset=1.0000000000000000, const double Tol=9.9999999999999995e-008, const BRepOffset_Mode Mode=BRepOffset_Skin, const bool Intersection=false, const bool SelfInter=false, const GeomAbs_JoinType Join=GeomAbs_Arc) Line 60 + 0xd bytes C++
    Part_d.pyd!Part::TopoShape::makeThickSolid(const TopTools_ListOfShape & remFace={...}, double offset=1.0000000000000000, double tol=9.9999999999999995e-008, bool intersection=false, bool selfInter=false, short offsetMode=0, short join=0) Line 2099 + 0xa2 bytes C++
    Part_d.pyd!Part::Thickness::execute() Line 605 + 0x64 bytes C++

    That's a bug in the OCC library.
    (0006870)
    jmaustpc   
    2016-03-01 15:11   
    Still crashes here with the OCE from tanderson, OCE patches over OCC 6.9.1

    OS: Ubuntu 12.04.5 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.16.6523 (Git)
    Build type: Release
    Branch: master
    Hash: ecd6517cb00fcf05edd41a38b3ce1fa8b16ec3ad
    Python version: 2.7.3
    Qt version: 4.8.2
    Coin version: 3.1.3
    OCC version: 6.9.1.oce-0.18-dev
    (0006907)
    wmayer   
    2016-03-14 19:52   
    Might be related: http://forum.freecadweb.org/viewtopic.php?f=3&t=14677
    (0008973)
    Kunda1   
    2017-05-12 12:32   
    @joostn do you mind re-uploading the attachment? It didn't survive are previous tracker backup restore.
    (0008974)
    joostn   
    2017-05-12 13:21   
    I hope this is the file (it has the same name).
    (0009976)
    Kunda1   
    2017-08-21 11:07   
    @normandc do you mind weighing in ?
    (0010060)
    wmayer   
    2017-09-02 11:27   
    With occ7.2 it still crashes and shows the identical stack trace.
    (0011731)
    Kunda1   
    2018-09-13 20:09   
    @chrisb would you please test to see if issue is still present. Thanks!
    (0013045)
    Kunda1   
    2019-04-24 11:53   
    Adding to 0.19 roadmap so that bug gets attention
    (0014509)
    abdullah   
    2020-06-07 14:55   
    I have reported the bug upstream and provided a possible patch to avoid the segfault:
    https://tracker.dev.opencascade.org/view.php?id=31601

    @Kunda1
    For your administration ;)
    (0014704)
    sfornengo   
    2020-08-14 17:00   
    Can we hope this 4 years bug to be solve in a near future ?
    I can see proposed patch but always testing newer version never solve the problem...
    This bug really kills Freecad experience and adoption because it prevents the realization of even simple shells that are the most common operation for boxes and enclose cases...
    So we have no workaround than using another 3D CAD... Really too bad !
    (0014706)
    Kunda1   
    2020-08-21 20:52   
    Added to https://forum.freecadweb.org/viewtopic.php?f=10&t=20264&p=425392#p425392
    (0014996)
    sfornengo   
    2020-11-17 10:34   
    I am coming back on this issue with the following example showing a weird behavior that can lead to better understand the bug.
    In the following example, removing the face without fillet and trying to create a thickness of 1mm inward leads to the famous bug...
    But if first of all I create a thickness of 0mm inward I obtain a new solid that then enables to create a thickness of 1mm inward without leading to the bug.
    So the bug could be on freecad side ?
    (0014997)
    andergrin   
    2020-11-18 13:22   
    (Last edited: 2020-11-18 13:36)
    When I do the same steps (thickness of 0 mm inward), the body is also rotating 90 degrees on the x axis
    As I understand it, problems arise when there are chamfer (or fillets) in the part. When a wall is created inward, the chamfer also scales, and at some point it seems to invert and create self-intersections. I more or less learned how to bypass this problem by adding fillets to the chamfers or chamfers to the fillets, but this is not the solution to the problem, because it takes a long time to guess the right values.
    OS: Windows 10 (10.0)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.22960 (Git)
    Build type: Release
    Branch: master
    Hash: c5a4b01d2e4218bcc0eb6650337650a6c65ef0e4
    Python version: 3.8.6
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: Ukrainian/Ukraine (uk_UA)
    
    (0014999)
    andergrin   
    2020-11-18 13:40   
    Here, I managed to make desired (2,4 mm) inward thickness and chamfers, but I have to add Fillet001 to apply Thickness
    (0016469)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5634.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2204 [Part] Bug crash always 2015-07-30 20:16 2022-01-24 19:16
    Reporter: biogeo Platform:  
    Assigned To: wmayer OS: Linux Mint  
    Priority: normal OS Version: 13 Maya  
    Status: resolved Product Version: 0.15  
    Product Build: Resolution: fixed  
    Projection: none      
    ETA: none Fixed in Version: 0.20  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Crash when unioning toruses (upstream OCC bug)
    Description: When using the part workbench to union two toruses, in certain situations FreeCAD will appear to enter an infinite loop, during which it gradually consumes more and more RAM until the system slows to a crawl and the only solution is to kill the process.

    I have found this to occur under the following conditions:
    1. For both toruses, Radius1 == Radius2, and they are also equal between the two toruses.
    2. For both toruses, Angle3 == 90 degrees, i.e., they are both a "quarter donut".
    3. The two toruses are positioned to share a circular face.

    Depending on the relative angle between the planes in which the toruses lie, the union operation will sometimes work correctly, sometimes "succeed" but produce an unexpected result (e.g., only three circular faces with no torus components), and sometimes produce the infinite loop condition described above.
    Tags: #pending, #ready-for-migration, OCC Bug, OCC NotOnRoadmap, upstream
    Steps To Reproduce: 1. Open a new file and go to the Part workbench
    2. Create a torus "Torus" with Radius1=2mm, Radius2=2mm, Angle3=90
    3. Create a second torus "Torus001" with Radius1=2mm, Radius2=2mm, Angle3=90
    4. Rotate Torus001 90 degrees about the z-axis. The two together should look like a single torus with Angle3=180.
    5. Select Torus and Torus001 and use the Union tool.

    FreeCAD enters an infinite loop gradually allocating more and more RAM until the system slows to a crawl and the process must be killed.

    The attached file is the result of steps 1-4. Opening this file in a new FreeCAD session and running Union on the two toruses reliably crashes FreeCAD on my system.
    Additional Information:
    Attached Files: Torus-union-test.fcstd (3,517 bytes) 2015-07-30 20:16
    https://tracker.freecad.org/file_download.php?file_id=1059&type=bug
    Torus-union.fcstd (11,597 bytes) 2017-09-02 10:43
    https://tracker.freecad.org/file_download.php?file_id=1717&type=bug
    Notes
    (0006264)
    biogeo   
    2015-07-30 20:25   
    Forgot to include as additional information:

    OS: Linux Mint 13 Maya
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.15.4671 (Git)
    Branch: releases/FreeCAD-0-15
    Hash: 244b3aef360841646cbfe80a1b225c8b39c8380c
    Python version: 2.7.3
    Qt version: 4.8.1
    Coin version: 3.1.3
    OCC version: 6.8.0.oce-0.17
    (0006855)
    wmayer   
    2016-02-28 18:32   
    That's clearly an OpenCascade bug which we are not able to fix.
    (0006871)
    jmaustpc   
    2016-03-01 15:17   
    It eventually crashes FreeCAD here, with the OCE from tanderson, OCE patches over OCC 6.9.1

    OS: Ubuntu 12.04.5 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.16.6523 (Git)
    Build type: Release
    Branch: master
    Hash: ecd6517cb00fcf05edd41a38b3ce1fa8b16ec3ad
    Python version: 2.7.3
    Qt version: 4.8.2
    Coin version: 3.1.3
    OCC version: 6.9.1.oce-0.18-dev
    (0007722)
    Kunda1   
    2017-01-13 17:12   
    Does this issue persist in OCC 7.x ?
    If so Is there an open upstream bug we can link to?
    (0009337)
    Kunda1   
    2017-06-10 19:54   
    @biogeo can you re-up the attachment? We restored recently from a backup after an issue we had with th tracker and some attachments like yours didn't make it.
    (0009974)
    Kunda1   
    2017-08-21 11:01   
    @jmaustpc do you mind testing this with OCC7.1 ?
    (0010057)
    wmayer   
    2017-09-02 10:43   
    Attached is a file that shows the behaviour with occ6.8 where the applications eats all memory.
    With occ7.2 it now returns immediately but the shape is invalid. On the other hand in practise such a shape doesn't make too much sense anyway.
    (0011307)
    Kunda1   
    2018-05-30 16:05   
    Needs to be tested with OCC7.3
    (0012796)
    Kunda1   
    2019-02-27 21:57   
    @wmayer can you reproduce in OCC7.3
    (0012802)
    wmayer   
    2019-02-28 10:22   
    Yes, the behaviour with OCC7.3 is the same as with 7.2
    (0016077)
    wmayer   
    2021-12-12 14:44   
    With OCC7.4 and 7.5 still invalid shapes are created but with 7.6 finally a correct shape is built.
    (0016078)
    wmayer   
    2021-12-12 14:45   
    Needs to be built with OCC 7.6
    (0016467)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5632.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2041 [FreeCAD] Bug minor always 2015-04-07 22:34 2022-01-24 19:16
    Reporter: chrisb Platform: Linux, Mac, Windows  
    Assigned To: OS: Ubuntu  
    Priority: low OS Version: 14.04  
    Status: confirmed Product Version: 0.14  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FreeCAD warns when applying thickness "BRepAlgo_Image::Bind"
    Description: FreeCAD crashes when applying thickness to the selected surface of a lofted part.

    EDIT: Jan 23 2017
    Not crashing in 0.17. It shows an alert instead:
    BRepAlgo_Image::Bind

    EDIT: Jan 24 2017
    Other users are reporting that this is still a crash bug but are still using version that is inferior to OCC 7.0

    EDIT: Mar 25 2017
    Using freecad-daily with OCCT 7.1.0, no crash and no error: the Thickness completes, but the result is unchanged from the Loft (no shelling operation is done). Part Check geometry reports the solid as invalid.

    Tags: #ready-for-migration, OCC Bug, upstream
    Steps To Reproduce: Open the file uploaded to the forum: http://forum.freecadweb.org/download/file.php?id=12633 , select part workbench, select the surface and click the thickness icon.
    OS: Ubuntu 16.04.2 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.10611 (Git)
    Build type: None
    Branch: master
    Hash: 44a9ecd25f27ec3efe52c9de9c95ef2b3e19dd17
    Python version: 2.7.12
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.1.0
    Additional Information: Other members checked the error via the forum: http://forum.freecadweb.org/viewtopic.php?f=3&t=10382

    Note: This ticket is being tracked via OCC Bugs in the Bugtracker forum thread
    Attached Files: errorThickness.FCStd (5,882 bytes) 2015-04-07 22:34
    https://tracker.freecad.org/file_download.php?file_id=976&type=bug
    Notes
    (0005977)
    shoogen   
    2015-04-08 08:21   
    pload MODELING
    restore thickness-crash1-tcl-Loft001-00-section.brep Loft001-00-section
    restore thickness-crash1-tcl-Loft001-01-section.brep Loft001-01-section
    thrusections Loft001 1 0 Loft001-00-section Loft001-01-section
    explode Loft001 F
    offsetparameter 1e-7 p a
    offsetload Loft001 1 Loft001_2
    offsetperform Thickness
    donly Thickness
    (0007936)
    Kunda1   
    2017-01-23 23:16   
    per chrisb in https://forum.freecadweb.org/viewtopic.php?f=3&t=10382&start=10#p155463
    Not crashing in 0.17. It shows an alert instead:
    BRepAlgo_Image::Bind.

    OS: Mac OS X
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.9586 (Git)
    Build type: Release
    Branch: (detached from 0e2cf2e)
    Hash: 0e2cf2ebcaaa50723de608cf030af740cb6ad548
    Python version: 2.7.13
    Qt version: 4.8.7
    Coin version: 3.1.3
    OCC version: 7.0.0
    (0008702)
    Kunda1   
    2017-03-25 11:38   
    Per @normandc in https://forum.freecadweb.org/viewtopic.php?f=3&t=10382&start=10#p167101

    Using freecad-daily with OCCT 7.1.0, no crash and no error: the Thickness completes, but the result is unchanged from the Loft (no shelling operation is done). Part Check geometry reports the solid as invalid.

    normandc
    OS: Ubuntu 16.04.2 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.10611 (Git)
    Build type: None
    Branch: master
    Hash: 44a9ecd25f27ec3efe52c9de9c95ef2b3e19dd17
    Python version: 2.7.12
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.1.0
    (0010524)
    Kunda1   
    2017-12-06 22:27   
    @wmayer please advise. Is this still an upstream OCC issue ?
    (0012464)
    wmayer   
    2019-01-18 23:00   
    For me it works only when selecting Face5 (with OCCT 7.0 and 7.2). But when selecting any other face it fails and the error message is: BRepAlgo_Image::Bind
    (0016457)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5622.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2024 [FreeCAD] Bug major always 2015-03-23 16:38 2022-01-24 19:16
    Reporter: bhs67 Platform:  
    Assigned To: shoogen OS: Windows 7  
    Priority: normal OS Version: SP1  
    Status: acknowledged Product Version: 0.14  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Boolean -> Difference leaves a extra hole (upstream OCC bug)
    Description: One attachment is a pdf indicating the problem. The other two attachments are before and after the Procedure.

    Tags: #ready-for-migration, bump, OCC Bug, OCC NotOnRoadmap, upstream
    Steps To Reproduce: Procedure ... Part -> Boolean -> Boolean -> Difference -> (first shape) cube -> (second shape) total hollow fillet -> Apply.
    Additional Information:
    Attached Files: bug after.FCStd (138,433 bytes) 2015-03-23 16:38
    https://tracker.freecad.org/file_download.php?file_id=962&type=bug
    bug after.pdf (26,056 bytes) 2015-03-23 16:39
    https://tracker.freecad.org/file_download.php?file_id=963&type=bug
    bug before.FCStd (89,353 bytes) 2015-03-23 16:39
    https://tracker.freecad.org/file_download.php?file_id=964&type=bug
    bug_repaired-no_autorefine.fcstd (36,774 bytes) 2015-03-23 17:02
    https://tracker.freecad.org/file_download.php?file_id=965&type=bug
    Notes
    (0005932)
    shoogen   
    2015-03-23 17:01   
    (Last edited: 2015-03-24 17:20)
    You did not mention whether you created this file with automated refines enabled.
    The total hollow fillet is invalid in both files.
    You did not specify your full FreeCAD version information.

    (0005933)
    bhs67   
    2015-03-23 17:14   
    I am using FreeCad 0.14 rev 3700.
    Where do I find automated recomputes?
    (0005936)
    shoogen   
    2015-03-23 22:30   
    sorry, i meant automated refines. The are enabled by a setting called "automatically refine shape after boolean operation"
    (0005940)
    bhs67   
    2015-03-24 14:58   
    Hmmm. I checked the Preferences ... do not have "automatically refine model after boolean operation" checked. Should it be checked or not checked? Thanks!
    (0005941)
    shoogen   
    2015-03-24 17:37   
    http://tracker.dev.opencascade.org/view.php?id=25979
    (0007797)
    Kunda1   
    2017-01-15 15:22   
    @shoogen should we bump the upstream bug ?
    (0010013)
    Kunda1   
    2017-08-27 12:38   
    @ickby do you mind asking the upstream devs to assign this to their roadmap?
    (0010046)
    ickby   
    2017-08-30 08:27   
    Kunda: the bug has been verified against current OCCT recently and a test case has been added: 2017-08-07 18:16

    I think this should be enough to gurantee the treatment, what
    do you think?
    (0010051)
    Kunda1   
    2017-08-30 18:32   
    @ickby it's your call. I personally would ask if they could at least assign it their 'unscheduled' list.
    (0016454)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5619.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1926 [Part] Bug crash always 2015-01-17 14:47 2022-01-24 19:16
    Reporter: wvmarle Platform:  
    Assigned To: shoogen OS:  
    Priority: normal OS Version:  
    Status: acknowledged Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Crash when creating sweep (fix pending on the upstream release of OCC 7.7)
    Description: Crash when creating a sweep.
    Tags: #ready-for-migration, OCC 7.7, OCC Bug, sweep, upstream
    Steps To Reproduce: Parts toolbox, select Sweep tool
    Add Wire, Wire001, Wire002 for the sweep
    Select the ellipse for sweep path
    Create the sweep: crash

    Probably I'm doing something illegal here by having the ellipse extend a little beyond the Wire and Wire002, but nevertheless it shouldn't crash.

    Making it a complete ellipse solves the problem, it only crashes when the ellipse is an arc.
    Additional Information: OS: Linux Mint 17 Qiana
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.15.4484 (Git)
    Branch: master
    Hash: f72c802f5daa378298ffbfc3f3a17ec2d35c1816
    Python version: 2.7.6
    Qt version: 4.8.6
    Coin version: 4.0.0a
    OCC version: 6.7.1
    Attached Files: sweep crash.fcstd (6,022 bytes) 2015-01-17 14:47
    https://tracker.freecad.org/file_download.php?file_id=906&type=bug
    Notes
    (0005668)
    cox   
    2015-01-17 15:25   
    (Last edited: 2015-01-17 16:27)
    EDIT -Disregard this comment. I can reproduce

    http://forum.freecadweb.org/viewtopic.php?f=3&t=9358#p75957

    OS: "Arch Linux"
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.15.4495 (Git)
    Branch: master
    Hash: 1f44226882071790a86a16f86bfacda0e7a5a880
    Python version: 2.7.9
    Qt version: 4.8.6
    Coin version: 3.1.3
    OCC version: 6.7.1

    (0005670)
    shoogen   
    2015-01-17 16:12   
    I created an example for DRAWEXE from the attached file and uploaded it as sweep-arc2.zip to http://tracker.dev.opencascade.org/view.php?id=24909
    (0005985)
    shoogen   
    2015-04-09 21:10   
    test http://forum.freecadweb.org/viewtopic.php?f=3&t=10445&p=84239#p84161 before closing the ticket.
    (0007622)
    Kunda1   
    2017-01-11 11:55   
    (Last edited: 2017-01-11 11:59)
    Upstream ticket was bumped to OCC 7.2 roadmap.

    Edit: tagged as 'upstream' and 'OCC 7.2' to indicate that this issue should be re-examined when 7.2 is released

    (0009975)
    Kunda1   
    2017-08-21 11:04   
    Upstream ticket was was bumped to OCC 7.2.1 roadmap. Tagged ticket "OCC 7.2.1"
    (0010990)
    Kunda1   
    2018-03-03 10:52   
    Upstream ticket was was bumped to OCC 7.4 roadmap. Notated in OCC bugtracker list: https://forum.freecadweb.org/viewtopic.php?f=10&t=20264
    (0013512)
    Kunda1   
    2019-09-01 19:35   
    Upstream ticket was was bumped to OCC 7.5 roadmap.
    Tagged this ticket OCC7.5
    Notated in OCC bugtracker list: https://forum.freecadweb.org/viewtopic.php?f=10&t=20264
    (0014798)
    Kunda1   
    2020-10-08 13:47   
    Upstream ticket was was bumped to OCC 7.6 roadmap.
    Tagged this ticket OCC7.6
    Notated in OCC bugtracker list: https://forum.freecadweb.org/viewtopic.php?f=10&t=20264
    (0016206)
    Kunda1   
    2022-01-15 12:58   
    Upstream ticket was was bumped to OCC 7.7 roadmap.
    Tagged this ticket OCC7.6
    Notated in OCC bugtracker list: https://forum.freecadweb.org/viewtopic.php?f=10&t=20264
    (0017150)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6319.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1858 [FreeCAD] Bug minor always 2014-12-16 21:37 2022-01-24 19:16
    Reporter: NikB Platform: x86  
    Assigned To: shoogen OS: Windows  
    Priority: normal OS Version: 8  
    Status: acknowledged Product Version: 0.14  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Loft tool incorrect result with rotated ellipses (Upstream OCC bug)
    Description: Loft tool gives unexpected result when using identical ellipses rotated. One end edge as expected, but other has scolloping, concave or convex dependent on two or more ellipses.
    Tags: #ready-for-migration, Bountysource Potential, bump, OCC Bug, OCC NotOnRoadmap, upstream
    Steps To Reproduce:
    Additional Information:
    Attached Files: prop001.FCStd (9,903 bytes) 2014-12-16 21:37
    https://tracker.freecad.org/file_download.php?file_id=873&type=bug
    loft-el1.zip (1,713 bytes) 2018-11-13 17:51
    https://tracker.freecad.org/file_download.php?file_id=2049&type=bug
    loft-el1.png (12,170 bytes) 2018-11-13 17:51
    https://tracker.freecad.org/file_download.php?file_id=2050&type=bug
    FC_issue_0001858.fcstd (13,674 bytes) 2018-11-15 01:53
    https://tracker.freecad.org/file_download.php?file_id=2051&type=bug
    Notes
    (0005400)
    shoogen   
    2014-12-17 10:14   
    (Last edited: 2014-12-17 10:32)
    reproduceable in DRAWEXE of OCCT 6.8.1-dev
    reported as http://tracker.dev.opencascade.org/view.php?id=25626

    (0009990)
    Kunda1   
    2017-08-22 11:47   
    Still reproducible on OCCT 7.1 and upstream isn't on the roadmap. Requires bump.
    (0012071)
    Kunda1   
    2018-10-19 13:36   
    @adbdullah would you be interested in bumping the upstream ticket in the hopes that it may be added to the OCC roadmap ?
    (0012173)
    normandc   
    2018-11-11 06:18   
    Original attachment is missing, and the attached files in the OCCT bug tracker can't be downloaded.

    A loft between three ellipses rotated 90 degrees from each other appear fine in FC 0.18-dev with latest OCCT 7.3.0...
    (0012179)
    Kunda1   
    2018-11-12 00:47   
    What should be we do about this ticket then?
    (0012180)
    normandc   
    2018-11-12 02:55   
    Maybe the OCCT bug tracker requires to be registered to download. Since @abdullah has an account, we could ask him to upload the files here so we could check with FreeCAD compiled with latest OCCT. From what I understand of the posted DRAWEXE script (in the upstream bug, "Steps to reproduce"), it reads from brep files that are probably included in the zip archive.
    (0012191)
    abdullah   
    2018-11-13 17:51   
    Files are attached. I will indicate that the FC project is monitoring this ticket and whether it will be assigned to a roadmap.
    (0012196)
    abdullah   
    2018-11-14 19:06   
    @normandc
    @Kunda1

    Bugnote #0081082 added by MSV (developer) 2018-11-14 10:12

    Dear abdullah, OCC has no fonds to solve this bug in the nearest future without external investment or contribution. You are welcome to propose your fix if you can.
    (0012197)
    abdullah   
    2018-11-14 19:08   
    Unfortunately it is a too big shoe for my feet.
    (0012198)
    normandc   
    2018-11-15 01:53   
    Thanks, abdullah. I imported the 3 brep files into FreeCAD and created a Part Loft. I'm attaching it for future reference. The issue indeed persists with OCC 7.3.0. Ellipses are rotated only a few degrees, I had tried 90 degrees between each ellipse and that worked.

    I also tried a sweep with a straight line from (0,0,0) to (0,0,20) as path; same issue.

    That's a bummer on OCC's reply...
    (0017149)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6318.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1840 [FreeCAD] Bug minor always 2014-11-26 16:26 2022-01-24 19:16
    Reporter: ShapeShifter Platform: Ubuntu  
    Assigned To: OS: Linux  
    Priority: normal OS Version: 12.04.5 lts  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Fillet after thickness gives invalid geometry (upstream OCC Bug)
    Description: Putting a fillet on the inside corner of a thickness box creates an invalid shape.
    Tags: #pending, #ready-for-migration, bump, OCC Bug, OCC NotOnRoadmap, upstream
    Steps To Reproduce: go to part workbench
    make a cube 100 mm all over
    run geometry checker - no errors
    select the top face of the cube
    use thickness to make +10 mm sides and bottom
    run geometry checker - no error
    Select one of the inside vertical edges
    fillet it with 6 mm radius
    run geometry checker - error is "bad orientation of sub shape"
    delete the fillet and thickness
    make a new thickness with -10 mm
    run geometry checker - no error
    select a vertical inside edge and fillet 6 mm radius
    run geometry checker - no error
    Additional Information: I am using:

    OS: Ubuntu 12.04.5 LTS
    Word size of OS: 32-bit
    Word size of FreeCAD: 32-bit
    Version: 0.15.4159 (Git)
    Branch: master
    Hash: fa3a2a0d3a7a0a619ab6323e236376bb43636e79
    Python version: 2.7.3
    Qt version: 4.8.1
    Coin version: 3.1.3
    OCC version: 6.7.1

    so the problem seems to be caused by the positive thickness somehow, when the part "grows"

    Hope this helps

    Attached Files:
    Notes
    (0005345)
    shoogen   
    2014-11-26 18:10   
    http://tracker.dev.opencascade.org/view.php?id=25521
    (0007970)
    Kunda1   
    2017-01-24 19:18   
    Can someone bump the upstream bug ?
    (0010062)
    wmayer   
    2017-09-02 13:07   
    In occ 7.2 the error is slightly different: it now reports that the tolerance value is invalid
    (0012020)
    Kunda1   
    2018-10-13 14:26   
    @wmayer any changes in 7.3 ?
    (0012025)
    wmayer   
    2018-10-14 17:18   
    Still the same behaviour with 7.3
    (0015943)
    chennes   
    2021-09-16 19:59   
    I do not get this problem with

    OS: Ubuntu 21.04 (ubuntu:GNOME/ubuntu)
    Word size of FreeCAD: 64-bit
    Version: 0.20.25731 (Git)
    Build type: Unknown
    Branch: master
    Hash: e305dbd49caa2ede83dab8e8c34a4180b2cf26cc
    Python version: 3.9.5
    Qt version: 5.15.2
    Coin version: 4.0.0
    OCC version: 7.5.1
    Locale: English/United States (en_US)
    (0015944)
    chrisb   
    2021-09-17 05:46   
    No issues, confirmed in the forum discussion. Before closing: how can we notify OCC?

    OS: macOS 10.16
    Word size of FreeCAD: 64-bit
    Version: 0.20.25645 (Git)
    Build type: Release
    Branch: master
    Hash: 37d9757399b4c2ec30318eb88d7cd7c508246345
    Python version: 3.9.7
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.5.2
    Locale: C/Default (C)
    (0016207)
    Kunda1   
    2022-01-15 13:06   
    Who has upstream tracker access? @chennes @abdullah ? Could someone notate the upstream ticket? (http://tracker.dev.opencascade.org/view.php?id=25521)
    (0016439)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5604.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1646 [PartDesign] Bug minor always 2014-07-29 19:58 2022-01-24 19:16
    Reporter: ngallaher Platform: x86_64  
    Assigned To: OS: Linux  
    Priority: normal OS Version: Ubuntu 12.04.4  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: TCollection_IndexedDataMap::FindFromKey error when sweeping along BezierCurve (upstream OCC bug)
    Description: Attempting to sweep a circle along a given BezierCurve to create a solid results in an error popup stating "TCollection_IndexedDataMap::FindFromKey"
    Tags: #ready-for-migration, bezier curve, OCC 7.7, OCC Bug, sweep, upstream
    Steps To Reproduce: 1) Open the reproduction file (unsweepable.fcstd).
    2) Open the Part workbench
    3) Click the "Utility to Sweep" tool
    4) Select the circle and add it to the Sweep column
    5) Click "Sweep Path".
    6) Click on the BezierCurve to select it.
    7) Click "Done"
    8) Check "Create Solid"
    9) Click "Ok"

    Observe a message box titled "Input Error", containing the message TCollection_IndexedDataMap::FindFromKey
    Additional Information: OS: Ubuntu 12.04.4 LTS
    Word size: 64-bit
    Version: 0.15.3781 (Git)
    Branch: master
    Hash: 996af8d808a818726bd66c0e515e2d7eb7306bad
    Python version: 2.7.3
    Qt version: 4.8.1
    Coin version: 3.1.3
    SoQt version: 1.5.0
    OCC version: 6.7.0
    Attached Files: unsweepable.fcstd (4,167 bytes) 2014-07-29 19:58
    https://tracker.freecad.org/file_download.php?file_id=785&type=bug
    Notes
    (0004871)
    shoogen   
    2014-07-29 20:53   
    0000005 0x00007f955ec02fd9 in TopTools_IndexedDataMapOfShapeListOfShape::FindFromKey (this=0x7fff41394450, K1=...)
        at occt/inc/TCollection_IndexedDataMap.gxx:354
    0000006 0x00007f955f6404c6 in IsSameOriented (aFace=..., aShell=...)
        at occt/src/BRepFill/BRepFill_PipeShell.cxx:198
    0000007 0x00007f955f643637 in BRepFill_PipeShell::MakeSolid (this=0x65b3440)
        at occt/src/BRepFill/BRepFill_PipeShell.cxx:840
    0000008 0x00007f955d4c98c8 in BRepOffsetAPI_MakePipeShell::MakeSolid (this=
        0x7fff41394720)
        at occt/src/BRepOffsetAPI/BRepOffsetAPI_MakePipeShell.cxx:274
    0000009 0x00007f95624d2c64 in Part::Sweep::execute (this=0x64beb60)
        at free-cad/src/Mod/Part/App/PartFeatures.cpp:463
    (0004872)
    shoogen   
    2014-07-29 20:59   
    Error 3d = 24188.4831432816
    30 Segment(s) of degree 11
    Sweep : Degenerated case
    An exception was caught 0x7f045d441b27 : Standard_OutOfRange: TCollection_IndexedDataMap::FindFromKey
    ** Exception ** 0x7f045d441b27 : Standard_OutOfRange: TCollection_IndexedDataMap::FindFromKey
    (0004873)
    shoogen   
    2014-07-29 21:08   
    reported upstream http://tracker.dev.opencascade.org/view.php?id=25110
    (0007663)
    Kunda1   
    2017-01-12 12:09   
    upstream set target to 0CCT7.2
    tagged this ticket accordingly
    (0010056)
    wmayer   
    2017-09-01 18:34   
    With
    OS: Ubuntu 14.04.5 LTS
    Word size of OS: 32-bit
    Word size of FreeCAD: 32-bit
    Version: 0.17.11949 (Git)
    Build type: Unknown
    Branch: master
    Hash: 5d2b22ca286207775ddcbeabef7c5850fda32203
    Python version: 2.7.6
    Qt version: 4.8.6
    Coin version: 4.0.0a
    OCC version: 7.2.0
    Locale: German/Germany (de_DE)

    it shows a different error message: BRepFill_Sweep::BuildEdge
    (0010992)
    Kunda1   
    2018-03-03 10:58   
    upstream set target to 0CCT7.4
    tagged this ticket accordingly
    updated OCC buglist https://forum.freecadweb.org/viewtopic.php?f=10&t=20264
    (0013513)
    Kunda1   
    2019-09-01 19:36   
    Upstream bumped this to OCC7.5
    tagged this ticket accordingly
    updated OCC buglist https://forum.freecadweb.org/viewtopic.php?f=10&t=20264
    (0014799)
    Kunda1   
    2020-10-08 13:53   
    Upstream ticket was was bumped to OCC 7.6 roadmap.
    Tagged this ticket OCC7.6
    Notated in OCC bugtracker list: https://forum.freecadweb.org/viewtopic.php?f=10&t=20264
    (0016426)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5591.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1570 [FreeCAD] Bug major always 2014-06-02 10:00 2022-01-24 19:16
    Reporter: denem Platform: All  
    Assigned To: OS: All  
    Priority: normal OS Version: All  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Part sweep bug with acute angle (Upstream OCC bug)
    Description: Sweep resulting figure contains invalid additional segments and/or obstructed parts. This bug affects FreeCAD .13 and .14
    Tags: #ready-for-migration, OCC 7.7, OCC Bug, sweep, upstream
    Steps To Reproduce: Make any sweep containing an acute corner in wire.
    Additional Information: Sample project is attached along with screenshot of result.
    Attached Files: Sweep bug.zip (307,927 bytes) 2014-06-02 10:00
    https://tracker.freecad.org/file_download.php?file_id=763&type=bug
    Notes
    (0004731)
    shoogen   
    2014-06-02 12:54   
    reproduceable with OCCT development version:
    > mksweep Sweep-0-spine
    > setsweep -CF
    > addsweep Sweep-0-section-00-Sketch001
    > buildsweep Sweep -C -S

    Compile with option DEB : if problems with intersection : IntWalk_PWalking_1.gxx (lbr le 1erdec98)
    Fail of TrimCorner

    Draw[5]> checkshape Sweep
    On Shape faulty_1 :
    BRepCheck_NotConnected
    Shape faulty_1 on shape faulty_2 :
    BRepCheck_NotConnected

    Faulty shapes in variables faulty_1 to faulty_2
    (0004735)
    shoogen   
    2014-06-05 21:31   
    http://tracker.dev.opencascade.org/view.php?id=24991
    (0007771)
    Kunda1   
    2017-01-14 21:30   
    upstream bumped ticket to OCC 7.2
    I've tagged this ticket accordingly
    (0009793)
    Kunda1   
    2017-07-22 12:05   
    upstream bumped to OCC 7.2.1
    (0009794)
    Kunda1   
    2017-07-22 12:08   
    Linking to 0001571
    @denem can you re-up zips for both tickets ?
    (0010991)
    Kunda1   
    2018-03-03 10:55   
    upstream bumped to OCC 7.4
    (0013514)
    Kunda1   
    2019-09-01 19:40   
    Upstream bumped this to OCC7.5
    tagged this ticket accordingly
    updated OCC buglist https://forum.freecadweb.org/viewtopic.php?f=10&t=20264
    (0014800)
    Kunda1   
    2020-10-08 13:54   
    Upstream ticket was was bumped to OCC 7.6 roadmap.
    Tagged this ticket OCC7.6
    Notated in OCC bugtracker list: https://forum.freecadweb.org/viewtopic.php?f=10&t=20264
    (0016423)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5588.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    938 [PartDesign] Bug minor always 2013-01-01 08:38 2022-01-24 19:16
    Reporter: ghia Platform:  
    Assigned To: wmayer OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.12  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Fillet can not round a face (upstream OCC bug)
    Description: See file in addendum of 0000937

    While the shape is 20 mm thick, you can not place 2 fillets of 10 mm
    Fillet001 which is 9 mm can not be set to 10
    Tags: #ready-for-migration, fillet, OCC Bug, OCC NotOnRoadmap, upstream
    Steps To Reproduce:
    Additional Information: This ticket is being tracked from OCC Bugs in the Bugtracker forum thread.
    Attached Files:
    Notes
    (0003322)
    wmayer   
    2013-07-02 03:37   
    Could be a float vs. double precision issue. Should be checked once the double-precision branch is merged into master.
    (0003644)
    tanderson69   
    2013-09-23 17:29   
    (Last edited: 2013-09-23 17:30)
    I tried this with the current assembly branch (has float to double change) and there was no change.

    I also tried this with the OCC DRAWEXE and witnessed the same behavior.

    also searched OCC forum. Here is one thread.
    http://www.opencascade.org/org/forum/thread_21317/?forum=3

    //OCC rant removed

    (0005652)
    wmayer   
    2015-01-14 13:34   
    http://tracker.dev.opencascade.org/view.php?id=25478
    (0015183)
    Kunda1   
    2020-12-31 12:02   
    (Last edited: 2020-12-31 12:04)
    Can someone test with OCC 7.5.0 ?

    Edit: Please remember to update the relationship with Feature 0001192 if this ticket is resolved.
    (0016396)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5561.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2526 [FreeCAD] Feature minor always 2016-04-28 04:04 2022-01-24 19:14
    Reporter: ollydbg Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: Tracking this via OCC bugs in the bugtracker forum thread
    Summary: Add an option to show or hide the seam edges for the 3D view
    Description: We need to add an option to filter out the seam edges and only shows the non-seam edges in the render output or the 3D view. But I still need to let the non-seam edges shown.

    To get an screen shot of the 3D view which can be used as a technical drawing(I would like to put the drawing in some papers or books), the seam lines are not needed from my point of view.

    See our discussion here in the forum: https://forum.freecadweb.org/viewtopic.php?f=3&t=14022
    Tags: #ready-for-migration, Bountysource Potential, Coin3d, OCC Bug, seam, UI, upstream
    Steps To Reproduce: It is very simple to see the seam line, just add a cylinder from the Part workbench, and you will see a straight line on the face, this is the seam edge.
    Additional Information:
    Attached Files: Loft-seam-issue.png (57,942 bytes) 2019-05-09 11:14
    https://tracker.freecad.org/file_download.php?file_id=2211&type=bug
    Notes
    (0013088)
    Kunda1   
    2019-05-09 11:14   
    (Last edited: 2019-07-30 00:23)
    Beside the above thread ( https://forum.freecadweb.org/viewtopic.php?f=3&t=14022 ) there is further discussion also at https://forum.freecadweb.org/viewtopic.php?f=24&t=36223&p=306787#p306743

    (0013393)
    Kunda1   
    2019-07-30 00:22   
    Yet another discussion on this topic: https://forum.freecadweb.org/viewtopic.php?f=3&t=29337
    (0014403)
    Kunda1   
    2020-05-06 11:29   
    Another discussion: https://forum.freecadweb.org/viewtopic.php?f=3&t=46081
    (0014404)
    openBrain   
    2020-05-06 16:45   
    @Kunda1 : I'm not sure this is really same thing. This ticket is only about being able to not display seams. Nothing more. The last topic you mentioned is more about geometric issues with seams (there are quite a lot, AFAIK all are actually OCC things). ;)
    (0015192)
    Kunda1   
    2020-12-31 13:05   
    Tracking this via OCC bugs in the bugtracker forum thread
    (0016488)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5653.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4129 [PartDesign] Bug crash always 2019-09-13 14:22 2022-01-24 18:47
    Reporter: uwestoehr Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: acknowledged Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Crash on setting certain dimensions in a sketch (Upstream OCC bug)
    Description: - open the attached example file
    - open the Sketch "Sketch-Pinpad"
    - set for the Edge 2 a vertical constraint (e.g. 3mm)
    - close the sketch

    result: crash
    One out of 5 times it does not crash and I get an "access violation" in the report view.

    The crash could be reproduced also on Mac.

    @TheMarkster analyzed the problem in this post:
    https://forum.freecadweb.org/viewtopic.php?p=327107#p327139
    Tags: #ready-for-migration, OCC Bug, OCC Unscheduled, sketcher, upstream
    Steps To Reproduce:
    Additional Information: Forum thread: https://forum.freecadweb.org/viewtopic.php?f=3&t=38590

    OS: Windows 10
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.17505 (Git)
    Build type: Release
    Branch: master
    Hash: 755536e9df94d2d39da1468420f1fd333c35da7a
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: German/Germany (de_DE)
    Attached Files: Crashfile.FCStd (259,803 bytes) 2019-09-13 14:22
    https://tracker.freecad.org/file_download.php?file_id=2327&type=bug
    Notes
    (0014438)
    abdullah   
    2020-05-29 13:51   
    Note: OCCT crashes in PartDesign::FeatureFillet
    (0014444)
    abdullah   
    2020-05-30 14:00   
    I have reported the bug upstream to OpenCascade and provided a patch for a possible solution. With the patch an exception is raised, which is catched by FreeCAD and the crash is avoided:
    https://tracker.dev.opencascade.org/view.php?id=31585

    @kunda1
    I think you do something with upstream reported OCCT tickets... so I let you do your magic ;)
    (0014445)
    Kunda1   
    2020-05-30 15:15   
    @abdullah I've added this ticket and companion upstream tickets to the thread tracking upstream OCC bugs: https://forum.freecadweb.org/viewtopic.php?t=20264 ;)
    (0014487)
    abdullah   
    2020-06-06 17:45   
    There is no solution other than wait for OCCT to solve the access violation:
    https://tracker.dev.opencascade.org/view.php?id=31585

    Until them, this ticket remains as acknowledged.
    (0015041)
    Kunda1   
    2020-12-01 11:39   
    Added 'OCC bug' to the bug summary for easier Identification
    (0016273)
    Kunda1   
    2022-01-24 18:40   
    @abdullah do you mind bumping the upstream ticket?
    (0016823)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5989.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3277 [Project Tools & Websites] General feature always 2017-11-27 22:23 2022-01-24 18:42
    Reporter: Kunda1 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Omitting translation pages in Wiki search results
    Description: Right now when searching the FC wiki many pages return that are duplicated because they are translation of the same page in english. It would be very effective to search the wiki without this inconvenience.
    Tags: #ready-for-migration, documentation, wiki
    Steps To Reproduce:
    Additional Information: Forum thread: https://forum.freecadweb.org/viewtopic.php?f=21&t=25591
    Attached Files:
    Notes
    (0010523)
    Kunda1   
    2017-12-06 19:32   
    (Last edited: 2017-12-06 19:51)
    Asked for some guidance on #Mediawiki on Freenode.
    TLDR: they recommend CirrusSearch extension ( https://www.mediawiki.org/wiki/Help:CirrusSearch#Inlanguage )

    
    [14:02] <kunda_> Is there a way to search mediawiki without bringing up translation pages ? (MediaWiki 1.28.2)
    [14:04] <Zppix> kunda_: explain please?
    [14:05] <bawolff> kunda_: So the search options are going to vary depending on what search extensions you have installed
    [14:05] <bawolff> CirrusSearch (what wikimedia uses) has very different options from mediawiki default
    [14:06] <kunda_> so lets say I put a search term in, the result is that many pages that have been translated with said term also appear. I'm wanting to search only in english in this example
    [14:06] <bawolff> but generally speaking, the Translation: namespace can be easily excluded, but the subpages are harder
    [14:06] <bawolff> I assume we're talking about translations made by Extension:Translate
    [14:06] <kunda_> The current wiki I'm referring to is https://www.freecadweb.org/wiki
    [14:07] <kunda_> yes, I think that is what we're running
    [14:07] <kunda_> how can i check ?
    [14:07] <bawolff> https://www.mediawiki.org/wiki/Help:CirrusSearch has some info on the advanced search options that apply only to CirrusSearch
    [14:07] <bawolff> If you go to Special:Version on your wiki
    [14:08] <kunda_> Translate 2016-10-28 (5addec5) 08:26, 13 February 2017
    [14:09] <bawolff> Looks like you're just using the default search, which has much less advanced options
    [14:10] <kunda_> bawolff: so you recommend doing what ?
    [14:10] <bawolff> honestly, I don't think its possible to filter out translations with the default search
    [14:11] <kunda_> as opposed to cirrusSearch ?
    [14:13] <kunda_> bawolff: so your recommendation is cirrussearch, correct ?
    [14:14] <bawolff> I think https://www.mediawiki.org/wiki/Help:CirrusSearch#Inlanguage is what you're looking for
    [14:14] <bawolff> so yes
    [14:14] <bawolff> CirrusSearch is not the easiest ext to install
    [14:16] <kunda_> Yes, Inlanguage is what I'm looking for
    [14:18] <kunda_> Looks like Elastica requires Composer which is a PHP dependency manager
    [14:19] <bawolff> Its possible to install without composer, but compser is probably the best way
    [14:19] <bawolff> For example, with the mediawiki/vendor.git repo
    [14:19] <kunda_> How do you install without composer ?
    [14:20] <bawolff> or mediawiki/core/vendor.git Can never remember which one it is
    [14:20] <bawolff> you have to manually install all the dependencies
    [14:20] <kunda_> is there a list of deps that I can look at ?
    [14:21] <bawolff> its in the composer.json file. but you have to recursively look at each one
    [14:22] <kunda_> ok.. thanks a lot bawolff
    [14:22] <bawolff> kunda_: if in your mediawiki directory, you do
    [14:22] <bawolff> git clone https://gerrit.wikimedia.org/r/p/mediawiki/vendor.git vendor
    [14:22] <bawolff> This will pull all of Wikimedia's dependencies, which might be enough to install cirrus without composer
    [14:22] <bawolff> you'd have to first remove the existing vendor repo
    [14:23] <bawolff> Note, that using the mediawiki/vendor.git repo isn't officially supported, so ymmv in the long term, but it will probably work fine as long as you remember to use the right branch that corresponds with your mediawiki version, and keep it in sync with your mediawiki version
    [14:27] <kunda_> thanks bawolff :)
    

    (0016586)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5751.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4420 [Project Tools & Websites] General major N/A 2020-08-19 07:58 2022-01-24 18:42
    Reporter: kkremitzki Platform:  
    Assigned To: OS:  
    Priority: high OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Debian GNU/Linux bullseye/sid
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.4.
    Build type: Release
    Python version: 3.8.3
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: English/United States (en_US)
    Summary: Shortage of high-quality issues suitable for bounties
    Description: Although we have a fund for bounties that can pay for FreeCAD work, it is difficult to use the fund because of a lack of suitable issues. They are often too small/specific bugs or too large issues like "fix toponaming". It would be beneficial to have someone go through some existing discussions in the forums and distill them into medium-sized work items suitable for a $100 bounty.

    The issues should be clearly described, and have concrete achievables as well as specific requirements laid out so that there would be no doubt when someone can claim the bounty. In order to close this issue, as the bug opener I would consider documenting 10 high-quality issues to be enough to claim this bounty. Note that the issues can encompass any task that would be considered a FreeCAD project activity, for example an issue similar to this one would be acceptable, valuable contributions are not only code.
    Tags: #ready-for-migration
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016934)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6101.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4564 [TechDraw] Bug major always 2021-02-12 23:55 2022-01-24 17:45
    Reporter: mattbaker.digital Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: feedback Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Windows 10 (10.0)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.23756 (Git)
    Build type: Release
    Branch: master
    Hash: 9c6e9184930a52b165a0b7274e3a45d1006bfe67
    Python version: 3.8.6
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: English/United Kingdom (en_GB)
    Summary: Excessive vertices generated for curved pocket on drawing projection which hangs application
    Description: Generating an XZ projection of the following part in the TechDraw WB results in an excessive number of vertices for the curved cut-out and blocks the UI thread (unresponsive).


    Original forum post: https://forum.freecadweb.org/viewtopic.php?f=3&t=55489&p=477314#p477264
    Tags:
    Steps To Reproduce: Open the attached model (Tube.FCStd)
    Open the drawing page and set the Front projection direction to X0, Y-1, Z0.000000
    FreeCAD hangs while generating the view and has an excessive number of vertices when complete.


    Set the projection direction to X0, Y-1, Z0.000001
    The view is now missing lines.


    Set the projection direction to X0, Y-1, Z0.000100
    The view is now almost perfect.

    Additional Information:
    Attached Files: Tube.FCStd (85,329 bytes) 2021-02-13 00:06
    https://tracker.freecad.org/file_download.php?file_id=2627&type=bug
    Missing lines.png (37,485 bytes) 2021-02-13 00:06
    https://tracker.freecad.org/file_download.php?file_id=2628&type=bug
    Almost perfect.png (36,674 bytes) 2021-02-13 00:06
    https://tracker.freecad.org/file_download.php?file_id=2629&type=bug
    Excessive vertices.png (41,993 bytes) 2021-02-13 00:06
    https://tracker.freecad.org/file_download.php?file_id=2630&type=bug
    Notes
    (0015334)
    mattbaker.digital   
    2021-02-13 00:06   
    Errors while uploading source files. Uploading again.
    (0016180)
    wandererfan   
    2022-01-02 17:18   
    is there a connection with 4639? Overlapping lines not drawn??
    (0016199)
    wandererfan   
    2022-01-10 13:19   
    The missing short lines seem to be a bug in OCCT. The number of vertices is appropriate for the projected BSpline.
    (0016269)
    Kunda1   
    2022-01-24 17:45   
    Can someone test this in the latest (OCC 7.6) ?
    (0016993)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6161.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4469 [FreeCAD] Feature feature always 2020-10-19 03:48 2022-01-24 17:28
    Reporter: jaxxor Platform:  
    Assigned To: openBrain OS: Ubuntu  
    Priority: normal OS Version: 18.04  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Ubuntu 18.04.5 LTS (ubuntu:GNOME/ubuntu)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.22756 (Git) AppImage
    Build type: Release
    Branch: master
    Hash: ce87f586ee36ffe8ebcdcd3947ced4ab389ae795
    Python version: 3.8.6
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: English/United States (en_US)
    Summary: consistant unit usage
    Description: Hey all
    Ugly american here to complain about the lack of support for the stupid foot/inch system.

    In the image tool set, the option to scale the image only comes up in mm.
    I am running the Appimage version of 0.19



    anyway,
    Thanks for any support.
    J.
    Tags: units
    Steps To Reproduce: normal use.
    Additional Information:
    Attached Files: Screenshot from 2020-10-18 20-26-32.png (101,443 bytes) 2020-10-19 03:48
    https://tracker.freecad.org/file_download.php?file_id=2547&type=bug
    Notes
    (0016951)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6118.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1951 [Draft] Bug trivial always 2015-02-04 15:03 2022-01-24 17:05
    Reporter: ctjctj Platform: Linux  
    Assigned To: openBrain OS: Ubuntu  
    Priority: normal OS Version: 14.10  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Draft workbench preferences snap settings does not use "units" settings
    Description: In preferences general select an imperial units. Go to draft workbench then bring preferences up. Select draft->snap settings. Grid spacing is always mm
    Tags: snap, units
    Steps To Reproduce:
    Additional Information:
    Attached Files: draft-snap_settings-grid_spacing_in_mm.png (72,750 bytes) 2017-01-09 20:00
    https://tracker.freecad.org/file_download.php?file_id=1421&type=bug
    Screenshot_20220122_203043.png (115,807 bytes) 2022-01-23 01:31
    https://tracker.freecad.org/file_download.php?file_id=2752&type=bug
    Screenshot_20220122_203252.png (130,632 bytes) 2022-01-23 01:34
    https://tracker.freecad.org/file_download.php?file_id=2753&type=bug
    Notes
    (0007585)
    Kunda1   
    2017-01-09 20:01   
    Still an issue 0.16
    Tested on OS: "Manjaro Linux"
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.16.Unknown
    Build type: Release
    Python version: 2.7.12
    Qt version: 4.8.7
    Coin version: 3.1.3
    OCC version: 6.9.1
    (0007698)
    Kunda1   
    2017-01-13 00:09   
    Devs, this ticket needs to move to the 'Draft' category
    (0010732)
    Kunda1   
    2018-01-09 10:34   
    Forum thread https://forum.freecadweb.org/viewtopic.php?f=8&t=26277
    (0010834)
    Kunda1   
    2018-01-23 19:08   

    All Draft/Arch prefs settings are in millimeters still.... Couldn't find out how to use the InputField widget in qt designer yet

    yorik
    (0012432)
    sopwith   
    2019-01-14 19:49   
    I ran into this problem just now with 0.18dev-15619 on Windows Conda build. Kind of hard to draft anything in feet and inches... Bump.
    (0012551)
    Kunda1   
    2019-01-29 18:14   
    @yorik will this make it in to 0.18 or bumped to 0.19?
    (0012645)
    yorik   
    2019-02-15 00:05   
    It seems possible already (the sketcher has one), but haven't looked at how they did it yet.. Let's bump it to 0.19
    (0016260)
    Kunda1   
    2022-01-23 01:31   
    (Last edited: 2022-01-23 01:37)
    @ctjctj can confirm
    After setting imperial units I still see:
    Preferences > Draft > 'Text and Dimensions'
    the units for the preferences are in mm


    OS: Ubuntu Core 20 (KDE/plasma)
    Word size of FreeCAD: 64-bit
    Version: 0.20.27148 (Git)
    Build type: Release
    Branch: master
    Hash: 88ded38ca16e38a556e432a651792c56a65fc80d
    Python version: 3.8.10
    Qt version: 5.15.3
    Coin version: 4.0.0
    OCC version: 7.5.2
    Locale: English/United States (en_US)
    (0016261)
    Kunda1   
    2022-01-23 01:34   
    Preferences > Draft > 'Grid and Snapping' also is showing mm units
    (0016445)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5610.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3778 [Project Tools & Websites] Feature minor have not tried 2019-01-17 21:33 2022-01-23 01:16
    Reporter: Kunda1 Platform:  
    Assigned To: Kunda1 OS:  
    Priority: normal OS Version:  
    Status: feedback Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Central translate function
    Description: https://forum.freecadweb.org/viewtopic.php?f=8&t=22324&start=60#p178380

    I think we already had a discussion about a centralized translate function. This stuff comes up again and again, so in my mind it would make sense to have a centralized function available. It would definetly simplify porting to new dependencies, as the same stuff doesn't have to be done in all kind of modules.

    loooo
    Tags: #pending
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016259)
    Kunda1   
    2022-01-23 01:14   
    @looo can you weigh in on this ticket? Has anything progressed on this front since?
    (0016698)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5863.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4491 [FreeCAD] Bug minor always 2020-11-13 00:03 2022-01-23 00:53
    Reporter: chrisb Platform:  
    Assigned To: chrisb OS: MacOS  
    Priority: normal OS Version:  
    Status: feedback Product Version:  
    Product Build: Resolution: reopened  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: macOS 10.15
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.22960 (Git)
    Build type: Release
    Branch: master
    Hash: c5a4b01d2e4218bcc0eb6650337650a6c65ef0e4
    Python version: 3.8.6
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: C/Default (C)
    Summary: In French version Preferences vanish on MacOS
    Description: If language is changed to Français on MacOS, then the preferences no longer open the preferences dialog.
    As a workaround they are available from the Start page.
    See forum posts
    and https://forum.freecadweb.org/viewtopic.php?f=12&t=51624
    Tags: #pending, locale, macOS, translation, UI
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0015752)
    chrisb   
    2021-07-26 07:39   
    Same issue still present with Russian locale, see forum discussion.
    (0016257)
    Kunda1   
    2022-01-23 00:52   
    @chrisb is this still an issue?
    (0016962)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6129.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4815 [FreeCAD] Feature feature N/A 2021-12-28 23:19 2022-01-23 00:41
    Reporter: mcgiwer Platform: amd64  
    Assigned To: OS: Debian  
    Priority: normal OS Version: 10+  
    Status: feedback Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: Version 0.19
    Summary: [Proposal] Run script (bash) for FreeCAD
    Description: Hello. I had wrote a script in bash that (after placing in the same folder as for example bin) would allow to launch FreeCAD directly from it and with creates a log file.

    I hope that it becomes included to the base FreeCAD. I also hope to recieve a upload permission on GitHub to be able to contribute as well.
    Tags: #pending-forum
    Steps To Reproduce:
    Additional Information:
    System Description Temporary system
    Attached Files: run (1,271 bytes) 2021-12-28 23:19
    https://tracker.freecad.org/file_download.php?file_id=2745&type=bug
    Notes
    (0016184)
    openBrain   
    2022-01-03 10:57   
    @mcgiwer : please address issues/proposals according our reporting guidelinesby opening a new thread in our forum.
    Notice that there is no need to get write access to GH repo to contribute. Just fork, code, then do a pull request. This is how contributions are merged.
    Thx
    (0016254)
    Kunda1   
    2022-01-23 00:41   
    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=4&t=65585
    (0017132)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6301.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3925 [Expressions] Bug minor always 2019-04-04 22:47 2022-01-23 00:01
    Reporter: metatheorem Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Negative numbers with multiple units interpeted as expressions
    Description: When typing in a negative measurement, such as in the Draft Move tool, combinations of units are interpreted as an addition expression. For example, the expression "-1m 10mm" is evaluated to "-990.0 mm" instead of "-1010.0 mm" as it should be. This appears to happen regardless of the units used.

    Forum disussion here: Negative numbers in feet/inches interpreted wrong
    Tags: units
    Steps To Reproduce: 1. In the Draft workspace, create a two-point rectangle.
    2. In any of the point value fields (x, y, or z), type in an expression such as "-1m 10mm".
    3. Move keyboard focus away from the field, and the entry changes to "-990.0 mm".
    Additional Information: This can happen either when a text entry field loses focus or when a tool is applied.

    Workarounds:
    1. If possible, key in a single type of unit.
    2. If not possible, such as when working with feet and inches, perform two operations that add up to the desired measurement. This may not work for all operations.

    OS: Linux
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.Unknown
    Build type: Unknown
    Python version: 2.7.15
    Qt version: 4.8.7
    Coin version: 3.1.3
    OCC version: 6.9.1.oce-0.18
    Locale: English/UnitedStates (en_US)
    Attached Files: Compound units negative values are substracted.PNG (110,230 bytes) 2019-04-27 03:46
    https://tracker.freecad.org/file_download.php?file_id=2196&type=bug
    Notes
    (0013041)
    Kunda1   
    2019-04-24 11:19   
    In the future, please follow our guidelines (mentioned in the yellow banner at the top of the page)

    How did you build FreeCAD?
    Can you please try with a Qt5/Py3/OCC7.3 build?
    https://github.com/FreeCAD/FreeCAD/releases/tag/0.18.1
    or even better try the 0.19_pre
    https://github.com/FreeCAD/FreeCAD/releases/tag/0.19_pre
    (0013059)
    Geoplace   
    2019-04-27 03:46   
    Hi

    I've teste the version 18.1

    But there is the same behavior.
    1.-Draw a line.
    2- Change its X end point typing -1m 10mm the result was -990mm instead of the -1010mm

    OS: Windows 8.1
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16110 (Git)
    Build type: Release
    Branch: (HEAD detached at upstream/releases/FreeCAD-0-18)
    Hash: f7dccfaa909e5b9da26bf50c4a22ccca9bb10c40
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    (0013195)
    Kunda1   
    2019-06-13 04:49   
    Another relevant forum thread: https://forum.freecadweb.org/viewtopic.php?f=3&t=35209
    (0016744)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5909.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2981 [FEM] Feature feature have not tried 2017-03-23 02:08 2022-01-20 12:03
    Reporter: kkremitzki Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: feedback Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FEM, GUI, constraint force should display units
    Description: Object FemConstraintForce needs to display appropriate units when applied as a point load, line load, or area load.

    Ideally, if line load or area load is selected, the appropriate length or area should display.

    An optional checkbox to input normalized force would be good too. So a user input of F newtons automatically gets converted to create the correct ConstraintForce which is a line load F/l on a line of length l, or an area load F/A when a face with area A is selected.
    Tags: #lowhangingfruit, #tobeclosed, units
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0008730)
    berndhahnebach   
    2017-03-29 11:51   
    Good point. Fully agree.
    (0008857)
    Kunda1   
    2017-05-02 21:16   
    Confirming based on bernd's response
    (0016229)
    Kunda1   
    2022-01-19 17:41   
    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=18&t=65474
    (0016235)
    Kunda1   
    2022-01-20 12:00   
    @kkremitzki see @thschrader response in https://forum.freecadweb.org/viewtopic.php?p=563409#p563409
    (0016525)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5690.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3572 [TechDraw] Feature feature N/A 2018-08-31 13:09 2022-01-19 17:53
    Reporter: Kunda1 Platform:  
    Assigned To: OS:  
    Priority: none OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: TechDraw: Easier Color Drawings
    Description: Pretty self-explanatory
    Reference: https://forum.freecadweb.org/viewtopic.php?f=3&t=30524&p=253695#p253670
    Tags: #pending-forum
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016231)
    Kunda1   
    2022-01-19 17:53   
    forum thread bumped https://forum.freecadweb.org/viewtopic.php?p=563252#p563252
    (0016637)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5802.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4083 [FreeCAD] Bug crash always 2019-08-08 14:48 2022-01-19 08:24
    Reporter: FrankGould Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: A bug in the Coin3D library causing app to crash on RPi4 (Upstream Raspbian libs need updating)
    Description: From the #freecad forum chat yesterday, "there's a bug in an underlying library (Coin3D)" that needs to be fixed. The results of running the FreeCAD app is that it crashes anytime someone tries to load a file or create a new one. FreeCAD should run on the new desktop Raspberry Pi 4B models running Raspbian Buster.
    Tags: Coin3d, raspberry pi, upstream
    Steps To Reproduce: Install buster on RPi4B, install FreeCAD, run app, and try to load an existing STL file or create a new file. In both cases, the app crashed on my 4GB system.
    Additional Information: Original forum thread: https://forum.freecadweb.org/viewtopic.php?f=42&t=37458
    Discussion thread related to this bug: https://forum.freecadweb.org/viewtopic.php?f=8&t=39444

    OS: Raspbian GNU/Linux 10 (buster)
    Word size of OS: 32-bit
    Word size of FreeCAD: 32-bit
    Version: 0.18.
    Build type: Release
    Python version: 2.7.16
    Qt version: 5.11.3
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    Attached Files:
    Notes
    (0013406)
    FrankGould   
    2019-08-08 15:14   
    (Last edited: 2019-08-08 15:38)
    https://forum.freecadweb.org/viewtopic.php?f=42&t=37458

    When running freecad from terminal CLI, received the following error message. Did not see this when running from drop-down menu. This is the same as reported in forum.

    Coin warning in cc_glglue_instance(): Error when setting up the GL context. This can happen if there is no current context, or if the context has been set up incorrectly.
    Program received signal SIGSEGV, Segmentation fault.
    #0 /lib/arm-linux-gnueabihf/libc.so.6(__default_sa_restorer+0) [0xb32b6120]

    (0013641)
    Kunda1   
    2019-09-19 03:30   
    Thread dedicated to discussion about this bug is https://forum.freecadweb.org/viewtopic.php?f=8&t=39444
    (0013667)
    Kunda1   
    2019-09-20 19:35   
    A bug was open on Debian for this as well: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931458
    (0014342)
    -alex-   
    2020-04-13 14:08   
    (Last edited: 2020-04-13 14:09)
    If FreeCAD compiled with PY2/Qt4 -> no crash
    If FreeCAD compiled with PY3/Qt4 -> no crash
    If FreeCAD compiled with PY2/Qt5 -> crash with segfault occurs
    If FreeCAD compiled with PY3/Qt5 -> crash with segfault occurs
    (0014619)
    Kunda1   
    2020-07-06 11:44   
    @FrankGould this is reproducible on 0.19.x as well ?
    (0014620)
    FrankGould   
    2020-07-06 12:02   
    @Kunda1 I have migrated to Arch Linux ARM due to several Buster issues and am no longer using FreeCAD.
    (0015042)
    Kunda1   
    2020-12-01 12:30   
    This issue has to do with the Raspbian libs that need to be updated.
    https://forum.freecadweb.org/viewtopic.php?f=42&t=37458&p=453369#p453369
    (0015126)
    -alex-   
    2020-12-10 23:37   
    update:
    If FreeCAD compiled with PY2/Qt4 RPIOS32B-> no crash
    If FreeCAD compiled with PY3/Qt4 RPIOS32B-> no crash when creating new document
    If FreeCAD compiled with PY2/Qt5 RPIOS32B-> crash with segfault occurs when creating new document
     
    If FreeCAD compiled with PY3/Qt5 RPIOS32B-> crash with segfault occurs when creating new document
    If FreeCAD compiled with PY3/Qt5 RPIOS64B(betatest)-> no crash when creating new document (it happens time to times when opening other documents, maybe not related)
    If FreeCAD compiled with PY3/Qt5 Ubuntu 20.04 LTS (XFCE/xubuntu)64B -> no crash when creating new document
    More details here: https://forum.freecadweb.org/viewtopic.php?f=8&t=39444&p=456568#p456568
    (0015367)
    Kunda1   
    2021-02-18 18:24   
    @-alex- anything still pending for this? Did downstream update their libs?
    (0016223)
    ShiftPlusOne   
    2022-01-18 12:46   
    (Last edited: 2022-01-18 13:17)
    I'm having trouble finding concrete information on what the issue is. Which libraries need to be updated? Since the issue hasn't been fixed in Raspbian, I'd like to push an update to Raspberry Pi OS to override it, but the linked threads don't seem to contain any viable solutions.
    (0016225)
    ShiftPlusOne   
    2022-01-19 08:24   
    I've confirmed the issue occurs in vanilla Debian as well and have sent another report there https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004007
    (0016807)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5973.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4831 [Path] Bug minor always 2022-01-16 15:57 2022-01-16 15:57
    Reporter: sliptonic Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Linux Mint 20 (i3/i3)
    Word size of FreeCAD: 64-bit
    Version: 0.20.27078 +6 (Git)
    Build type: Unknown
    Branch: feature/drill-refactor
    Hash: 9ca8e01771210cbcc6159629dc675cb43bd4053b
    Python version: 3.8.10
    Qt version: 5.12.8
    Coin version: 4.0.0
    OCC version: 7.5.2
    Locale: English/United States (en_US)
    Summary: Path Command parameters are not mutable.
    Description: The Path Command object is central to the path workbench. It contains all the axis words and parameters for a single line of pseudo gcode.
    However, the parameters are not mutable through the python interface. This often causes confusion, especially for new developers.

    Tags:
    Steps To Reproduce: >>> p = obj.Path.Commands[8]
    >>> p
    Command G3 [ F:0.8333 I:0 J:-2.5 K:0 X:-1.5 Y:76.038 Z:6 ]
    >>> p.toGCode()
    'G3 F0.833300 I0.000000 J-2.500000 K0.000000 X-1.500000 Y76.037957 Z6.000000'
    >>> p.Parameters['F'] = 200
    >>> p
    Command G3 [ F:0.8333 I:0 J:-2.5 K:0 X:-1.5 Y:76.038 Z:6 ]
    >>> p.Parameters
    {'F': 200, 'I': 0.0, 'J': -2.5, 'K': 0.0, 'X': -1.5, 'Y': 76.037957, 'Z': 6.0}
    >>> p.toGCode()
    'G3 F0.833300 I0.000000 J-2.500000 K0.000000 X-1.500000 Y76.037957 Z6.000000'
    >>> params = p.Parameters
    >>> params['F'] = 200
    >>> p.Parameters = params
    >>> p
    Command G3 [ F:200 I:0 J:-2.5 K:0 X:-1.5 Y:76.038 Z:6 ]
    >>> p.toGCode()
    'G3 F200.000000 I0.000000 J-2.500000 K0.000000 X-1.500000 Y76.037957 Z6.000000'
    >>>
    Additional Information: comment by iromero91 in pull request code review: https://github.com/FreeCAD/FreeCAD/pull/5229

    DOH, that's the problem with mutable properties in wrapped objects, seems to always be a 50/50 if they are going to work properly or not. I'm a bit tempted to call this a bug in the Path.Command object, you should be expected to modify a mutable property and have it, you know, change. The workaround using the temp variable should be ok but we should consider fixing the wrapping later. There are a few solutions I would deem more acceptable than what we got now there.

        Remove the property interface and use something like getParameters() and setParameters() instead. To make it clear that objects are passed by-copy and you cannot mutate them.
        Make Parameters return a proxy object so that mutating it actually does the changes expected.
        Make Parameters return an immutable object and have a function like setParameter() to be able to write to them
        Remove the extra indirection and implement the parameters dictionary on the command class itself via __getitem__ and __setitem__, that way you could do p["F"] = 200. Also possible to implement the rest of the basic dictionary interface with keys() and items()

    Attached Files:
    Notes
    (0017141)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6310.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4830 [TechDraw] Feature minor have not tried 2022-01-15 15:58 2022-01-15 15:58
    Reporter: wandererfan Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Linux Mint 20.3 (X-Cinnamon/cinnamon)
    Word size of FreeCAD: 64-bit
    Version: 0.20.
    Build type: Release
    Branch: unknown
    Hash: cd089a82c741c3725058df4a082d9a27fb857a71
    Python version: 3.8.10
    Qt version: 5.12.8
    Coin version: 4.0.0
    OCC version: 7.5.2
    Locale: English/United States (en_US)
    Summary: Add Advanced Section Views
    Description: Add half, broken out, offset, rotated and removed sections.

    Forum discussion.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0017140)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6309.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4128 [TechDraw] Feature minor have not tried 2019-09-13 11:49 2022-01-15 15:39
    Reporter: wandererfan Platform: all  
    Assigned To: wandererfan OS:  
    Priority: normal OS Version:  
    Status: feedback Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Allow Angled Section Views
    Description: Forum discussion

    Currently, the Section tool will only create sections in 4 directions (left, right, up, down). There are occasions where a Section at an angle (say 45*, left/down to right/up) to the Base view would be useful.
    Tags:
    Steps To Reproduce:
    Additional Information: There was a question about this in the German forum some time ago. German forum thread re angled Section
    Attached Files:
    Notes
    (0016215)
    wandererfan   
    2022-01-15 15:37   
    This can be accomplished by changing the Direction and SectionNormal properties of the SectionView after it is created.
    (0016216)
    wandererfan   
    2022-01-15 15:39   
    Is this request still valid given the ability to adjust the direction after creation?
    (0016822)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5988.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4818 [FreeCAD] Bug minor always 2022-01-04 04:57 2022-01-14 09:30
    Reporter: benjamin.morris.32 Platform: Windows  
    Assigned To: OS: Windows 11 home  
    Priority: normal OS Version: 21H2  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Windows 10 Version 2009
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24267 +99 (Git)
    Build type: Release
    Branch: Branch_0.19.3
    Hash: 6530e364184ce05ccff39501e175cf2237e6ee4b
    Python version: 3.8.6+
    Qt version: 5.15.2
    Coin version: 4.0.1
    OCC version: 7.5.3
    Locale: English/United States (en_US)
    Summary: Unable to open the help documents
    Description: I am unable to open the Help menu from the menu bar. It also seems that it is mixing forward and back slashes could also cause issues.
    Tags:
    Steps To Reproduce: Using the Default installation directory for Freecad for Windows "C:\Program Files\FreeCAD 0.19"
    To Reproduce:
    1. Open FreeCad
    2. Press F1
    Additional Information:
    Attached Files: Screenshot 2022-01-03 223527.png (8,189 bytes) 2022-01-04 04:57
    https://tracker.freecad.org/file_download.php?file_id=2747&type=bug
    Notes
    (0016203)
    sohxm7   
    2022-01-14 09:27   
    (Last edited: 2022-01-14 09:30)
    Hey the problem seems that FreeCAD needs to run as admin once so that it can create the files and dirs, related to your error message.

    Solution: Run FreeCAD with Admin privileges once.

    Windows:
    • Open Search
    • Type FreeCAD
    • Click on Run as administrator below FreeCAD name
    • Once loaded, close it, hopefully everything should now onward.

    Linux:
    • Open Terminal
    • Type sudo freecad
    • Once loaded, close it, hopefully everything should now onward.

    I tested this on Arch Linux and Windows 11.
    (0017133)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6302.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4828 [TechDraw] Feature minor have not tried 2022-01-13 14:52 2022-01-13 14:52
    Reporter: wandererfan Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Linux Mint 20.2 (X-Cinnamon/cinnamon)
    Word size of FreeCAD: 64-bit
    Version: 0.20.
    Build type: Release
    Branch: unknown
    Hash: dfa62af40f2955d73c6ff48ee73f238bce7d0db2
    Python version: 3.8.10
    Qt version: 5.12.8
    Coin version: 4.0.0
    OCC version: 7.5.2
    Locale: English/United States (en_US)
    Summary: Allow Entry of Section Origin Before Setting Section Normal
    Description: It is not possible to adjust the SectionOrigin until after SectionNormal is selected and the section view is created.

    This introduces a long wait on complex models.

    Forum discussion.
    Tags: TechDraw
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0017139)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6308.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4827 [TechDraw] Feature minor have not tried 2022-01-13 14:42 2022-01-13 14:42
    Reporter: wandererfan Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Linux Mint 20.2 (X-Cinnamon/cinnamon)
    Word size of FreeCAD: 64-bit
    Version: 0.20.
    Build type: Release
    Branch: unknown
    Hash: dfa62af40f2955d73c6ff48ee73f238bce7d0db2
    Python version: 3.8.10
    Qt version: 5.12.8
    Coin version: 4.0.0
    OCC version: 7.5.2
    Locale: English/United States (en_US)
    Summary: Show Section Line if Base View is a Section
    Description: If a section view is used as the base view of a new section, no section line is displayed. A section line should be displayed.

    Forum discussion.
    Tags: TechDraw
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0017138)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6307.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4780 [Draft] Bug minor always 2021-11-08 10:17 2022-01-12 14:58
    Reporter: joelmo Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Windows 10 Version 2009
    Word size of FreeCAD: 64-bit
    Version: 0.20.26155 (Git)
    Build type: Release
    Branch: master
    Hash: 0926a4148bcff11249fd4f56bc30256102ffe105
    Python version: 3.8.6+
    Qt version: 5.15.2
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: English/United Kingdom (en_GB)
    Summary: Rounding error when drawing in XZ plane
    Description: When I draw in XZ (front) plane I get that some points are placed on the Y axis at around ~0.3 nm. I'm guessing this is a rounding error. This does not happen when I draw in XY. When drawing in XZ, the Z field in the UI is the Y axis.
    Tags:
    Steps To Reproduce: Open draft. Create a line and move it around while watching X, Y, Z fields.
    Additional Information:
    Attached Files: image.png (7,860 bytes) 2021-11-08 10:17
    https://tracker.freecad.org/file_download.php?file_id=2731&type=bug
    Notes
    (0016202)
    marioalexis   
    2022-01-12 14:58   
    With https://github.com/FreeCAD/FreeCAD/pull/5307/commits/1cd01248e0fb42baace06ae7ff2475e6dd60c68d the precision on the projected points was increased to ~1e-14, so this rounding error should no longer be seen.
    (0017111)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6280.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4801 [Addon Manager] Feature minor have not tried 2021-12-11 21:41 2022-01-08 04:09
    Reporter: roipoussiere Platform:  
    Assigned To: chennes OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    Summary: addon manager: display addon version and last commit date
    Description: This is useful information, that can be used to quickly know if an add-on is still in development.

    It can be located for instance, just under the warning / info box above the add-on description.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016086)
    openBrain   
    2021-12-14 11:05   
    @roipoussiere : please proceed according our reporting guidelines by first discussing your request in our forum. Thx
    (0016092)
    roipoussiere   
    2021-12-14 17:02   
    suggestion message on the forum: https://forum.freecadweb.org/viewtopic.php?p=553702#p553702
    (0016101)
    chennes   
    2021-12-16 19:41   
    Addon Manager is in the process of being redesigned. I will eventually incorporate this suggestion into the display of whether an addon needs to be updated.
    (0016197)
    chennes   
    2022-01-08 04:09   
    Half of this is done (the display of version info), but displaying the last commit info is more complex. Discussion topic here: https://forum.freecadweb.org/viewtopic.php?f=8&t=65109
    (0017124)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6293.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4250 [Sketcher] Feature feature always 2020-01-16 19:09 2022-01-07 23:36
    Reporter: Pauvres_honteux Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: openSUSE Leap 15.1 (KDE//usr/share/xsessions/default)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.Unknown
    Build type: Release
    Python version: 3.6.5
    Qt version: 5.9.7
    Coin version: 4.0.0a
    OCC version: 7.4.1.dev
    Summary: Sketcher placement and its axis visualisation
    Description: Sketcher placement and its axis visualisation
    Tags:
    Steps To Reproduce:
    Additional Information: Extra information: when moving the plane and point the sketch is attached to, the sketch shall move with it. The same goes for its orientation.
    Attached Files:
    Notes
    (0015700)
    Pauvres_honteux   
    2021-06-06 06:10   
    More people wants this, albeit expressed differently:

    Datum plane orientation request
    Feature Request: show orientation in attachment dialog
    (0015701)
    Pauvres_honteux   
    2021-06-06 06:18   
    @Kunda1: Any chance you can change this issue's "project" to Sketcher?
    (0015703)
    Kunda1   
    2021-06-06 13:05   
    @Pauvres_honteux done
    (0016196)
    adrianinsaval   
    2022-01-07 23:36   
    I propose to close this one in favor of 0004821
    (0016859)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6025.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4821 [Sketcher] Feature feature always 2022-01-07 22:26 2022-01-07 22:35
    Reporter: chrisb Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: FC 0.20
    Summary: Offer full Placement dialog when creating a sketch
    Description: When creating a new sketch it should be possible to see the full attachment dialog. The current procedure is laborious.
    The corresponding forum discussion discusses als a configurable option
    for the currently implemented simpler workflow.

    The implementation could be similar to realthunder's branch with the additional goody of showing a local coordinate system, so that the user can see where the sketch is placed and how it is oriented.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0017136)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6305.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4819 [FreeCAD] Feature feature always 2022-01-05 16:06 2022-01-05 16:06
    Reporter: Pauvres_honteux Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: N/A
    Summary: Zoom tree with mouse
    Description: See forum Zoom tree with mouse
    Tags: tree view
    Steps To Reproduce: N/A
    Additional Information: N/A
    Attached Files:
    Notes
    (0017134)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6303.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3963 [FreeCAD] Bug major always 2019-05-08 22:31 2022-01-03 11:23
    Reporter: openBrain Platform:  
    Assigned To: openBrain OS:  
    Priority: normal OS Version:  
    Status: resolved Product Version: 0.18  
    Product Build: Resolution: fixed  
    Projection: none      
    ETA: none Fixed in Version: 0.20  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Only alpha comma key can be used as decimal separator
    Description: On some values in the Property editor panel, only the alpha comma key is accepted as decimal separator.
    This is suboptimal (mainly compared to num dot key) when entering numbers
    OS: Linux Mint 19.1
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16093 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-18
    Hash: 690774c0effe4fd7b8d2b5e2fb2b8c8d145e21ce
    Python version: 2.7.15rc1
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: French/France (fr_FR)
    Tags: 0.18, input, keyboard, units
    Steps To Reproduce: Edit a value directly in the property editing panel.
    Some will indifferently accept comma or dot (alpha comma, alpha dot, num dot) - eg Placement Angle - and some will enforce user to use alpha comma - eg Placement x Axis -.
    Additional Information: Linked forum thread

    AFAIK, no FC forumer natively using dot sign as decimal separator (eg en_US) has confirmed or not the bug. Only users using comma as decimal separator did.
    Proposed fix in the forum discussion :
    • Numpad dot key is always accepted as decimal separator
    • User options to enforce FC to specifically accept alpha dot and/or alpha comma as decimal separator
    Attached Files:
    Notes
    (0014276)
    openBrain   
    2020-03-24 12:09   
    https://github.com/FreeCAD/FreeCAD/pull/3256
    (0014277)
    openBrain   
    2020-03-24 12:40   
    For specific case of TechDraw in the forum discussion, UI files have to be updated to use 'Gui::DoubleSpinBox' instead of 'QDoubleSpinBox'
    (0014279)
    uwestoehr   
    2020-03-24 13:25   
    Duplicate of 0003795
    (0014280)
    uwestoehr   
    2020-03-24 13:26   
    Duplicate of 0003795
    (0014281)
    openBrain   
    2020-03-24 13:57   
    Not duplicate. Related to.
    (0016160)
    chennes   
    2021-12-29 05:15   
    I know there has been some work in this direction recently: where does this bug report stand @openBrain and @uwestoehr?
    (0016182)
    openBrain   
    2022-01-03 08:51   
    @chennes : to me the problem as described in this ticket is indeed solved. I had no complaints about the fix till now, so I guess we can close.
    (0016187)
    uwestoehr   
    2022-01-03 11:23   
    Fixed in FC 0.20dev but cannot be backported to FC 0.19 -> marking the bug fixed but keep it open to be transferred to GitHub as reference for 0.19 users.
    (0016762)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5928.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4803 [Spreadsheet] Bug minor have not tried 2021-12-11 23:08 2021-12-30 03:55
    Reporter: roipoussiere Platform: Linux  
    Assigned To: chennes OS: Kubuntu  
    Priority: normal OS Version: 20.04  
    Status: resolved Product Version: 0.19  
    Product Build: Resolution: fixed  
    Projection: none      
    ETA: none Fixed in Version: 0.20  
        Target Version:  
    Summary: spreadsheet: the alias content is not visible (black on black)
    Description: The "content" textbox content is displayed with white color, but the "alias" textbox content is displayed with black color, so it's not really visible. See image attached.

    I use a dark theme on my system btw.
    Tags:
    Steps To Reproduce:
    Additional Information: OS: Ubuntu 20.04.3 LTS (KDE/plasma)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24291 (Git) AppImage
    Build type: Release
    Branch: (HEAD detached at 0.19.2)
    Hash: 7b5e18a0759de778b74d3a5c17eba9cb815035ac
    Python version: 3.8.8
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: French/France (fr_FR)
    Attached Files: image.png (10,285 bytes) 2021-12-11 23:08
    https://tracker.freecad.org/file_download.php?file_id=2736&type=bug
    Notes
    (0016135)
    chennes   
    2021-12-29 03:12   
    This is happening because a QPalette is being used to set the text color to either "red" in the case of an error, or "black" in the case of no error. Obviously "black" should be replaced by "the original color".
    (0016170)
    chennes   
    2021-12-30 03:55   
    This is fixed by commit 4098c8817.
    (0017125)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6294.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3713 [Part] Feature feature always 2018-12-03 14:20 2021-12-29 05:35
    Reporter: paullee Platform: All  
    Assigned To: OS: All  
    Priority: normal OS Version: n/a  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Sweep Missing Path / Spine in Dialog or Properties
    Description: Discussion in forum Sweep Missing Path / Spine in Dialog or Properties:-

    "...want to edit a sweep object.

    In the property dialog, there is 'Sections' to change, but there is none for the ''path' or 'spine'. Double-click it return a translation dialog only.

    Need to access through python sweep.spine attribute."
    1. It would be good if the property tab has the Spine attribute to edti.
    2. Even better is something like Curve WB's intuitive and interactive dialog could be included
    Tags:
    Steps To Reproduce: See above copy of forum discussion.
    Additional Information:
    Attached Files:
    Notes
    (0012235)
    paullee   
    2018-12-03 14:23   
    See more discussion and suggestion here
    (0016167)
    chennes   
    2021-12-29 05:35   
    @uwestoehr this sounds like something you've worked on during the 0.20 dev cycle. Can you comment on the status of this report?
    (0016677)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5842.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3923 [FreeCAD] Feature minor N/A 2019-04-02 11:05 2021-12-29 05:20
    Reporter: berndhahnebach Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: TreeView widget, reorder the object in tree view by user
    Description: See https://forum.freecadweb.org/viewtopic.php?f=3&t=35316
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0012989)
    Kunda1   
    2019-04-03 14:56   
    @berndhahnebach in the title of this ticket, do you mean s/widged/widget/ ?
    (0015526)
    Kunda1   
    2021-03-16 21:09   
    FreeCAD Pull Request 4626
    (0016162)
    chennes   
    2021-12-29 05:20   
    Just a note that PR 4626 was merged and then reverted due to some severe problems. This is a challenging issue, and will require further work to resolve.
    (0016742)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5907.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3935 [Sketcher] Feature feature N/A 2019-04-16 16:38 2021-12-29 05:17
    Reporter: abdullah Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Improved Sketcher Messages
    Description: a) Informing (solver messages):

    Unconstrained sketch with 1 DoF / Fully Constrained sketch (As today)
    Some constraints are partially redundant (in blue, for information)
    Solved in 0.5 seconds (As today)

    b) In the constraints list "mark" somehow those constraints which are partially redundant.

    https://forum.freecadweb.org/viewtopic.php?p=301281#p301231
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016161)
    chennes   
    2021-12-29 05:17   
    I believe that the first part of this feature request is resolved now, still leaving the second part (marking the partially-redundant constraints).
    (0016749)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5915.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4041 [FreeCAD] Bug minor always 2019-06-28 12:52 2021-12-29 05:12
    Reporter: leong Platform:  
    Assigned To: OS: Linux  
    Priority: normal OS Version: Mageia 6  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Navigation cube hardcoded to use Helvetica
    Description: in the latest 17147 and in the build before it the navigation cube has lost its lettering.
    Tags: #lowhangingfruit
    Steps To Reproduce: Happens everytime I open FreeCAD
    Additional Information: OS: Mageia 6 (KDE//usr/share/xsessions/01plasma)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.17147 (Git) AppImage
    Build type: Release
    Branch: master
    Hash: 251a3b1ff5517d929b4993d8836e17e01ae2623c
    Python version: 3.7.3
    Qt version: 5.9.7
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    Attached Files: freeCAD0191747.png (30,201 bytes) 2019-06-28 12:52
    https://tracker.freecad.org/file_download.php?file_id=2251&type=bug
    Notes
    (0013322)
    openBrain   
    2019-06-30 14:28   
    @leong as suggested by tag, could you please open a topic in the "Help on using FreeCAD" subforum ?
    The ticket is vague and a community discussion will probably allow to narrow down the possible cause(s). ;)
    Thanks
    (0013323)
    leong   
    2019-06-30 17:25   
    OK. It appears this may be an issue with my system and some font change, but I cannot find it. Will do as you suggest/
    (0013324)
    Kunda1   
    2019-07-01 01:00   
    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=3&t=37401
    (0013325)
    jmaustpc   
    2019-07-01 01:12   
    It works perfectly here in both PPA versions. I have a 10 year old laptop with an Nvidea GPU with open source drivers. We saw that "save picture" was not working with a combination of some QT versions and Intel GPU/Driver .... I wonder if this is also related to the QT version and Intel GPU/Driver?


    OS: Ubuntu 18.04.2 LTS (KDE/plasma)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.
    Build type: Release
    Python version: 3.6.8
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/Australia (en_AU)


    OS: Ubuntu 18.04.2 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.1.
    Build type: Release
    Python version: 3.6.7
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/Australia (en_AU)
    (0013408)
    leong   
    2019-08-09 11:37   
    (Last edited: 2019-08-09 11:38)
    I posted answer on forum FreeCAD forum
    Basically the navigation cube uses Helvetica font and it is not on my system. Had to add it.
    Maybe the code should specify another font? that would fix the issue.

    (0016159)
    chennes   
    2021-12-29 05:12   
    I've changed the title of the issue to reflect the actual bug here: we assume Helvetica is available on all systems, to be used as a Sans Serif font, but that is not a good assumption.
    (0016793)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5959.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4210 [Arch] Bug minor have not tried 2019-12-03 08:21 2021-12-29 04:47
    Reporter: michaelberg Platform: Surface Book 2  
    Assigned To: yorik OS: Windows 10  
    Priority: normal OS Version: 10.0.18363  
    Status: confirmed Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 10
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.4 (GitTag)
    Build type: Release
    Branch: releases/FreeCAD-0-18
    Hash: 980bf9060e28555fecd9e3462f68ca74007b70f8
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: German/Germany (de_DE)
    Summary: Impossible to export a PartDesign Body
    Description: Hi,

    I created a part design project. This project contains 9 bodies. I tried to export all bodies as wavefront obj. But there is no possiblitiy to export the first body. If i do a single export the result is a empty obj file. There are no errors. My current workaround is to clone the body and export the new body. I cant find any differences within the body data.

    Python Console output:

    >>< __objs__=[]
    >>> __objs__.append(FreeCAD.getDocument("LadenRegal").getObject("Body"))
    >>> __objs__.append(FreeCAD.getDocument("LadenRegal").getObject("Body002"))
    >>> __objs__.append(FreeCAD.getDocument("LadenRegal").getObject("Body003"))
    >>> __objs__.append(FreeCAD.getDocument("LadenRegal").getObject("Body006"))
    >>> __objs__.append(FreeCAD.getDocument("LadenRegal").getObject("Body004"))
    >>> __objs__.append(FreeCAD.getDocument("LadenRegal").getObject("Body005"))
    >>> __objs__.append(FreeCAD.getDocument("LadenRegal").getObject("Body001"))
    >>> __objs__.append(FreeCAD.getDocument("LadenRegal").getObject("Body008"))
    >>> __objs__.append(FreeCAD.getDocument("LadenRegal").getObject("Body007"))
    >>> import importOBJ
    >>> importOBJ.export(__objs__,u"C:/Users/micha/Nextcloud/Documents/Freecad/Regal.obj")
    >>>
    >>> del __objs__
    >>>

    The 'Body' object is actually not exported.

    Ausgabefenster:
    Form mit Kurven gefunden, Trianguliere (annäherung mittels Geraden)
    Form mit Kurven gefunden, Trianguliere (annäherung mittels Geraden)
    Form mit Kurven gefunden, Trianguliere (annäherung mittels Geraden)
    Form mit Kurven gefunden, Trianguliere (annäherung mittels Geraden)
    Form mit Kurven gefunden, Trianguliere (annäherung mittels Geraden)
    Form mit Kurven gefunden, Trianguliere (annäherung mittels Geraden)
    Form mit Kurven gefunden, Trianguliere (annäherung mittels Geraden)
    Form mit Kurven gefunden, Trianguliere (annäherung mittels Geraden)
    Erfolgreich geschrieben C:/Users/micha/Nextcloud/Documents/Freecad/Regal.obj
    Erfolgreich geschrieben C:/Users/micha/Nextcloud/Documents/Freecad/Regal.mtl
    Tags:
    Steps To Reproduce:
    • Open attached file
    • Export 'SeitenwandLinks' as Wavefront obj.
    • Open th exported file.
    • There is nothing in the file.
    Additional Information: Link to forum discussion
    Attached Files: LadenRegal.FCStd (70,686 bytes) 2019-12-03 08:21
    https://tracker.freecad.org/file_download.php?file_id=2393&type=bug
    Thekenschrank.FCStd (105,765 bytes) 2019-12-04 12:29
    https://tracker.freecad.org/file_download.php?file_id=2394&type=bug
    Notes
    (0013861)
    michaelberg   
    2019-12-04 12:29   
    2th project, next problem. this time the "Deckel" cant be exported.
    (0013864)
    openBrain   
    2019-12-05 12:33   
    @michaelberg : thanks for reporting. However per our guidelines (big yellow box on top of the page), could you please first open a topic in our forum so issue can be discussed, confirmed and identified by the community ?
    Also notice that ticket here shall only be filled in English.
    A ticket is quite well filled in, I'll set it on hold till the discussion on forum is over. Thanks
    (0016847)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6013.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4269 [FreeCAD] Feature minor always 2020-02-18 15:55 2021-12-29 04:39
    Reporter: wucke13 Platform:  
    Assigned To: chennes OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: NixOS 19.09.1977.1dadefec574 (Loris)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.Unknown
    Build type: Release
    Python version: 3.7.5
    Qt version: 5.12.3
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/United States (en_US)
    Summary: Allow user specified line thickness for SVG export
    Description: Some lasercutters present themselves as printers. In order to cut something, the one has to send a PDF/SVG as print job to the cutter. The thickness of lines determines whether something is cut or engraved. Our current workflow includes exporting an SVG from our CAD model in FreeCAD, and then modifying this model in Inkscape to adjust the thickness of all cut-lines to the desired value for cutting and the thickness of all other lines to a distinct thickness. This is tedious and error prone. It would greatly improve said workflow if FreeCAD lets one specify the desired thickness for the lines in the exported SVG. Even better would be, if the user can choose different thicknesses for both the cutted and not cutted lines.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0014164)
    wandererfan   
    2020-02-20 15:06   
    I can think of at least 3 different SVG exports (DrawingWB, Flattened SVG from 3D and TechDrawWB.

    Was there one in particular that causes your issue?
    (0014167)
    wucke13   
    2020-02-20 19:37   
    I've used the GUI. First I marked the flattened 2D geometry, then I used the File -> Export (or CTRL + E) dialog to export as a Flattened SVG.
    (0014168)
    Kunda1   
    2020-02-20 21:01   
    Ticket is missing a forum thread. Please follow the FreeCAD tracker guidelines (yellow banner top of page)next time before opening a ticket.
    (0015075)
    Kunda1   
    2020-12-04 04:15   
    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=52876
    (0016868)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6034.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4520 [FreeCAD] Bug minor always 2020-12-24 14:03 2021-12-29 04:02
    Reporter: DrC Platform: HP laptop  
    Assigned To: chennes OS: Windows 10  
    Priority: normal OS Version:  
    Status: feedback Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 10 (10.0)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.23141 (Git)
    Build type: Release
    Branch: master
    Hash: 0eba78d40096720f7a637a9a73c382a08b820bca
    Python version: 3.8.6
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: English/United Kingdom (en_GB)
    Summary: Doubleclick when drawing a polygon seems to results in an unresolvable double point.
    Description: When drawing a polygon to complete a closed shape that starts with an arc:

    1. A gratuitous tangent is added in some circumstances. This is minor and easily deleted. I plan to open a new bug on this later.

    2. A double click (a previous way of terminating a polygon) resulted in an intractable double point, possibly because it inadvertently coincided with a construction line. I have prioritised reporting it over finding out how to deal with it as I suspect I will have to redo a chunk of drawing and forget how it happened!

    13:12:25 Updating geometry: Error build geometry(8): Both points are equal
    13:12:25 Invalid solution from DogLeg solver.
    13:12:26 Updating geometry: Error build geometry(8): Both points are equal
    13:12:26 Invalid solution from DogLeg solver.
    13:12:41 Delete: Selection not restricted to one sketch and its subelementsDelete: Selection not restricted to one sketch and its subelementsDelete: Selection not restricted to one sketch and its subelementsDelete: Selection not restricted to one sketch and its subelementsDelete: Selection not restricted to one sketch and its subelements


    Tags: #post-to-forum, 0.19, Poly-line, UI
    Steps To Reproduce: The attached part is to become a split cable bush. So far it is a pair of hinged semicircular cylinders with a reduced diameter section added at one end. The next step is to add a rim at the original diameter with cut-outs for lugs on the parent body to enter the groove left by the reduced diameter. It will be installed by push and twist.

    For the time being it is a solid plug. The cableway will come later.

    The rim design starts with two arcs at the full size, but they do not come down to the base line. They stop 2mm above at the construction line. The task now to is to add four straight sides to each arc making two closed shapes. The bottom edge would be on the base line, the connections to the arc are to be at 45 degrees to facilitate 3D printing.

    Select the polygon tool, start at one end of one of the arcs and try to draw it. The tangent appears. Draw a polygon in the other direction to edit later and stop by double clicking accidentally on the construction line.
    Additional Information: 12:23:06 Delete: Selection not restricted to one sketch and its subelementsTraceback (most recent call last):
      File "<string>", line 1, in <module>
    <class 'ValueError'>: Datum 17.50 mm for the constraint with index 11 is invalid
    12:35:35 App.getDocument('Unnamed').getObject('Sketch002').setDatum(11,App.Units.Quantity('17.500000 mm'))
    12:36:08 Traceback (most recent call last):
      File "<string>", line 1, in <module>
    <class 'ValueError'>: Datum 11.91 mm for the constraint with index 11 is invalid
    12:36:08 App.getDocument('Unnamed').getObject('Sketch002').setDatum(11,App.Units.Quantity('11.910000 mm'))
    12:41:39 Delete: Selection not restricted to one sketch and its subelementsDelete: Selection not restricted to one sketch and its subelementsUpdating geometry: Error build geometry(9): Both points are equal
    13:04:47 Invalid solution from DogLeg solver.
    13:04:47 Updating geometry: Error build geometry(9): Both points are equal
    13:04:47 Invalid solution from LevenbergMarquardt solver.
    13:05:01 Updating geometry: Error build geometry(9): Both points are equal
    13:05:01 Invalid solution from DogLeg solver.
    13:05:01 Updating geometry: Error build geometry(9): Both points are equal
    13:05:01 Invalid solution from DogLeg solver.
    13:05:01 Updating geometry: Error build geometry(9): Both points are equal
    13:05:01 Invalid solution from DogLeg solver.
    13:05:01 Updating geometry: Error build geometry(9): Both points are equal
    13:05:01 Invalid solution from DogLeg solver.
    13:05:01 Updating geometry: Error build geometry(9): Both points are equal
    13:05:01 Invalid solution from DogLeg solver.
    13:05:01 Updating geometry: Error build geometry(9): Both points are equal
    13:05:01 Invalid solution from DogLeg solver.
    13:05:01 Updating geometry: Error build geometry(9): Both points are equal
    13:05:01 Invalid solution from DogLeg solver.
    13:05:01 Updating geometry: Error build geometry(9): Both points are equal
    13:05:01 Invalid solution from DogLeg solver.
    13:05:01 Updating geometry: Error build geometry(9): Both points are equal
    13:05:01 Invalid solution from DogLeg solver.
    13:05:01 Updating geometry: Error build geometry(9): Both points are equal
    13:05:01 Invalid solution from DogLeg solver.
    13:05:03 Updating geometry: Error build geometry(9): Both points are equal
    13:05:03 Invalid solution from DogLeg solver.
    13:05:11 Updating geometry: Error build geometry(9): Both points are equal
    13:05:11 Invalid solution from DogLeg solver.
    13:05:11 Updating geometry: Error build geometry(9): Both points are equal
    13:05:11 Invalid solution from DogLeg solver.
    13:05:11 Updating geometry: Error build geometry(9): Both points are equal
    13:05:11 Invalid solution from DogLeg solver.
    13:05:11 Updating geometry: Error build geometry(9): Both points are equal
    13:05:11 Invalid solution from DogLeg solver.
    13:05:11 Updating geometry: Error build geometry(9): Both points are equal
    13:05:11 Invalid solution from DogLeg solver.
    13:05:11 Updating geometry: Error build geometry(9): Both points are equal
    13:05:11 Invalid solution from DogLeg solver.
    13:05:11 Updating geometry: Error build geometry(9): Both points are equal
    13:05:11 Invalid solution from DogLeg solver.
    13:05:11 Updating geometry: Error build geometry(9): Both points are equal
    13:05:11 Invalid solution from DogLeg solver.
    13:05:11 Updating geometry: Error build geometry(9): Both points are equal
    13:05:11 Invalid solution from DogLeg solver.
    13:05:11 Updating geometry: Error build geometry(9): Both points are equal
    13:05:11 Invalid solution from DogLeg solver.
    13:05:11 Updating geometry: Error build geometry(9): Both points are equal
    13:05:11 Invalid solution from DogLeg solver.
    13:05:11 Updating geometry: Error build geometry(9): Both points are equal
    13:05:11 Invalid solution from DogLeg solver.
    13:05:11 Updating geometry: Error build geometry(9): Both points are equal
    13:05:11 Invalid solution from DogLeg solver.
    13:05:11 Updating geometry: Error build geometry(9): Both points are equal
    13:05:11 Invalid solution from DogLeg solver.
    13:05:11 Updating geometry: Error build geometry(9): Both points are equal
    13:05:11 Invalid solution from DogLeg solver.
    13:05:11 Updating geometry: Error build geometry(9): Both points are equal
    13:05:11 Invalid solution from DogLeg solver.
    13:05:11 Updating geometry: Error build geometry(9): Both points are equal
    13:05:11 Invalid solution from DogLeg solver.
    13:05:11 Updating geometry: Error build geometry(9): Both points are equal
    13:05:11 Invalid solution from DogLeg solver.
    13:05:11 Updating geometry: Error build geometry(9): Both points are equal
    13:05:11 Invalid solution from DogLeg solver.
    13:05:11 Updating geometry: Error build geometry(9): Both points are equal
    13:05:11 Invalid solution from DogLeg solver.
    13:05:12 Updating geometry: Error build geometry(9): Both points are equal
    13:05:12 Invalid solution from DogLeg solver.
    13:05:12 Updating geometry: Error build geometry(9): Both points are equal
    13:05:12 Invalid solution from DogLeg solver.
    13:05:12 Updating geometry: Error build geometry(9): Both points are equal
    13:05:12 Invalid solution from DogLeg solver.
    13:05:12 Updating geometry: Error build geometry(9): Both points are equal
    13:05:12 Invalid solution from DogLeg solver.
    13:05:12 Updating geometry: Error build geometry(9): Both points are equal
    13:05:12 Invalid solution from DogLeg solver.
    13:05:12 Updating geometry: Error build geometry(9): Both points are equal
    13:05:12 Invalid solution from DogLeg solver.
    13:05:12 Updating geometry: Error build geometry(9): Both points are equal
    13:05:12 Invalid solution from DogLeg solver.
    13:05:12 Updating geometry: Error build geometry(9): Both points are equal
    13:05:12 Invalid solution from DogLeg solver.
    13:05:12 Updating geometry: Error build geometry(9): Both points are equal
    13:05:12 Invalid solution from DogLeg solver.
    13:05:12 Updating geometry: Error build geometry(9): Both points are equal
    13:05:12 Invalid solution from DogLeg solver.
    13:05:12 Updating geometry: Error build geometry(9): Both points are equal
    13:05:12 Invalid solution from DogLeg solver.
    13:05:12 Updating geometry: Error build geometry(9): Both points are equal
    13:05:12 Invalid solution from DogLeg solver.
    13:05:12 Updating geometry: Error build geometry(9): Both points are equal
    13:05:12 Invalid solution from DogLeg solver.
    13:05:12 Updating geometry: Error build geometry(9): Both points are equal
    13:05:12 Invalid solution from DogLeg solver.
    13:05:12 Updating geometry: Error build geometry(9): Both points are equal
    13:05:12 Invalid solution from DogLeg solver.
    13:05:12 Updating geometry: Error build geometry(9): Both points are equal
    13:05:12 Invalid solution from DogLeg solver.
    13:05:12 Updating geometry: Error build geometry(9): Both points are equal
    13:05:12 Invalid solution from DogLeg solver.
    13:05:12 Updating geometry: Error build geometry(9): Both points are equal
    13:05:12 Invalid solution from DogLeg solver.
    13:05:12 Updating geometry: Error build geometry(9): Both points are equal
    13:05:12 Invalid solution from DogLeg solver.
    13:05:12 Updating geometry: Error build geometry(9): Both points are equal
    13:05:12 Invalid solution from DogLeg solver.
    13:05:12 Updating geometry: Error build geometry(9): Both points are equal
    13:05:12 Invalid solution from DogLeg solver.
    13:05:12 Updating geometry: Error build geometry(9): Both points are equal
    13:05:12 Invalid solution from DogLeg solver.
    13:05:12 Updating geometry: Error build geometry(9): Both points are equal
    13:05:12 Invalid solution from DogLeg solver.
    13:05:13 Updating geometry: Error build geometry(9): Both points are equal
    13:05:13 Invalid solution from DogLeg solver.
    13:05:13 Updating geometry: Error build geometry(9): Both points are equal
    13:05:13 Invalid solution from DogLeg solver.
    13:05:13 Updating geometry: Error build geometry(9): Both points are equal
    13:05:13 Invalid solution from DogLeg solver.
    13:05:13 Updating geometry: Error build geometry(9): Both points are equal
    13:05:13 Invalid solution from DogLeg solver.
    13:05:13 Updating geometry: Error build geometry(9): Both points are equal
    13:05:13 Invalid solution from DogLeg solver.
    13:05:13 Updating geometry: Error build geometry(9): Both points are equal
    13:05:13 Invalid solution from DogLeg solver.
    13:05:13 Updating geometry: Error build geometry(9): Both points are equal
    13:05:13 Invalid solution from DogLeg solver.
    13:05:13 Updating geometry: Error build geometry(9): Both points are equal
    13:05:13 Invalid solution from DogLeg solver.
    13:05:13 Updating geometry: Error build geometry(9): Both points are equal
    13:05:13 Invalid solution from DogLeg solver.
    13:05:13 Updating geometry: Error build geometry(9): Both points are equal
    13:05:13 Invalid solution from DogLeg solver.
    13:05:13 Updating geometry: Error build geometry(9): Both points are equal
    13:05:13 Invalid solution from DogLeg solver.
    13:05:13 Updating geometry: Error build geometry(9): Both points are equal
    13:05:13 Invalid solution from DogLeg solver.
    13:05:13 Updating geometry: Error build geometry(9): Both points are equal
    13:05:13 Invalid solution from DogLeg solver.
    13:05:13 Updating geometry: Error build geometry(9): Both points are equal
    13:05:13 Invalid solution from DogLeg solver.
    13:05:13 Updating geometry: Error build geometry(9): Both points are equal
    13:05:13 Invalid solution from DogLeg solver.
    13:05:13 Updating geometry: Error build geometry(9): Both points are equal
    13:05:13 Invalid solution from DogLeg solver.
    13:05:13 Updating geometry: Error build geometry(9): Both points are equal
    13:05:13 Invalid solution from DogLeg solver.
    13:05:13 Updating geometry: Error build geometry(9): Both points are equal
    13:05:13 Invalid solution from DogLeg solver.
    13:05:13 Updating geometry: Error build geometry(9): Both points are equal
    13:05:13 Invalid solution from DogLeg solver.
    13:05:13 Updating geometry: Error build geometry(9): Both points are equal
    13:05:13 Invalid solution from DogLeg solver.
    13:05:13 Updating geometry: Error build geometry(9): Both points are equal
    13:05:13 Invalid solution from DogLeg solver.
    13:11:20 Updating geometry: Error build geometry(9): Both points are equal
    13:11:20 Invalid solution from DogLeg solver.
    13:11:20 Updating geometry: Error build geometry(9): Both points are equal
    13:11:20 Invalid solution from DogLeg solver.
    13:11:20 Updating geometry: Error build geometry(9): Both points are equal
    13:11:20 Invalid solution from DogLeg solver.
    13:11:21 Updating geometry: Error build geometry(9): Both points are equal
    13:11:21 Invalid solution from DogLeg solver.
    13:11:21 Updating geometry: Error build geometry(9): Both points are equal
    13:11:21 Invalid solution from DogLeg solver.
    13:11:21 Updating geometry: Error build geometry(9): Both points are equal
    13:11:21 Invalid solution from DogLeg solver.
    13:11:21 Updating geometry: Error build geometry(9): Both points are equal
    13:11:21 Invalid solution from DogLeg solver.
    13:11:22 Updating geometry: Error build geometry(9): Both points are equal
    13:11:22 Invalid solution from DogLeg solver.
    13:12:03 Updating geometry: Error build geometry(8): Both points are equal
    13:12:03 Invalid solution from DogLeg solver.
    13:12:03 Updating geometry: Error build geometry(8): Both points are equal
    13:12:03 Invalid solution from DogLeg solver.
    13:12:03 Updating geometry: Error build geometry(8): Both points are equal
    13:12:03 Invalid solution from DogLeg solver.
    13:12:03 Updating geometry: Error build geometry(8): Both points are equal
    13:12:03 Invalid solution from DogLeg solver.
    13:12:03 Updating geometry: Error build geometry(8): Both points are equal
    13:12:03 Invalid solution from DogLeg solver.
    13:12:03 Updating geometry: Error build geometry(8): Both points are equal
    13:12:03 Invalid solution from DogLeg solver.
    13:12:03 Updating geometry: Error build geometry(8): Both points are equal
    13:12:03 Invalid solution from DogLeg solver.
    13:12:04 Updating geometry: Error build geometry(8): Both points are equal
    13:12:04 Invalid solution from DogLeg solver.
    13:12:04 Updating geometry: Error build geometry(8): Both points are equal
    13:12:04 Invalid solution from DogLeg solver.
    13:12:04 Updating geometry: Error build geometry(8): Both points are equal
    13:12:04 Invalid solution from DogLeg solver.
    13:12:04 Updating geometry: Error build geometry(8): Both points are equal
    13:12:04 Invalid solution from DogLeg solver.
    13:12:04 Updating geometry: Error build geometry(8): Both points are equal
    13:12:04 Invalid solution from DogLeg solver.
    13:12:04 Updating geometry: Error build geometry(8): Both points are equal
    13:12:04 Invalid solution from DogLeg solver.
    13:12:04 Updating geometry: Error build geometry(8): Both points are equal
    13:12:04 Invalid solution from DogLeg solver.
    13:12:04 Updating geometry: Error build geometry(8): Both points are equal
    13:12:04 Invalid solution from DogLeg solver.
    13:12:04 Updating geometry: Error build geometry(8): Both points are equal
    13:12:04 Invalid solution from DogLeg solver.
    13:12:04 Updating geometry: Error build geometry(8): Both points are equal
    13:12:04 Invalid solution from DogLeg solver.
    13:12:04 Updating geometry: Error build geometry(8): Both points are equal
    13:12:04 Invalid solution from DogLeg solver.
    13:12:04 Updating geometry: Error build geometry(8): Both points are equal
    13:12:04 Invalid solution from DogLeg solver.
    13:12:05 Updating geometry: Error build geometry(8): Both points are equal
    13:12:05 Invalid solution from DogLeg solver.
    13:12:05 Updating geometry: Error build geometry(8): Both points are equal
    13:12:05 Invalid solution from DogLeg solver.
    13:12:05 Updating geometry: Error build geometry(8): Both points are equal
    13:12:05 Invalid solution from DogLeg solver.
    13:12:05 Updating geometry: Error build geometry(8): Both points are equal
    13:12:05 Invalid solution from DogLeg solver.
    13:12:05 Updating geometry: Error build geometry(8): Both points are equal
    13:12:05 Invalid solution from DogLeg solver.
    13:12:05 Updating geometry: Error build geometry(8): Both points are equal
    13:12:05 Invalid solution from DogLeg solver.
    13:12:05 Updating geometry: Error build geometry(8): Both points are equal
    13:12:05 Invalid solution from DogLeg solver.
    13:12:05 Updating geometry: Error build geometry(8): Both points are equal
    13:12:05 Invalid solution from DogLeg solver.
    13:12:05 Updating geometry: Error build geometry(8): Both points are equal
    13:12:05 Invalid solution from DogLeg solver.
    13:12:05 Updating geometry: Error build geometry(8): Both points are equal
    13:12:05 Invalid solution from DogLeg solver.
    13:12:05 Updating geometry: Error build geometry(8): Both points are equal
    13:12:05 Invalid solution from DogLeg solver.
    13:12:05 Updating geometry: Error build geometry(8): Both points are equal
    13:12:05 Invalid solution from DogLeg solver.
    13:12:05 Updating geometry: Error build geometry(8): Both points are equal
    13:12:05 Invalid solution from DogLeg solver.
    13:12:05 Updating geometry: Error build geometry(8): Both points are equal
    13:12:05 Invalid solution from DogLeg solver.
    13:12:05 Updating geometry: Error build geometry(8): Both points are equal
    13:12:05 Invalid solution from DogLeg solver.
    13:12:05 Updating geometry: Error build geometry(8): Both points are equal
    13:12:05 Invalid solution from DogLeg solver.
    13:12:05 Updating geometry: Error build geometry(8): Both points are equal
    13:12:05 Invalid solution from DogLeg solver.
    13:12:05 Updating geometry: Error build geometry(8): Both points are equal
    13:12:05 Invalid solution from DogLeg solver.
    13:12:05 Updating geometry: Error build geometry(8): Both points are equal
    13:12:05 Invalid solution from DogLeg solver.
    13:12:05 Updating geometry: Error build geometry(8): Both points are equal
    13:12:05 Invalid solution from DogLeg solver.
    13:12:05 Updating geometry: Error build geometry(8): Both points are equal
    13:12:05 Invalid solution from DogLeg solver.
    13:12:06 Updating geometry: Error build geometry(8): Both points are equal
    13:12:06 Invalid solution from DogLeg solver.
    13:12:06 Updating geometry: Error build geometry(8): Both points are equal
    13:12:06 Invalid solution from DogLeg solver.
    13:12:06 Updating geometry: Error build geometry(8): Both points are equal
    13:12:06 Invalid solution from DogLeg solver.
    13:12:06 Updating geometry: Error build geometry(8): Both points are equal
    13:12:06 Invalid solution from DogLeg solver.
    13:12:06 Updating geometry: Error build geometry(8): Both points are equal
    13:12:06 Invalid solution from DogLeg solver.
    13:12:06 Updating geometry: Error build geometry(8): Both points are equal
    13:12:06 Invalid solution from DogLeg solver.
    13:12:06 Updating geometry: Error build geometry(8): Both points are equal
    13:12:06 Invalid solution from DogLeg solver.
    13:12:06 Updating geometry: Error build geometry(8): Both points are equal
    13:12:06 Invalid solution from DogLeg solver.
    13:12:06 Updating geometry: Error build geometry(8): Both points are equal
    13:12:06 Invalid solution from DogLeg solver.
    13:12:06 Updating geometry: Error build geometry(8): Both points are equal
    13:12:06 Invalid solution from DogLeg solver.
    13:12:06 Updating geometry: Error build geometry(8): Both points are equal
    13:12:06 Invalid solution from DogLeg solver.
    13:12:06 Updating geometry: Error build geometry(8): Both points are equal
    13:12:06 Invalid solution from DogLeg solver.
    13:12:06 Updating geometry: Error build geometry(8): Both points are equal
    13:12:06 Invalid solution from DogLeg solver.
    13:12:07 Updating geometry: Error build geometry(8): Both points are equal
    13:12:07 Invalid solution from DogLeg solver.
    13:12:22 Updating geometry: Error build geometry(8): Both points are equal
    13:12:22 Invalid solution from DogLeg solver.
    13:12:22 Updating geometry: Error build geometry(8): Both points are equal
    13:12:22 Invalid solution from DogLeg solver.
    13:12:22 Updating geometry: Error build geometry(8): Both points are equal
    13:12:22 Invalid solution from DogLeg solver.
    13:12:22 Updating geometry: Error build geometry(8): Both points are equal
    13:12:22 Invalid solution from DogLeg solver.
    13:12:22 Updating geometry: Error build geometry(8): Both points are equal
    13:12:22 Invalid solution from DogLeg solver.
    13:12:23 Updating geometry: Error build geometry(8): Both points are equal
    13:12:23 Invalid solution from DogLeg solver.
    13:12:23 Updating geometry: Error build geometry(8): Both points are equal
    13:12:23 Invalid solution from DogLeg solver.
    13:12:23 Updating geometry: Error build geometry(8): Both points are equal
    13:12:23 Invalid solution from DogLeg solver.
    13:12:23 Updating geometry: Error build geometry(8): Both points are equal
    13:12:23 Invalid solution from DogLeg solver.
    13:12:23 Updating geometry: Error build geometry(8): Both points are equal
    13:12:23 Invalid solution from DogLeg solver.
    13:12:23 Updating geometry: Error build geometry(8): Both points are equal
    13:12:23 Invalid solution from DogLeg solver.
    13:12:23 Updating geometry: Error build geometry(8): Both points are equal
    13:12:23 Invalid solution from DogLeg solver.
    13:12:23 Updating geometry: Error build geometry(8): Both points are equal
    13:12:23 Invalid solution from DogLeg solver.
    13:12:23 Updating geometry: Error build geometry(8): Both points are equal
    13:12:23 Invalid solution from DogLeg solver.
    13:12:23 Updating geometry: Error build geometry(8): Both points are equal
    13:12:23 Invalid solution from DogLeg solver.
    13:12:23 Updating geometry: Error build geometry(8): Both points are equal
    13:12:23 Invalid solution from DogLeg solver.
    13:12:23 Updating geometry: Error build geometry(8): Both points are equal
    13:12:23 Invalid solution from DogLeg solver.
    13:12:23 Updating geometry: Error build geometry(8): Both points are equal
    13:12:23 Invalid solution from DogLeg solver.
    13:12:23 Updating geometry: Error build geometry(8): Both points are equal
    13:12:23 Invalid solution from DogLeg solver.
    13:12:23 Updating geometry: Error build geometry(8): Both points are equal
    13:12:23 Invalid solution from DogLeg solver.
    13:12:23 Updating geometry: Error build geometry(8): Both points are equal
    13:12:23 Invalid solution from DogLeg solver.
    13:12:24 Updating geometry: Error build geometry(8): Both points are equal
    13:12:24 Invalid solution from DogLeg solver.
    13:12:24 Updating geometry: Error build geometry(8): Both points are equal
    13:12:24 Invalid solution from DogLeg solver.
    13:12:24 Updating geometry: Error build geometry(8): Both points are equal
    13:12:24 Invalid solution from DogLeg solver.
    13:12:24 Updating geometry: Error build geometry(8): Both points are equal
    13:12:24 Invalid solution from DogLeg solver.
    13:12:24 Updating geometry: Error build geometry(8): Both points are equal
    13:12:24 Invalid solution from DogLeg solver.
    13:12:24 Updating geometry: Error build geometry(8): Both points are equal
    13:12:24 Invalid solution from DogLeg solver.
    13:12:24 Updating geometry: Error build geometry(8): Both points are equal
    13:12:24 Invalid solution from DogLeg solver.
    13:12:24 Updating geometry: Error build geometry(8): Both points are equal
    13:12:24 Invalid solution from DogLeg solver.
    13:12:24 Updating geometry: Error build geometry(8): Both points are equal
    13:12:24 Invalid solution from DogLeg solver.
    13:12:24 Updating geometry: Error build geometry(8): Both points are equal
    13:12:24 Invalid solution from DogLeg solver.
    13:12:24 Updating geometry: Error build geometry(8): Both points are equal
    13:12:24 Invalid solution from DogLeg solver.
    13:12:24 Updating geometry: Error build geometry(8): Both points are equal
    13:12:24 Invalid solution from DogLeg solver.
    13:12:24 Updating geometry: Error build geometry(8): Both points are equal
    13:12:24 Invalid solution from DogLeg solver.
    13:12:24 Updating geometry: Error build geometry(8): Both points are equal
    13:12:24 Invalid solution from DogLeg solver.
    13:12:24 Updating geometry: Error build geometry(8): Both points are equal
    13:12:24 Invalid solution from DogLeg solver.
    13:12:24 Updating geometry: Error build geometry(8): Both points are equal
    13:12:24 Invalid solution from DogLeg solver.
    13:12:24 Updating geometry: Error build geometry(8): Both points are equal
    13:12:24 Invalid solution from DogLeg solver.
    13:12:24 Updating geometry: Error build geometry(8): Both points are equal
    13:12:24 Invalid solution from DogLeg solver.
    13:12:24 Updating geometry: Error build geometry(8): Both points are equal
    13:12:24 Invalid solution from DogLeg solver.
    13:12:24 Updating geometry: Error build geometry(8): Both points are equal
    13:12:24 Invalid solution from DogLeg solver.
    13:12:24 Updating geometry: Error build geometry(8): Both points are equal
    13:12:24 Invalid solution from DogLeg solver.
    13:12:25 Updating geometry: Error build geometry(8): Both points are equal
    13:12:25 Invalid solution from DogLeg solver.
    13:12:25 Updating geometry: Error build geometry(8): Both points are equal
    13:12:25 Invalid solution from DogLeg solver.
    13:12:25 Updating geometry: Error build geometry(8): Both points are equal
    13:12:25 Invalid solution from DogLeg solver.
    13:12:25 Updating geometry: Error build geometry(8): Both points are equal
    13:12:25 Invalid solution from DogLeg solver.
    13:12:25 Updating geometry: Error build geometry(8): Both points are equal
    13:12:25 Invalid solution from DogLeg solver.
    13:12:25 Updating geometry: Error build geometry(8): Both points are equal
    13:12:25 Invalid solution from DogLeg solver.
    13:12:26 Updating geometry: Error build geometry(8): Both points are equal
    13:12:26 Invalid solution from DogLeg solver.
    13:12:41 Delete: Selection not restricted to one sketch and its subelementsDelete: Selection not restricted to one sketch and its subelementsDelete: Selection not restricted to one sketch and its subelementsDelete: Selection not restricted to one sketch and its subelementsDelete: Selection not restricted to one sketch and its subelements
    Attached Files: Bug-in-Lock-inHangingBush.FCStd (40,774 bytes) 2020-12-24 14:03
    https://tracker.freecad.org/file_download.php?file_id=2588&type=bug
    Notes
    (0015242)
    Kunda1   
    2021-01-31 12:07   
    Forum thread?
    (0015272)
    DrC   
    2021-02-05 05:37   
    Sorry - there was no thread to attach this to. I had a bug mid-job and needed to get it down while I could still remember how it happened.

    I probably shouldn't even be here because I'm not a developer and not a professional bug fixer (any more) but merely trying to use FreeCad. Trouble is I feel an obligation to tell you about as bug when I see it even when (as it always will be) it's mid job and I'm doing something new.

    A section headed 'report all bugs here' in the forum might help me - but would it help you?

    I really need it to be a one step process unless you can't replicate it.
    (0015275)
    DrC   
    2021-02-05 06:29   
    https://forum.freecadweb.org/viewtopic.php?f=3&t=5236&p=474546#p474546
    (0015282)
    chennes   
    2021-02-07 03:25   
    I can reproduce in:
    OS: Windows 10 Version 2004
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.23935 (Git)
    Build type: Debug
    Branch: master
    Hash: d5b68febbb4989b290b9af36bb2cb21d61a87a2e
    Python version: 3.8.6+
    Qt version: 5.15.1
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: English/United States (en_US)

    It is not limited to polygons, or to double-clicks on the construction line. I can achieve the same error state with all shapes I tried as long as they began at one end of those arcs. I can't replicate it on a new sketch with an arbitrary arc, however.
    (0015288)
    DrC   
    2021-02-07 12:08   
    Thanks for looking at this. Apologies for the stress-generated errors and omissions in my description of the process. I really appreciate the effort you must have put in to work out what I meant.

    DrC
    (0015872)
    chennes   
    2021-08-26 17:32   
    I revisited this today -- setting aside the tangent behavior (which hasn't changed), I think the current double-click behavior is correct. When I "accidentally" double-click, FreeCAD refuses to create the second (identical) point. I have no problems deleting the line segment I did create, and no longer get the "Selection not restricted to one sketch and its subelements" error. This is with:

    OS: Windows 10 Version 2009
    Word size of FreeCAD: 64-bit
    Version: 0.20.25552 +1 (Git)
    Build type: Debug
    Branch: hiddenPrefToLockToolbars
    Hash: c1f7407b255d7e4a5e63e37f69b5c0190519f95e
    Python version: 3.8.6+
    Qt version: 5.15.1
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: English/United States (en_US)

    (Pay no attention to the branch, it's just what I had handy)
    (0016153)
    chennes   
    2021-12-29 04:02   
    @DrC I believe this has been resolved and plan on closing out this bug -- can you re-test in a recent development build to confirm?
    (0016975)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6142.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4523 [PartDesign] Bug crash always 2020-12-25 18:22 2021-12-29 03:59
    Reporter: robryk Platform: x86_64  
    Assigned To: OS: NixOS  
    Priority: normal OS Version: release-20.09  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: NixOS 20.09 (Nightingale) (none+i3/none+i3)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.Unknown
    Build type: Release
    Python version: 3.8.5
    Qt version: 5.15.0
    Coin version: 4.0.0
    OCC version: 7.3.0
    Locale: English/United States (en_US)
    Summary: Crash (SIGSEGV) when moving elements of a constrained sketch
    Description: The crash seems to be triggered by movement of points of lines that are involved in reference constraints *and* have points constrained to lie on them. It seems that the crash can be prevented by saving the project between subsequent operations (see repro instructions for more details).
    Tags: crash
    Steps To Reproduce: 1. Create a new project, enable Part Design workbench, create a body and a sketch.
    2. Create a line. (The issue reproduces both for lines with no constraints and lines with a vertical constraint.)
    3. Create a point constrained to stay on the line. (The issue doesn't reproduce with line alone.)
    4. Create a reference constraint for the length of the line. (The issue doesn't reproduce for non-reference constraints.)
    5. Optionally: save the project. The attached project was saved at this stage.
    6. Add a name to the constraint.
    7. Do _not_ save the project again. (Saving appears to prevent the issue from occurring.)
    8. Drag one of the ends of the line around until FreeCAD crashes (usually takes 0-5 seconds).

    What happens:
    FreeCAD prints "Program received signal SIGSEGV, Segmentation fault." and either
    a) hangs, or
    b) prints a backtrace and exits.
    Additional Information: My FreeCAD is compiled from commit 7616153b3c31ace006169cdc2fdafab484498858. I haven't tried the current tip of the master branch, because compiling would take a long time for me right now.

    Backtrace:

    
    Program received signal SIGSEGV, Segmentation fault.
    #0  /nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6(+0x380f0) [0x7fc5238270f0]
    #1  0x7fc5258b4a05 in SoBaseList::operator[](int) const from /nix/store/yzi7nsv752xn4qcxk83vxbggd22hbmv3-coin-4.0.0/lib/libCoin.so.80+0x15
    0000002  0x7fc5258c3605 in SoChildList::truncate(int) from /nix/store/yzi7nsv752xn4qcxk83vxbggd22hbmv3-coin-4.0.0/lib/libCoin.so.80+0x45
    0000003  0x7fc5258c36ab in SoChildList::~SoChildList() from /nix/store/yzi7nsv752xn4qcxk83vxbggd22hbmv3-coin-4.0.0/lib/libCoin.so.80+0xb
    0000004  0x7fc52590eef9 in SoGroup::~SoGroup() from /nix/store/yzi7nsv752xn4qcxk83vxbggd22hbmv3-coin-4.0.0/lib/libCoin.so.80+0x29
    0000005  0x7fc5259295b9 in SoSeparator::~SoSeparator() from /nix/store/yzi7nsv752xn4qcxk83vxbggd22hbmv3-coin-4.0.0/lib/libCoin.so.80+0x9
    0000006  0x7fc5258bf079 in SoBase::destroy() from /nix/store/yzi7nsv752xn4qcxk83vxbggd22hbmv3-coin-4.0.0/lib/libCoin.so.80+0x99
    0000007  0x7fc5258b49b2 in SoBaseList::truncate(int) from /nix/store/yzi7nsv752xn4qcxk83vxbggd22hbmv3-coin-4.0.0/lib/libCoin.so.80+0x52
    0000008  0x7fc5258cfcaf in SoPath::truncate(int, int) from /nix/store/yzi7nsv752xn4qcxk83vxbggd22hbmv3-coin-4.0.0/lib/libCoin.so.80+0x6f
    0000009  0x7fc5258cfd49 in SoPath::~SoPath() from /nix/store/yzi7nsv752xn4qcxk83vxbggd22hbmv3-coin-4.0.0/lib/libCoin.so.80+0x19
    0000010  0x7fc5258cfd89 in SoPath::~SoPath() from /nix/store/yzi7nsv752xn4qcxk83vxbggd22hbmv3-coin-4.0.0/lib/libCoin.so.80+0x9
    0000011  0x7fc5258bf079 in SoBase::destroy() from /nix/store/yzi7nsv752xn4qcxk83vxbggd22hbmv3-coin-4.0.0/lib/libCoin.so.80+0x99
    0000012  0x7fc5258d234d in SoPickedPoint::~SoPickedPoint() from /nix/store/yzi7nsv752xn4qcxk83vxbggd22hbmv3-coin-4.0.0/lib/libCoin.so.80+0xd
    0000013  0x7fc4626c365f in SketcherGui::ViewProviderSketch::mouseButtonPressed(int, bool, SbVec2s const&, Gui::View3DInventorViewer const*) from /nix/store/knmz55iw0kq4k1y0dpsvvzgzr4x1bak5-freecad-unstable-2020-09-25/lib/SketcherGui.so+0x17f
    0000014  0x7fc5276312be in Gui::ViewProvider::eventCallback(void*, SoEventCallback*) from /nix/store/knmz55iw0kq4k1y0dpsvvzgzr4x1bak5-freecad-unstable-2020-09-25/lib/libFreeCADGui.so+0x12e
    0000015  0x7fc525906761 in SoEventCallback::handleEvent(SoHandleEventAction*) from /nix/store/yzi7nsv752xn4qcxk83vxbggd22hbmv3-coin-4.0.0/lib/libCoin.so.80+0xc1
    0000016  0x7fc5256f8e85 in SoAction::traverse(SoNode*) from /nix/store/yzi7nsv752xn4qcxk83vxbggd22hbmv3-coin-4.0.0/lib/libCoin.so.80+0x65
    0000017  0x7fc5258c3af8 in SoChildList::traverse(SoAction*, int, int) from /nix/store/yzi7nsv752xn4qcxk83vxbggd22hbmv3-coin-4.0.0/lib/libCoin.so.80+0x168
    0000018  0x7fc52590f2b8 in SoGroup::doAction(SoAction*) from /nix/store/yzi7nsv752xn4qcxk83vxbggd22hbmv3-coin-4.0.0/lib/libCoin.so.80+0x58
    0000019  0x7fc5259295f8 in SoSeparator::doAction(SoAction*) from /nix/store/yzi7nsv752xn4qcxk83vxbggd22hbmv3-coin-4.0.0/lib/libCoin.so.80+0x28
    0000020  0x7fc527552210 in Gui::SoFCUnifiedSelection::handleEvent(SoHandleEventAction*) from /nix/store/knmz55iw0kq4k1y0dpsvvzgzr4x1bak5-freecad-unstable-2020-09-25/lib/libFreeCADGui.so+0x90
    0000021  0x7fc5256f8e85 in SoAction::traverse(SoNode*) from /nix/store/yzi7nsv752xn4qcxk83vxbggd22hbmv3-coin-4.0.0/lib/libCoin.so.80+0x65
    0000022  0x7fc5258c3af8 in SoChildList::traverse(SoAction*, int, int) from /nix/store/yzi7nsv752xn4qcxk83vxbggd22hbmv3-coin-4.0.0/lib/libCoin.so.80+0x168
    0000023  0x7fc52590f2b8 in SoGroup::doAction(SoAction*) from /nix/store/yzi7nsv752xn4qcxk83vxbggd22hbmv3-coin-4.0.0/lib/libCoin.so.80+0x58
    0000024  0x7fc5259295f8 in SoSeparator::doAction(SoAction*) from /nix/store/yzi7nsv752xn4qcxk83vxbggd22hbmv3-coin-4.0.0/lib/libCoin.so.80+0x28
    0000025  0x7fc5256f8e85 in SoAction::traverse(SoNode*) from /nix/store/yzi7nsv752xn4qcxk83vxbggd22hbmv3-coin-4.0.0/lib/libCoin.so.80+0x65
    0000026  0x7fc5257025d3 in SoHandleEventAction::beginTraversal(SoNode*) from /nix/store/yzi7nsv752xn4qcxk83vxbggd22hbmv3-coin-4.0.0/lib/libCoin.so.80+0xa3
    0000027  0x7fc5256f9ac2 in SoAction::apply(SoNode*) from /nix/store/yzi7nsv752xn4qcxk83vxbggd22hbmv3-coin-4.0.0/lib/libCoin.so.80+0x2d2
    0000028  0x7fc5258dc3d9 in SoEventManager::actuallyProcessEvent(SoEvent const*) from /nix/store/yzi7nsv752xn4qcxk83vxbggd22hbmv3-coin-4.0.0/lib/libCoin.so.80+0x69
    0000029  0x7fc5275cf73e in SIM::Coin3D::Quarter::QuarterWidget::processSoEvent(SoEvent const*) from /nix/store/knmz55iw0kq4k1y0dpsvvzgzr4x1bak5-freecad-unstable-2020-09-25/lib/libFreeCADGui.so+0x1e
    0000030  0x7fc5275d7bf7 in SIM::Coin3D::Quarter::SoQTQuarterAdaptor::processSoEvent(SoEvent const*) from /nix/store/knmz55iw0kq4k1y0dpsvvzgzr4x1bak5-freecad-unstable-2020-09-25/lib/libFreeCADGui.so+0x57
    0000031  0x7fc52760b7e9 in Gui::View3DInventorViewer::processSoEventBase(SoEvent const*) from /nix/store/knmz55iw0kq4k1y0dpsvvzgzr4x1bak5-freecad-unstable-2020-09-25/lib/libFreeCADGui.so+0x9
    0000032  0x7fc5275e028c in Gui::NavigationStyle::processSoEvent(SoEvent const*) from /nix/store/knmz55iw0kq4k1y0dpsvvzgzr4x1bak5-freecad-unstable-2020-09-25/lib/libFreeCADGui.so+0xbc
    0000033  0x7fc5275e558b in Gui::CADNavigationStyle::processSoEvent(SoEvent const*) from /nix/store/knmz55iw0kq4k1y0dpsvvzgzr4x1bak5-freecad-unstable-2020-09-25/lib/libFreeCADGui.so+0x31b
    0000034  0x7fc5275e2245 in Gui::NavigationStyle::processEvent(SoEvent const*) from /nix/store/knmz55iw0kq4k1y0dpsvvzgzr4x1bak5-freecad-unstable-2020-09-25/lib/libFreeCADGui.so+0x75
    0000035  0x7fc52760b75c in Gui::View3DInventorViewer::processSoEvent(SoEvent const*) from /nix/store/knmz55iw0kq4k1y0dpsvvzgzr4x1bak5-freecad-unstable-2020-09-25/lib/libFreeCADGui.so+0x6c
    0000036  0x7fc5275c86b1 in SIM::Coin3D::Quarter::EventFilter::eventFilter(QObject*, QEvent*) from /nix/store/knmz55iw0kq4k1y0dpsvvzgzr4x1bak5-freecad-unstable-2020-09-25/lib/libFreeCADGui.so+0xd1
    0000037  0x7fc5240a156b in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) from /nix/store/m1bvfyy6m7j3r75x72npprnmqvm7ql2a-qtbase-5.15.0/lib/libQt5Core.so.5+0x9b
    0000038  0x7fc524b60cde in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /nix/store/m1bvfyy6m7j3r75x72npprnmqvm7ql2a-qtbase-5.15.0/lib/libQt5Widgets.so.5+0x6e
    #39  0x7fc524b69da3 in QApplication::notify(QObject*, QEvent*) from /nix/store/m1bvfyy6m7j3r75x72npprnmqvm7ql2a-qtbase-5.15.0/lib/libQt5Widgets.so.5+0x583
    #40  0x7fc5272fb998 in Gui::GUIApplication::notify(QObject*, QEvent*) from /nix/store/knmz55iw0kq4k1y0dpsvvzgzr4x1bak5-freecad-unstable-2020-09-25/lib/libFreeCADGui.so+0x88
    0000041  0x7fc5240a17fa in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /nix/store/m1bvfyy6m7j3r75x72npprnmqvm7ql2a-qtbase-5.15.0/lib/libQt5Core.so.5+0x12a
    0000042  0x7fc524b68eb7 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool, bool) from /nix/store/m1bvfyy6m7j3r75x72npprnmqvm7ql2a-qtbase-5.15.0/lib/libQt5Widgets.so.5+0x1b7
    0000043  /nix/store/m1bvfyy6m7j3r75x72npprnmqvm7ql2a-qtbase-5.15.0/lib/libQt5Widgets.so.5(+0x1cfe19) [0x7fc524bbde19]
    0000044  /nix/store/m1bvfyy6m7j3r75x72npprnmqvm7ql2a-qtbase-5.15.0/lib/libQt5Widgets.so.5(+0x1d3114) [0x7fc524bc1114]
    0000045  0x7fc524b60cef in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /nix/store/m1bvfyy6m7j3r75x72npprnmqvm7ql2a-qtbase-5.15.0/lib/libQt5Widgets.so.5+0x7f
    0000046  0x7fc524b69b50 in QApplication::notify(QObject*, QEvent*) from /nix/store/m1bvfyy6m7j3r75x72npprnmqvm7ql2a-qtbase-5.15.0/lib/libQt5Widgets.so.5+0x330
    0000047  0x7fc5272fb998 in Gui::GUIApplication::notify(QObject*, QEvent*) from /nix/store/knmz55iw0kq4k1y0dpsvvzgzr4x1bak5-freecad-unstable-2020-09-25/lib/libFreeCADGui.so+0x88
    0000048  0x7fc5240a17fa in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /nix/store/m1bvfyy6m7j3r75x72npprnmqvm7ql2a-qtbase-5.15.0/lib/libQt5Core.so.5+0x12a
    0000049  0x7fc5244c1013 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) from /nix/store/m1bvfyy6m7j3r75x72npprnmqvm7ql2a-qtbase-5.15.0/lib/libQt5Gui.so.5+0x6c3
    0000050  0x7fc5244c0b48 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) from /nix/store/m1bvfyy6m7j3r75x72npprnmqvm7ql2a-qtbase-5.15.0/lib/libQt5Gui.so.5+0x1f8
    0000051  0x7fc5244c26a5 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) from /nix/store/m1bvfyy6m7j3r75x72npprnmqvm7ql2a-qtbase-5.15.0/lib/libQt5Gui.so.5+0x255
    0000052  0x7fc52449adab in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /nix/store/m1bvfyy6m7j3r75x72npprnmqvm7ql2a-qtbase-5.15.0/lib/libQt5Gui.so.5+0xbb
    0000053  /nix/store/fl7g5dqfbxa52c5dmcg98cb6p701hgzn-qtbase-5.15.0-bin/lib/qt-5.15.0/plugins/platforms/../../../../../m1bvfyy6m7j3r75x72npprnmqvm7ql2a-qtbase-5.15.0/lib/libQt5XcbQpa.so.5(+0x6973a) [0x7fc511de173a]
    0000054  /nix/store/fzxhbcyzsfv1v8523jxlzvpsmvfhx2pz-glib-2.64.5/lib/libglib-2.0.so.0(g_main_context_dispatch+0x27d) [0x7fc520a4f44d]
    0000055  /nix/store/fzxhbcyzsfv1v8523jxlzvpsmvfhx2pz-glib-2.64.5/lib/libglib-2.0.so.0(+0x536d0) [0x7fc520a4f6d0]
    0000056  /nix/store/fzxhbcyzsfv1v8523jxlzvpsmvfhx2pz-glib-2.64.5/lib/libglib-2.0.so.0(g_main_context_iteration+0x2f) [0x7fc520a4f75f]
    0000057  0x7fc5240fa6be in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /nix/store/m1bvfyy6m7j3r75x72npprnmqvm7ql2a-qtbase-5.15.0/lib/libQt5Core.so.5+0x5e
    0000058  0x7fc5240a038b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) from /nix/store/m1bvfyy6m7j3r75x72npprnmqvm7ql2a-qtbase-5.15.0/lib/libQt5Core.so.5+0x12b
    0000059  0x7fc5240a85f0 in QCoreApplication::exec() from /nix/store/m1bvfyy6m7j3r75x72npprnmqvm7ql2a-qtbase-5.15.0/lib/libQt5Core.so.5+0x90
    0000060  0x7fc52726cad1 in Gui::Application::runApplication() from /nix/store/knmz55iw0kq4k1y0dpsvvzgzr4x1bak5-freecad-unstable-2020-09-25/lib/libFreeCADGui.so+0x1861
    0000061  /nix/store/knmz55iw0kq4k1y0dpsvvzgzr4x1bak5-freecad-unstable-2020-09-25/bin/FreeCAD() [0x4058e0]
    0000062  /nix/store/33idnvrkvfgd5lsx2pwgwwi955adl6sk-glibc-2.31/lib/libc.so.6(__libc_start_main+0xed) [0x7fc523812c7d]
    0000063  /nix/store/knmz55iw0kq4k1y0dpsvvzgzr4x1bak5-freecad-unstable-2020-09-25/bin/FreeCAD() [0x405bea]
    
    Attached Files: repro1.FCStd (5,668 bytes) 2020-12-25 18:22
    https://tracker.freecad.org/file_download.php?file_id=2589&type=bug
    Notes
    (0015195)
    chennes   
    2021-01-02 02:14   
    I could not reproduce on a fresh compile of HEAD (either following your steps from the beginning, or loading your file and starting from there). Abdullah has been doing a ton of work on Sketcher recently, so it may be that the underlying cause here has been fixed already. I'm currently testing on:
    OS: Windows 10 Version 2004
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.23574 (Git)
    Build type: Debug
    Branch: master
    Hash: 01072f370965f9f3cb5774ffcb60511fc4d4a88b
    Python version: 3.8.6+
    Qt version: 5.15.1
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: English/United States (en_US)
    (0015876)
    Kunda1   
    2021-08-27 12:27   
    @robryk why OCC 7.3? The current release is 7.5.2
    (0016152)
    chennes   
    2021-12-29 03:59   
    @robryk can you reproduce this on a recent development build? If not, I'll close this bug out.
    (0016977)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6145.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4644 [Sketcher] Bug minor always 2021-04-25 19:50 2021-12-29 03:33
    Reporter: run_the_race Platform: PC  
    Assigned To: OS: Windows 10  
    Priority: normal OS Version: 2004  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Windows 10 Version 2004
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24276 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-19
    Hash: a88db11e0a908f6e38f92bfc5187b13ebe470438
    Python version: 3.8.6+
    Qt version: 5.15.1
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: English/United Kingdom (en_GB)
    Summary: Hotkeys working incorrectly for view mode in sketcher
    Description: In sketcher, display/render mode hotkeys dont work.
    Tags:
    Steps To Reproduce: In Sketcher press `v, 3` to switch to shader mode wireframe, then `v, 1` to switch back to `normal`. It won't switch shader modes, instead it switches perspective.
    Additional Information: Forum discussion: [link]https://forum.freecadweb.org/viewtopic.php?f=3&t=58125[/link]
    Attached Files:
    Notes
    (0016138)
    chennes   
    2021-12-29 03:33   
    @abdullah, where does this bug (and 0003796) stand now that you've reworked the Sketcher shortcuts?
    (0017038)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6206.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4762 [OpenSCAD] Bug major always 2021-10-09 13:31 2021-12-29 02:54
    Reporter: ozzee Platform:  
    Assigned To: chennes OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    Summary: CSG file from OpenScad does not render correctly
    Description: Attached CSG model file from OpenScad (see attached .scad file) appears to have a number of errors when rendering in FreeCAD.

    1. The difference operations do not seem to be respected.
    2. The multmatrix transformations do not seem to produce the same transforms in OpenSCAD (note many objects in the wrong places).
    Tags: #post-to-forum
    Steps To Reproduce: Import the attached CSG file.
    Additional Information: 00:15:28 This function will be deprecated. Please use 'make_layer'.
    00:15:28 ----------------
    00:15:28 Layer
    00:15:28 name: 0
    00:15:28 line_color: (0.0, 0.0, 0.0)
    00:15:28 line_width: 2.0
    00:15:28 draw_style: Solid
    00:15:28 transparency: 0
    00:15:28 drawing 272 lines...
    00:15:28 skipping texts...
    00:15:28 skipping dimensions...
    00:15:28 skipping points...
    00:15:28 skipping leaders...
    00:15:28 skipping hatches...
    00:15:28 skipping *blocks...
    00:15:28 successfully imported C:\Users\gianni\AppData\Local\Temp\fc-12712-528727-000001.dxf
    00:15:28 End processing CSG file
    00:15:28 Traceback (most recent call last):
      File "C:\Users\gianni\Downloads\FreeCAD_0.20.25645_Win-LPv12.5.4_vc17.x-x86-64\Mod\OpenSCAD\OpenSCADFeatures.py", line 406, in execute
        self.createGeometry(fp)
      File "C:\Users\gianni\Downloads\FreeCAD_0.20.25645_Win-LPv12.5.4_vc17.x-x86-64\Mod\OpenSCAD\OpenSCADFeatures.py", line 448, in createGeometry
        pipe_shell.build()
    <class 'Part.OCCError'>: Approx_CurvlinFunc::GetUParameter
    00:15:31 <Exception> Input shape is null
    00:15:31 <Exception> Input shape is null
    00:15:46 Traceback (most recent call last):
      File "C:\Users\gianni\Downloads\FreeCAD_0.20.25645_Win-LPv12.5.4_vc17.x-x86-64\Mod\OpenSCAD\OpenSCADFeatures.py", line 406, in execute
        self.createGeometry(fp)
      File "C:\Users\gianni\Downloads\FreeCAD_0.20.25645_Win-LPv12.5.4_vc17.x-x86-64\Mod\OpenSCAD\OpenSCADFeatures.py", line 448, in createGeometry
        pipe_shell.build()
    <class 'Part.OCCError'>: Approx_CurvlinFunc::GetUParameter
    00:15:46 <Exception> Input shape is null
    00:15:46 <Exception> Input shape is null
    00:16:50 Traceback (most recent call last):
      File "C:\Users\gianni\Downloads\FreeCAD_0.20.25645_Win-LPv12.5.4_vc17.x-x86-64\Mod\OpenSCAD\OpenSCADFeatures.py", line 406, in execute
        self.createGeometry(fp)
      File "C:\Users\gianni\Downloads\FreeCAD_0.20.25645_Win-LPv12.5.4_vc17.x-x86-64\Mod\OpenSCAD\OpenSCADFeatures.py", line 448, in createGeometry
        pipe_shell.build()
    <class 'Part.OCCError'>: Approx_CurvlinFunc::GetUParameter
    00:16:50 <Exception> Input shape is null
    00:16:50 <Exception> Input shape is null
    00:16:53 Traceback (most recent call last):
      File "C:\Users\gianni\Downloads\FreeCAD_0.20.25645_Win-LPv12.5.4_vc17.x-x86-64\Mod\OpenSCAD\OpenSCADFeatures.py", line 406, in execute
        self.createGeometry(fp)
      File "C:\Users\gianni\Downloads\FreeCAD_0.20.25645_Win-LPv12.5.4_vc17.x-x86-64\Mod\OpenSCAD\OpenSCADFeatures.py", line 448, in createGeometry
        pipe_shell.build()
    <class 'Part.OCCError'>: Approx_CurvlinFunc::GetUParameter
    00:16:53 <Exception> Input shape is null
    00:16:53 <Exception> Input shape is null
    00:16:56 Traceback (most recent call last):
      File "C:\Users\gianni\Downloads\FreeCAD_0.20.25645_Win-LPv12.5.4_vc17.x-x86-64\Mod\OpenSCAD\OpenSCADFeatures.py", line 406, in execute
        self.createGeometry(fp)
      File "C:\Users\gianni\Downloads\FreeCAD_0.20.25645_Win-LPv12.5.4_vc17.x-x86-64\Mod\OpenSCAD\OpenSCADFeatures.py", line 448, in createGeometry
        pipe_shell.build()
    <class 'Part.OCCError'>: Approx_CurvlinFunc::GetUParameter
    00:16:56 <Exception> Input shape is null
    00:16:56 <Exception> Input shape is null
    00:24:41 Traceback (most recent call last):
      File "C:\Users\gianni\Downloads\FreeCAD_0.20.25645_Win-LPv12.5.4_vc17.x-x86-64\Mod\OpenSCAD\OpenSCADFeatures.py", line 406, in execute
        self.createGeometry(fp)
      File "C:\Users\gianni\Downloads\FreeCAD_0.20.25645_Win-LPv12.5.4_vc17.x-x86-64\Mod\OpenSCAD\OpenSCADFeatures.py", line 448, in createGeometry
        pipe_shell.build()
    <class 'Part.OCCError'>: Approx_CurvlinFunc::GetUParameter
    00:24:41 <Exception> Input shape is null
    00:24:41 <Exception> Input shape is null
    00:24:43 Traceback (most recent call last):
      File "C:\Users\gianni\Downloads\FreeCAD_0.20.25645_Win-LPv12.5.4_vc17.x-x86-64\Mod\OpenSCAD\OpenSCADFeatures.py", line 406, in execute
        self.createGeometry(fp)
      File "C:\Users\gianni\Downloads\FreeCAD_0.20.25645_Win-LPv12.5.4_vc17.x-x86-64\Mod\OpenSCAD\OpenSCADFeatures.py", line 448, in createGeometry
        pipe_shell.build()
    <class 'Part.OCCError'>: Approx_CurvlinFunc::GetUParameter
    00:24:43 <Exception> Input shape is null
    00:24:43 <Exception> Input shape is null
    Attached Files: anchorcad_RaspberryPi4Case_bottom_example.csg (70,293 bytes) 2021-10-09 13:31
    https://tracker.freecad.org/file_download.php?file_id=2715&type=bug
    anchorcad_RaspberryPi4Case_bottom_example.scad (112,257 bytes) 2021-10-09 13:31
    https://tracker.freecad.org/file_download.php?file_id=2716&type=bug
    Notes
    (0015973)
    openBrain   
    2021-10-13 14:17   
    @ozzee : could you please open a new thread in our forum (per our reporting guidelines) and add link here ? Thx
    (0016133)
    chennes   
    2021-12-29 02:51   
    In both the SCAD and CSG files there are many empty unions -- it's not clear what their intended purpose is, but FreeCAD is not currently treating them the same way that OpenSCAD does, which leads to a divergence between the two results. I will try to figure out what OpenSCAD does with those elements.
    (0017102)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6271.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4812 [FreeCAD] Patch trivial always 2021-12-25 12:54 2021-12-25 13:14
    Reporter: Frank_Schruefer Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: openSUSE Tumbleweed (KDE//usr/share/xsessions/plasma5)
    Word size of FreeCAD: 64-bit
    Version: 0.20.26651 (Git) AppImage
    Build type: Release
    Branch: (HEAD detached at d357d52)
    Hash: d357d524d97db884b9bb562415e6b6d782ec02b4
    Python version: 3.9.7
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.5.3
    Locale: German/Germany (de_DE)
    Summary: Using custom threads in fasteners ScrewTab generates variable used before assigned exception
    Description: Hy, I have a path for a trivial bug in the fasteners workbench code.
    Without it the use of custom thread diameters and pitch won't work.
    Tags:
    Steps To Reproduce: -Choose fasteners Workbench
    -Create 'Add threaded Rod for tapping holes'
    -Change 'diameter' to 'Custom'
    -Change 'diameter Custom' and 'pitch Custom'
    Additional Information: Patch created via:
    stone@merlin:~/.local/share> diff -c FreeCAD/Mod/fasteners/screw_maker.py.orig FreeCAD/Mod/fasteners/screw_maker.py

    Diff output:
    *** FreeCAD/Mod/fasteners/screw_maker.py.orig 2021-12-22 00:43:13.164645112 +0100
    --- FreeCAD/Mod/fasteners/screw_maker.py 2021-12-22 00:44:23.605517538 +0100
    ***************
    *** 3792,3798 ****
          else: # custom pitch and diameter
            P = customPitch
            if self.sm3DPrintMode:
    ! dia = self.smNutThrScaleA * dia + self.smNutThrScaleB
            else:
              dia = customDia
          residue, turns = math.modf((l)/P)
    --- 3792,3798 ----
          else: # custom pitch and diameter
            P = customPitch
            if self.sm3DPrintMode:
    ! dia = self.smNutThrScaleA * customDia + self.smNutThrScaleB
            else:
              dia = customDia
          residue, turns = math.modf((l)/P)
    ***************
    *** 3831,3837 ****
          else: # custom pitch and diameter
            P = customPitch
            if self.sm3DPrintMode:
    ! dia = self.smScrewThrScaleA * dia + self.smScrewThrScaleB
            else:
              dia = customDia
          if self.rThread:
    --- 3831,3837 ----
          else: # custom pitch and diameter
            P = customPitch
            if self.sm3DPrintMode:
    ! dia = self.smScrewThrScaleA * customDia + self.smScrewThrScaleB
            else:
              dia = customDia
          if self.rThread:
    ***************
    *** 3870,3876 ****
          else: # custom pitch and diameter
            P = customPitch
            if self.sm3DPrintMode:
    ! dia = self.smScrewThrScaleA * dia + self.smScrewThrScaleB
            else:
              dia = customDia
          dia = dia*1.01
    --- 3870,3876 ----
          else: # custom pitch and diameter
            P = customPitch
            if self.sm3DPrintMode:
    ! dia = self.smScrewThrScaleA * customDia + self.smScrewThrScaleB
            else:
              dia = customDia
          dia = dia*1.01
    Attached Files:
    Notes
    (0016130)
    Frank_Schruefer   
    2021-12-25 13:14   
    P.S.: Forgot to mention that in order to reproduce the bug the 'Thread generation' option in the fasteners workbench settings must be set to '3D printer compatible'.
    (0017131)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6300.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4811 [Arch] Bug minor always 2021-12-25 09:51 2021-12-25 09:51
    Reporter: Lucchesi Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: <!--ATTENTION:
    COMPLETELY ERASE THIS AFTER PASTING YOUR
    Help > About FreeCAD > Copy to clipboard
    NOTE: just the snippet alone will do without anything else included.
    The ticket will not be submitted without it.
    -->
    Summary: Workbench Texture Arch non viene applicato correttamente
    Description: Ambiente di lavoro :
    Freecad 0.19 - Windows 10 64 bit - Processore Intel i5 _Scheda grafica Vidia Gforce 710
    Problema
    Utilizzando la workbench Texture Arch non si trasferisce l'immagine sulla superficie selezionata .
    La procedura seguita è la seguente :
    Creazione di un cubo con Part
    Mostra tutto nella finestra "Vista Combinata "
    Cliccando alla voce "Expression" con il tasto destro del mouse aggiungo "Proprieta --> App :: property Link --> Base --> Material
    Cambiamo Workbench da PART--> a --> Arch Texture
    Selezioniamo "MATERIAL ARCH " --> "WOOD GENERIC "
    A questo Punto dovrei trovarmi alla Voce "CUBO" -->"BASE" --> Material --> "WOOD GENERIC "
    Quest'ultimo passaggio non viene eseguito e quindi il successivo e cioè Texture Config ( la scelta di una immagine da associare al solido ).
    Riporto quanto trovato nel Forum :
    Leonardo Chiruzzi
    Vezio Lucchesi Ho riprovato con una installazione "particolare", qualcosa è cambiato ma continua a non funzionare[/b]. Mentre con un altra versione:
    FreeCAD: 64-bit
    Version: 0.19.23964 (Git) AppImage
    Python version: 3.8.6
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    sta funzionando.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0017130)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6299.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4621 [Sketcher] Feature tweak always 2021-04-07 08:04 2021-12-23 09:42
    Reporter: chrisb Platform:  
    Assigned To: openBrain OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: macOS 10.16
    Word size of FreeCAD: 64-bit
    Version: 0.20.24612 (Git)
    Build type: Release
    Branch: master
    Hash: f525904c1be10a0f55aa3502151c2c55e5054259
    Python version: 3.9.2
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.5.1
    Locale: C/Default (C)
    Summary: Driven angle constraints are different from driving constraints
    Description: When switching an angle constraint of an arc between driven (blue) and driving (red), it switches between the angle and the opposite angle.
    Forum post.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016128)
    openBrain   
    2021-12-23 09:42   
    https://github.com/FreeCAD/FreeCAD/pull/5279
    (0017027)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6195.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4808 [PartDesign] Bug minor always 2021-12-20 23:56 2021-12-22 00:41
    Reporter: lual Platform: PC  
    Assigned To: uwestoehr OS: Linux Manjaro  
    Priority: normal OS Version: stable  
    Status: resolved Product Version: 0.20  
    Product Build: Resolution: fixed  
    Projection: none      
    ETA: none Fixed in Version: 0.20  
        Target Version: 0.20  
    FreeCAD Information: OS: Manjaro Linux (KDE/plasma)
    Word size of FreeCAD: 64-bit
    Version: 0.20.26683 (Git) AppImage
    Build type: Release
    Branch: (HEAD detached at 0388fbc)
    Hash: 0388fbc98d49d874fb341b9037a743bc691d501f
    Python version: 3.9.7
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.5.3
    Locale: German/Germany (de_DE)
    Summary: "Part Design" > "Hole" > "Model Thread" > "Thread Depth" > "Dimension"
    Description:
    "Part Design" >
    "Hole" >
    "Model Thread" >
    "Thread Depth" >
    "Dimension" >
    pressing "OK" resets the given value to the value for the for hole-depth!
    Tags:
    Steps To Reproduce:
    1. Open the Attached File
    2. doubleclick on "Hole"
    3. Click "OK"
    4. Thread Depth is changed unexpected!
    Additional Information: Discussion in Forum
    https://forum.freecadweb.org/viewtopic.php?f=3&t=64682

    This Pull Request from Github may helps to find the code...
    https://github.com/FreeCAD/FreeCAD/pull/4274
    Attached Files:
    Notes
    (0016122)
    uwestoehr   
    2021-12-21 01:55   
    proposed fix: https://github.com/FreeCAD/FreeCAD/pull/5272
    (0016127)
    uwestoehr   
    2021-12-22 00:41   
    fix merged
    (0017128)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6297.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4765 [FreeCAD] Bug minor always 2021-10-15 09:42 2021-12-22 00:40
    Reporter: QuellaZhang Platform:  
    Assigned To: chennes OS:  
    Priority: normal OS Version:  
    Status: acknowledged Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: We using latest source code 217db02 from FreeCAD master branch.
    Summary: [MSVC][Build][Permissive-][std:c++latest] FreeCAD failed to build on MSVC
    Description: Hi All,

    The MSVC team recently added FreeCAD as part of RWC testing to detect compiler regressions. And we found some errors when building FreeCAD with '/permissive-' and '/std:c++latest' option. Can you help to fix these issues? Thanks.

    I noticed that some of these errors are come from Boost library, and these issue have been fixed on Boost latest version. After I fixed Boost errors, more errors were exposed by the project itself.
    Tags:
    Steps To Reproduce:
    1. open VS2019 x64 tools command
    2. git clone https://github.com/FreeCAD/FreeCAD.git F:\gitP\FreeCAD\FreeCAD
    3. download https://github.com/apeltauer/FreeCAD/releases/tag/LibPack_12.5.2 F:\gitP\FreeCAD\tools\FreeCADLibs_12.5.2_x64_VC17
    4. mkdir F:\gitP\FreeCAD\FreeCAD\build_amd64 && cd F:\gitP\FreeCAD\FreeCAD\build_amd64
    5. set _CL_= /permissive- or set _CL_= /std:c++latest
    6. set PATH=F:\gitP\FreeCAD\tools\FreeCADLibs_12.5.2_x64_VC17\bin;%PATH%
    7. set PATH=F:\gitP\FreeCAD\tools\FreeCADLibs_12.5.2_x64_VC17\bin\Scripts;%PATH%
    8. cmake -G "Visual Studio 16 2019" -A x64 -DCMAKE_SYSTEM_VERSION=10.0.18362.0 -DFREECAD_LIBPACK_DIR=F:\gitP\FreeCAD\tools\FreeCADLibs_12.5.2_x64_VC17 -DBUILD_FEM_NETGEN=OFF -DFREECAD_RELEASE_PDB=OFF -DFREECAD_RELEASE_SEH=OFF -DCMAKE_BUILD_TYPE=Release ..
    9. msbuild /m /p:Platform=x64 /p:Configuration=Release FreeCAD.sln /t:Rebuild
    Additional Information:
    Attached Files: FreeCAD_build_log.7z (116,569 bytes) 2021-10-15 09:42
    https://tracker.freecad.org/file_download.php?file_id=2719&type=bug
    Notes
    (0016005)
    chennes   
    2021-11-01 16:50   
    Thank you for the report -- we'll look into these issues.
    (0016013)
    chennes   
    2021-11-04 02:42   
    https://github.com/FreeCAD/FreeCAD/commit/833868bd1394862f6fab079fa74685f09675129a fixes one of the issues.
    (0016016)
    chennes   
    2021-11-06 15:57   
    https://github.com/FreeCAD/FreeCAD/commit/6d2aa6acc9f58d8f8cf0d4744d9a0ed86ac18ed5 fixes another.
    (0016115)
    uwestoehr   
    2021-12-20 10:02   
    https://github.com/FreeCAD/FreeCAD/commit/6ad156b6b77 fixes another one
    (0016126)
    uwestoehr   
    2021-12-22 00:40   
    and another one: https://github.com/FreeCAD/FreeCAD/commit/5fba9cec
    (0017103)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6272.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4737 [Sketcher] Bug minor always 2021-08-30 16:58 2021-12-20 20:11
    Reporter: ifohancroft Platform: GNU/Linux  
    Assigned To: abdullah OS: Manjaro  
    Priority: normal OS Version: 5.10 Kernel  
    Status: assigned Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Manjaro Linux (MATE/mate)
    Word size of FreeCAD: 64-bit
    Version: 0.20.25288 (Git) AppImage
    Build type: Release
    Branch: master
    Hash: bbb557aab6129efd9486d6df19f06c2976fdb7e5
    Python version: 3.9.6
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.5.2
    Locale: English/United States (en_US)
    Summary: Increasing Number of decimals doesn't incrase the number of decimal places shown
    Description: If for a dimension constraint (pretty much anything requiring you to enter a number) I set a floating point number that has 5 decimal places, unless I open the dimension for editing, I only see 4 decimal places, despite Number of Decimals under Preferences > General > Units being set to 5 (Chrisb has it set to 6 and can see 6 decimal places).

    If I increase Number of decimals, I still continue to see only 4 decimal places. The only thing that changes is that if I open the dimension for editing, there is now an extra 0 at the end.

    Forum Post
    Tags:
    Steps To Reproduce: 1. Set a dimension constraint on an element in Sketcher and set it to a floating point number having more decimal places than what Number of decimals is set to
    2. Check how many of the decimal places are being shown
    3. Increase the value of Number of decimals
    4. See that the number is showing the same and the only thing that changed is that you now have an extra 0 or more at the end of the number when you open the constraint for editing.
    Additional Information:
    Attached Files:
    Notes
    (0015886)
    openBrain   
    2021-08-30 17:43   
    The current behavior is much probably correct regarding what the coder wants to implement.
    Let's talk on if we want something different on the forum thread before continuing this ticket.
    (0016120)
    uwestoehr   
    2021-12-20 20:05   
    This bug also applies when you set e.g. only 2 digits in the general preferences of FreeCAD. Here is a bug report about this: https://forum.freecadweb.org/viewtopic.php?f=10&t=64645#p554894
    (0016121)
    uwestoehr   
    2021-12-20 20:11   
    Here is an idea what the bug could be: https://forum.freecadweb.org/viewtopic.php?f=10&t=64645&p=555225#p555225
    (0017087)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6256.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4217 [FreeCAD] Bug tweak N/A 2019-12-06 02:56 2021-12-20 01:43
    Reporter: apelleti Platform:  
    Assigned To: chennes OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: macOS 10.14
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16146 (Git)
    Build type: Release
    Branch: (HEAD detached at 0.18.4)
    Hash: 980bf9060e28555fecd9e3462f68ca74007b70f8
    Python version: 3.6.7
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/Canada (en_CA)
    Summary: Simple perf improvement: avoid 'if somekey in mydict.keys()'
    Description: This ticket is a suggestion to fix some very simple (common) coding errors that can seriously degrade performance in python.

    Doing a python dictionary hash lookup the recommended way:
    
        # test if 'somekey' is in dictionary mydict. order-1
        if "somekey" in mydict:
            do_something()
    

    Doing a python dictionary hash lookup the wrong way:
    
        # walk the dictionary to compile an unsorted list of keys: order-N,
        # then brute force search for desired key in this unsorted set: order-N
        if "somekey" in mydict.keys():
            do_something()
    

    ======

    Performance comparison:
    
    # good way:
    import random
    mydict={k: random.random() for k in range(200000)}
    for i in mydict:
        if i not in mydict:
            print("FAIL!")
    
    Runtime=0.07 seconds to test 200k keys exist in the dictionary of 200k entries.

    ----------
    
    # bad way:
    import random
    mydict={k: random.random() for k in range(200000)}
    for i in mydict:
        if i not in mydict.keys():
            print("FAIL!")
    
    Runtime=11min 29sec.....10000 times slower!! :-(

    See "additional info" for a partial list.
    Tags:
    Steps To Reproduce: N/A
    Additional Information: Here's a partial list of potential fixes, using a rudimentary grep to search the codebase for occurrences.

    DISCLAIMER: likely a few false-positives.
    
    [dhcp-161-44-212-77:~/Downloads/FreeCAD-master] apelleti% find . -name "*.py" | xargs egrep "if.* in .*keys" 
    ./src/Tools/MakeMacBundleRelocatable.py:                    if dk not in visited.keys():
    ./src/Tools/generateBase/generateDS.py:        if 'maxOccurs' in self.attrs.keys():
    ./src/Tools/generateBase/generateDS.py:        if 'mixed' in self.attrs.keys():
    ./src/Tools/generateBase/generateDS.py:            if 'substitutionGroup' in attrs.keys()and 'name' in attrs.keys():
    ./src/Tools/generateBase/generateDS.py:            if 'name' in attrs.keys():
    ./src/Tools/generateBase/generateDS.py:            elif 'ref' in attrs.keys():
    ./src/Tools/generateBase/generateDS.py:            if 'type' in attrs.keys():
    ./src/Tools/generateBase/generateDS.py:            if 'use' in attrs.keys():
    ./src/Tools/generateBase/generateDS.py:            if 'name' in attrs.keys():
    ./src/Tools/generateBase/generateDS.py:            if 'ref' in attrs.keys():
    ./src/Tools/generateBase/generateDS.py:            if 'base' in attrs.keys() and len(self.stack) > 0:
    ./src/Mod/Draft/Draft.py:            if str(obj.ViewObject.Pattern) in list(svgpatterns().keys()):
    ./src/Mod/Draft/Draft.py:                            if str(vobj.Pattern) in list(svgpatterns().keys()):
    ./src/Mod/Drawing/DrawingPatterns.py:    if not (name in Patterns.keys()):
    ./src/Mod/Drawing/DrawingPatterns.py:    if not (name in Patterns.keys()):
    ./src/Mod/Drawing/DrawingPatterns.py:    if not (name in Patterns.keys()):
    ./src/Mod/Spreadsheet/App/Spreadsheet_legacy.py:                if key in self._cells.keys():
    ./src/Mod/Spreadsheet/App/Spreadsheet_legacy.py:            if "Type" in self._cells.keys():
    ./src/Mod/Spreadsheet/App/Spreadsheet_legacy.py:            if "Object" in self._cells.keys():
    ./src/Mod/Spreadsheet/App/Spreadsheet_legacy.py:                if key in self.spreadsheet.Proxy._cells.keys():
    ./src/Mod/Spreadsheet/App/Spreadsheet_legacy.py:                if key in obj.Proxy._cells.keys():
    ./src/Mod/Path/PathScripts/PathPost.py:        if item.text() in self.tooltips.keys():
    ./src/Mod/Path/PathScripts/PathPreferencesPathJob.py:        if not name in self.processor.keys():
    ./src/Mod/Path/PathScripts/PathToolLibraryManager.py:        if target in tt.Tools.keys():
    ./src/Mod/Path/PathScripts/PathToolLibraryManager.py:        if target in tt.Tools.keys():
    ./src/Mod/Idf/Idf.py:        if len(model_records)>1 and model_records[0] and not model_records[0] in keys:
    ./src/Mod/Arch/importDAE.py:                                if "target" in mnode.keys():
    ./src/Mod/Arch/ArchReference.py:            if self.obj.Part in parts.keys():
    ./src/Mod/Arch/ArchReference.py:                    if self.obj.Part in parts.keys():
    ./src/Mod/Arch/exportIFC.py:            if "IfcUID" in obj.IfcData.keys():
    ./src/Mod/Arch/exportIFC.py:        if ifctype not in ArchIFCSchema.IfcProducts.keys():
    ./src/Mod/Arch/exportIFC.py:            if "FlagForceBrep" in obj.IfcData.keys():
    ./src/Mod/Arch/exportIFC.py:                    if c.Name in products.keys():
    ./src/Mod/Arch/exportIFC.py:                        if c.Name in products.keys():
    ./src/Mod/Arch/exportIFC.py:                if c.Name in products.keys():
    ./src/Mod/Arch/exportIFC.py:            if g[0] in groups.keys():
    ./src/Mod/Arch/exportIFC.py:                if o in products.keys():
    ./src/Mod/Arch/exportIFC.py:                elif o in annos.keys():
    ./src/Mod/Arch/exportIFC.py:    if ifctype in translationtable.keys():
    ./src/Mod/Arch/ArchCommands.py:        if "FlagForceBrep" in d.keys():
    ./src/Mod/Arch/ArchComponent.py:        self.psetkeys = [''.join(map(lambda x: x if x.islower() else " "+x, t[5:]))[1:] for t in self.psetdefs.keys()]
    ./src/Mod/Arch/ArchIFC.py:IfcTypes = [''.join(map(lambda x: x if x.islower() else " "+x, t[3:]))[1:] for t in ArchIFCSchema.IfcProducts.keys()]
    ./src/Mod/Arch/ArchIFC.py:            if attribute["name"] not in ifcComplexAttributes.keys():
    ./src/Mod/Arch/ArchIFC.py:        return [''.join(map(lambda x: x if x.islower() else " "+x, t[3:]))[1:] for t in schema.keys()]
    ./src/Mod/Arch/importIFClegacy.py:            if "FlagForceBrep" in obj.IfcAttributes.keys():
    ./src/Mod/Arch/importSH3D.py:            if "angle" in attributes.keys():
    ./src/Mod/Arch/importSH3D.py:                if "angle" in attributes.keys():
    ./src/Mod/Arch/importSH3D.py:                if "elevation" in attributes.keys():
    ./src/Mod/Arch/ArchIFCView.py:            if lineEdit.objectName() in data.keys():
    ./src/Mod/Arch/importIFC.py:            if currentid in additions.keys():
    ./src/Mod/Arch/importIFC.py:                    if layer_name not in list(layers.keys()):
    ./src/Mod/Arch/importIFC.py:            if "FreeCADPropertySet" in [ifcfile[pset].Name for pset in psets.keys()]:
    ./src/Mod/Arch/importIFC.py:                    if c in structshapes.keys():
    ./src/Mod/Arch/importIFC.py:                if host in objects.keys():
    ./src/Mod/Arch/importIFC.py:                        if child in objects.keys():
    ./src/Mod/Arch/importIFC.py:                if child in objects.keys():
    ./src/Mod/Arch/importIFC.py:                    if c in shapes.keys():
    ./src/Mod/Arch/importIFC.py:                    if c in additions.keys():
    ./src/Mod/Arch/importIFC.py:                            if c2 in shapes.keys():
    ./src/Mod/Arch/importIFC.py:                if (subtraction[0] in objects.keys()) and (subtraction[1] in objects.keys()):
    ./src/Mod/Arch/importIFC.py:            if host not in objects.keys():
    ./src/Mod/Arch/importIFC.py:                if child in objects.keys() \
    ./src/Mod/Arch/importIFC.py:            if aid in remaining.keys():
    ./src/Mod/Arch/importIFC.py:                    if (aid in children) and (host in objects.keys()):
    ./src/Mod/Arch/importIFC.py:        if "FreeCADType" in appset.keys():
    ./src/Mod/Arch/importIFC.py:            if "FreeCADName" in appset.keys():
    ./src/Mod/AddonManager/addonmanager_workers.py:                            if not wb.strip() in FreeCADGui.listWorkbenches().keys():
    ./src/Mod/AddonManager/addonmanager_workers.py:                                if not wb.strip()+"Workbench" in FreeCADGui.listWorkbenches().keys():
    ./src/Mod/PartDesign/FeatureHole/Standards.py:    if not standard in standards.keys():
    ./src/Mod/PartDesign/FeatureHole/Standards.py:    if not standard in standards_through.keys():
    ./src/Mod/PartDesign/FeatureHole/Standards.py:    if not standard in standards_counterbore_through.keys():
    ./src/Mod/PartDesign/FeatureHole/Standards.py:    if not standard in standards_counterbore.keys():
    ./src/Mod/PartDesign/FeatureHole/Standards.py:    if not standard in standards_counterbore_rows.keys():
    ./src/Mod/PartDesign/FeatureHole/Standards.py:    if not standard in standards_countersink.keys():
    ./src/Mod/PartDesign/FeatureHole/Standards.py:    if not standard in standards_countersink.keys():
    ./src/Mod/PartDesign/FeatureHole/Standards.py:    if not standard in standards_thread.keys():
    ./src/Mod/PartDesign/FeatureHole/Standards.py:    if not standard in standards_threaded.keys():
    ./src/Mod/Material/importFCMat.py:                if k in group.keys():
    ./src/Mod/Material/materialtools/cardutils.py:            if k in registed_cardkeys:
    ./src/Mod/Material/materialtools/cardutils.py:        if (k not in used_and_registered_cardkeys) and (k not in used_and_not_registered_cardkeys):
    
    Attached Files:
    Notes
    (0013877)
    openBrain   
    2019-12-06 11:01   
    @apelleti : please open a forum topic and cross-link with this ticket (per the guidelines in the huge yellow box on the top of the page).
    BTW : your command line will be better written like
    find . -name "*.py" -exec egrep -Hn "if.* in .*\.keys\(\)" {} \;
    (0014074)
    Kunda1   
    2020-01-14 18:14   
    (Last edited: 2020-01-14 20:02)
    Forum thread https://forum.freecadweb.org/viewtopic.php?f=3&t=41483

    (0016110)
    chennes   
    2021-12-17 05:03   
    These issues do exist, and simply represent a misunderstanding on the part of the original programmer on what exactly they are asking Python to do. With the exception of the false positives (e.g. where a container's name contains the word "keys") these can all be replaced wholesale without concern that we are breaking something. Best to remove all of them, so later copy-and-paste programmers don't inherit the performance penalty.
    (0016849)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6015.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4102 [FEM] Bug minor always 2019-08-27 19:44 2021-12-17 05:11
    Reporter: Jee-Bee Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Contact constraint feature intensive
    Description: In the FEM workbench the contact constraint is feature-tree intensive. for EVERY set of surfaces a new feature has to be created.
    I have created a example where two bodies have contact by 3 surfaces all in the same plane. I have to create 3 contact constraints.
    I would give two ideas
    1. give 1 master and serval slaves (or reverse: 1 slave and serval masters) this create automatically a set of master and slave for every set inside the feature
    2. give equal set of masters and slaves and create a master-slave for each index in the list. (just master[0] and [slave[0] to master[N] and slave[N] no crossrelations...)
    Tags: constraints, contact, FEM
    Steps To Reproduce: See example
    Additional Information: see forum page https://forum.freecadweb.org/viewtopic.php?f=18&t=15699&start=130#p325864
    Attached Files: example_contact.FCStd (47,691 bytes) 2019-08-27 19:44
    https://tracker.freecad.org/file_download.php?file_id=2287&type=bug
    Notes
    (0016814)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5980.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    597 [FreeCAD] Feature minor N/A 2012-02-08 12:50 2021-12-17 03:26
    Reporter: gafvert Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.12  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: New feature naming convention
    Description: I suggest a new more informative naming convention for new generated features (such as fillets, cuts, fusions etc). Right now the newly generated feature is only given the feature name and a number (if it's not the first).

    You can see the history, of what it is based on in the project tree by expanding the item, but not in the name alone. So you usually end up with a lot of "Fillet012" and "Chamfer003" in the list.

    My suggestion is to introduce a new first part in the naming convention, the name of the base object. Giving the standard format ObjectName_FeatureName_Number
    This is to make it easier to keep track of your parts and which on is which without manually renaming them.

    An example:
    1. You create a box, and it is named "Box1".

    2. You create a fillet on one of the edges of this box, it will be named "Box1_Fillet1". Using the name of the base object.

    3. You create another fillet on this "Box1_Fillet1", this time, to make sure the names don't grow too much, the entire name isn't used for the base object name, only the ObjectName part. So the new fillet will be named "Box1_Fillet2".

    4. This "Box1_Fillet2" is then cut using a boolean operation, and given the name "Box1_Cut1".

    etc etc.

    The same can then be used for all types of features, with new features being given names containing the based object name with the addition of a feature name.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0004003)
    wmayer   
    2014-01-02 14:30   
    It's best to have an option in the preferences to add the base name or not.
    (0016107)
    chennes   
    2021-12-17 03:26   
    Maybe this could be implemented in a similar manner to our generation of default export filenames, via a format string set in the preferences.
    (0016387)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5552.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    19 [FreeCAD] Feature major have not tried 2009-09-28 15:45 2021-12-17 03:18
    Reporter: Jriegel Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: acknowledged Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Resource framework for FreeCAD
    Description: Often in 3D modeling we use Objects and files from 3rd party resources.
    This things are just used and rarely changed. like e.g. standard parts
    (ISO), complete products from a catalog and so on.
    We need in FreeCAD a framework to access/share/distribute such resources.
    It shut be possible to locate such resources locally or in the web and
    allow FreeCAD to find and access such resources referenced in a modeling
    document.

    Specification:
    * can be used loacally or in the web
    * unique id to find resources
    * central repository to collect resources
    * revision control
    * accessibly through http: and https:

    Design so far:
    * use SVN to host resources for revision control and restricted access
    * use webserver to host resources without revision control
    * use a XML description file to specify a resource, this file holds:
    - a UUID as global unique identifier
    - a name and description of the resource
    - a specifier it its a SVN or a PLAIN resource
    - addition meta infromation
    * use WGET or SVN to make the resources lokaly available
    * deliver a set of Resource description files with the installer/packages
    * Host on the FreeCAD website a repository of Resource description where
    FreeCAD can search for unknown UUIDs

    So far...

    Jürgen
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0011425)
    Kunda1   
    2018-06-13 13:28   
    Unassigning Jriegel
    (0016106)
    chennes   
    2021-12-17 03:18   
    It's not exactly what was envisioned here, but we do have the FreeCAD parts library now. It needs some work, but it may be worth closing this bug and re-opening more specific changes that need to be made to the parts library. This request doesn't really have any action items at this point.
    (0016374)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5539.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4705 [Draft] Bug minor always 2021-07-16 12:07 2021-12-16 22:17
    Reporter: uwestoehr Platform:  
    Assigned To: yorik OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: Forum thread: https://forum.freecadweb.org/viewtopic.php?f=3&t=60215

    OS: Windows 10 Version 2009
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24291 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-19
    Hash: 7b5e18a0759de778b74d3a5c17eba9cb815035ac
    Python version: 3.8.6+
    Qt version: 5.15.2
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: German/Germany (de_DE)
    Summary: [Draft] toolbar is active for all workbenches
    Description: - change to the Draft toolbar
    - close FreeCAD
    - open FreeCAD

    result: no matter in what workbench you are, the toolbar containing Draft's "Create working plane proxy" is always shown, and moreover active. As it is active, you can click on the toolbar buttons and get errors.

    The bug is in FC 0.19. and current FC 0.20 master.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files: firefox_fct2lVoz0W.png (54,759 bytes) 2021-12-16 22:17
    https://tracker.freecad.org/file_download.php?file_id=2740&type=bug
    Notes
    (0015736)
    uwestoehr   
    2021-07-16 12:09   
    In the forum this workaround was reported:
    - open FC
    - go to the Draft WB
    - go to another WB

    then the toolbar disappears.
    (0016099)
    yorik   
    2021-12-16 15:17   

    - change to the Draft toolbar
    - close FreeCAD
    - open FreeCAD

    result: no matter in what workbench you are, the toolbar containing Draft's "Create working plane proxy" is always shown, and moreover active. As it is active, you can click on the toolbar buttons and get errors.

    uwestoehr

    I cannot reproduce this (master branch). The bar is not present on relaunching FreCAD. Can you look again @uwestoehr ?
    (0016105)
    uwestoehr   
    2021-12-16 22:17   
    > I cannot reproduce this (master branch).

    This is still there (one of my favorite "annoyants" ;-) )

    1. open FC
    2. set in the preferences that FC is started with the PartDesign workbench
    3. change to the Draft WB
    4. close FC and restart it

    result: the Draft toolbar is there, see attached image

    OS: Windows 10 Version 2009
    Word size of FreeCAD: 64-bit
    Version: 0.20.26656 (Git)
    Build type: Release
    Branch: master
    Hash: 8585149ab4ee0c165c5c443e84915741968d5624
    Python version: 3.8.6+
    Qt version: 5.15.2
    Coin version: 4.0.1
    OCC version: 7.5.3
    Locale: German/Germany (de_DE)
    (0017073)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6242.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3796 [FreeCAD] Bug minor always 2019-01-25 22:10 2021-12-16 21:35
    Reporter: markus51 Platform:  
    Assigned To: abdullah OS: Win7  
    Priority: low OS Version:  
    Status: confirmed Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Shortcuts "V1" .. "V7" to change the "Draw-Style" didn't work in sketch view
    Description: The shortcuts "V1" .. "V7" to change the "Draw-Style" didn't work in the sketch view.

    When i change to "Part Design" the shortcuts "V1" .. "V7" working correctly.
    Tags: shortcuts
    Steps To Reproduce: 1.) Open a sketch.
    2.) Press "V"+"1" --> the "Draw-Style" din't change
    3.) Press "V"+"4" --> the "Draw-Style" din't change
    4.) Change in the toolbar to "Part Design"
    5.) Press "V"+"1" --> the "Draw-Style" changes correctly
    6.) Press "V"+"4" --> the "Draw-Style" changes correctly
    Additional Information:
    Attached Files:
    Notes
    (0012519)
    Kunda1   
    2019-01-25 23:22   
    @markus51 Have you tested first in 0.18dev before posting (as we ask in the enormous yellow banner at the top of the page)?
    We also ask very clearly at the top of the page not to post bugs (especially v0.17) unless they are verified in the forum.
    Please download 0.18dev and verify 0003794 0003795 0003796
    (0012538)
    markus51   
    2019-01-28 12:00   
    The same problem exists on version 0.18dev
    (0012554)
    Kunda1   
    2019-01-29 18:19   
    Making an 0.18 target. Devs please review (and decide if it should be in the 0.18 or 0.19 roadmap) Thanks.
    (0012704)
    yorik   
    2019-02-20 13:18   
    This is because the shortuct key "V" is used by the vertical constraint. So V1, V2... never happens.

    I don't see any obvious solution here, either remap V1-->V7 to something else or remap V to something else...
    (0012728)
    Dargazo   
    2019-02-22 23:10   
    Because the "V" shortcut is a subset of the "V + n" (with n = 1, 2, 3, ...) shortcut, I am thinking that we might need to have a look at the activatedAmbiguously QT signal. Maybe this will give more insight. Perhaps it is triggered, but no SLOT is attached?

    I'd like to test this out myself, but after having tried to compile + debug run the current FreeCAD 0.18 version multiple times today (Windows 10 + VS 2013 + libpack), I am done for today :)
    (0016104)
    chennes   
    2021-12-16 21:33   
    These no longer map to the vertical constraints, but are now being used for the view orientation. This is still not the "draw style", however.
    (0016707)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5872.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4343 [OpenSCAD] Bug minor always 2020-05-14 20:46 2021-12-16 19:45
    Reporter: denns Platform:  
    Assigned To: looo OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    Summary: OpenSCAD broken with AppImage
    Description:




    Attempting to use OpenSCAD features results in the following error:
    
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/home/denns/tmp/freecadapp/squashfs-root/usr/Mod/OpenSCAD/importCSG.py", line 105, in insert
        tmpfile=callopenscad(filename)
      File "/home/denns/tmp/freecadapp/squashfs-root/usr/Mod/OpenSCAD/OpenSCADUtils.py", line 179, in callopenscad
        check_output2([osfilename,'-o',outputfilename, inputfilename])
      File "/home/denns/tmp/freecadapp/squashfs-root/usr/Mod/OpenSCAD/OpenSCADUtils.py", line 158, in check_output2
        raise OpenSCADError('%s %s\n' % (stdoutd.strip(),stderrd.strip()))
    <class 'OpenSCADUtils.OpenSCADError'>: " /usr/bin/openscad: /home/denns/tmp/freecadapp/squashfs-root/usr/lib/libQt5Core.so.5: version `Qt_5.14' not found (required by /usr/bin/openscad)\n/usr/bin/openscad: /home/denns/tmp/freecadapp/squashfs-root/usr/lib/libQt5Core.so.5: version `Qt_5.13' not found (required by /usr/lib/libqscintilla2_qt5.so.15)\n"
    

    This is caused by a mismatch between the version of QT in the AppImage and the version used by OpenSCAD (outside of the AppImage). It can be fixed by unsetting LD_LIBRARY_PATH in prior to calling OpenSCAD.
    Tags: #lowhangingfruit, appimage, OpenSCAD, packaging
    Steps To Reproduce: Import an OpenSCAD file with the AppImage release of OpenSCAD. Tested on Arch linux with 0.18.
    Additional Information: Forum discussion: https://forum.freecadweb.org/viewtopic.php?t=40848

    Patch for 0.18 (tested working for me):
    
    148c148,153
    <         kwargs.update({'stdout':subprocess.PIPE,'stderr':subprocess.PIPE})
    ---
    >         env = os.environ.copy()
    >         try:
    >             env.pop('LD_LIBRARY_PATH')
    >         except KeyError:
    >             None
    >         kwargs.update({'stdout':subprocess.PIPE,'stderr':subprocess.PIPE,'env':env})
    

    Patch for git master:
    
    157c157,162
    <         kwargs.update({'stdout':subprocess.PIPE,'stderr':subprocess.PIPE})
    ---
    >         env = os.environ.copy()
    >         try:
    >             env.pop('LD_LIBRARY_PATH')
    >         except KeyError:
    >             None
    >         kwargs.update({'stdout':subprocess.PIPE,'stderr':subprocess.PIPE,'env':env})
    
    Attached Files:
    Notes
    (0015436)
    Kunda1   
    2021-02-25 19:40   
    @denns sorry about neglecting this. Not sure what happened is this still an issue that requires this patch?
    (0015437)
    Kunda1   
    2021-02-25 19:51   
    opened ticket on https://github.com/FreeCAD/FreeCAD-AppImage/issues/56
    (0015505)
    Kunda1   
    2021-03-13 17:55   
    What's blocking is a missing openscad package on conda. Anyone willing to create one?
    (0016896)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6063.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4284 [GCS] Bug minor always 2020-03-08 06:55 2021-12-16 13:20
    Reporter: chrisb Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: macOS High Sierra (10.13)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.19717 (Git)
    Build type: Release
    Branch: master
    Hash: 43e6be9020199e6453653e1b041679679efee574
    Python version: 3.8.1
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: C/Default (C)
    Summary: Solver reports false positive redundancy message after applying equality
    Description: In certain cases the solver can - after having applied an equality constraint - report a false redundancy message.
    Forum discussion.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016097)
    chrisb   
    2021-12-16 13:20   
    Thsi seems to be the same issue with multiple equality constraints: forum topic.
    (0016872)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6038.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4713 [Sketcher] Bug crash have not tried 2021-07-25 18:53 2021-12-15 09:44
    Reporter: orionrobots Platform: Intel  
    Assigned To: OS: MacOS  
    Priority: normal OS Version: 11.4 (20F71)  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: macOS 10.16
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24291 (Git)
    Build type: Release
    Branch: (HEAD detached at 0.19.2)
    Hash: 7b5e18a0759de778b74d3a5c17eba9cb815035ac
    Python version: 3.8.8
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: C/Default (C)
    Summary: Crash when editing patterns in sketch workbench
    Description: I have been trying to make a complex pattern - the holes in a breadboard. I have a face and sketching on the face, I create first a construction line 4.5mm from the side of the board.
    I then made a 1.5mm square.
    I created a pattern of 2 x 5 of these, at 2.54mm separation. I used the symmetry tool to place the 2 columns on either side of the construction line.

    Making sure the angle was good and that it made sense, I then attempted to create a pattern of 5x1 f these 2x5 blocks. I had made a number of attempts to get the parameters correct - 4 or 5 attempts to adjust and then undo loops to get the style I wanted. However, at the last undo, FreeCAD crashed.
    Tags: #tobeclosed
    Steps To Reproduce: * Make a pattern in sketch mode - with multiple columns.
    * Make a further pattern of these patterns.
    * Adjust these - lengths, and angles.
    * Undo a retry with different row/column counts.
    * Attempt to recreate the patterns.
    Additional Information: Backtrace/report:

    See backtrace in attached log2.txt
    Attached Files: Screenshot 2021-08-07 at 15.23.54.png (310,483 bytes) 2021-08-07 14:31
    https://tracker.freecad.org/file_download.php?file_id=2684&type=bug
    Screenshot 2021-08-07 at 15.24.10.png (80,182 bytes) 2021-08-07 14:31
    https://tracker.freecad.org/file_download.php?file_id=2685&type=bug
    log2.txt (3,695 bytes) 2021-12-15 09:42
    https://tracker.freecad.org/file_download.php?file_id=2738&type=bug
    Notes
    (0015749)
    orionrobots   
    2021-07-25 18:54   
    Please can this be moved to sketcher? It should be there.
    (0015759)
    Kunda1   
    2021-07-27 23:56   
    @oriobrobots Thanks for the report. In general we ask users to first post to the forum. Because this for example may be fixed in the 0.20 dev version. For now, do you mind installing the weekly-build and testing to see if the crash still happens? https://github.com/FreeCAD/FreeCAD-Bundle/releases/tag/weekly-builds
    (0015780)
    Kunda1   
    2021-08-07 11:32   
    @orionrobots bump
    (0015782)
    orionrobots   
    2021-08-07 14:31   
    Build: OS: macOS 10.16
    Word size of FreeCAD: 64-bit
    Version: 0.20.25311 (Git)
    Build type: Release
    Branch: master
    Hash: c5524bb58a7126fa2242d6137eb82ee9d54e82d4
    Python version: 3.9.6
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.5.2
    Locale: C/Default (C)

    Steps taken:
    * Part Design
    * New part
    * Sketch - XY Plane.
    * Create rect - consider it the outer rect for this sketch
    * Use the symmetry constraint - horiz/vertical.
    * Shift-D constrain both (let's say 54mm by 84mm for example). Should be fully constrained.
    * Close sketch and Pad this 10mm.
    * Select top surface, then tasks, create sketch.
    * Create external geom references to the four edges.
    * Create a further rect - make it 2mm on the vertical left. Make other edge equal.
    * Select the 4 edges of this shape.
    * Create array -> 5 x 2 - drag 90 degrees. It won't be spot on, so double click the angle - set to -90. Select the distance, and set it to 2.54mm.
    * This is where I perform an undo step - since 2mm would be too large. Undo until there's no array - just the rect.
    * Set the rect edge to 1.5mm.
    * Reseelect, create 5 by 2 array. Reset -90 and 2.54mm.
    * Select the existing array. Now we create a further array of these. we want a 5 x 1 array, still at -90 ish.
    * Set the distance for the second array to 6.54mm apart. This won't give quite the right result. Ctrl -z and redo as 6 * 2.54mm.
    * Set the angle to exactly -90. FreecCAD will start feeling slow at this point.
    * Find the two middle rectangles. on the left-most edge, select the two points, and the horizontal centre line - perform a symmetry constraint. This will take some time to resolve. And didn't behave as expected (that rect had moved, with the whole reference group moving, but not by the same amount).
    * ctrl-z to undo. Try a top and bottom point - and perform symmetry with them. Again - this will take some time to resolve. And still be wrong - ctrl-z and wait.
    * Try top and bottom of middle set... result is still wrong, and it took ages to resolve.

    Good news - I don't seem to be making it crash - but it is slow and not creating the symmetry I expect.
    * I finally get it symmetrical by selecting the middle rectangle of the second column in the middle array.
    * Create a dimension - 2.54mm horizontal to the one of the left edge points.
    * Select the whole array (Freecad will stall here) - mirror around the vertical centre line. Long time - but no crash. The view is pretty cluttered - but it's still alive.
    * To enforce the mirror - select the rightmost top point of the left array, and the mirror point on the right array, then the vertical centre line. Add a symmetry constraint. Takes a while - but succeeds.
    * The sketch seems under constrained - so use the under-constrained to see where the problem is, and on this basis, make a symmetry constraint for the points of the middle box of the right array to match the symmetry constraint on the left array - this constraint didn't get mirrored.

    Should be fully constrained. Cut this into the original shape 5mm.

    It' looks like I can't reproduce the crash. We can close this.
    (0015791)
    jnxd   
    2021-08-10 07:26   
    @orionrobots, is there any reason you want to make a pattern in sketcher rather than trying to make a pattern of the pocket made from just one rectangle? That might be able to make your life a little easier. We should move this discussion to the forum.
    (0015839)
    Kunda1   
    2021-08-20 14:35   
    @orionrobots please open a new thread per @jnxd comment in 0004713:0015791 and x-post to here
    (0015848)
    orionrobots   
    2021-08-21 21:24   
    Ok - thread opened at https://forum.freecadweb.org/viewtopic.php?f=3&t=61418
    (0016095)
    yorik   
    2021-12-15 09:42   
    (Last edited: 2021-12-15 09:44)
    Put the backtrace of the OP in an attached txt file to workaround export issues
    (0017074)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6243.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4800 [FreeCAD] Feature trivial always 2021-12-11 21:35 2021-12-14 17:11
    Reporter: roipoussiere Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: <!--ATTENTION:
    COMPLETELY ERASE THIS AFTER PASTING YOUR
    Help > About FreeCAD > Copy to clipboard
    NOTE: just the snippet alone will do without anything else included.
    The ticket will not be submitted without it.
    -->
    Summary: customize window: merge SpaceBall Movement and SpaceBall Buttons tabs
    Description: The "SpaceBall Movement" and "SpaceBall buttons" tabs takes a lot of place.

    The tab bar could be more clean and concise if those tabs was merged in one "Spaceball" tab.

    With default size, the window is even not large enough to disaply all the tabs (at least in French, didn't tried in other languages).
    Tags: #post-to-forum
    Steps To Reproduce:
    Additional Information:
    Attached Files: image.png (16,818 bytes) 2021-12-11 21:35
    https://tracker.freecad.org/file_download.php?file_id=2735&type=bug
    Notes
    (0016085)
    openBrain   
    2021-12-14 11:05   
    @roipoussiere : please proceed according our reporting guidelines by first discussing your request in our forum. Thx
    (0016093)
    roipoussiere   
    2021-12-14 17:11   
    forum thread: https://forum.freecadweb.org/viewtopic.php?f=34&t=64533
    (0017123)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6292.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4805 [FreeCAD] Feature minor have not tried 2021-12-12 13:15 2021-12-14 16:52
    Reporter: roipoussiere Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Ubuntu 20.04.3 LTS (KDE/plasma)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24291 (Git) AppImage
    Build type: Release
    Branch: (HEAD detached at 0.19.2)
    Hash: 7b5e18a0759de778b74d3a5c17eba9cb815035ac
    Python version: 3.8.8
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: French/France (fr_FR)
    Summary: use a more explicit file name for backup files
    Description: The presence of some files like
    project.FCStd1
    that I didn't created really confused me. After some research I discovered that it was a backup file.

    I may suggest to rename it to
    .project.FCStd1.backup
    instead.

    First, .backup makes the purpose of the file explicit.
    Then, the presence of the dot hides the file (so it doesn't bother the user, when there are many FC files in the same folder) and it also avoid to commit it unintentionally.
    Tags: #post-to-forum
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016089)
    openBrain   
    2021-12-14 11:06   
    @roipoussiere : please proceed according our reporting guidelines by first discussing your request in our forum. Thx
    (0016090)
    roipoussiere   
    2021-12-14 16:52   
    I just created forum thread for this suggestion: https://forum.freecadweb.org/viewtopic.php?f=34&t=64530
    (0017126)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6295.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4806 [PartDesign] Bug minor always 2021-12-14 01:34 2021-12-14 01:34
    Reporter: garya Platform: PC  
    Assigned To: OS: FreeBSD  
    Priority: normal OS Version: 11.4-RELEASE  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: FreeBSD 11.4-RELEASE-p6 (XFCE/xfce)
    Word size of FreeCAD: 64-bit
    Version: 0.20.master
    Build type: Release
    Python version: 3.7.9
    Qt version: 5.15.2
    Coin version: 4.0.0
    OCC version: 7.5.0
    Locale: C/Default (C)
    Summary: Part Design, moving sketch from one body to a new body removes other features from the original body.
    Description: Moving a sketch from one body to a new body removes other features from the original body.
    Tags: Part Design
    Steps To Reproduce: Open the file tmp_StripCut1.FCStd from this topic:
      https://forum.freecadweb.org/viewtopic.php?f=3&t=64463&p=553269#p553269
    Create a new body.
    Right click on Sk_Cut2_HoldDown and choose "Move object to other body"; use Body001 and click "OK"
    Additional Information:
    Attached Files:
    Notes
    (0017127)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6296.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4760 [FreeCAD] Bug crash always 2021-10-08 04:23 2021-12-13 23:45
    Reporter: electro707 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Arch Linux (KDE/plasma)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24291 (Git)
    Build type: Release
    Branch: makepkg
    Hash: 7b5e18a0759de778b74d3a5c17eba9cb815035ac
    Python version: 3.9.6
    Qt version: 5.15.2
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: English/United States (en_US)
    Summary: Crashing when extending dimension
    Description: When changing the length of a certain sketch's geometry in the attached file from 3mm to 4mm or 5mm, FreeCAD crashes with the attached debug trace with a segmentation fault.
    Tags: #post-to-forum
    Steps To Reproduce: Open at the attached file
    Edit Sketch001
    Change the 3mm dimension to 5mm
    Exit out of editing the sketch
    Additional Information: Program received signal SIGSEGV, Segmentation fault.
    #0 /usr/lib/libc.so.6(+0x3cda0) [0x7f8b333aeda0]
    #1 0x7f8a7913bae8 in Geom2d_Curve::Value(double) const from /usr/lib/libTKG2d.so.7+0x18
    0000002 0x7f8a7b5ba94d in ChFi3d_Builder::PerformMoreThreeCorner(int, int) from /usr/lib/libTKFillet.so.7+0xb73d
    0000003 0x7f8a7b59db6f in ChFi3d_Builder::PerformIntersectionAtEnd(int) from /usr/lib/libTKFillet.so.7+0x80bf
    0000004 0x7f8a7b5a28ac in ChFi3d_Builder::PerformOneCorner(int, bool) from /usr/lib/libTKFillet.so.7+0x2d2c
    0000005 0x7f8a7b53fa59 in ChFi3d_Builder::PerformFilletOnVertex(int) from /usr/lib/libTKFillet.so.7+0x499
    0000006 0x7f8a7b540ad3 in ChFi3d_Builder::Compute() from /usr/lib/libTKFillet.so.7+0xfa3
    0000007 0x7f8a7b6d52ce in BRepFilletAPI_MakeFillet::Build() from /usr/lib/libTKFillet.so.7+0x2e
    0000008 0x7f89dc5a7479 in PartDesign::Fillet::execute() from /usr/lib/freecad/lib/_PartDesign.so+0x3e9
    0000009 0x7f8b352e3f62 in App::DocumentObject::recompute() from /usr/lib/freecad/lib/libFreeCADApp.so+0x122
    0000010 0x7f8a8c76bdea in Part::Feature::recompute() from /usr/lib/freecad/lib/Part.so+0xa
    0000011 0x7f8b3525fead in App::Document::_recomputeFeature(App::DocumentObject*) from /usr/lib/freecad/lib/libFreeCADApp.so+0x33d
    0000012 0x7f8b3527b314 in App::Document::recompute(std::vector<App::DocumentObject*, std::allocator<App::DocumentObject*> > const&, bool, bool*, int) from /usr/lib/freecad/lib/libFreeCADApp.so+0x8f4
    0000013 0x7f8b35335eed in App::DocumentPy::recompute(_object*) from /usr/lib/freecad/lib/libFreeCADApp.so+0x2dd
    0000014 0x7f8b353360b9 in App::DocumentPy::staticCallback_recompute(_object*, _object*) from /usr/lib/freecad/lib/libFreeCADApp.so+0x29
    0000015 /usr/lib/libpython3.9.so.1.0(+0x148f08) [0x7f8b34ba2f08]
    0000016 /usr/lib/libpython3.9.so.1.0(_PyObject_MakeTpCall+0x2e3) [0x7f8b34b8b333]
    0000017 /usr/lib/libpython3.9.so.1.0(_PyEval_EvalFrameDefault+0x52a8) [0x7f8b34b87218]
    0000018 /usr/lib/libpython3.9.so.1.0(+0x126fd9) [0x7f8b34b80fd9]
    0000019 /usr/lib/libpython3.9.so.1.0(_PyEval_EvalCodeWithName+0x51) [0x7f8b34b80c41]
    0000020 /usr/lib/libpython3.9.so.1.0(PyEval_EvalCode+0x23) [0x7f8b34c37ae3]
    0000021 /usr/lib/libpython3.9.so.1.0(+0x1ed9f4) [0x7f8b34c479f4]
    0000022 /usr/lib/libpython3.9.so.1.0(+0x1e96cb) [0x7f8b34c436cb]
    0000023 /usr/lib/libpython3.9.so.1.0(PyRun_StringFlags+0xa0) [0x7f8b34c3c330]
    0000024 0x7f8b34f48cfc in Base::InterpreterSingleton::runString[abi:cxx11](char const*) from /usr/lib/freecad/lib/libFreeCADBase.so+0x6c
    0000025 0x7f8b35b23656 in Gui::Command::_runCommand(char const*, int, Gui::Command::DoCmd_Type, char const*) from /usr/lib/freecad/lib/libFreeCADGui.so+0x96
    0000026 0x7f8b35b237e6 in Gui::Command::_doCommand(char const*, int, Gui::Command::DoCmd_Type, char const*, ...) from /usr/lib/freecad/lib/libFreeCADGui.so+0xe6
    0000027 0x7f8b35b23915 in Gui::Command::updateActive() from /usr/lib/freecad/lib/libFreeCADGui.so+0x45
    0000028 0x7f89d902e583 in SketcherGui::ViewProviderSketch::unsetEdit(int) from /usr/lib/freecad/lib/SketcherGui.so+0x1f3
    0000029 0x7f8b35e5d773 in Gui::ViewProvider::finishEditing() from /usr/lib/freecad/lib/libFreeCADGui.so+0x13
    0000030 0x7f8b35aa781d in Gui::Document::_resetEdit() from /usr/lib/freecad/lib/libFreeCADGui.so+0x9d
    0000031 0x7f8b35a39dda in Gui::Application::setEditDocument(Gui::Document*) from /usr/lib/freecad/lib/libFreeCADGui.so+0x3a
    0000032 0x7f8b35ad2522 in Gui::DocumentPy::resetEdit(_object*) from /usr/lib/freecad/lib/libFreeCADGui.so+0x32
    0000033 0x7f8b35ad2559 in Gui::DocumentPy::staticCallback_resetEdit(_object*, _object*) from /usr/lib/freecad/lib/libFreeCADGui.so+0x29
    0000034 /usr/lib/libpython3.9.so.1.0(+0x148f08) [0x7f8b34ba2f08]
    0000035 /usr/lib/libpython3.9.so.1.0(_PyObject_MakeTpCall+0x2e3) [0x7f8b34b8b333]
    0000036 /usr/lib/libpython3.9.so.1.0(_PyEval_EvalFrameDefault+0x52a8) [0x7f8b34b87218]
    0000037 /usr/lib/libpython3.9.so.1.0(+0x126fd9) [0x7f8b34b80fd9]
    0000038 /usr/lib/libpython3.9.so.1.0(_PyEval_EvalCodeWithName+0x51) [0x7f8b34b80c41]
    #39 /usr/lib/libpython3.9.so.1.0(PyEval_EvalCode+0x23) [0x7f8b34c37ae3]
    #40 /usr/lib/libpython3.9.so.1.0(+0x1ed9f4) [0x7f8b34c479f4]
    0000041 /usr/lib/libpython3.9.so.1.0(+0x1e96cb) [0x7f8b34c436cb]
    0000042 /usr/lib/libpython3.9.so.1.0(PyRun_StringFlags+0xa0) [0x7f8b34c3c330]
    0000043 0x7f8b34f48cfc in Base::InterpreterSingleton::runString[abi:cxx11](char const*) from /usr/lib/freecad/lib/libFreeCADBase.so+0x6c
    0000044 0x7f8b35b23656 in Gui::Command::_runCommand(char const*, int, Gui::Command::DoCmd_Type, char const*) from /usr/lib/freecad/lib/libFreeCADGui.so+0x96
    0000045 0x7f8b35b237e6 in Gui::Command::_doCommand(char const*, int, Gui::Command::DoCmd_Type, char const*, ...) from /usr/lib/freecad/lib/libFreeCADGui.so+0xe6
    0000046 0x7f89d905f529 in SketcherGui::TaskDlgEditSketch::reject() from /usr/lib/freecad/lib/SketcherGui.so+0x159
    0000047 0x7f8b35dd5979 in Gui::TaskView::TaskView::reject() from /usr/lib/freecad/lib/libFreeCADGui.so+0x69
    0000048 /usr/lib/libQt5Core.so.5(+0x2f07a0) [0x7f8b33a5f7a0]
    0000049 /usr/lib/libQt5Widgets.so.5(+0x2ff761) [0x7f8b346a4761]
    0000050 /usr/lib/libQt5Core.so.5(+0x2f07a0) [0x7f8b33a5f7a0]
    0000051 0x7f8b345f74e3 in QAbstractButton::clicked(bool) from /usr/lib/libQt5Widgets.so.5+0x43
    0000052 /usr/lib/libQt5Widgets.so.5(+0x25276c) [0x7f8b345f776c]
    0000053 /usr/lib/libQt5Widgets.so.5(+0x254374) [0x7f8b345f9374]
    0000054 0x7f8b345f9595 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) from /usr/lib/libQt5Widgets.so.5+0xf5
    0000055 0x7f8b345430be in QWidget::event(QEvent*) from /usr/lib/libQt5Widgets.so.5+0x20e
    0000056 0x7f8b344ffd62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /usr/lib/libQt5Widgets.so.5+0x82
    0000057 0x7f8b34507ac9 in QApplication::notify(QObject*, QEvent*) from /usr/lib/libQt5Widgets.so.5+0xaa9
    0000058 0x7f8b35af2ab9 in Gui::GUIApplication::notify(QObject*, QEvent*) from /usr/lib/freecad/lib/libFreeCADGui.so+0x89
    0000059 0x7f8b33a283ba in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /usr/lib/libQt5Core.so.5+0x13a
    0000060 0x7f8b3450657b in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool, bool) from /usr/lib/libQt5Widgets.so.5+0x1bb
    0000061 /usr/lib/libQt5Widgets.so.5(+0x1b7a84) [0x7f8b3455ca84]
    0000062 /usr/lib/libQt5Widgets.so.5(+0x1badb5) [0x7f8b3455fdb5]
    0000063 0x7f8b344ffd62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /usr/lib/libQt5Widgets.so.5+0x82
    0000064 0x7f8b35af2ab9 in Gui::GUIApplication::notify(QObject*, QEvent*) from /usr/lib/freecad/lib/libFreeCADGui.so+0x89
    0000065 0x7f8b33a283ba in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /usr/lib/libQt5Core.so.5+0x13a
    0000066 0x7f8b33e031f0 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) from /usr/lib/libQt5Gui.so.5+0x6b0
    0000067 0x7f8b33dd87d5 in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /usr/lib/libQt5Gui.so.5+0xb5
    0000068 /usr/lib/libQt5XcbQpa.so.5(+0x62fcc) [0x7f8b2df7ffcc]
    0000069 /usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x26c) [0x7f8b317a44dc]
    0000070 /usr/lib/libglib-2.0.so.0(+0xa8749) [0x7f8b317f8749]
    0000071 /usr/lib/libglib-2.0.so.0(g_main_context_iteration+0x31) [0x7f8b317a1bc1]
    0000072 0x7f8b33a80fe6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /usr/lib/libQt5Core.so.5+0x66
    0000073 0x7f8b33a26d2c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) from /usr/lib/libQt5Core.so.5+0x12c
    0000074 0x7f8b33a2f294 in QCoreApplication::exec() from /usr/lib/libQt5Core.so.5+0x94
    0000075 0x7f8b35a4482e in Gui::Application::runApplication() from /usr/lib/freecad/lib/libFreeCADGui.so+0x1b9e
    0000076 freecad(+0x4858) [0x560a8a909858]
    0000077 /usr/lib/libc.so.6(__libc_start_main+0xd5) [0x7f8b33399b25]
    0000078 freecad(+0x4b8e) [0x560a8a909b8e]
    Attached Files: bench_meter.FCStd (69,264 bytes) 2021-10-08 04:23
    https://tracker.freecad.org/file_download.php?file_id=2712&type=bug
    Notes
    (0015962)
    electro707   
    2021-10-08 04:42   
    Note: This is also an issue in the most recent git version:
    OS: Arch Linux (KDE/plasma)
    Word size of FreeCAD: 64-bit
    Version: 0.20.25997 (Git)
    Build type: Release
    Branch: master
    Hash: 77b198048a63f1e9ca15eef64c8042d599a14cf3
    Python version: 3.9.7
    Qt version: 5.15.2
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: English/United States (en_US)
    (0015971)
    openBrain   
    2021-10-13 14:14   
    @electro707 : could you please open a new thread in our forum (per our reporting guidelines) and add link here ? Thx
    (0015990)
    electro707   
    2021-10-16 04:54   
    (Last edited: 2021-10-16 04:54)
    Created, as https://forum.freecadweb.org/viewtopic.php?f=3&t=62912
    (0015995)
    electro707   
    2021-10-22 03:09   
    Issue is closed due to issue #992 as mentioned in the forum thread.
    (0016080)
    wmayer   
    2021-12-12 15:38   
    It crashes with OCC 7.3 and I get the same stack trace. However, it's an OCC bug and when using the latest version 7.6 it doesn't crash any more but only creates an invalid shape.
    (0017100)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6269.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4746 [Arch] Bug minor always 2021-09-21 09:16 2021-12-13 17:22
    Reporter: robocat Platform: Windows  
    Assigned To: OS: Windows 10  
    Priority: normal OS Version: 2009  
    Status: assigned Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Windows 10 Version 2009
    Word size of FreeCAD: 64-bit
    Version: 0.20.25645 (Git)
    Build type: Release
    Branch: master
    Hash: 37d9757399b4c2ec30318eb88d7cd7c508246345
    Python version: 3.8.6+
    Qt version: 5.15.2
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: English/United Kingdom (en_GB)
    Summary: Section View Shows Hidden Stairs
    Description: Upon making a simple level containing a floor with a staircase going through it in BIM, a problem is found whereby if the staircase is of structure "One stringer" or "Two stringers", any section view of that staircase will be faulty. (Please see example files).

    By putting the section into a TechDraw ArchView the result is that the entire staircase is shown on top of other geometry regardless of if it is obscured by the floor or even if it is above the horizontal section plane.

    For the prior forum discussion see: https://forum.freecadweb.org/viewtopic.php?f=23&t=62227

    The suspected affected parts of FreeCAD are: "both Stairs and ArchSection/TechDraw-ArchView has some bug" - paullee

    The summary of the discussion: "So, to summarize, "Structure" - "One Stringer" / "Two Stringer" are broken somehow, and no solid is resulted and thus the strange error. Making Riser / Tread Thickness > 0 make Stair return solid, thus also 'fix the problem'." - paullee

    The current workaround is to set "Structure" to "Massive" or change "Riser Thickness" from 0 to 1.
    Tags: Arch, BIM, section, TechDraw
    Steps To Reproduce: 1. In the BIM workbench create a slab with a hole in it.
    2. Create a wall next to the hole in the floor.
    3. Add a staircase through the hole.
    4. Set the staircase structure property to "One stringer" or "Two stringers".
    5. Move all these components into a level.
    6. Section plane the level. This should be horizontally by default. This should also pass through the staircase. If it does not make the staircase longer by increasing Height and Length properties.
    7.Swap to the TechDraw workbench.
    8. Insert default page.
    9. Click on the section in the tree and then click Insert Arch Workbench Object
    10. Change the "Scale" of the ArchView if needed (0.02) and change the "Line Width" and "Cut Line Width" if needed (0.2).
    Additional Information:
    Attached Files: 3d view.png (230,761 bytes) 2021-09-21 09:16
    https://tracker.freecad.org/file_download.php?file_id=2695&type=bug
    archview.png (132,959 bytes) 2021-09-21 09:16
    https://tracker.freecad.org/file_download.php?file_id=2696&type=bug
    staircase_test.FCStd (70,133 bytes) 2021-09-21 09:16
    https://tracker.freecad.org/file_download.php?file_id=2697&type=bug
    Notes
    (0016081)
    wandererfan   
    2021-12-12 18:54   
    This can't be fixed in TechDraw. Arch created the view using SVG and TechDraw just displays whatever it is given.
    (0016082)
    paullee   
    2021-12-13 00:20   
    Can change the Project from TechDraw to Arch ?
    (0016083)
    chennes   
    2021-12-13 02:47   
    I've changed the project this is categorized under from TechDraw to Arch.
    (0016084)
    paullee   
    2021-12-13 17:22   
    Thanks !
    (0017090)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6259.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4666 [FreeCAD] Bug major always 2021-05-24 14:36 2021-12-09 11:50
    Reporter: tarun.johar Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Ubuntu 20.04.2 LTS (KDE/plasma)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24291 (Git) AppImage
    Build type: Release
    Branch: (HEAD detached at 0.19.2)
    Hash: 7b5e18a0759de778b74d3a5c17eba9cb815035ac
    Python version: 3.8.8
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: English/United States (en_US)
    Summary: Undo does not reset the document saved state
    Description: Undo does not reset the document saved state. The issue is reproducible with version 0.19 and 0.19.2

    The cylinder disappears but there is still a '*' in the document tab.

    We are developing a workbench that creates temporary objects for preview purposes. When an operation is canceled, the transaction is properly aborted but the document saved state is not reverted. Applications such as Emacs and LibreOffice keep track of the saved state as part of the undo stack, so this is a reasonable expectation for the user.
    Tags:
    Steps To Reproduce: Steps to reproduce:

    1. Create a new document
    2. Create a Part Design box
    3. Save the document
    4. There is no '*' next to the document name
    5. Create a Part Design cylinder
    6. There is a '*' next to the document name
    7. Select Edit | Undo
    Additional Information: The topic is already discussed at following Help on using FreeCAD forum link : viewtopic.php?f=3&t=58752&e=1&view=unread#unread
    Attached Files:
    Notes
    (0015678)
    tarun.johar   
    2021-05-28 18:50   
    Hi team,

    Can this be looked into?
    (0016071)
    wmayer   
    2021-12-09 11:50   
    https://forum.freecadweb.org/viewtopic.php?f=3&t=58752&p=504797#p504797
    (0017051)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6220.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4799 [FreeCAD] Bug minor always 2021-12-08 16:43 2021-12-08 16:43
    Reporter: drmacro Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Debian GNU/Linux 10 (buster) (XFCE/lightdm-xsession)
    Word size of FreeCAD: 64-bit
    Version: 0.20.26583 (Git)
    Build type: Release
    Branch: master
    Hash: 4bd77b3b35ea794057ffe6a55858b7b1abee7ed0
    Python version: 3.7.3
    Qt version: 5.11.3
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    Summary: Part Design Loft between two shapbinders fails, but Part Loft works with only an out of scope warning.
    Description: Part Design Loft between two shapbinders fails, but Part Loft works with only an out of scope warning.

    This inconsistent behavior; shapebinders can be used with Part Design Pad.

    In addition, A Part Sweep of a Part Helix and a shapebinder works, but the Part Design Helix also fails with a Shapebinder.

    Unless there is a specific reason the ShapeBinder can't work with Part Design tools, for consistency, it should work with none or all?

    Forum thread contains example file and discussion.
    Tags:
    Steps To Reproduce: Create two shapbinders and attempt to Loft, Helix etc.

    Forum thread contains example file and discussion.
    Additional Information:
    Attached Files:
    Notes
    (0017122)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6291.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4797 [Sketcher] Feature feature always 2021-12-05 14:25 2021-12-05 14:25
    Reporter: chrisb Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: macOS 10.16
    Word size of FreeCAD: 64-bit
    Version: 0.20.26155 (Git)
    Build type: Release
    Branch: master
    Hash: 0926a4148bcff11249fd4f56bc30256102ffe105
    Python version: 3.9.7
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.5.3
    Locale: C/Default (C)
    Summary: Do not mark the sketch as changed if it is only visited without any changes.
    Description: See option b2 in this forum discussion
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0017121)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6290.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4794 [Sketcher] Feature feature always 2021-11-29 18:50 2021-11-29 18:50
    Reporter: chrisb Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: macOS 10.16
    Word size of FreeCAD: 64-bit
    Version: 0.20.26375 (Git)
    Build type: Release
    Python version: 3.9.7
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.5.3
    Locale: C/Default (C)
    Summary: Remove CloseShape and ConnectLines
    Description: CloseShape and ConnectLines should be removed from Sketcher, see forum discussion.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0017120)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6289.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2100 [Spreadsheet] Feature tweak always 2015-05-14 05:34 2021-11-24 15:31
    Reporter: FreeCadder Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: feedback Product Version: 0.15  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    Summary: Spreadsheet: Additional Inverse Display Units
    Description: It would be nice if in addition to "K^-1" there could be cell display units like "1/K" or "/K" or "K?¹", see code below.
    Tags: #post-to-forum, spreadsheet
    Steps To Reproduce: App.newDocument("Unnamed")
    App.setActiveDocument("Unnamed")
    App.ActiveDocument=App.getDocument("Unnamed")
    Gui.ActiveDocument=Gui.getDocument("Unnamed")

    App.activeDocument().addObject('Spreadsheet::Sheet','Spreadsheet')
    App.ActiveDocument.Spreadsheet.set('B1', 'Feature /K')
    App.ActiveDocument.Spreadsheet.set('C1', 'Feature 1/K')
    App.ActiveDocument.Spreadsheet.set('D1', 'Feature 1/°C')
    App.ActiveDocument.Spreadsheet.set('E1', 'Feature 1/°F')
    App.ActiveDocument.Spreadsheet.set('F1', 'Feature K?¹')
    App.ActiveDocument.Spreadsheet.set('G1', 'Workaround K^-1')
    App.ActiveDocument.Spreadsheet.set('A2', 'Linear Expansion Coefficient')
    App.ActiveDocument.Spreadsheet.set('B2', '1.6e-4')
    App.ActiveDocument.Spreadsheet.set('C2', '1.6e-4')
    App.ActiveDocument.Spreadsheet.set('D2', '1.6e-4')
    App.ActiveDocument.Spreadsheet.set('E2', '1.6e-4')
    App.ActiveDocument.Spreadsheet.set('F2', '1.6e-4')
    App.ActiveDocument.Spreadsheet.set('G2', '1.6e-4')
    App.ActiveDocument.Spreadsheet.setDisplayUnit('B2', '/K')
    App.ActiveDocument.Spreadsheet.setDisplayUnit('C2', '1/K')
    App.ActiveDocument.Spreadsheet.setDisplayUnit('D2', '1/°F')
    App.ActiveDocument.Spreadsheet.setDisplayUnit('E2', '1/°C')
    App.ActiveDocument.Spreadsheet.setDisplayUnit('F2', 'K?¹')
    App.ActiveDocument.Spreadsheet.setDisplayUnit('G2', 'K^-1')
    App.ActiveDocument.Spreadsheet.setColumnWidth('A', 180)
    App.ActiveDocument.Spreadsheet.setColumnWidth('G', 120)

    App.ActiveDocument.recompute()
    # Application->Unnamed->Spreadsheet: "Show spreadsheet"
    Additional Information:
    Attached Files: code-utf8.txt (1,585 bytes) 2015-05-14 05:39
    https://tracker.freecad.org/file_download.php?file_id=1010&type=bug
    Notes
    (0006131)
    FreeCadder   
    2015-05-14 05:40   
    'K?¹' = U+004B U+207B U+00B9
    (0006132)
    FreeCadder   
    2015-05-14 06:29   
    (Last edited: 2015-05-14 06:44)
    # other useful workarounds
    App.ActiveDocument.Spreadsheet.set('H1', 'Workaround m/m/K')
    App.ActiveDocument.Spreadsheet.set('H2', '1.6e-4')
    App.ActiveDocument.Spreadsheet.setDisplayUnit('H2', 'm/m/K')
    App.ActiveDocument.Spreadsheet.set('I1', 'Workaround mm/m/K')
    App.ActiveDocument.Spreadsheet.set('I2', '1.6e-4')
    App.ActiveDocument.Spreadsheet.setDisplayUnit('I2', 'mm/m/K')
    App.ActiveDocument.Spreadsheet.setColumnWidth('H', 130)
    App.ActiveDocument.Spreadsheet.setColumnWidth('I', 130)
    App.ActiveDocument.recompute()

    # fails?
    App.ActiveDocument.Spreadsheet.set('J1', 'Workaround µm/m/K')
    App.ActiveDocument.Spreadsheet.set('J2', '1.6e-4')
    App.ActiveDocument.Spreadsheet.setDisplayUnit('J2', 'µm/m/K') # U+00B5
    App.ActiveDocument.Spreadsheet.setColumnWidth('J', 130)
    App.ActiveDocument.recompute()

    (0008263)
    Kunda1   
    2017-02-10 11:29   
    Reminder sent to: eivindkvedalen
    @eivindkvedalen would you kindly weigh in on this?
    (0009766)
    Kunda1   
    2017-07-17 11:21   
    @FreeCadder do you mind re-upping code-utf8.txt ?
    (0009999)
    Kunda1   
    2017-08-23 12:03   
    @FreeCadder do you mind re-upping code-utf8.txt ?
    (0011229)
    ulrich1a   
    2018-05-04 20:44   
    The unit Kelvin is available in FreeCAD.

    The above code does not work anymore. The code
    App.ActiveDocument.Spreadsheet.setDisplayUnit('B2', '/K')

    gives: Failed to parse expression. So there is some improvement in FreeCAD to avoid false expectations.

    What remains is the feature request for the addition of °C and °F to the quantity-framework.
    (0011666)
    Kunda1   
    2018-08-26 15:36   
    (Last edited: 2018-08-26 15:37)

    What remains is the feature request for the addition of °C and °F to the quantity-framework.

    ulrich1a

    @ulrich1a is there a feature request open for that yet ?

    (0013379)
    Kunda1   
    2019-07-23 23:44   
    @ulrich1a please respond

    Also @eivindkvedalen care to weigh in ?
    (0016464)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5629.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2472 [Spreadsheet] Feature feature N/A 2016-03-14 20:54 2021-11-24 15:30
    Reporter: Spindoctor Platform:  
    Assigned To: eivindkvedalen OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.15  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    Summary: Spreadsheet - Move Cells
    Description: TL;DR:
    It would be very convenient if there was a way to move (and/or copy/paste) cells in FreeCAD spreadsheets. This would really help to keep the variables stored in the spreadsheet organized.
    Tags: spreadsheet
    Steps To Reproduce:
    Additional Information: Long version:
    I started to use spreadsheets in FreeCAD 0.16. I use them to set "variables" I can later utilize in my sketches (and other parts of the model). This is a great feature I learned to love in OpenSCAD - I am glad I can do similar things in FreeCAD now.

    However, the spreasheet seems to lack some helpful features.

    One of them is the possibility to move cells. I would like to keep the spreadsheet (or the data inside) organized.
    Maybe I start by adding some basic information, like overall model height. I then leave a blank line below the first one and add some other information - let's say a thread radius. Later I decide the overall width of the model would also be helpful. I'd like to add that just below the overall model height and still have an empty line below. Without copy/paste or moving cells this is not really possible. (I could start over and make a new spreadsheet, but this is not desirable). Therefore the possibility to move cells would be great!
    Attached Files:
    Notes
    (0007005)
    eivindkvedalen   
    2016-04-25 17:23   
    You can insert and remove both rows and columns if you right click on the header names to the left and at the top. Moving by copy/cut and paste of individual cells are not yet supported (for the time being, FreeCAD only supports copying complete objects).
    (0009882)
    silopolis   
    2017-08-08 10:24   
    Copy/paste/move of cells and rows is indeed very much needed when the model grows in size and complexity. Designing a kitchen, I found myself modifying the spreadsheets for almost each new part and it's a "pain" not to have the complete basic set of features for cells/rows/columns manipulation.
    (0010873)
    silopolis   
    2018-01-27 08:06   
    A quick note to mention that the Spreadsheet Tools macro has some copy/cut/paste features, with content/aliases/formating handling (or at least will to). Needs a little of love and a better UI (toolbar buttons ? dockable panel ?) but was a game changer for the last couple of days keeping my spreadsheets in order :)
    (0016480)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5645.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3460 [Spreadsheet] Feature minor have not tried 2018-05-04 21:04 2021-11-24 15:30
    Reporter: ulrich1a Platform:  
    Assigned To: realthunder OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    Summary: Add the following functions to expressions and spreadsheet: concatenate text and indirect
    Description: It would be an advantage, if a spreadsheet can be filled with different sets of parameters to create a model and then just change one cell to select a certain parameter set.

    This can be done in a traditional spreadsheet with text concatenation and a line with indirect-functions that use the concatenated text as a cell-adress.

    Tags: expressions, spreadsheet
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0014186)
    realthunder   
    2020-02-27 05:54   
    Implemented with this commit in upstream. String can be concatenated using simple '+', or '%' similar to Python string formatter. Indirect reference can be done by just referring to another string property/cell.
    (0016623)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5788.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4003 [Spreadsheet] Bug major always 2019-06-06 03:36 2021-11-24 15:28
    Reporter: grog Platform: PC  
    Assigned To: OS: Windows 10  
    Priority: normal OS Version: 1803  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    Summary: Renaming spreadsheet no longer has any affect on field tags.
    Description: I have one computer with v0.17 and I can reliably change the Spreadsheet. Typically I rename it to 'S' for less typing. On my other computer which I just upgraded to v0.18 I can no longer reference tags by my typical S.tagname. I have to state Spreadsheet.tagname. I marked it as major as it's serious enough for me to downgrade to regain the functionality.
    Tags: spreadsheet
    Steps To Reproduce:
    1. new file
    2. Select Spreadsheet workbench and click on the spreadsheet icon to create a new spreadsheet.
    3. Select spreadsheet on navigation window.
    4. type: F2 - S (To rename the spreadsheet to 'S')
    5. enter a number in a cell
    6. [CTRL][SHIFT]a - <cell tag name>
    7. now switch to Part workbench
    8. create a primitave part
    9. select one of it's dimensions,
    10. click on the calculation icon, and enter S.tagname. (This fails in v0.18 but works in v0.17)
    11. now try Spreadsheet.tagname (This works)

    Thanks for an awesome program.
    GROG
    Additional Information: OS: Windows 10
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16110 (Git)
    Build type: Release
    Branch: (HEAD detached at upstream/releases/FreeCAD-0-18)
    Hash: f7dccfaa909e5b9da26bf50c4a22ccca9bb10c40
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    Attached Files:
    Notes
    (0013151)
    Kunda1   
    2019-06-06 14:30   
    (Last edited: 2019-06-06 14:30)
    Moved to Expressions category.
    @grog Please x-post this to the freecad forum to validate by the community (per our guidelines in the large yellow banner at the top of this page)

    (0013155)
    wmayer   
    2019-06-07 10:45   
    Forum link: https://forum.freecadweb.org/viewtopic.php?f=3&t=36877

    According to the replies there you have to write <<S>> instead of S.
    (0013265)
    Kunda1   
    2019-06-19 22:34   
    Per @openBrain this seems to look like a dupe of 0003379
    (0013466)
    grog   
    2019-08-25 14:55   
    Thus far the answer is to avoid problem characters for naming.
    Is there a simple way to change the Spreadsheet name and adjust the references to it? I created a nice collection of documents that can't be read in newer versions because of this bug.
    (0016777)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5943.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4410 [Spreadsheet] Feature feature N/A 2020-07-25 04:35 2021-11-24 15:22
    Reporter: TomB19 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    Summary: Feature Request: Spreadsheet zoom, as per Excel and LibreCalc
    Description: I would like to request the ability to zoom spreadsheets. This would be useful, as I appreciate being able to shrink the spreadsheet to get more information on the screen.

    This feature has been implemented using Python by OpenBrain and posted in the forum.

    This request is to add implement this feature, likely in C++, in the next release or whenever you feel appropriate.

    https://forum.freecadweb.org/viewtopic.php?f=3&t=48517
    Tags:
    Steps To Reproduce: https://forum.freecadweb.org/viewtopic.php?f=3&t=48517
    Additional Information:
    Attached Files:
    Notes
    (0016927)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6094.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4024 [Spreadsheet] Feature feature always 2019-06-17 10:00 2021-11-24 15:22
    Reporter: uwestoehr Platform:  
    Assigned To: OS:  
    Priority: high OS Version:  
    Status: confirmed Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    Summary: any change in a spreadsheet forces a recomputation of the whole part
    Description: Currently for each change in a spreadsheet a recompute is done. For larger projects this a big problem because a recompute easily took a minute or more.

    Formerly the same problem occurred for sketches. It was fixed by removing all invocations of an automatic recomputation from the code. The recomputation for sketches is now either done if the user manually clicks the Refresh button or when he leaves the sketch.

    So we need to do something similar for spreadsheets.
    Tags: spreadsheet
    Steps To Reproduce:
    Additional Information: Forum thread: https://forum.freecadweb.org/viewtopic.php?f=3&t=37060

    Confirmed by @wmayer

    OS: Windows 10
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16117 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-18
    Hash: dbb4cc6415bac848a294f03b80f65e888d531742
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: German/Germany (de_DE)
    Attached Files:
    Notes
    (0013464)
    kenjo   
    2019-08-23 05:06   
    I hit the same issue.
    https://forum.freecadweb.org/viewtopic.php?f=3&t=38591
    (0016782)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5948.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3560 [Spreadsheet] Bug minor always 2018-08-15 12:28 2021-11-24 15:22
    Reporter: lokomoko Platform:  
    Assigned To: eivindkvedalen OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    Summary: Renaming alias in spreadsheet changes the spreadsheet part of the reference from label to internal name
    Description: Renaming an alias in a spreadsheet changes the spreadsheet-part of a reference to the alias from Label (e.g. "MyInputData") to internal name/Id (e.g. "Spreadsheet001").

    Discussed in Forum under Renaming alias in spreadsheet changes the name of the spreadsheet in any reference
    Tags: equation, expressions, formula, spreadsheet
    Steps To Reproduce: 1. Create new document
    2. In spreadsheet workbench create a spreadsheet by the name "MyData"
    3. Create cell with an alias e.g. "BoxSize" and a value
    4. In part workbench create a 3D-object (e.g. cube) and therein a reference to the alias (e.g. "=MyData.BoxSize").
    5. In spreadsheet change name of alias to BoxLength

    Actual Result: The reference in the 3D-Object is "=Spreadsheet001.BoxLength" now, that is the alias was changed, but also the name of the spreadsheet
    Expected Result: The reference in the 3D-Object should be "=MyData.BoxLength"
    Additional Information: OS: Ubuntu 16.04.5 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.13528 (Git) AppImage
    Build type: None
    Branch: releases/FreeCAD-0-17
    Hash: 5c3f7bf8ec51e2c7187789f7edba71a7aa82a88b
    Python version: 2.7.6
    Qt version: 4.8.6
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: German/Germany (de_DE)
    Attached Files:
    Notes
    (0011625)
    lokomoko   
    2018-08-15 12:41   
    Direct link to forum topic Renaming alias in spreadsheet changes the name of the spreadsheet in any reference
    (0012176)
    wmayer   
    2018-11-11 11:27   
    When renaming an alias then at some point the functions Document::renameObjectIdentifiers, DocumentObject::renameObjectIdentifiers, PropertyExpressionEngine::renameObjectIdentifiers and ObjectIdentifier::relativeTo are called.
    Because the ObjectIdentifier hasn't explicitly set documentObjectName it gets the (internal) name from the pointer to the DocumentObject.
    (0016635)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5800.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2474 [Spreadsheet] Feature feature N/A 2016-03-14 22:38 2021-11-24 15:22
    Reporter: Spindoctor Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    Summary: Integrate LibreOffice Calc via GUI
    Description: A convenient way to integrate a spreadsheet from LibreOffice Calc via GUI would be nice to have
    Tags: spreadsheet
    Steps To Reproduce:
    Additional Information: The FreeCAD spreadsheets offer some awesome functionalities for FreeCAD while still being slim and fast. However, for some applications it is necessary to do more difficult calculations.

    Most of them would be more or less doable in FreeCAD spreadsheets but sometimes it can be more convenient to use a "full grown" spreadsheet program like LibreOffice Calc. For those cases an integration of LibreOffice Calc would be good.

    If this is going to be implemented one difficulty might be to handle cell aliases. LibreOffice however has that feature, see https://help.libreoffice.org/Calc/Naming_Cells
    Attached Files:
    Notes
    (0009881)
    silopolis   
    2017-08-08 09:02   
    Without a doubt, power of a full featured spreadsheet program should certainly be useful in a number of projects !
    AFAIC, linking models to external spreadsheets presents another VERY important and powerful advantage that is being able to centralize and share parameters between models. This would allow me to put all common parameters in a LO Calc "project sheet", and link/dynamicaly import it in all parts and assembly files.
    This way:
       * modifying a parameter in the central sheet would "spread" into the whole project
       * misses and errors in duplicating values and cells aliases in all spreadsheets in all project files would be avoided.
    Looking for a solution for this, I found this page https://freecad-tutorial.blogspot.fr/2011/10/oosheet-as-freecad-and-libreoffice.html which may present the beginning of a solution with 2 way (!) communication between a OO sheet and a FreeCAD model.
    (0009883)
    Kunda1   
    2017-08-08 17:12   
    @silopolis please open a forum thread to generate more community discussion on this topic. Thanks for the link. Very interesting.
    (0009895)
    silopolis   
    2017-08-12 19:14   
    Discussion opened here
    (0014230)
    Kunda1   
    2020-03-14 21:59   
    Integration attempt happening in https://github.com/myoldz/FC_LibreOffice.git
    (0014959)
    Kunda1   
    2020-11-03 15:08   
    Moved to https://github.com/myoldz/FC_Libre
    (0014960)
    Kunda1   
    2020-11-03 15:12   
    (Last edited: 2020-11-03 15:53)
    Another project thread by @salp (AKA myoldz on github) at https://forum.freecadweb.org/viewtopic.php?f=8&t=44005
    (0016481)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5646.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4792 [FreeCAD] Bug feature always 2021-11-24 13:12 2021-11-24 13:29
    Reporter: Carlos Machado Platform: Mac (Retina 5K, 27-inch, 2017)  
    Assigned To: OS: macOS  
    Priority: normal OS Version: OS: macOS 10.16  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: <!--ATTENTION:
    COMPLETELY ERASE THIS AFTER PASTING YOUR
    Help > About FreeCAD > Copy to clipboard
    NOTE: just the snippet alone will do without anything else included.
    The ticket will not be submitted without it.
    -->
    Summary: No ficheiro de trabalho que acaba de abrir a funcionalidade é bastante reduzida!
    Description: Boa tarde!

    Ao trabalhar neste ficheiro deparei-me com um arrasto na execução de qualquer comando a executar.
    Ao abrir dá-me esta mensagem: "12:25:23 3.1e-08 <App> Document.cpp(3172): The graph must be a DAG.".
    Estará relacionado?
    Tem resolução? Qual?
    Não esquecer que eu não entendo nada de programação!

    OS: macOS 10.16
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24291 (Git)
    Build type: Release
    Branch: (HEAD detached at 0.19.2)
    Hash: 7b5e18a0759de778b74d3a5c17eba9cb815035ac
    Python version: 3.8.8
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: C/Default (C)

    3,4 GHz Intel Core i5 de núcleo quádruplo
    40 GB 2400 MHz DDR4
    Radeon Pro 570 4 GB

    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016052)
    Carlos Machado   
    2021-11-24 13:29   
    Será que a reprodução seguinte ajuda?

    12:25:23 3.1e-08 <App> Document.cpp(3172): The graph must be a DAG.
    13:19:28 3224.01 <App> Document.cpp(3172): The graph must be a DAG.
    13:19:28 3245.17 <App> Document.cpp(3527): Altera____o#Extrude007 still touched after recompute
    13:19:28 3245.17 <App> Document.cpp(3527): Altera____o#Sketch027 still touched after recompute
    13:19:28 3245.17 <App> Document.cpp(3527): Altera____o#Extrude006 still touched after recompute
    13:19:28 3245.17 <App> Document.cpp(3527): Altera____o#Sketch019 still touched after recompute
    13:19:28 3245.17 <App> Document.cpp(3527): Altera____o#Extrude005 still touched after recompute
    13:19:28 3245.17 <App> Document.cpp(3527): Altera____o#Sketch018 still touched after recompute
    13:20:05 ----------------
    13:20:05 GuiCommand: Move
    13:20:05 Pick start point
    13:20:10 Pick end point
    13:20:51 3306.97 <App> Document.cpp(3172): The graph must be a DAG.
    13:20:51 3328.03 <App> Document.cpp(3527): Altera____o#Extrude007 still touched after recompute
    13:20:51 3328.03 <App> Document.cpp(3527): Altera____o#Sketch027 still touched after recompute
    13:20:51 3328.03 <App> Document.cpp(3527): Altera____o#Extrude006 still touched after recompute
    13:20:51 3328.03 <App> Document.cpp(3527): Altera____o#Sketch019 still touched after recompute
    13:20:51 3328.03 <App> Document.cpp(3527): Altera____o#Extrude005 still touched after recompute
    13:20:51 3328.03 <App> Document.cpp(3527): Altera____o#Sketch018 still touched after recompute
    13:21:58 3374.25 <App> Document.cpp(3172): The graph must be a DAG.
    13:21:58 3395.37 <App> Document.cpp(3527): Altera____o#Extrude007 still touched after recompute
    13:21:58 3395.37 <App> Document.cpp(3527): Altera____o#Sketch027 still touched after recompute
    13:21:58 3395.37 <App> Document.cpp(3527): Altera____o#Extrude006 still touched after recompute
    13:21:58 3395.37 <App> Document.cpp(3527): Altera____o#Sketch019 still touched after recompute
    13:21:58 3395.37 <App> Document.cpp(3527): Altera____o#Extrude005 still touched after recompute
    13:21:58 3395.37 <App> Document.cpp(3527): Altera____o#Sketch018 still touched after recompute
    13:24:09 3504.58 <App> Document.cpp(3172): The graph must be a DAG.
    13:24:09 3526.19 <App> Document.cpp(3527): Altera____o#Extrude007 still touched after recompute
    13:24:09 3526.19 <App> Document.cpp(3527): Altera____o#Sketch027 still touched after recompute
    13:24:09 3526.19 <App> Document.cpp(3527): Altera____o#Extrude006 still touched after recompute
    13:24:09 3526.19 <App> Document.cpp(3527): Altera____o#Sketch019 still touched after recompute
    13:24:09 3526.19 <App> Document.cpp(3527): Altera____o#Extrude005 still touched after recompute
    13:24:09 3526.19 <App> Document.cpp(3527): Altera____o#Sketch018 still touched after recompute
    13:25:23 3556.75 <App> Document.cpp(3172): The graph must be a DAG.
    13:25:23 3578.41 <App> Document.cpp(3527): Altera____o#Extrude007 still touched after recompute
    13:25:23 3578.41 <App> Document.cpp(3527): Altera____o#Sketch027 still touched after recompute
    13:25:23 3578.41 <App> Document.cpp(3527): Altera____o#Extrude006 still touched after recompute
    13:25:23 3578.41 <App> Document.cpp(3527): Altera____o#Sketch019 still touched after recompute
    13:25:23 3578.41 <App> Document.cpp(3527): Altera____o#Extrude005 still touched after recompute
    13:25:23 3578.41 <App> Document.cpp(3527): Altera____o#Sketch018 still touched after recompute
    13:25:23 3578.85 <App> Document.cpp(3172): The graph must be a DAG.
    13:25:23 3600.13 <App> Document.cpp(3527): Altera____o#Extrude007 still touched after recompute
    13:25:23 3600.13 <App> Document.cpp(3527): Altera____o#Sketch027 still touched after recompute
    13:25:23 3600.13 <App> Document.cpp(3527): Altera____o#Extrude006 still touched after recompute
    13:25:23 3600.13 <App> Document.cpp(3527): Altera____o#Sketch019 still touched after recompute
    13:25:23 3600.13 <App> Document.cpp(3527): Altera____o#Extrude005 still touched after recompute
    13:25:23 3600.13 <App> Document.cpp(3527): Altera____o#Sketch018 still touched after recompute
    (0017118)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6287.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3795 [FreeCAD] Feature minor always 2019-01-25 22:02 2021-11-23 21:38
    Reporter: markus51 Platform:  
    Assigned To: openBrain OS: Windows  
    Priority: low OS Version:  
    Status: feedback Product Version: 0.17  
    Product Build: Resolution: reopened  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Input of floating point values with point ('.') instead of comma (',')
    Description: I use FreeCad 0.17 with Win7, in Germany.
    The country settings uses a comma (',') for floating point values.

    Many peoples usees a point to input floating point valuses,
    but FreeCad needs sometimes a comma, or sometimes are comma and points allowed.

    Combo-View/Model: only comma
    Combo-View/Tracks/Constaints: only comma
    Spreadsheet: comma and points

    I would be nice when always both floating formats will be accepted.


     

    Tags: units
    Steps To Reproduce: 1.) Create a new sketch and add some constraints with a length
    2.) Double click in Combo-View/Tracks/Constraints on the new item
    3.) Input "12.3" and press ENTER
    4.) The new value is "123" instead of "12.3"

    11.) Create a new sketch and add some constraints with a length
    12.) Double click in Combo-View/Model on a Constraint
    13.) Input "12.3" and press ENTER
    14.) The new value is "123" instead of "12.3"

    Additional Information:
    Attached Files:
    Notes
    (0012517)
    Kunda1   
    2019-01-25 23:16   
    @markus51 Have you tested first in 0.18dev before posting (as we ask in the enormous yellow banner at the top of the page)?
    We also ask very clearly at the top of the page not to post bugs (especially v0.17) unless they are verified in the forum.
    Please download 0.18dev and verify 0003794 0003795 0003796
    (0012518)
    Kunda1   
    2019-01-25 23:16   
    @markus51 Have you tested first in 0.18dev before posting (as we ask in the enormous yellow banner at the top of the page)?
    We also ask very clearly at the top of the page not to post bugs (especially v0.17) unless they are verified in the forum.
    Please download 0.18dev and verify 0003794 0003795 0003796
    (0012540)
    markus51   
    2019-01-28 12:38   
    The same problem exists on version 0.18dev
    (0012542)
    uwestoehr   
    2019-01-28 13:04   
    As a new user I stumbled over the same problem.
    I get this with:

    OS: Windows 7
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.15711 (Git)
    Build type: Release
    Branch: master
    Hash: 5caae5f430237a73cd17e283d45b3ac9ab005feb
    Python version: 2.7.14
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.2.0
    Locale: German/Germany (de_DE)
    (0012553)
    Kunda1   
    2019-01-29 18:17   
    CC @wmayer
    (0012714)
    wmayer   
    2019-02-21 16:48   
    When using a standard QDoubleSpinBox from the Qt library then it also changes the number to 123 when you enter 12.3.
    This is because a dot in German locale is the group separator and not a decimal separator and the dot is only a visual aid for the user. When the user leaves the widget then it automatically removes the dot.
    The QuantitySpinBox is a FreeCAD widget and follows the same logic as Qt's QDoubleSpinBox. So, there is no need to change anything with the current behaviour.
    (0012718)
    markus51   
    2019-02-21 19:01   
    I have fixed this ugly stuf in my private version (only 30 min work)
    Now point and comma will be accepted.

    That is user-friendliness !
    (0012722)
    uwestoehr   
    2019-02-22 00:20   
    > Now point and comma will be accepted.

    Very good. However I learned meanwhile that some German users use the dot to separate thousands. E.g. they input "18.000" and don't want to have it treated as "18,000" but as "18000". Therefore I understand @wmayer that FC should not add a workaround but let Qt do the job.
    (0012729)
    markus51   
    2019-02-23 12:30   
    German bakers usualy use the comma and sometimes a point to separate thousands.

    German engineers use in the most cases the point. The geraman technical software which is writen in my company also uses the point for floating point values. Other technical software from other companies usualy to the same.

    If we talk about financial software, you're right. In technical software, it looks a little different.
    (0012735)
    uwestoehr   
    2019-02-24 00:23   
    > If we talk about financial software, you're right. In technical software, it looks a little different.

    I recently realized that my engineer colleagues use µm as base unit instead of mm because we build microsystems. Always entering values like "0,060" annoyed them. So now they can write simply "60" and if there is a mm length, they then write 12.000.

    Many engineering software offers to use the decimal separator of the UI language. That is why I did not yet noticed that - I use in most cases the English UI. Yesterday I made a test and setting the UI to German I have to use the comma. So things are changing in the software development and I think it makes sense to consistently follow the rules of the language.
    The same is with FC. Use the English locale and you can use the dot as decimal separator.

    Therefore I vote to mark this issue as already fixed since you can use FC with English UI andg get the dot as you like.
    (0012753)
    wmayer   
    2019-02-24 17:48   

    That is user-friendliness !

    markus51
    It's user-friendly for you personally but this does not mean that's user-friendly for everybody and it's at the cost of consistency.

    Then in FreeCAD in dozens of places Qt's QDoubleSpinBox is used which strictly follows the locale settings of the OS. How do you deal with this, then?
    (0012758)
    uwestoehr   
    2019-02-24 18:15   
    @wmayer I notice that there is an inconsistency because in tables FC automatically changes inputs like "2,3" to "2.3". Should I open a new tracker issue for that?
    (0012815)
    uwestoehr   
    2019-03-01 15:02   
    > Should I open a new tracker issue for that?

    I did it: 0003875

    Since the spreadsheet issue is now covered I think this bug report could be closed.
    (0012892)
    Kunda1   
    2019-03-12 02:30   
    Closing ticket
    (0014278)
    uwestoehr   
    2020-03-24 13:23   
    The discussion about this popped up again:
    https://forum.freecadweb.org/viewtopic.php?f=3&t=35927
    thus reopen the ticket for now.
    (0016006)
    uwestoehr   
    2021-11-02 14:57   
    Was there any decision made for this?

    @openBrain, do you maybe know something since you are assigned to a related bug?
    (0016008)
    openBrain   
    2021-11-02 17:35   
    @uwestoehr : yes, the PR that was pending has been integrated and I required for testing here : https://forum.freecadweb.org/viewtopic.php?f=8&t=62546
    AFAIK there is no regression declared ATM, but the fix may still be a bit incomplete. From the feedback, it works well for QSpinBox-like widgets, but not for example for Gui::InputField type.
    I have to investigate to be sure this latter type can only hold "formulas" but no "expressions" before I extend the fix.
    (0016009)
    uwestoehr   
    2021-11-02 18:30   
    (Last edited: 2021-11-02 18:30)
    Thanks for your work!

    > it works well for QSpinBox-like widgets

    Not for me, I reported this now in the forum thread to be discussed further.
    (0016033)
    openBrain   
    2021-11-16 17:54   
    @uwestoehr : new version has been integrated in daily that should work well in all situations. You can test again and report if needed. ;)
    (0016051)
    uwestoehr   
    2021-11-23 21:38   
    How can I test this? I added the Boolean "SubstituteDecimalSeparator" under General in the parameters, then restarted FC but cannot see any difference. So e.g. an input of "3,0" results in 3 mm, but "3.0" results in 30 mm.

    (By the way, reading my own statements from years ago, it is interesting how I changed my mind.)
    (0016706)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5871.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4670 [FreeCAD] Bug minor always 2021-05-29 02:39 2021-11-19 17:46
    Reporter: TychoPrince Platform:  
    Assigned To: chennes OS:  
    Priority: normal OS Version:  
    Status: feedback Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information:
    Summary: Datum (mm) for the constraint with index 14) is invalid
    Description: This same error code appears for horizontal distance editing also but refers to index 11
    Tags: #pending-forum
    Steps To Reproduce: Sketch a rectangle. Sketch a line from the corner of a rectangle parallel to a vertical edge and attempt to edit the vertical distance.
    Additional Information:
    Attached Files:
    Notes
    (0015810)
    chennes   
    2021-08-11 21:52   
    I cannot reproduce this error: is there as associated forums discussion?
    (0017053)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6222.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4782 [File formats] Bug minor always 2021-11-10 10:02 2021-11-16 17:52
    Reporter: knittely Platform: Notebook i7-9750H, 16GB ram  
    Assigned To: OS: Windows 10 Home  
    Priority: normal OS Version: 19042.1288  
    Status: confirmed Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Windows 10 Version 2009
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24291 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-19
    Hash: 7b5e18a0759de778b74d3a5c17eba9cb815035ac
    Python version: 3.8.6+
    Qt version: 5.15.2
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: German/Germany (de_DE)
    Summary: freecadcmd exportStep breaking model
    Description: importing the attached .iges file and exporting the model in freecadcmd breaks the model, while using the GUI works fine.
    Tags: #post-to-forum, IGES, python, STEP
    Steps To Reproduce: Run freecadcmd.exe
    
    import Part
    part = Part.read("f.iges")
    part.exportStep("f.step")
    
    -> generates f.step, but the model is broken
    Additional Information: Using the GUI:
    - File > Open > f.iges
    - selecting the model
    - File > Export... < f.step
    works fine
    Attached Files: f.zip (1,010,863 bytes) 2021-11-10 10:02
    https://tracker.freecad.org/file_download.php?file_id=2732&type=bug
    Notes
    (0016031)
    openBrain   
    2021-11-16 17:47   
    @knittely : please address your issue by opening a new topic in our forum according our reporting guidelines
    (0017113)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6282.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4750 [Expressions] Bug minor always 2021-09-24 00:26 2021-11-16 17:46
    Reporter: gbroques Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information:
    
    OS: Ubuntu 20.04.3 LTS (ubuntu:GNOME/ubuntu)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24291 (Git) AppImage
    Build type: Release
    Branch: (HEAD detached at 0.19.2)
    Hash: 7b5e18a0759de778b74d3a5c17eba9cb815035ac
    Python version: 3.8.8
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: English/United States (en_US)
    
    Summary: "Invalid property owner" for Visibility Expression of Link Array
    Description: I'm trying to bind an expression to the Visibility property of a link array created with the Draft workbench from a spreadsheet.

    However, I see this error in the Report View:
    17:44:57 <Exception> Invalid property owner.

    It seems like I see this error no matter what the Visibility property expression of the Link Array references.

    For example, referencing itself (e.g. Count or .NumberX) or referencing some property of the underlying linked object (e.g. Cube.Length).

    Essentially, what I want to do is toggle the Visibility to False when the Count is 0.

    Since Link Arrays still show the object when the count is 0 (e.g. Number X, Y, and Z are 0 for an Ortho array still shows 1 object).

    In my case, the number of objects in the the array is dynamic and based on an expression.

    "Invalid property owner" Error in FreeCAD Soure Code:
    https://github.com/FreeCAD/FreeCAD/blob/0.19.2/src/App/PropertyExpressionEngine.cpp#L547-L549
    Tags: array, expressions, python feature
    Steps To Reproduce: Steps to Reproduce

    1. Create new document
    2. Create spreadsheet from Spreadheet workbench
    3. Add expression like =5 > 1 ? True : False with an alias of CubeArrayVisibility to newly created spreadsheet
    4. Create Cube from Part workbench
    5. Create Link Array (ortho) from Draft workbench using Cube
    6. Select Link Array from Tree View
    7. Right click data tab in combo view, Select "Show All".
    8. Right click Visibility property. Select Expression
    9. Bind the CubeArrayVisibility to the Visbility property of the Array
    Additional Information: FreeCAD Forum Post
    https://forum.freecadweb.org/viewtopic.php?f=3&t=62468
    Attached Files: LinkArrayVisibilityIssue.FCStd (6,848 bytes) 2021-09-25 00:22
    https://tracker.freecad.org/file_download.php?file_id=2704&type=bug
    Notes
    (0015953)
    gbroques   
    2021-09-25 00:22   
    See attached LinkArrayVisibilityIssue.FCStd.
    (0017094)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6263.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4784 [Sketcher] Bug minor always 2021-11-11 23:12 2021-11-16 17:45
    Reporter: chrisb Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: macOS 10.16
    Word size of FreeCAD: 64-bit
    Version: 0.20.26155 (Git)
    Build type: Release
    Branch: master
    Hash: 0926a4148bcff11249fd4f56bc30256102ffe105
    Python version: 3.9.7
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.5.3
    Locale: C/Default (C)
    Summary: Double Constraint symbols not selectable
    Description: When multiple symbols are associated with the same geometric element like horizontal and the orthogonal constraint on the bottom line in the example attached to the forum, then it is not possible to select either of them.
    Forum discussion.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0017114)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6283.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4789 [Path] Bug crash always 2021-11-14 21:32 2021-11-14 21:32
    Reporter: fcuser123 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Linux Mint 20.2 (X-Cinnamon/cinnamon)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24291 (Git) AppImage
    Build type: Release
    Branch: (HEAD detached at 0.19.2)
    Hash: 7b5e18a0759de778b74d3a5c17eba9cb815035ac
    Python version: 3.8.8
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: English/Canada (en_CA)
    Summary: Path simulator crash
    Description: FreeCAD crashes when trying to run path simulator. The issue is confirmed in 0.20 version.
    Forum discussion: https://forum.freecadweb.org/viewtopic.php?f=15&t=63656
    The topic contains a project file that was used to reproduce the issue.
    Tags:
    Steps To Reproduce: 1. Start the program
    2. Open the project
    3. Activate Path workbench
    4. Click on "Simulate Path..."
    5. Click on "Activate..."
    6. FreeCAD crashes
    Additional Information: FreeCAD 0.19, Libs: 0.19R24291 (Git)
    © Juergen Riegel, Werner Mayer, Yorik van Havre and others 2001-2021
    FreeCAD is free and open-source software licensed under the terms of LGPL2+ license.
    FreeCAD wouldn't be possible without FreeCAD community.
      ##### #### ### ####
      # # # # # #
      # ## #### #### # # # # #
      #### # # # # # # # ##### # #
      # # #### #### # # # # #
      # # # # # # # # # ## ## ##
      # # #### #### ### # # #### ## ## ##

    Assembly4 workbench (v0.11.4) loaded
    Sheet Metal workbench loaded
    Manipulator WB Activated(v 1.4.1)
    Enumeration index -1 is out of range, ignore it
    Enumeration index -1 is out of range, ignore it
    Enumeration index -1 is out of range, ignore it
    Enumeration index -1 is out of range, ignore it
    Enumeration index -1 is out of range, ignore it
    Enumeration index -1 is out of range, ignore it
    Enumeration index -1 is out of range, ignore it
    Enumeration index -1 is out of range, ignore it
    Enumeration index -1 is out of range, ignore it
    Enumeration index -1 is out of range, ignore it
    Coin info in MeshRenderer(): GL_ARB_vertex_buffer_object extension not supported
    Manipulator WB Deactivated()

    Program received signal SIGSEGV, Segmentation fault.
    #0 /lib/x86_64-linux-gnu/libc.so.6(+0x46210) [0x7f4d2804f210]
    #1 0x7f4c6a3ebc83 in cSimTool::GetToolProfileAt(float) from /tmp/.mount_FreeCAqeJXt2/usr/lib/PathSimulator.so+0x43
    0000002 0x7f4c6a3ec0d6 in cStock::ApplyLinearTool(Point3D&, Point3D&, cSimTool&) from /tmp/.mount_FreeCAqeJXt2/usr/lib/PathSimulator.so+0x436
    0000003 0x7f4c6a3ea3c5 in PathSimulator::PathSim::ApplyCommand(Base::Placement*, Path::Command*) from /tmp/.mount_FreeCAqeJXt2/usr/lib/PathSimulator.so+0x125
    0000004 0x7f4c6a3eeb77 in PathSimulator::PathSimPy::ApplyCommand(_object*, _object*) from /tmp/.mount_FreeCAqeJXt2/usr/lib/PathSimulator.so+0xa7
    0000005 0x7f4c6a3eebf9 in PathSimulator::PathSimPy::staticCallback_ApplyCommand(_object*, _object*, _object*) from /tmp/.mount_FreeCAqeJXt2/usr/lib/PathSimulator.so+0x29
    0000006 /tmp/.mount_FreeCAqeJXt2/usr/bin/../lib/libpython3.8.so.1.0(PyCFunction_Call+0x66) [0x7f4d2a2ca696]
    0000007 /tmp/.mount_FreeCAqeJXt2/usr/bin/../lib/libpython3.8.so.1.0(_PyObject_MakeTpCall+0x230) [0x7f4d2a272550]
    0000008 /tmp/.mount_FreeCAqeJXt2/usr/bin/../lib/libpython3.8.so.1.0(_PyEval_EvalFrameDefault+0x4ddd) [0x7f4d2a2dc28d]
    0000009 /tmp/.mount_FreeCAqeJXt2/usr/bin/../lib/libpython3.8.so.1.0(_PyFunction_Vectorcall+0xfb) [0x7f4d2a2a45bb]
    0000010 /tmp/.mount_FreeCAqeJXt2/usr/bin/../lib/libpython3.8.so.1.0(_PyEval_EvalFrameDefault+0x6e3) [0x7f4d2a2d7b93]
    0000011 /tmp/.mount_FreeCAqeJXt2/usr/bin/../lib/libpython3.8.so.1.0(_PyFunction_Vectorcall+0xfb) [0x7f4d2a2a45bb]
    0000012 /tmp/.mount_FreeCAqeJXt2/usr/bin/../lib/libpython3.8.so.1.0(+0x17ad13) [0x7f4d2a2c0d13]
    0000013 /tmp/.mount_FreeCAqeJXt2/usr/bin/../lib/libpython3.8.so.1.0(PyVectorcall_Call+0x71) [0x7f4d2a2781c1]
    0000014 0x7f4d27cf8bad in PySide::SignalManager::callPythonMetaMethod(QMetaMethod const&, void**, _object*, bool) from /tmp/.mount_FreeCAqeJXt2/usr/bin/../lib/./libpyside2.cpython-38-x86_64-linux-gnu.so.5.13+0x9d
    0000015 /tmp/.mount_FreeCAqeJXt2/usr/bin/../lib/./libpyside2.cpython-38-x86_64-linux-gnu.so.5.13(+0x1a081) [0x7f4d27d02081]
    0000016 0x7f4d2858fa7f in QMetaObject::activate(QObject*, int, int, void**) from /tmp/.mount_FreeCAqeJXt2/usr/bin/../lib/libQt5Core.so.5+0x727
    0000017 0x7f4d28596912 in QTimer::timeout(QTimer::QPrivateSignal) from /tmp/.mount_FreeCAqeJXt2/usr/bin/../lib/libQt5Core.so.5+0x2a
    0000018 /tmp/.mount_FreeCAqeJXt2/usr/lib/python3.8/site-packages/PySide2/QtCore.cpython-38-x86_64-linux-gnu.so(+0x2ad94d) [0x7f4d0f65b94d]
    0000019 0x7f4d2858e533 in QObject::event(QEvent*) from /tmp/.mount_FreeCAqeJXt2/usr/bin/../lib/libQt5Core.so.5+0x5b
    0000020 /tmp/.mount_FreeCAqeJXt2/usr/lib/python3.8/site-packages/PySide2/QtCore.cpython-38-x86_64-linux-gnu.so(+0x2ad4d5) [0x7f4d0f65b4d5]
    0000021 0x7f4d28d9f7f2 in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /tmp/.mount_FreeCAqeJXt2/usr/bin/../lib/libQt5Widgets.so.5+0xdc
    0000022 0x7f4d28da531d in QApplication::notify(QObject*, QEvent*) from /tmp/.mount_FreeCAqeJXt2/usr/bin/../lib/libQt5Widgets.so.5+0x1ac9
    0000023 0x7f4d2a94fdf9 in Gui::GUIApplication::notify(QObject*, QEvent*) from /tmp/.mount_FreeCAqeJXt2/usr/bin/../lib/libFreeCADGui.so+0x89
    0000024 0x7f4d28579606 in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /tmp/.mount_FreeCAqeJXt2/usr/bin/../lib/libQt5Core.so.5+0x86
    0000025 0x7f4d285a78a4 in QTimerInfoList::activateTimers() from /tmp/.mount_FreeCAqeJXt2/usr/bin/../lib/libQt5Core.so.5+0x24c
    0000026 /tmp/.mount_FreeCAqeJXt2/usr/bin/../lib/libQt5Core.so.5(+0x1dbf54) [0x7f4d285a7f54]
    0000027 /tmp/.mount_FreeCAqeJXt2/usr/bin/../lib/./libglib-2.0.so.0(g_main_context_dispatch+0x27d) [0x7f4d2549623d]
    0000028 /tmp/.mount_FreeCAqeJXt2/usr/bin/../lib/./libglib-2.0.so.0(+0x554d1) [0x7f4d254964d1]
    0000029 /tmp/.mount_FreeCAqeJXt2/usr/bin/../lib/./libglib-2.0.so.0(g_main_context_iteration+0x31) [0x7f4d25496571]
    0000030 0x7f4d285a80e8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /tmp/.mount_FreeCAqeJXt2/usr/bin/../lib/libQt5Core.so.5+0x5e
    0000031 0x7f4d28576019 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) from /tmp/.mount_FreeCAqeJXt2/usr/bin/../lib/libQt5Core.so.5+0x187
    0000032 0x7f4d28579e8f in QCoreApplication::exec() from /tmp/.mount_FreeCAqeJXt2/usr/bin/../lib/libQt5Core.so.5+0xfd
    0000033 0x7f4d2a8d9926 in Gui::Application::runApplication() from /tmp/.mount_FreeCAqeJXt2/usr/bin/../lib/libFreeCADGui.so+0x15f6
    0000034 /tmp/.mount_FreeCAqeJXt2/usr/bin/freecad(+0x44bf) [0x5562cc5124bf]
    0000035 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x7f4d280300b3]
    0000036 /tmp/.mount_FreeCAqeJXt2/usr/bin/freecad(+0x47d9) [0x5562cc5127d9]
    Attached Files:
    Notes
    (0017117)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6286.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4788 [PartDesign] Bug minor always 2021-11-14 04:17 2021-11-14 04:17
    Reporter: garya Platform: PC  
    Assigned To: OS: FreeBSD  
    Priority: normal OS Version: 11.4-RELEASE  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: FreeBSD 11.4-RELEASE-p6 (XFCE/xfce)
    Word size of FreeCAD: 64-bit
    Version: 0.20.master (Built from source 2021-11-01)
    Build type: Release
    Python version: 3.7.9
    Qt version: 5.15.2
    Coin version: 4.0.0
    OCC version: 7.5.0
    Locale: C/Default (C)
    Summary: Polar pattern of loft up to arc surface fails
    Description: If a loft is done from a square pillar resting on a ring, the resulting loft cannot be replicated in a polar array.

    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=3&t=63689

    Several example files are posted in forum thread; the simplest is PolarPatrn_4.


    Tags: Loft, Part Design, PolarPattern
    Steps To Reproduce: Load PolarPatrn_4
    Select Proto_WindingRib
    Click PolarPattern
      Result: Two posts are visible, 180 degrees apart
              The original post has the additive loft; the patterned one does not (ok so far)
    Click Add Feature
      Result: The added post is removed (still ok)
    Click on the AdditiveLoft
      Result: AdditiveLoft is added to the PolarPattern parameters list in the dialog (correct)
              The original additive loft disappears and no lofts are visible on either post (incorrect)
    Additional Information: See the forum thread for other manifestations of this bug and attempts to work around.
    It was suggested this is a problem with OpenCascade.
    Attached Files:
    Notes
    (0017116)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6285.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4787 [Expressions] Bug minor always 2021-11-12 11:47 2021-11-12 11:47
    Reporter: Roy_043 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Windows 8.1 (6.3)
    Word size of FreeCAD: 64-bit
    Version: 0.20.26306 (Git)
    Build type: Release
    Python version: 3.8.12
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.5.3
    Locale: Dutch/Netherlands (nl_NL)
    Summary: Labels in expressions not updated correctly when Std_MergeProjects is used.
    Description: When merging the same project more than once, Labels used in expressions are only updated if they match the Name of the object they refer to.
    Tags:
    Steps To Reproduce:
    1. Open a new document.
    2. Use Std_MergeProjects to merge the attached file twice.
    3. The expression for the Radius of Cylinder001 is
      <<Cube>>.Width
      , it should be
      <<Cube001>>.Width
      .
    4. The expression for the Height of Cylinder001 has been correctly updated to
      <<BoxFromCode001>>.Height
    Additional Information: Related forum pots:
    https://forum.freecadweb.org/viewtopic.php?f=3&t=28511
    https://forum.freecadweb.org/viewtopic.php?f=3&t=63285
    Attached Files: box.FCStd (9,967 bytes) 2021-11-12 11:47
    https://tracker.freecad.org/file_download.php?file_id=2733&type=bug
    Notes
    (0017115)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6284.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4781 [FreeCAD] Bug major always 2021-11-08 14:41 2021-11-08 14:42
    Reporter: vectronic Platform: Intel  
    Assigned To: OS: MacOS  
    Priority: normal OS Version: 11.6  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: macOS 10.16
    Word size of FreeCAD: 64-bit
    Version: 0.20.Unknown
    Build type: Release
    Python version: 3.9.7
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.5.3
    Locale: C/Default (C)
    Summary: Issue with Linear Pattern in the Part Design workbench when replicating an Additive Pipe based on an elliptical path.
    Description: I am trying to use Linear Pattern to duplicate a flange on a pin. The flange is created using an additive pipe which uses a path sketch involving an ellipse.

    This doesn't work.

    I have queried in the forum to see if this was:

    - a known bug (doesn't seem to be)
    - more experienced users can get it to work (they can't)
    - more experienced users thought it might be a bug (they do)

    Forum link: https://forum.freecadweb.org/viewtopic.php?f=3&t=63409

    I have taken my sample from the forum, improved it based on their feedback and simplified it a lot more. I have also included a comparison of using a circle (instead of an ellipse) for the additive pipe path and this seems to work fine with the linear pattern feature.


    In the linear-pattern-attempt-1.FCStd you will see:

    • attempt-1-01.png : Linear pattern of a pin and a flange based on a circular path is rendered.
    • attempt-1-02.png : Another flange based on an elliptical path is added to the first pin.
    • attempt-1-03.png : When another linear pattern for the elliptical flange is added, the result is not as expected.




    In the linear-pattern-attempt-2.FCStd you will see:

    • attempt-2-01.png : A pin with a circular flange and elliptical flange is created first.
    • attempt-2-02.png : If I try to create a linear pattern involving all of these at once (the pin, the circular flange and the elliptical flange) the linear pattern dialog displays an unexpected error.
    • attempt-2-03.png : The final result is not as expected.

    Tags: Part Design
    Steps To Reproduce: Open the linear-pattern-attempt-1.FCStd file and observe that:

    - the linear pattern using the feature of an additive pipe based on a circle path sketch IS rendered.
    - the linear pattern using the feature of an additive pipe based on an ellipse path sketch IS NOT rendered.

    OR

    Open the linear-pattern-attempt-2.FCStd file and observe that the linear pattern including both additive pipes is rendered incorrectly.sketch is not rendered.
    Additional Information: Screenshots: https://f001.backblazeb2.com/file/vectronic-public/freecad/screenshots.zip

    Sample models: https://f001.backblazeb2.com/file/vectronic-public/freecad/models.zip

    Attached Files:
    Notes
    (0017112)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6281.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4556 [File formats] Feature feature always 2021-02-07 13:12 2021-11-08 01:59
    Reporter: dprojects Platform:  
    Assigned To: chennes OS:  
    Priority: low OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Ubuntu 20.04.2 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.4.
    Build type: Release
    Python version: 3.8.2
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.3.0
    Locale: English/United States (en_US)
    Summary: allow export and import of ODS files
    Description: Please allow to import and export ODS files.
    More info: https://forum.freecadweb.org/viewtopic.php?f=4&t=25691&start=40
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016989)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6157.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1352 [FreeCAD] Bug major always 2014-01-11 17:53 2021-11-05 16:43
    Reporter: jobermayr Platform: Linux  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: trunk  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: DOS line endings makes applying patches on Linux really hard
    Description: I must apply patches on pmbs via "patch --merge -p1 <$PATCH" instead of just "patch -p1 <$PATCH" due to silly DOS line endings:
    https://pmbs.links2linux.de/package/show?package=FreeCAD&project=Extra
    Tags: #tobeclosed
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0004052)
    jobermayr   
    2014-01-12 15:10   
    Btw. it seems to be an easy task:
    https://help.github.com/articles/dealing-with-line-endings
    (0004060)
    shoogen   
    2014-01-12 18:28   
    Did i get your right? You proposed to normalize the whole repo to LF line endings?
    http://stackoverflow.com/questions/1510798/trying-to-fix-line-endings-with-git-filter-branch-but-having-no-luck/1511273#1511273
    (0004062)
    jobermayr   
    2014-01-12 19:14   
    Please try to apply https://pmbs.links2linux.de/package/view_file?expand=1&file=0001-Add-support-for-different-libdir.patch&package=FreeCAD&project=Extra

    1. git am $file # fails
    2. git reset --hard origin/master
    3. patch -p1 <$file # fails
    4. git reset --hard origin/master
    5. patch --merge -p1 <$file # works
    6. git commit -a --date="Mon, 2 Dec 2013 22:21:02 +0100" --author="Johannes Obermayr <johannesobermayr@gmx.de>" -m "Add support for different libdir."
    7. git format-patch origin/master
    8. git reset --hard origin/master
    9. git am 0001-Add-support-for-different-libdir.patch # fails because of silly DOS line endings

    So if you have another fix please let it know ...
    (0004065)
    shoogen   
    2014-01-12 20:07   
    i don't even get to download the patch. <summary>Authentication required</summary>
    (0004066)
    shoogen   
    2014-01-12 20:20   
    (Last edited: 2014-01-12 20:25)
    You could ask the packman build service guys to invoke "git am" with the parameter --keep-cr
    or "diff" with "--binary"

    (0004067)
    jobermayr   
    2014-01-12 21:16   
    Since I stepped in and am the de facto maintainer of FreeCAD on Packman I can tell you that %patch macro from openSUSE (main distro) applies patches via "patch $level -fuzz=0" also Fedora and some other RPM based Linux distros are doing it this way.

    JFYI: None of the other packages on build.opensuse.org and pmbs.links2linux.de makes problems in the way FreeCAD makes (not FHS conform, RPATH issues, silly DOS line endings, ...)
    Hacks and workarounds as well as hacks and workarounds to get them applied are needed to fulfill minimal requirements to get it working and accepted ...
    Proper fixing is not possible in just a few minutes because jumping between c/c++ and python is a hell ...

    Fixing OCE to our needs was a laugher:
    https://github.com/tpaviot/oce/issues/created_by/jobermayr?state=closed
    https://pmbs.links2linux.de/package/view_file?expand=1&file=0002-OpenGl_GlCore12.hxx-undef-GL_VERSION_x_y-in-all-case.patch&package=oce&project=Extra

    Btw. the download problem is (WONTFIX on pmbs):
    https://github.com/openSUSE/open-build-service/issues/458
    Maybe you can copy & paste it?
    (0004074)
    shoogen   
    2014-01-13 16:57   
    IMHO adding a single commit to our repo that will remove all Carriage Returns has some drawbacks.
    The most important is that it will render the "git blame" command useless and that will make the repo bigger.
    I would prefer to orphan the commit that will remove all the CRs. But would break all branches that have diverged from master.
    But I am just an ordinary contributer.
    Maybe we can just remove the CRs in all places touched by your patches, so they will apply cleanly. This won't solve the problem, as it would have to be repeated for every patch you add (in the future). But it will provide time to think about a suitable solutions, whilst allowing you to continue using PMBS.
    And as this bug flagged as 'urgend' I think that it might be worth it.
    (0004103)
    shoogen   
    2014-01-19 13:26   
    (Last edited: 2014-01-19 13:41)
    this ticket is one week old. I see it is still major issue, but don't think that it is urgent anymore, sine there seems to be a workaround in place.

    BTW: when debugging line end ending issues, i would usually avoid copy & paste.
    https://github.com/openSUSE/open-build-service/issues/458
    openSUSE 13.1 was out the day you wrote that

    (0007608)
    Kunda1   
    2017-01-10 16:25   
    @shoogen Does this workaround need to be documented somewhere and then we can close this ticket?
    (0007829)
    Kunda1   
    2017-01-17 04:05   
    Related forum threads:
    http://forum.freecadweb.org/viewtopic.php?t=15443
    http://forum.freecadweb.org/viewtopic.php?t=19866 <-Active
    (0008536)
    blacey   
    2017-03-03 22:06   
    To me, this is something that @wmayer or @yorik should do because it will create a broad swath commit across the repo. I think with a little bit of communication, this can, and should, be done quite easily.
    (0008537)
    ian.rees   
    2017-03-03 22:50   
    I think that if we're going to do a massive line-ending-change (my vote is to not to), it would be best to do it using something like filter-branch that rewrites history so we don't have a commit that touches every line in the project. We also need to have a process in place to make sure that the line endings stay consistent.

    It will be a pain either way, but with the rewrite option, pain goes away once everyone's dev branches are based off the "new" history. Otherwise, it's always going to be more difficult to understand history from before the line ending fix.

    Someone would need to come up with the process for moving the project to the new line ending style, and to handle a few common scenarios (like how to merge in branches that were made from the history with the wrong line endings).
    (0008538)
    yorik   
    2017-03-04 00:22   
    Won't it be an endless struggle, that even if we unify everything, very soon new commits will be added with "wrong" file endings again and we'll need to do this forever?
    (0008539)
    ian.rees   
    2017-03-04 02:50   
    yorik - I think you're right. To keep line endings nice, we would also need a system to screen changes. That system might be nice, because it would help avoid individual files with both types of line endings.

    As I understand the original issue above, unifying line endings to be "Unix" type isn't really going to solve the problem. The issue seems to be that the patches have line endings that aren't consistent with the file being patched. So, if we standardise on Unix then it makes creating good patches easier on Linux/MacOS, but harder on Windows.
    (0008540)
    blacey   
    2017-03-04 06:38   
    The "endless struggle" could be averted through two methods: 1) add the line ending config to the .gitattributes file and 2) Add checks to Travis.

    If everything is configured properly, all operating systems should conform to the line ending config while modifying files within the FreeCAD git repo. If someone goes astray, Travis can catch it while validating the Pull Request.
    (0010331)
    Kunda1   
    2017-10-19 13:12   
    Linking 0003206
    (0013539)
    Kunda1   
    2019-09-05 20:27   
    @wmayer do you think this ticket still has merit ?
    (0013564)
    wmayer   
    2019-09-10 11:50   
    In >99% of all cases we get contributions via GH (or Gitlab) and very rarely real patch files. So, patches with incompatible line endings is not a big issue any more.

    But I would still leave this open because also on GH it happens from time to time that the line endings of a file has completely changed while only a single line has been modified by the author. This complicates the review, then.
    (0015925)
    chennes   
    2021-09-15 16:06   
    @wmayer, since there is no action to be taken on anyone's part, except to make sure your PRs don't mess up all the line endings, I suggest we close this. It's not a bug at this point, as much as "how to be a good open source developer" advice that would best be suited to a statement on the Wiki.
    (0015945)
    wmayer   
    2021-09-17 14:57   
    We haven't had any serious issues with line endings in the last couple of years or got patches that couldn't be merged easily. Also if a PR would change all line endings I found the trick to add ?w=1 to the url to ignore white spaces changes when reviewing the code.

    @yorik what do you think?
    (0016015)
    ferdymercury   
    2021-11-05 16:43   
    Suggestion: one could mark the "big" commit changing all the line endings in a .git-blame-ignore-revs file, so that it can be easily 'hidden' from history, but does not make a mess with rewriting history and branches. This is also useful if one wants to use auto-formatters to reformat old code into a specific consistent style.

    See:
    https://github.community/t/support-ignore-revs-file-in-githubs-blame-view/3256
    https://michaelheap.com/git-ignore-rev/
    https://gitlab.com/gitlab-org/gitlab/-/issues/31423
    (0016413)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5578.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4778 [Path] Bug minor always 2021-11-03 20:01 2021-11-03 20:01
    Reporter: sliptonic Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: Issue reported on machine config below but reproduced on other platforms.


    OS: Windows 10 Version 2009
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24291 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-19
    Hash: 7b5e18a0759de778b74d3a5c17eba9cb815035ac
    Python version: 3.8.6+
    Qt version: 5.15.2
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: English/United States (en_US)
    Summary: Tag dressup throws error if applied after boundary dressup.
    Description: https://forum.freecadweb.org/viewtopic.php?f=15&t=63433
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0017110)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6279.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4775 [Sketcher] Bug major sometimes 2021-10-31 10:44 2021-10-31 10:44
    Reporter: kisolre Platform: PC  
    Assigned To: OS: Windows  
    Priority: normal OS Version:  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Windows 8.1 Version 6.3 (Build 9600)
    Word size of FreeCAD: 64-bit
    Version: 0.20.26255 (Git)
    Build type: Release
    Branch: master
    Hash: 2a9fd08e7f74630c1ad25ec06d984ce06d609d13
    Python version: 3.8.6+
    Qt version: 5.15.2
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: Bulgarian/Bulgaria (bg_BG)
    Summary: Duplicate object results in <Exception> Object can only be in a single GeoFeatureGroup
    Description: When duplicating a PD body object sometimes features from the newly created body are mapped to the duplicated body.
    Tags:
    Steps To Reproduce: Start FreeCAD.
    Create new Body.
    Draw something in a sketch, pad sketch.
    Select Body.
    Invoke Duplicate selected object, confirm dialog.
    Error is thrown:
    
    16:29:00  Traceback (most recent call last):
      File "<string>", line 1, in <module>
    <class 'RuntimeError'>: Object can only be in a single GeoFeatureGroup
    and sketch from the second body is mapped to a plane in the first body.
    Additional Information: Forum thread
    Attached Files: SingleGeofeatureGroup.JPG (127,790 bytes) 2021-10-31 10:44
    https://tracker.freecad.org/file_download.php?file_id=2729&type=bug
    Notes
    (0017109)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6278.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2755 [PartDesign] Bug major have not tried 2016-11-01 13:41 2021-10-29 22:14
    Reporter: wmayer Platform:  
    Assigned To: OS:  
    Priority: high OS Version:  
    Status: confirmed Product Version: 0.16  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Order of external edges may change
    Description: See http://forum.freecadweb.org/viewtopic.php?f=13&t=18189
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0009312)
    sheinz   
    2017-06-08 13:50   
    Is this the same issue?
    https://youtu.be/6057gygfRhw
    When new edges added to the original shape the feature might change the edges it was originally applied for.
    (0016506)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5671.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4771 [FreeCAD] Bug crash always 2021-10-20 02:18 2021-10-29 21:53
    Reporter: DevWang Platform: Windows  
    Assigned To: OS: Win10  
    Priority: high OS Version:  
    Status: feedback Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Windows 10 Version 1909
    Word size of FreeCAD: 64-bit
    Version: 0.20.25836 (Git)
    Build type: Debug
    Branch: master
    Hash: e94d7c32b53863b33462864405dfc508a60eae68
    Python version: 3.8.6+
    Qt version: 5.15.1
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: Chinese/China (zh_CN)
    Summary: Import Stp file Failed And FreeCAD Crashed
    Description: The Stp file Which export by NX 12.0, Import the stp file to FreeCAD in Debug Model , first asset error, then FreeCAD Crashed.
    Tags:
    Steps To Reproduce: Step1: Import the Stp file in to FreeCAD;
    Additional Information:
    Attached Files: 1634694595(1).jpg (104,922 bytes) 2021-10-20 02:18
    https://tracker.freecad.org/file_download.php?file_id=2725&type=bug
    15-MO.stp (98,831 bytes) 2021-10-20 02:18
    https://tracker.freecad.org/file_download.php?file_id=2726&type=bug
    Screenshot at 2021-10-29 14-40-03.png (115,786 bytes) 2021-10-29 18:40
    https://tracker.freecad.org/file_download.php?file_id=2727&type=bug
    Notes
    (0016000)
    jnxd   
    2021-10-29 18:40   
    Not reproducible with the following build, but there appear to be artifacts:

    OS: Ubuntu 20.04.3 LTS (MATE/mate)
    Word size of FreeCAD: 64-bit
    Version: 0.20.26203 (Git)
    Build type: Unknown
    Branch: fem-constraint-qol
    Hash: 3a5c5576ea269b8bae14325db844e4d9201a7fa4
    Python version: 3.8.10
    Qt version: 5.12.8
    Coin version: 4.0.0
    OCC version: 7.5.2
    Locale: English/United States (en_US)
    (0016001)
    jnxd   
    2021-10-29 18:43   
    @DevWang I see your version is around 500 commits behind master. Please verify with the latest build, and if the bug is still there, please make a forum post as described here: https://wiki.freecadweb.org/Tracker
    (0017107)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6276.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3777 [Project Tools & Websites] Feature feature N/A 2019-01-17 15:46 2021-10-26 11:50
    Reporter: Kunda1 Platform:  
    Assigned To: OS:  
    Priority: low OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Add Crowdin API Issue lister to Crowdin scripts
    Description: Using the Crowdin API a Crowdin admin can view all open issues that are created through the Crowdin translation interface. This can help to solve user experience issues etc...
    Tags: translation
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0015468)
    Kunda1   
    2021-03-01 18:25   
    @hyarion would you be interested in this task aswell. Right now it's a real PITA to traverse the crowdin UI to see open issues. This feature could be a game changer.
    (0016697)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5862.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4772 [FreeCAD] Bug major always 2021-10-24 07:21 2021-10-24 07:21
    Reporter: Sylva1n Platform: x86  
    Assigned To: OS: Ubuntu  
    Priority: high OS Version: 20.04  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Ubuntu 20.04.3 LTS (ubuntu:GNOME/ubuntu)
    Word size of FreeCAD: 64-bit
    Version: 0.20.
    Build type: Release
    Branch: unknown
    Hash: 123906034cf0671a8838f3b44f858d6ad4989ea8
    Python version: 3.8.10
    Qt version: 5.12.8
    Coin version: 4.0.0
    OCC version: 7.5.2
    Locale: English/United States (en_US)
    Summary: Red screen after any 3D View interaction
    Description: Any action that refreshes 3D View (move Camera, select Object... ) leads to a freeze or red screen. Freecad can be closed without crash.

    Note that I use a daily Freecad running inside a ParallelsDesktop Ubuntu 20.04 virtual machine (since about one year).
    Tags:
    Steps To Reproduce: Any action leading to refresh 3D View.
    Additional Information:
    Attached Files:
    Notes
    (0017108)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6277.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4768 [Part] Bug trivial always 2021-10-18 19:06 2021-10-19 13:02
    Reporter: jack9603301 Platform: Linux  
    Assigned To: OS: Kubuntu  
    Priority: normal OS Version: 21.04  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: <!--ATTENTION:
    COMPLETELY ERASE THIS AFTER PASTING YOUR
    Help > About FreeCAD > Copy to clipboard
    NOTE: just the snippet alone will do without anything else included.
    The ticket will not be submitted without it.
    -->

    OS: Ubuntu 21.04 (KDE/plasma)
    Word size of FreeCAD: 64-bit
    Version: 0.20.
    Build type: Release
    Branch: unknown
    Hash: 0926a4148bcff11249fd4f56bc30256102ffe105
    Python version: 3.9.5
    Qt version: 5.15.2
    Coin version: 4.0.0
    OCC version: 7.5.2
    Locale: Chinese/China (zh_CN)
    Summary: Source code installation failed
    Description: see: https://forum.freecadweb.org/viewtopic.php?f=4&t=63002&p=540842#p540842

    This appears to be caused by
    StartGui.so
    and
    Start.so
    not having the permissions it should have, when executing the following command:

    
    cd /usr/lib/x86_64-linux-gnu/
    find -type f -name "*.so" | xargs -I {} sudo chmod a+x {}
    

    It is normal for
    Tags:
    Steps To Reproduce: To compile and install, run the following command:

    
    cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DPYTHON_EXECUTABLE=/usr/bin/python3 -DFREECAD_USE_PCL=ON -DFREECAD_USE_PYBIND11=ON -DCMAKE_BUILD_TYPE=Release
    make
    sudo make install
    
    Additional Information:
    System Description
    Attached Files: 2021-10-19_03-21.png (188,096 bytes) 2021-10-18 19:22
    https://tracker.freecad.org/file_download.php?file_id=2721&type=bug
    2021-10-19_03-22.png (136,973 bytes) 2021-10-18 19:22
    https://tracker.freecad.org/file_download.php?file_id=2722&type=bug
    Notes
    (0015992)
    jack9603301   
    2021-10-18 19:16   
    Well, I should add that it doesn't seem to be caused by a permissions issue, but rather by my accidental execution in the following path. Strange..
    
    cd /usr/lib/x86_64-linux-gnu/
    FreeCAD
    
    (0015993)
    jack9603301   
    2021-10-18 19:22   
    The problem seems to be related to the fact that the associated dynamic libraries are not python3 working paths (such as /usr/mod)...

    
    FreeCAD  -M /usr/lib/x86_64-linux-gnu
    
    (0015994)
    jack9603301   
    2021-10-19 10:22   
    (Last edited: 2021-10-19 13:02)
    Run the following command to start:
    
    FreeCAD  -M /usr/lib/x86_64-linux-gnu
    

    I think this is a mistake, and if those dynamic library were in the same directory as python mods, then everything would be fine.
    Perhaps the people concerned just need to modify the Cmake installation configuration to fix this error.
    This problem has been tested.
    Although the cause of the error was misjudged once, it was indeed a flaw in the installation process
    This is not a serious error because it can be resolved by -M, but it is a defect.
    Some people like to compile and install (maybe to track and participate in freecad development in the future, maybe to track the latest changes in development branches, participate in the community, or simply want to compile themselves to meet 100% compatible ABI, but in any case, they want to compile and install)
    As the most commonly used manual installation method of Linux, especially the operation and maintenance personnel, the use of compilation and installation should not be hindered by defects (tracing the exact directory of each dynamic library often wastes redundant time)

    ps: Can someone help me move this bug report to the right project? It should not belong to part, but to freecad
    (0017105)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6274.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4769 [Path] Bug minor always 2021-10-18 20:36 2021-10-18 20:36
    Reporter: sliptonic Platform:  
    Assigned To: sliptonic OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: All versions and platforms are affected
    Summary: Changing TC with same tool number but different spindle speed doesn't produce correct gcode
    Description: The user may desire to run the same tool at different feeds and speeds within a job. This is achieved by creating two tool controllers and using the same tool number for both. During post processing, the tool number of the new tool is compared to the old one and if they are the same, the tool change code is suppressed. This is correct behavior. However, if the spindle speed changes, an M3 (or M4) with the new spindle speed should be emitted and it is not.



    Tags:
    Steps To Reproduce:
    Additional Information: https://forum.freecadweb.org/viewtopic.php?f=15&t=62762&start=10
    Attached Files:
    Notes
    (0017106)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6275.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4767 [FreeCAD] Bug minor always 2021-10-17 20:08 2021-10-17 20:08
    Reporter: BruceL Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Debian GNU/Linux bookworm/sid (GNOME/gnome)
    Word size of FreeCAD: 64-bit
    Version: 0.20.25997 (Git) AppImage
    Build type: Release
    Branch: master
    Hash: 77b198048a63f1e9ca15eef64c8042d599a14cf3
    Python version: 3.9.7
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.5.2
    Locale: English/Canada (en_CA)
    Summary: Pocket using SubShapeBinder does not occur on orthogonal axis.
    Description: Forum Post

    When making pockets with sub-shapebinders, FreeCAD insists on pocketing along the z-axis.
    Tags:
    Steps To Reproduce: 1. Open the attached SM-PLB03A case file.
    2. make "SLIDE_IN" the active body
    3. select the "vent_binder" subshapebinder in "SLIDE_IN"
    4. pocket the "vent_binder"
    5. observe that the pocket appears to be along the z axis as it appears in the section below the "vent binder" instead of along the y axis where I would expect it.
    6. note that the "thread_holes_2" pocket, which is also based on a subshapebinder from "MAIN_CASE" works fine (but it's along the z-axis)
    Additional Information:
    Attached Files: SM-PLB03A case.FCStd (723,727 bytes) 2021-10-17 20:08
    https://tracker.freecad.org/file_download.php?file_id=2720&type=bug
    Notes
    (0017104)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6273.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4753 [Draft] Bug major always 2021-09-25 20:26 2021-10-15 08:20
    Reporter: tudorapo Platform: PC  
    Assigned To: OS: Ubuntu  
    Priority: high OS Version: 21.4  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Ubuntu 21.04 (ubuntu:GNOME/ubuntu-xorg)
    Word size of FreeCAD: 64-bit
    Version: 0.20.
    Build type: Release
    Branch: unknown
    Hash: 582c26ea8b5f9d85957a6cb1bf798839fa2ce94c
    Python version: 3.9.5
    Qt version: 5.15.2
    Coin version: 4.0.0
    OCC version: 7.5.2
    Locale: English/United States (en_US)
    Summary: Objects jumping and appearing randomly I - drawing a Dimension moves object
    Description: When trying to add a dimension to an object, another object jumps around. In the screenshot I'll try to attach the I tried to add a dimension to the pentagonal object on the lower right corner and the "bounding box", actually the walls of the room jumped up and left.
    Tags: #post-to-forum
    Steps To Reproduce: 1. add a dmiension
    2. watch your object fly.
    Additional Information:
    Attached Files: Screenshot from 2021-09-25 22-24-11.png (282,195 bytes) 2021-09-25 20:26
    https://tracker.freecad.org/file_download.php?file_id=2706&type=bug
    Screenshot from 2021-09-25 22-21-29.png (445,195 bytes) 2021-09-25 20:26
    https://tracker.freecad.org/file_download.php?file_id=2707&type=bug
    fsztutoriallal.FCStd (58,358 bytes) 2021-09-25 20:26
    https://tracker.freecad.org/file_download.php?file_id=2708&type=bug
    Notes
    (0015966)
    openBrain   
    2021-10-13 13:42   
    @tudorapo : a single forced recompute of your file makes the frame to jump. No link with adding a direction.
    Please check your file and if you think there is still a problem, please open a new thread in our forum per our reporting guidelines. Thx
    (0015986)
    tudorapo   
    2021-10-14 17:56   
    I'm sorry, I did not do any forced recomputing and I did not create any frame, that's an object I draw.
    Your reply thus makes no sense for me.
    (0015989)
    openBrain   
    2021-10-15 08:20   
    @tudorapo : I'm not so familiar with Arch.
    Please do a forced recompute on your document (RMB on document name in the tree -> Mark to recompute -> F5) and you'll see the wall (what I previously called frame, but now I guess it's a wall) will jump. So for sure it's not linked to adding dimension. And I suspect it's a problem in your model.
    (0017096)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6265.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4756 [Arch] Bug major always 2021-09-29 02:12 2021-10-13 22:28
    Reporter: SB Platform:  
    Assigned To: OS: Windows  
    Priority: normal OS Version: 2010  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: <!--ATTENTION:
    COMPLETELY ERASE THIS AFTER PASTING YOUR
    Help > About FreeCAD > Copy to clipboard
    NOTE: just the snippet alone will do without anything else included.
    The ticket will not be submitted without it.
    -->
    Summary: When creating a wall from a rectangle in Arch it makes a oversize wall on the outskirts of the area for manipulation
    Description: I can't sign up for forums, it won't let me sign up.
    Separately in FreeCAD I just create a rectangle in Arch and want it to make a wall.
    What it does is make a oversized wall on the perimeters of the platform to make the architecture and all that was expected for a wall to be made with the perimeters of the rectangle.
    Tags: #post-to-forum
    Steps To Reproduce: 1. Open FreeCAD 0.19
    2. Pick new project
    3. Pick Arch
    4. make rectangle
    5.turn off face of rectangle: make false
    6.highlight rectangle
    7.pick wall and click on rectangle
    8. Oversize wall outside perimeters of Area for manipulation shows up instead of on rectangle
    9. must zoom out and rotate to see incorrect wall.
    Additional Information:
    Attached Files: image.png (36,823 bytes) 2021-10-02 02:52
    https://tracker.freecad.org/file_download.php?file_id=2710&type=bug
    Notes
    (0015954)
    doia   
    2021-10-01 09:15   
    This is actually the normal and expected behaviour. The Arch Wall is created from all 4 edges of the drawn rectangle, making it a rectangular shape enclosed by 4 walls. The drawn rectangle acts as the base line for the walls. You can now change the orientation of the walls on this base line to center/left/right. If you want to create a single straight wall, use the Draft_Line command (draw a single line), select this line and then select Arch_Wall.

    Maintainer -> please close this ticket as it is no bug.
    (0015955)
    SB   
    2021-10-02 02:52   
    That's not is what is happening to mine. It produces a wall outside the perimeters of the area for manipulation that is not along the rectangle produced and the wall is extremely large but now I don't even get a wall but an error message when I try the same procedure.
    (0015956)
    doia   
    2021-10-02 08:43   
    Could you please post your version information and a simple example file -> point 4 and 6 of the really BIG yellow banner!
    (0015958)
    SB   
    2021-10-03 02:19   
    I thought that I already put in the version as 0.19 in product and I don't know how to do a simple example file.
    I don't know what to do now to show the problem.
    (0015959)
    SB   
    2021-10-03 02:20   
    Can I show an example in the notes?
    (0015969)
    openBrain   
    2021-10-13 13:59   
    @SB : please open a new thread in our forum to discuss your issue with the community (per our reporting guidelines)
    (0015975)
    SB   
    2021-10-13 14:23   
    The forum wouldn't let me on. This tracker is the only place I can go.
    (0015976)
    doia   
    2021-10-13 14:45   
    (Last edited: 2021-10-13 14:45)
    Then please try one of the other discussion boards like Reddit, Discord or Gitter. You will find the links to these on the https://www.freecad.org main page at the bottom. There you can sort out your problems with the forum access and will get more help with your problem in creating an Arch wall.
    (0015984)
    SB   
    2021-10-13 22:28   
    If your implying you want this taken down I don't know how to do that. What do I do to take it down?
    (0017098)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6267.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4758 [PartDesign] Bug crash always 2021-10-03 12:25 2021-10-13 14:00
    Reporter: hcbang Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Ubuntu 21.04 (KDE/plasma)
    Word size of FreeCAD: 64-bit
    Version: 0.20.25541 (Git) AppImage
    Build type: Release
    Branch: master
    Hash: ca043dcb6d20d70b8e24d75e810683214eecc5d4
    Python version: 3.9.6
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.5.2
    Locale: German/Germany (de_DE)
    Summary: Crash with AdditivePipe
    Description: FC crashes when trying additivePipe with CornerTransition set to RightCorner
    Tags: upstream
    Steps To Reproduce: get the added FC File
    Click on Sketch005, which is the closed curve to be extruded.
    Click on AdditivePipe
    Change CornerTransition to RightCorner
    Click on Buttom Object
    Click on one Part of Sketch002, which is the line for the pipe direction
    Et voila, FC crashes on my computer
    Additional Information: whas discussed in the help forum with the same title,
    the same error under windows10
    Attached Files: AdditivePipeError1.FCStd (12,738 bytes) 2021-10-03 12:25
    https://tracker.freecad.org/file_download.php?file_id=2711&type=bug
    Notes
    (0015960)
    hcbang   
    2021-10-03 12:40   
    I get no error, when the sketch to be extruded is on the endpoint or startingpoint? of the path sketch
    (0015961)
    openBrain   
    2021-10-05 07:40   
    As we may expect, it crashes deep in OCC :
    Program received signal SIGSEGV, Segmentation fault.
    #0  /lib/x86_64-linux-gnu/libc.so.6(+0x41040) [0x7fbaac35c040]
    #1  0x7fba6ff50c0c in BRepFill_PipeShell::BuildHistory(BRepFill_Sweep const&) from /lib/x86_64-linux-gnu/libTKBool.so.7+0x49c
    0000002  0x7fba6ff46f5a in BRepFill_PipeShell::Build() from /lib/x86_64-linux-gnu/libTKBool.so.7+0x92a
    0000003  0x7fba6efd3ae1 in BRepOffsetAPI_MakePipeShell::Build() from /lib/x86_64-linux-gnu/libTKOffset.so.7+0x11
    0000004  0x7fba6fb566fd in BRepBuilderAPI_MakeShape::Shape() from /lib/x86_64-linux-gnu/libTKTopAlgo.so.7+0x3d
    0000005  0x7fba15d2b4c8 in PartDesign::Pipe::execute() from /home/OB/dev/FCBuild/Mod/PartDesign/_PartDesign.so+0xc4e
    0000006  0x7fbaaedd5dd5 in App::DocumentObject::recompute() from /home/OB/dev/FCBuild/lib/libFreeCADApp.so+0xeb
    0000007  0x7fba75f56f51 in Part::Feature::recompute() from /home/OB/dev/FCBuild/Mod/Part/Part.so+0x1f
    0000008  0x7fbaaecd8c4d in App::Document::_recomputeFeature(App::DocumentObject*) from /home/OB/dev/FCBuild/lib/libFreeCADApp.so+0x1d1
    0000009  0x7fbaaecd994b in App::Document::recomputeFeature(App::DocumentObject*, bool) from /home/OB/dev/FCBuild/lib/libFreeCADApp.so+0x10b
    0000010  0x7fba1572c0a0 in PartDesignGui::TaskFeatureParameters::recomputeFeature() from /home/OB/dev/FCBuild/Mod/PartDesign/PartDesignGui.so+0x82
    0000011  0x7fba157c19fa in PartDesignGui::TaskPipeParameters::onSelectionChanged(Gui::SelectionChanges const&) from /home/OB/dev/FCBuild/Mod/PartDesign/PartDesignGui.so+0x558
    (0017099)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6268.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4751 [Arch] Bug minor always 2021-09-24 13:18 2021-09-24 13:20
    Reporter: hlg Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Windows 10 Version 2009
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24291 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-19
    Hash: 7b5e18a0759de778b74d3a5c17eba9cb815035ac
    Python version: 3.8.6+
    Qt version: 5.15.2
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: German/Germany (de_DE)
    Summary: Wrong shape generation for ArchStructure with non-normalized node coordinates
    Description: When a beam is created, nodes are normalized to the internal model with second node at (positive length, 0,0) and rotation, hence beam axis aligned to local x-axis and rotation stored in placement. Then subsequently, only length and rotation are used for shape generation. For example, if a beam is entered with node coordinates (0,0,0) and (-4010,0,0), they are normalized to (0,0,0) and (4010,0,0) and the structure rotation will be set to 180° around z-axis (see example file in forum discussion.

    With a legacy file, where at one point apparently shapes where generated differently and node coordinates where not normalized, the once properly generated shape may have a wrong orientation after recompute. Also, when node coordinates are edited directly, they are not normalized and length and rotation are not updated, leading to the same discrepancy between node coordinates and shape.

    Instead, I believe normalization should be checked and recalculated to the internal model before shape generation and on change of node coordinates, but I cannot oversee the implications on previous behaviour and potential legacy files.
    Tags:
    Steps To Reproduce: 1. Open the file from forum https://forum.freecadweb.org/download/file.php?id=163600
    2. Switch on node display for the structure and observe generated shape.
    3. Recompute shape.
    4. The shape will be in the wrong place.
    Additional Information:
    Attached Files: 1_before-recompute.PNG (3,471 bytes) 2021-09-24 13:18
    https://tracker.freecad.org/file_download.php?file_id=2702&type=bug
    2_after-recompute.PNG (3,055 bytes) 2021-09-24 13:18
    https://tracker.freecad.org/file_download.php?file_id=2703&type=bug
    Notes
    (0017095)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6264.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4748 [Sketcher] Feature feature always 2021-09-21 23:42 2021-09-21 23:42
    Reporter: chrisb Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: macOS High Sierra (10.13)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24276 (Git)
    Build type: Release
    Branch: (HEAD detached at 0.19.1)
    Hash: a88db11e0a908f6e38f92bfc5187b13ebe470438
    Python version: 3.8.8
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: C/Default (C)
    Summary: Make "Missing coincidences" and "Open vertices" available in Sketcher
    Description: The functions "Missing coincidences" and "Open vertices" from the Validate Sketch tool would be very convenient if they were available directly in Sketcher while editing a sketch.
    Forum discussion
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0017092)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6261.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4747 [PartDesign] Bug minor always 2021-09-21 19:44 2021-09-21 19:44
    Reporter: M4x Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Ubuntu 20.04.3 LTS (ubuntu:GNOME/ubuntu)
    Word size of FreeCAD: 64-bit
    Version: 0.20.25645 (Git) AppImage
    Build type: Release
    Branch: master
    Hash: 37d9757399b4c2ec30318eb88d7cd7c508246345
    Python version: 3.9.7
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.5.2
    Locale: English/United States (en_US)
    Summary: Setting depth in hole feature to "Through all" leads to error message (<Exception> Linked shape object is empty)
    Description: Setting depth in hole feature to "Through all" leads to error message:
    
    22:12:47  No profile linked
    22:12:47  Linked shape object is empty
    22:12:47  Linked shape object is empty
    22:12:47  <Exception> Linked shape object is empty
    

    forum discussion
    PD hole: <Exception> Linked shape object is empty
    linked shape object empty - 0.20 and Link (not 0.19)
    Tags:
    Steps To Reproduce: using the example file example_PD_hole_Link_shape_object_empty_v3
    1. open file
    2. change hole feature depth from "Dimension" to "Through all"
    3. save file
    4. close file
    5. open file

    from scratch
    1. create a new document
    2. ...
    3. create a pad
    4. create a new sketch
    5. use the sketch to create a hole feature
    6. set depth to "Through all"
    7. save the file
    8. close the file
    9. open the file
    Additional Information:
    Attached Files: example_PD_hole_Link_shape_object_empty_v3.FCStd (16,410 bytes) 2021-09-21 19:44
    https://tracker.freecad.org/file_download.php?file_id=2698&type=bug
    Notes
    (0017091)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6260.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1823 [Arch] Bug minor always 2014-11-10 20:52 2021-09-21 08:56
    Reporter: lanciaux Platform:  
    Assigned To: yorik OS:  
    Priority: low OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Working plane not reset under Arch when making new project
    Description: Current working plane settings are not reset after you create a new Project/Sheet.
    Tags: python
    Steps To Reproduce: 1. Make anything you want
    2. Go to Arch
    3. Setup a plane setting by selecting any face of your model
    4. Close this Project/Sheet without saving it
    5. Create a new Project/Sheet

    Additional Information:
    Attached Files:
    Notes
    (0005303)
    yorik   
    2014-11-10 23:55   
    Hm these are two independent things... I'm not sure if it would be a good thing or not to reset the work plane when opening a new model. You might have set it a certain way in another file, that might be convenient to keep it.

    Besides, at the moment there is no mechanism to detect when a new document is opened from python, so this feature cannot be imlemented right now.

    But let's leave it open, an idea could arise.
    (0009277)
    Kunda1   
    2017-06-03 15:47   
    @yorik can you weigh in on this again?
    (0009287)
    yorik   
    2017-06-05 15:46   
    Still no idea on how to detect when a new document has been created/opened :(
    (0010313)
    Kunda1   
    2017-10-18 11:03   

    Besides, at the moment there is no mechanism to detect when a new document is opened from python, so this feature cannot be imlemented right now.

    yorik
    @wmayer care to weigh in?
    (0012237)
    yorik   
    2018-12-05 12:58   
    This is now possible with the DocumentObserver. But since it can be disruptive, it's best to implement after the 0.18 release.
    (0015116)
    Kunda1   
    2020-12-08 01:41   
    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=23&t=53021
    (0015951)
    yorik   
    2021-09-21 08:56   
    New proposal: implementing per-document working plane

    • The grid system is already per view, so each view can display a different grid already.
    • The python interface should stays the same. You just get and set the working plane and shouldn't worry about anything else
    • Two possibilities: 1) FreeCAD.DraftWorkingPlane still give you the current working plane of the document. On switching documents, this value gets changed. A doc observer changes the value each time the active doc is changed or 2) FreeCAD.DraftWorkingPlane is replaced with Draft.getWorkingPlane() which does all the work. I favour 2) but it will break some workbenches
    • The working plane data can be stringified and saved to document meta
    • Draft.getWorkingPlane() always reads from the document meta
    (0016438)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5603.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4636 [Sketcher] Bug minor always 2021-04-17 19:57 2021-09-18 23:00
    Reporter: chrisb Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: <!--ATTENTION:
    COMPLETELY ERASE THIS AFTER PASTING YOUR
    Help > About FreeCAD > Copy to clipboard
    NOTE: just the snippet alone will do without anything else included.
    The ticket will not be submitted without it.
    -->
    Summary: Solver doesn't detect overconstraints
    Description: See forum post.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0015946)
    chrisb   
    2021-09-18 23:00   
    Here is another example of probably the same error: Willem's example.
    (0017033)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6201.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4745 [Path] Bug major always 2021-09-17 07:15 2021-09-17 07:17
    Reporter: mclane Platform: X86-64  
    Assigned To: OS: Linux  
    Priority: normal OS Version: Manjaro  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Manjaro Linux (XFCE/xfce)
    Word size of FreeCAD: 64-bit
    Version: 0.20.25697 (Git)
    Build type: Release
    Branch: master
    Hash: da918350c9efbd7751bd7e48a71cd4bded571500
    Python version: 3.9.6
    Qt version: 5.15.2
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: German/Germany (de_DE)
    Summary: Creating a 2D path job for ShapeStrings fails
    Description: see forum thread

    The creation of a path job with a 2D ShapeString fails with a Python error. This seems to happen only in Linux environments, not in Windows. However, the Python versions are different, see forum thread.
    Tags: Path
    Steps To Reproduce:
    1. Create new document
    2. Go to Draft workbench and create ShapeString
    3. Go To Path workpench and click on CreatePathJob; check 2D ShapeString and click ok
    4. --> Python error is thrown
    Additional Information: 09:10:50 Traceback (most recent call last):
      File "/usr/lib/freecad/Mod/Path/PathScripts/PathStock.py", line 153, in onChanged
        self.execute(obj)
      File "/usr/lib/freecad/Mod/Path/PathScripts/PathStock.py", line 147, in execute
        shape = Part.makeBox(self.length, self.width, self.height, self.origin)
    <class 'ValueError'>: height of box too small
    09:10:50 PathJobGui.ERROR: height of box too small
    09:10:50 Traceback (most recent call last):
    09:10:50 File "/usr/lib/freecad/Mod/Path/PathScripts/PathJobGui.py", line 1561, in Create
        obj = PathJob.Create("Job", base, template)
    09:10:50 File "/usr/lib/freecad/Mod/Path/PathScripts/PathJob.py", line 718, in Create
        obj.Proxy = ObjectJob(obj, models, templateFile)
    09:10:50 File "/usr/lib/freecad/Mod/Path/PathScripts/PathJob.py", line 244, in __init__
        obj.Stock = PathStock.CreateFromTemplate(obj, json.loads(stockTemplate))
    09:10:50 File "/usr/lib/freecad/Mod/Path/PathScripts/PathStock.py", line 390, in CreateFromTemplate
        return CreateFromBase(job, neg, pos, placement)
    09:10:50 File "/usr/lib/freecad/Mod/Path/PathScripts/PathStock.py", line 267, in CreateFromBase
        obj.Proxy.execute(obj)
    09:10:50 File "/usr/lib/freecad/Mod/Path/PathScripts/PathStock.py", line 147, in execute
        shape = Part.makeBox(self.length, self.width, self.height, self.origin)
    09:10:50 ValueError: height of box too small
    09:10:50
    Attached Files:
    Notes
    (0017089)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6258.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3956 [FreeCAD] Bug tweak always 2019-05-02 10:31 2021-09-16 03:51
    Reporter: Phalax Platform:  
    Assigned To: chennes OS:  
    Priority: normal OS Version:  
    Status: feedback Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Possible conflict between QT and Opengl, titlebar overlaps menubar
    Description:
    • Titlebar overlaps menubar
    • Mouse alignment is not correct
    • Working area is blurry

    Found fix here i think: https://doc.qt.io/qt-5/windows-issues.html#fullscreen-opengl-based-windows

    Blender (2.8) have the same problem, there for this is maybe something else.
    Tags:
    Steps To Reproduce:
    Additional Information: OS: Windows 10 (10.0)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.16388 (Git)
    Build type: Release
    Branch: master
    Hash: 473f7ff0113a0f059a832fb74e4e050a12215d3c
    Python version: 3.6.8
    Qt version: 5.12.1
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: Swedish/Sweden (sv_SE)
    Attached Files: 2019-05-02 12_29_23-Clipboard.png (60,099 bytes) 2019-05-02 10:31
    https://tracker.freecad.org/file_download.php?file_id=2205&type=bug
    Notes
    (0015857)
    chennes   
    2021-08-25 03:47   
    The image attached to this report does not seem to work anymore: is there a forums discussion? It looks like the fix is straightforward if this problem is still happening.
    (0015933)
    chennes   
    2021-09-16 03:51   
    @Phalax can you reconfirm this issue, and upload a new version of your screenshot (which seems to have gone missing at some point here)?
    (0016758)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5924.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4734 [FreeCAD] Bug crash always 2021-08-25 18:39 2021-09-08 20:23
    Reporter: Night_Gryphon Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Windows 8.1 (6.3)
    Word size of FreeCAD: 64-bit
    Version: 0.20.24894 (Git)
    Build type: Release
    Branch: master
    Hash: a378b6b66f8a5992fc1452567ff59bdb613abc80
    Python version: 3.8.10
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.5.2
    Locale: Russian/Russia (ru_RU)
    Summary: Crash on start within RDP session
    Description: FreeCad crash on win 8.1 while starting within RDP session. The blank main window appears immediately followed by two crash windows.
    If i start FreeCad from local console and than login with RDP it continue to work.

    Tried with build 0.20.24894 and 0.20.25429 (latest). Same result with 0.19.24267

    The crash log show multiple "Access Violation" errors.

    Forum
    https://forum.freecadweb.org/viewtopic.php?f=3&t=61571
    Tags: crash, Win
    Steps To Reproduce: Login to windows 8.1 machine via RDP
    Start freecad.exe
    Additional Information: Log: Id: 6504: SymInit: Symbol-SearchPath: '.;C:\DIST\FreeCAD_weekly-builds-24894-Win-Conda_vc14.x-x86_64\bin;C:\DIST\FreeCAD_weekly-builds-24894-Win-Conda_vc14.x-x86_64\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: '*****'
    Log: Id: 6504: OS-Version: 6.2.9200 () 0x300-0x1
    Log: Id: 6504: C:\DIST\FreeCAD_weekly-builds-24894-Win-Conda_vc14.x-x86_64\bin\freecad.exe:freecad.exe (00007FF789770000), size: 163840 (result: 0), SymType: '-nosymbols-', PDB: 'C:\DIST\FreeCAD_weekly-builds-24894-Win-Conda_vc14.x-x86_64\bin\freecad.exe', fileVersion: 0.20.0.0
    Log: Id: 6504: C:\WINDOWS\SYSTEM32\ntdll.dll:ntdll.dll (00007FF91CD50000), size: 1757184 (result: 0), SymType: '-exported-', PDB: 'C:\WINDOWS\SYSTEM32\ntdll.dll', fileVersion: 6.3.9600.19678
    Log: Id: 6504: C:\WINDOWS\system32\KERNEL32.DLL:KERNEL32.DLL (00007FF91C570000), size: 1306624 (result: 0), SymType: '-exported-', PDB: 'C:\WINDOWS\system32\KERNEL32.DLL', fileVersion: 6.3.9600.19719
    Log: Id: 6504: C:\WINDOWS\system32\KERNELBASE.dll:KERNELBASE.dll (00007FF91A1B0000), size: 1134592 (result: 0), SymType: '-exported-', PDB: 'C:\WINDOWS\system32\KERNELBASE.dll', fileVersion: 6.3.9600.19724
    Log: Id: 6504: C:\DIST\FreeCAD_weekly-builds-24894-Win-Conda_vc14.x-x86_64\bin\FreeCADGui.dll:FreeCADGui.dll (00007FF8FB5E0000), size: 19902464 (result: 0), SymType: '-exported-', PDB: 'C:\DIST\FreeCAD_weekly-builds-24894-Win-Conda_vc14.x-x86_64\bin\FreeCADGui.dll'
    Log: Id: 6504: C:\DIST\FreeCAD_weekly-builds-24894-Win-Conda_vc14.x-x86_64\bin\FreeCADApp.dll:FreeCADApp.dll (00007FF8FD6F0000), size: 7098368 (result: 0), SymType: '-exported-', PDB: 'C:\DIST\FreeCAD_weekly-builds-24894-Win-Conda_vc14.x-x86_64\bin\FreeCADApp.dll'
    Log: Init: Showing main window
    Log: Main window restored
    Log: Id: 6504: C:\DIST\FreeCAD_weekly-builds-24894-Win-Conda_vc14.x-x86_64\bin\FreeCADBase.dll:FreeCADBase.dll (00007FF9074D0000), size: 2256896 (result: 0), SymType: '-exported-', PDB: 'C:\DIST\FreeCAD_weekly-builds-24894-Win-Conda_vc14.x-x86_64\bin\FreeCADBase.dll'
    Err: Unhandled Base::Exception caught in GUIApplication::notify.
    The error message is: Access violation
    Log: The event type 14 was sent to QtWebEngineCore::RenderWidgetHostViewQtDelegateWidget
    Object tree:
        QtWebEngineCore::RenderWidgetHostViewQtDelegateWidget is child of
        WebGui::WebView is child of
        WebGui::BrowserView is child of
        QMdiSubWindow is child of
        QWidget is child of
        QMdiArea is child of
        Gui::MainWindowErr: Unhandled Base::Exception caught in GUIApplication::notify.
    The error message is: Access violation
    Log: The event type 17 was sent to QtWebEngineCore::RenderWidgetHostViewQtDelegateWidget
    Object tree:
        QtWebEngineCore::RenderWidgetHostViewQtDelegateWidget is child of
        WebGui::WebView is child of
        WebGui::BrowserView is child of
        QMdiSubWindow is child of
        QWidget is child of
        QMdiArea is child of
        Gui::MainWindowLog: Show main window
    Log: Toolbars restored
    Log: 3Dconnexion device not attached.
    Log: Init: Entering event loop
    Err: Unhandled Base::Exception caught in GUIApplication::notify.
    The error message is: Access violation
    Log: The event type 1 was sent to QtWebEngineCore::RenderWidgetHostViewQtDelegateWidget
    Object tree:
        QtWebEngineCore::RenderWidgetHostViewQtDelegateWidget is child of
        WebGui::WebView is child of
        WebGui::BrowserView is child of
        QMdiSubWindow is child of
        QWidget is child of
        QMdiArea is child of
        Gui::MainWindowLog: Id: 6504: C:\DIST\FreeCAD_weekly-builds-24894-Win-Conda_vc14.x-x86_64\bin\MSVCP140.dll:MSVCP140.dll (00007FF9055E0000), size: 598016 (result: 0), SymType: '-exported-', PDB: 'C:\DIST\FreeCAD_weekly-builds-24894-Win-Conda_vc14.x-x86_64\bin\MSVCP140.dll', fileVersion: 14.28.29325.2
    Log: Id: 6504: C:\DIST\FreeCAD_weekly-builds-24894-Win-Conda_vc14.x-x86_64\bin\VCRUNTIME140.dll:VCRUNTIME140.dll (00007FF908D60000), size: 102400 (result: 0), SymType: '-exported-', PDB: 'C:\DIST\FreeCAD_weekly-builds-24894-Win-Conda_vc14.x-x86_64\bin\VCRUNTIME140.dll', fileVersion: 14.28.29325.2
    Log: Id: 6504: C:\WINDOWS\SYSTEM32\api-ms-win-crt-runtime-l1-1-0.dll:api-ms-win-crt-runtime-l1-1-0.dll (00007FF9031C0000), size: 16384 (result: 0), SymType: '-exported-', PDB: 'C:\WINDOWS\SYSTEM32\api-ms-win-crt-runtime-l1-1-0.dll', fileVersion: 10.0.14393.2247
    Log: Id: 6504: C:\WINDOWS\SYSTEM32\api-ms-win-crt-environment-l1-1-0.dll:api-ms-win-crt-environment-l1-1-0.dll (00007FF9129D0000), size: 12288 (result: 0), SymType: '-exported-', PDB: 'C:\WINDOWS\SYSTEM32\api-ms-win-crt-environment-l1-1-0.dll', fileVersion: 10.0.14393.2247
    Log: Id: 6504: C:\WINDOWS\SYSTEM32\api-ms-win-crt-heap-l1-1-0.dll:api-ms-win-crt-heap-l1-1-0.dll (00007FF9031D0000), size: 12288 (result: 0), SymType: '-exported-', PDB: 'C:\WINDOWS\SYSTEM32\api-ms-win-crt-heap-l1-1-0.dll', fileVersion: 10.0.14393.2247
    Log: Id: 6504: C:\WINDOWS\SYSTEM32\api-ms-win-crt-math-l1-1-0.dll:api-ms-win-crt-math-l1-1-0.dll (00007FF912240000), size: 20480 (result: 0), SymType: '-exported-', PDB: 'C:\WINDOWS\SYSTEM32\api-ms-win-crt-math-l1-1-0.dll', fileVersion: 10.0.14393.2247
    Log: Id: 6504: C:\WINDOWS\SYSTEM32\api-ms-win-crt-stdio-l1-1-0.dll:api-ms-win-crt-stdio-l1-1-0.dll (00007FF9031E0000), size: 16384 (result: 0), SymType: '-exported-', PDB: 'C:\WINDOWS\SYSTEM32\api-ms-win-crt-stdio-l1-1-0.dll', fileVersion: 10.0.14393.2247
    Err: Unhandled Base::Exception caught in GUIApplication::notify.
    The error message is: Access violation
    Log: The event type 14 was sent to QtWebEngineCore::RenderWidgetHostViewQtDelegateWidget
    Object tree:
        QtWebEngineCore::RenderWidgetHostViewQtDelegateWidget is child of
        WebGui::WebView is child of
        WebGui::BrowserView is child of
        QMdiSubWindow is child of
        QWidget is child of
        QMdiArea is child of
        Gui::MainWindowLog: Id: 6504: C:\WINDOWS\SYSTEM32\api-ms-win-crt-locale-l1-1-0.dll:api-ms-win-crt-locale-l1-1-0.dll (00007FF910270000), size: 12288 (result: 0), SymType: '-exported-', PDB: 'C:\WINDOWS\SYSTEM32\api-ms-win-crt-locale-l1-1-0.dll', fileVersion: 10.0.14393.2247
    Log: Init: Processing command line files
    Err: Unhandled Base::Exception caught in GUIApplication::notify.
    The error message is: Access violation
    Err: Unhandled Base::Exception caught in GUIApplication::notify.
    The error message is: Access violation
    Log: Id: 6504: C:\DIST\FreeCAD_weekly-builds-24894-Win-Conda_vc14.x-x86_64\bin\Qt5Widgets_conda.dll:Qt5Widgets_conda.dll (00007FF8FD190000), size: 5591040 (result: 0), SymType: '-exported-', PDB: 'C:\DIST\FreeCAD_weekly-builds-24894-Win-Conda_vc14.x-x86_64\bin\Qt5Widgets_conda.dll', fileVersion: 5.12.9.0
    Err: Unhandled Base::Exception caught in GUIApplication::notify.
    The error message is: Access violation
    Log: The event type 77 was sent to Gui::MainWindow
    Object tree:
        Gui::MainWindowErr: Unhandled Base::Exception caught in GUIApplication::notify.
    The error message is: Access violation
    Log: The event type 77 was sent to Gui::MainWindow
    Object tree:
        Gui::MainWindowErr: Unhandled Base::Exception caught in GUIApplication::notify.
    The error message is: Access violation
    Log: The event type 77 was sent to Gui::MainWindow
    Object tree:
        Gui::MainWindowErr: Unhandled Base::Exception caught in GUIApplication::notify.
    The error message is: Access violation
    Log: The event type 77 was sent to Gui::MainWindow
    Object tree:
        Gui::MainWindowErr: Unhandled Base::Exception caught in GUIApplication::notify.
    The error message is: Access violation
    Log: The event type 77 was sent to Gui::MainWindow
    ...
    Attached Files:
    Notes
    (0015914)
    Night_Gryphon   
    2021-09-08 09:00   
    Using MESA3D solved the problem

    https://forum.freecadweb.org/viewtopic.php?p=414094#p414094

    Please add MESA3D library to FreeCAD distribution and some checks to load Mesa3D in case system OpenGL lib is non functional...
    (0017084)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6253.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1980 [Draft] Feature minor always 2015-02-23 14:51 2021-09-08 13:58
    Reporter: microelly2 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.14  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: better hatch Pattern presentation for planes not parallel to xy
    Description: please change the Draft.py

    see http://forum.freecadweb.org/viewtopic.php?f=9&t=4264&start=10#p79888
    Tags: hatch
    Steps To Reproduce: testcase file see forum entry
    Additional Information:
    Attached Files:
    Notes
    (0008928)
    Kunda1   
    2017-05-10 02:57   
    @microelly2 any progress on this?
    (0016450)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5615.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4454 [FreeCAD] Feature feature always 2020-10-09 13:20 2021-09-07 21:40
    Reporter: efa Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 10 (10.0)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.22665 (Git)
    Build type: Release
    Branch: master
    Hash: b0d7850406e046f3b7a8cd5da261e7d54df6bd99
    Python version: 3.8.6
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: Italian/Italy (it_IT)
    Summary: DXF files open with wrong line thickness. Resaving lost thickness information
    Description: hi,
    the line thickness when importing DXF is wrong.
    The exported files become corrupt lost thickness information
    Tags: DXF
    Steps To Reproduce: Open a DXF file with line thinckness set, use the attached as test.
    The line property "polyline width" is not rendered
    Export as DXF
    Open the exported DXF with QCAD pro, the line thinkness is wrong
    Additional Information: the problem is present in LibreCAD and QCAD Community edition too, see:
    https://sourceforge.net/p/librecad/bugs/520/

    QCAD Pro and Autodesk TrueView open DXF correctly
    Attached Files: PCBtracks_demo.7z (14,832 bytes) 2020-10-09 13:20
    https://tracker.freecad.org/file_download.php?file_id=2537&type=bug
    PCBtracks_demo.png (119,668 bytes) 2020-10-09 13:20
    https://tracker.freecad.org/file_download.php?file_id=2538&type=bug
    PCBtracks_demo_FreeCAD.png (154,729 bytes) 2020-10-10 20:15
    https://tracker.freecad.org/file_download.php?file_id=2539&type=bug
    FreeCAD_DXFinport.png (291,515 bytes) 2021-09-07 17:35
    https://tracker.freecad.org/file_download.php?file_id=2690&type=bug
    PCB_Test.png (77,483 bytes) 2021-09-07 21:15
    https://tracker.freecad.org/file_download.php?file_id=2691&type=bug
    Notes
    (0014805)
    openBrain   
    2020-10-09 21:09   
    @efa : please address your issue according our reporting guidelines by opening a new topic on our forum. Thx
    (0014827)
    efa   
    2020-10-10 19:59   
    https://forum.freecadweb.org/viewtopic.php?f=8&t=51003
    (0014828)
    efa   
    2020-10-10 20:15   
    (Last edited: 2020-10-10 20:18)

    (0014829)
    efa   
    2020-10-10 20:18   
    see how is rendered by FreeCAD last stable on Linux:

    OS: LMDE 4 (debbie)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.
    Build type: Release
    Python version: 2.7.16rc1
    Qt version: 5.11.3
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: Italian/Italy (it_IT)

    same as 0.19 on Windows
    (0015285)
    chennes   
    2021-02-07 06:02   
    I can confirm this in:
    OS: Windows 10 Version 2004
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.23935 (Git)
    Build type: Debug
    Branch: master
    Hash: d5b68febbb4989b290b9af36bb2cb21d61a87a2e
    Python version: 3.8.6+
    Qt version: 5.15.1
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: English/United States (en_US)

    The width is simply being exported as the scale, rather than whatever the value of the width was supposed to be. If you use the FreeCAD option renderPolylineWidth in the DXF import preferences settings you can get FC to try to render the line with width, but this does not fix the export issue.
    (0015297)
    efa   
    2021-02-07 15:34   
    on Linux, 0.19dev also with renderPolylineWidth in the DXF import active, I can't see right tickness:

    OS: LMDE 4 (debbie) (MATE/mate)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.23756 (Git) AppImage
    Build type: Release
    Branch: master
    Hash: 9c6e9184930a52b165a0b7274e3a45d1006bfe67
    Python version: 3.8.6
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: Italian/Italy (it_IT)
    (0015869)
    chennes   
    2021-08-26 15:10   
    FreeCAD's lines don't have the concept of individual width -- using the user preference option "Render Polylines with Width" will allow the conversion of the lines into rectangles internally so that this file displays more correctly. But note that this will change their representation in any DXF file that is then exported from FreeCAD. I've marked this as a "feature request" as in the long term, improved import and export of DXF files might be desirable.
    (0015878)
    efa   
    2021-08-27 14:08   
    (Last edited: 2021-08-28 14:10)
    just upgraded from
    FreeCAD_0.19-23756-Linux-Conda_glibc2.12-x86_64.AppImage
    to
    FreeCAD_0.19-24291-Linux-Conda_glibc2.12-x86_64.AppImage
    I keep the Preference, Import/Export, DXF: Draw polyline width set
    but I still get all lines at minimum width as in the PCBtracks_demo_FreeCAD.png
    I cannot get rectangles
    (0015906)
    chennes   
    2021-09-06 20:11   
    Are you using the legacy Python importer? I don't think the newer C++ importer supports the width parameter at all yet.
    (0015907)
    efa   
    2021-09-06 20:28   
    I think it is the default one.
    How can I check which importer is used?
    (0015908)
    chennes   
    2021-09-07 14:02   
    Preferences->Import/Export->DXF->Use Python Legacy Importer (which is not the default, I don't think).
    (0015910)
    efa   
    2021-09-07 17:35   
    it was selected "Usa il vecchio importatore python" that should be the Python Legacy Importer, I de-selected it, but the results is the same.
    Attached the dialog box, is there something I had to set different?
    (0015911)
    chennes   
    2021-09-07 21:15   
    You should have "Usa il vecchio importatore python" checked, but that's otherwise correct I think. When I select those options this is what I get:
    (0015912)
    efa   
    2021-09-07 21:38   
    (Last edited: 2021-09-07 21:40)
    OK, using the old python importer I get your output, and its lot better.
    Probably in the past I had selected only old python exporter
    (0016945)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6112.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2839 [Path] Feature minor always 2017-01-11 01:20 2021-09-06 10:21
    Reporter: mlampert Platform: all  
    Assigned To: mlampert OS: all  
    Priority: normal OS Version: all  
    Status: acknowledged Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Dogbone dressup needs visualisation and preferences
    Description: Dogbone should have a way of visualising the currently selected bone, similar to how HoldingTags displays the currently selected tags (and synchronises the visualisation with the list selection).

    Similarly the default settings for the dressup should be held in the preferences
    Tags: dogbone
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0010925)
    flopsy   
    2018-02-05 23:45   
    (Last edited: 2018-02-05 23:46)
    i'm on it to do some artwork/pictures/visualization. For Dogbone is on my todo-list, too...(just pictures not "hard-code"-visualization like "tag-dressup", but maybe it will help, too...)

    (0015531)
    mlampert   
    2021-03-18 03:08   
    https://github.com/FreeCAD/FreeCAD/pull/4634

    Can't think of any preferences to add
    (0015905)
    Kunda1   
    2021-09-06 10:20   
    (Last edited: 2021-09-06 10:21)
    FreeCAD master 515c7deb

    edit: manually associated commit to this ticket
    (0016512)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5677.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4740 [Path] Bug minor always 2021-09-04 18:46 2021-09-06 10:18
    Reporter: kormorix Platform: Ryzentosh  
    Assigned To: OS: MacOS  
    Priority: normal OS Version: Catalina  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: macOS 10.15
    Word size of FreeCAD: 64-bit
    Version: 0.20.25566 (Git)
    Build type: Release
    Branch: master
    Hash: 8c361dd3fc83840a911da950a845eb9f9342a0b6
    Python version: 3.9.6
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.5.2
    Locale: C/Default (C)

    Summary: Dogbone Dressup does not work in corners with an edge length of less than 1.9mm
    Description: de: DogboneDressup funktioniert nicht in Ecken mit Kantenlänge kleiner 1,9mm, wenn die Ecke aus Richtung der kurzen Kante angefahren wird.

    en: DogboneDressup does not work in corners with an edge length of less than 1.9mm if the corner is approached from the direction of the short edge.
    Tags: dogbone
    Steps To Reproduce: de: Rechteckiges Teil, Dicke z.B. 4mm, mit Zapfen konstruieren (siehe Anhang).
    In "path" einen Job anlegen, 2mm Schaftfräser soll Aussenkontur des Teils fräsen. Das erzeugte "Profile" mit der Eigenschaft "DogboneDressup" versehen. Bei Kantenlängen des Zapfens von weniger als 1,9mm erzeugt FreeCAD nur an der einen (in der Bearbeitungsrichtung ersten Ecke) von zwei Innenecken den Dogbone, wenn clockwise gefräst wird. Bei CCW gar kein Dogbone.

    Nachtrag: ist vom Fräser-Durchmesser abhängig! Das oben beschriebene gilt für Fräser-Durchmesser = 2mm!
    Nachtrag: Abhängig direkt vom Fräserdurchmesser. In obigem Beispiel war der Fräserdurchmesser real 1,9mm (und nicht 2,0mm!).

    Die Dogbone-Eigenschaften (Doppelklick auf DogboneDressup) funktionieren entsprechend auch nicht richtig.

    en: Construct a rectangular part, e.g. 4mm thick, with tenons (see appendix).
    Create a job in "path", the 2mm end mill is to mill the outer contour of the part. Provide the created "Profile" with the property "DogboneDressup". If the tenon edge lengths are less than 1.9mm, FreeCAD only creates the dogbone at one (first corner in the machining direction) of two inside corners when milling clockwise. At CCW no dogbone at all.

    Addendum: depends on the cutter diameter! The above described applies to cutter diameter = 2mm!
    Addendum: Depending directly on the cutter diameter. In the example above, the cutter diameter was actually 1.9mm (and not 2.0mm!).

    The dogbone properties (double click on DogboneDressup) do not work properly either.
    Additional Information: de:Bei der vorangegangenen Version 24276 habe ich das nicht beobachtet (muß aber nicht heißen, daß es dort nicht auftrat).

    en: I did not observe this in the previous version 24276 (but does not have to mean that it did not occur there).
    Attached Files: Bildschirmfoto 2021-09-04 um 18.41.59.png (182,276 bytes) 2021-09-04 18:49
    https://tracker.freecad.org/file_download.php?file_id=2687&type=bug
    Bildschirmfoto 2021-09-04 um 18.41.28.png (43,827 bytes) 2021-09-04 18:49
    https://tracker.freecad.org/file_download.php?file_id=2688&type=bug
    Bildschirmfoto 2021-09-04 um 18.40.39.png (43,087 bytes) 2021-09-04 18:49
    https://tracker.freecad.org/file_download.php?file_id=2689&type=bug
    Notes
    (0015900)
    kormorix   
    2021-09-04 18:49   
    ... hier noch die Anlagen (screenshots)
    (0015901)
    kormorix   
    2021-09-04 20:28   
  • (0015903)
    Kunda1   
    2021-09-06 10:14   
    Thank you, in the future please discuss the issue on the Path forum first (our guidelines for reporting bugs is to use the forum, that's because sometimes tickets aren't necessary due to fixes made on the spot. Also please translate bugs to english. Thanks again.)
    (0015904)
    Kunda1   
    2021-09-06 10:17   
    CC @sliptonic
    (0017088)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6257.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2584 [Arch] Feature minor have not tried 2016-06-11 15:06 2021-09-06 10:08
    Reporter: yorik Platform: PC  
    Assigned To: yorik OS: Debian  
    Priority: normal OS Version: Testing 64bit  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Support for SweetHome3D xml-based files
    Description: SweetHome3D ( http://www.sweethome3d.com/ ) has a plugin ( http://www.sweethome3d.com/blog/2016/05/05/export_to_html5_plug_in.html ) that exports the contents of a file as a zip that contains a master xml file describing the walls and the objects placements, and an obj file for each piece of furniture.

    This format could be easily imported and exported by FreeCAD.

    Currently that .zip is not reimportable in SH3D, but that's in their plans...
    Tags: #lowhangingfruit, export, import
    Steps To Reproduce:
    Additional Information: Using Yorik's SweetHome3D importer https://forum.freecadweb.org/viewtopic.php?f=23&t=16205
    Sweet Home 3D integration/collaboration - https://forum.freecadweb.org/viewtopic.php?f=8&t=23965
    System Description
    Attached Files: testhouse.zip (840,821 bytes) 2016-06-13 14:41
    https://tracker.freecad.org/file_download.php?file_id=1281&type=bug
    Notes
    (0007143)
    yorik   
    2016-06-13 14:41   
    New version of the plugin that exports walls as xml: http://www.sweethome3d.com/plugins/ExportToXMLOBJ-1.1.sh3p see annexed example file

    Discussion thread: http://www.sweethome3d.com/support/forum/viewthread_thread,6708_offset,25

    Discussion about reimporting such data in SH3d: http://www.sweethome3d.com/support/forum/viewthread_thread,6708_offset,20
    (0008715)
    Kunda1   
    2017-03-27 15:33   
    (Last edited: 2017-03-27 15:33)
    @yorik FYI plugins updated per http://www.sweethome3d.com/support/forum/viewthread_thread,6708_offset,30#32844
    Here's the new versions 1.2 of Export to HTML5 and Export to XML/OBJ plug-ins.
    Both plug-ins are now based on the management of the new XML entry that was added to .sh3d files in Sweet Home 3D 5.3. The JavaScript part of the Export to HTML5 plug-in now supports pinch for zoom under Android and Windows, and was optimized to draw 3D lines faster.

    (0008872)
    yorik   
    2017-05-02 22:56   
    Yes the plugin is now part of the 5.3 version, no need to install anything more, normally. I still need to test, though
    (0009925)
    Kunda1   
    2017-08-14 00:24   
    @yorik can you test this and confirm ?
    (0011365)
    Kunda1   
    2018-06-07 21:53   
    Relevant:
    SweetHome3D HTML5/XML to Blender importer
    (0015902)
    Kunda1   
    2021-09-06 10:08   
    Progress made by user 'laschrocket' in https://forum.freecadweb.org/viewtopic.php?p=530893#p530893
    (0016493)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5658.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4658 [Path] Bug major always 2021-05-12 11:06 2021-09-03 22:27
    Reporter: dmitry_sushkov Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information:
    Summary: Incorrect paths generated by adaptive clearing
    Description: Adaptive clearing without "use outline" generating incomplete path. With "use outline" it goes out of boundary in one place.

    here is the file:
    https://drive.google.com/file/d/1kwrOw5bVSPOU0QoOWJmXbtGHRwC3RMcf/view?usp=sharing

    Here is the forum discussion:
    https://forum.freecadweb.org/viewtopic.php?f=15&t=58547&p=503248#p503248
    Tags:
    Steps To Reproduce: Use attached file and create adaptive clearing operation with settings from screenshots.
    Both paths with "use outline" and without are incorrect.
    Additional Information:
    Attached Files: adaptiveError.FCStd (312,272 bytes) 2021-08-29 13:46
    https://tracker.freecad.org/file_download.php?file_id=2686&type=bug
    Notes
    (0015661)
    chrisb   
    2021-05-13 10:01   
    (Last edited: 2021-05-13 10:03)
    I have simplified the file so that it still shows the error. The file couldn't be added to the tracker, I add it to the forum.
    (0015881)
    Kunda1   
    2021-08-29 13:46   
    Added chrisb's simplified example
    (0015899)
    russ4262   
    2021-09-03 22:27   
    Confirmed. The Adaptive operation has some internal bugs related to path generation, mainly of two types.
    The first type is an odd lateral path from the correct clearing area outward to the perimeter of the target area. The second type is a larger path generation bug resulting in a partial path set for a given target area, as though part of the target area is ignored or truncated. This second type seems to have some correlation to complex shapes and curves.
    (0017048)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6217.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4647 [Path] Bug minor always 2021-04-28 15:23 2021-09-03 22:19
    Reporter: dubstar_04 Platform:  
    Assigned To: russ4262 OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: <!--ATTENTION:
    COMPLETELY ERASE THIS AFTER PASTING YOUR
    Help > About FreeCAD > Copy to clipboard
    NOTE: just the snippet alone will do without anything else included.
    The ticket will not be submitted without it.
    -->
    Summary: [Path] - Releative location of Toolbit files
    Description:
    It's currently not possible to create a toolbit library using relative paths.

    This means that is not possible to share libraries between machines / different OS'

    https://github.com/FreeCAD/FreeCAD/blob/master/src/Mod/Path/PathScripts/PathToolBit.py#L107-L117

    https://forum.freecadweb.org/viewtopic.php?f=15&t=58174&sid=5c2c7fda248c0380c556a4813e7f749b
    Tags:
    Steps To Reproduce: 1. Delete FreeCAD config
    2. Create completely new tool library in an empty directory
    3. Create a toolbit
    4. check fctl and tctb
    Additional Information:
    Attached Files:
    Notes
    (0015647)
    dubstar_04   
    2021-05-04 06:48   
    Forum Link: https://forum.freecadweb.org/viewtopic.php?f=15&t=58174&sid=3d0acf6eccb83839ec06242a3d5469f7
    (0015748)
    russ4262   
    2021-07-25 04:09   
    PR #4906 contains a possible fix for this issue.
    (0015894)
    russ4262   
    2021-09-03 22:03   
    @dubstar_04, @sliptonic
    Has this issue been fixed? Are we accepting PR #4906 as the fix for this bug, or only a partial fix since it limits the scope of the relative paths to within a given set of `Library`, `Bit`, and `Shape` folders? Any ideas?
    (0015898)
    russ4262   
    2021-09-03 22:19   
    I can confirm bug as reported.
    (0017041)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6209.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4645 [Path] Bug tweak always 2021-04-27 03:51 2021-09-03 22:16
    Reporter: c4g Platform:  
    Assigned To: russ4262 OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Ubuntu 20.04 LTS snap Core 20 (Unity:Unity7:ubuntu/unity)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24276 (Git)
    Build type: Unknown
    Branch: releases/FreeCAD-0-19
    Hash: a88db11e0a908f6e38f92bfc5187b13ebe470438
    Python version: 3.8.5
    Qt version: 5.12.8
    Coin version: 4.0.0
    OCC version: 7.5.0
    Locale: English/United States (en_US)
    Summary: Add python exceptions to PathJob.py
    Description: 23:12:10 Traceback (most recent call last):
      File "/snap/freecad/22/opt/local/FreeCAD-0.19/Mod/Path/PathScripts/PathJob.py", line 401, in execute
        obj.Path = obj.Operations.Path
    <class 'AttributeError'>: 'NoneType' object has no attribute 'Path'
    23:12:10 <Exception> ObjectIdentifier.cpp(1511): Document object 'SetupSheet' not found in 'SetupSheet.ClearanceHeightOffset'
    in property binding 'ClearanceHeight'
    23:12:17 Traceback (most recent call last):
      File "/snap/freecad/22/opt/local/FreeCAD-0.19/Mod/Path/PathScripts/PathJob.py", line 401, in execute
        obj.Path = obj.Operations.Path
    <class 'AttributeError'>: 'NoneType' object has no attribute 'Path'
    23:12:22 Traceback (most recent call last):
      File "/snap/freecad/22/opt/local/FreeCAD-0.19/Mod/Path/PathScripts/PathJobGui.py", line 232, in onDelete
        self.obj.Proxy.onDelete(self.obj, arg2)
      File "/snap/freecad/22/opt/local/FreeCAD-0.19/Mod/Path/PathScripts/PathJob.py", line 227, in onDelete
        PathLog.debug('taking down ops: %s' % [o.Name for o in self.allOperations()])
      File "/snap/freecad/22/opt/local/FreeCAD-0.19/Mod/Path/PathScripts/PathJob.py", line 470, in allOperations
        for op in self.obj.Operations.Group:
    <class 'AttributeError'>: 'NoneType' object has no attribute 'Group'
    Tags: Path
    Steps To Reproduce: Create a Path Job and add an operation. Then delete the child entries from the job. Try to edit or delete the empty job. This python exception then blocks PathJob.py from functioning.
    Additional Information:
    Attached Files: camtest_bug.FCStd (19,783 bytes) 2021-04-27 03:51
    https://tracker.freecad.org/file_download.php?file_id=2680&type=bug
    Notes
    (0015771)
    gift   
    2021-08-03 06:25   
    Hello c4g,

    you choose the wrong project. It should Path and not Part.
    (0015860)
    Kunda1   
    2021-08-25 14:29   
    @c4g Please post to the forum first next time per our guidelines
    I went ahead and opened a thread for you: https://forum.freecadweb.org/viewtopic.php?f=15&t=61563
    (0015896)
    russ4262   
    2021-09-03 22:15   
    PR #5008 is active and addresses this bug.
    (0015897)
    russ4262   
    2021-09-03 22:16   
    I can confirm an error is thrown if one or more children of a Job object are deleted.
    (0017039)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6207.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4704 [Path] Bug minor always 2021-07-11 09:06 2021-09-03 22:13
    Reporter: Giulio Buccini Platform: Ubuntu  
    Assigned To: russ4262 OS:  
    Priority: normal OS Version:  
    Status: resolved Product Version: 0.20  
    Product Build: Resolution: fixed  
    Projection: none      
    ETA: none Fixed in Version: 0.20  
        Target Version:  
    FreeCAD Information: OS: Ubuntu 16.04.7 LTS (XFCE/xfce)
    Word size of FreeCAD: 64-bit
    Version: 0.20.25065 (Git) AppImage
    Build type: Release
    Branch: master
    Hash: 4de2ad46b2b9c78ac2721a0dbea7c19306261095
    Python version: 3.9.4
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.5.2
    Locale: English/United States (en_US)
    Summary: [Path] Arrays are not included in the Path Simulation
    Description: An "Array" operation is not displayed by the Path-Simulator. Only the original, single, operation is shown after pressing the "Play" button.
    On the other side, the generated g-code is correct.

    The Freecad file is attached.
    Tags: Path
    Steps To Reproduce: Refer to thread:
    https://forum.freecadweb.org/viewtopic.php?f=15&t=60049&sid=5dcbec38eac8eb4c4b843c6e5ada0615
    Additional Information: The "active" property must be added and flagged to true, as depicted in the thread.
    Attached Files:
    Notes
    (0015746)
    russ4262   
    2021-07-25 03:33   
    Fix is contained in PR 0004818.
    (0015895)
    russ4262   
    2021-09-03 22:13   
    PR 0004818
    (0017072)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6241.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4736 [FreeCAD] Feature feature N/A 2021-08-26 17:07 2021-08-30 17:43
    Reporter: NewJoker Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Windows 10 Version 2009
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24276 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-19
    Hash: a88db11e0a908f6e38f92bfc5187b13ebe470438
    Python version: 3.8.6+
    Qt version: 5.15.1
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: Polish/Poland (pl_PL)
    Summary: Integration of Curves workbench
    Description: Curves workbench is one of the most useful and important add-on modules for FreeCAD. It provides tools that can be considered as crucial for many designs, regardless of the branch of engineering. Thus, it would be great to have it integrated with FreeCAD.

    Forum thread (mentioned): https://forum.freecadweb.org/viewtopic.php?f=8&t=61453&start=13
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0015887)
    openBrain   
    2021-08-30 17:43   
    Would upvote this one. :)
    (0017086)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6255.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4561 [Path] Bug crash always 2021-02-11 15:05 2021-08-29 18:31
    Reporter: sliptonic Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.19  
    FreeCAD Information: OS: Linux Mint 20 (i3/i3)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.23964 +1 (Git)
    Build type: Unknown
    Branch: (HEAD detached at upstream/pr/4383)
    Hash: 9dce167073d90460478efb0d38056e4fcb116e6e
    Python version: 3.8.5
    Qt version: 5.12.8
    Coin version: 4.0.0
    OCC version: 7.3.0
    Locale: English/United States (en_US)
    Summary: OpenCamLib (OCL) raises an error on incorrect tool attributes and causes FreeCAD segfault
    Description: https://forum.freecadweb.org/viewtopic.php?f=15&t=55240

    The sample file requires the legacy tools to be enabled but appears to be related to passing incorrectly defined tools to OCL.

    FreeCAD: /home/brad/opencamlib/src/cutters/ballcutter.cpp:41: ocl::BallCutter::BallCutter(double, double): Assertion `length>0.0' failed.
    Aborted (core dumped)

    Tool type: Engraver
    FreeCAD: /home/brad/opencamlib/src/cutters/conecutter.cpp:46: ocl::ConeCutter::ConeCutter(double, double, double): Assertion `center_height > 0.0' failed.
    Aborted (core dumped
    Tags:
    Steps To Reproduce: Open the cone crasher file. Change the surface operation to use one of the other tools and recompute.
    Additional Information: May not affect all platforms.
    Known to crash on Mint and Fedora

    We don't plan to fix legacy tools to prevent bad user data but handling of the OCL error should be fixed
    Attached Files: cone-crasher.FCStd (224,307 bytes) 2021-02-11 15:05
    https://tracker.freecad.org/file_download.php?file_id=2618&type=bug
    Notes
    (0015325)
    fremen   
    2021-02-11 17:23   
    C++ assert() will cause a core dump unless NBEBUG is set. That may need doing for release builds.
    (0015346)
    fremen   
    2021-02-15 09:52   
    https://github.com/FreeCAD/FreeCAD/pull/4433
    (0015419)
    StefanBruens   
    2021-02-22 21:37   
    The pull request has been merged, so this can be closed, correct?
    (0015421)
    fremen   
    2021-02-23 07:59   
    The PR I provided fixed two specific errors in FC which were triggering coredumps. The question remains, is this error trap outcome desirable in a stable release or should it be trapped/handled differently.

    If there is a future error condition is discovered, is it desirable that the user gets faced with a core dump?

    This was clearly intended as debugging outcome in OCL and there is a variable to turn it off. Since OLC is currently compiled outside of FC and to all intents and purposes has no active developer this cannot be fixed from FC.

    One option would be to fork OCL into FC tree and detect the error condition in a more contorlled manner or submit a PR to OLC if that is preferable.

    In short the PR fixed a local bug triggering an instance of the problem, it does not fix the problem.
    (0015882)
    Kunda1   
    2021-08-29 18:29   
    FreeCAD master ab186aa0
    (0015883)
    Kunda1   
    2021-08-29 18:31   
    @sliptonic when you get a chance, can you weigh in on this ?
    (0016992)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6160.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4576 [FreeCAD] Bug minor have not tried 2021-02-27 15:12 2021-08-27 02:59
    Reporter: StefanBruens Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: openSUSE Tumbleweed (KDE//usr/share/xsessions/plasma5)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.Unknown
    Build type: Release
    Python version: 3.8.7
    Qt version: 5.15.2
    Coin version: 3.1.3
    OCC version: 7.5.1
    Locale: English/United States (en_US)
    Summary: Prefer new-style/functor QObject::connect over string based
    Description: New-style or functor based connects allow compile-time checking of signal/slot arguments.

    Usage of small lambdas often also allows to get rid of small helper slots/functions.

    E.g. (src/Gui/Filedialog.cpp):

    
        connect(this, SIGNAL(filterSelected(const QString&)),
                this, SLOT(onSelectedFilter(const QString&)));
    
    becomes
    
        connect(this, &Filedialog::filterSelected,
                this, &Filedialog::onSelectedFilter);
    
    Tags: Qt
    Steps To Reproduce:
    Additional Information: https://doc.qt.io/qt-5/signalsandslots-syntaxes.html

    https://wiki.qt.io/New_Signal_Slot_Syntax

    Attached Files:
    Notes
    (0015456)
    wmayer   
    2021-02-28 07:07   
    With v0.19 we still support Qt4 (and Py2) which doesn't support the offered method. Now with the started development of v0.20 we will drop Qt4/Py2 support and can start to use the new stuff.
    (0015564)
    Kunda1   
    2021-03-28 11:44   
    @wmayer should we do this before or after Toponaming patch (@realthunder is planning to submit a patch by the end of the month, is what he mentioned to me)
    (0015874)
    chennes   
    2021-08-27 02:59   
    This is not really a bug, more of a "going forward we should code like this" -- while I agree with the sentiment, and my recent PRs have followed this practice, I don't think it's something we want to go back through the whole codebase and replace. We can just update over time as the code gets modified.
    (0016998)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6166.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4735 [FreeCAD] Feature feature N/A 2021-08-26 16:58 2021-08-26 16:58
    Reporter: NewJoker Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Windows 10 Version 2009
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24276 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-19
    Hash: a88db11e0a908f6e38f92bfc5187b13ebe470438
    Python version: 3.8.6+
    Qt version: 5.15.1
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: Polish/Poland (pl_PL)
    Summary: Integration of 3D Parametric Curve macro
    Description: I think that it would be nice to have the 3D Parametric Curve macro implemented as a built-in function in FreeCAD. That's because this can be considered as one of the core functionalities of CAD software.

    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=61453
    Tags: macros
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0017085)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6254.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4036 [Path] Bug minor always 2019-06-25 18:43 2021-08-25 17:49
    Reporter: freman Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Job | Tool editor does not get keystrokes when mm/s items are selected.
    Description: when attempting to input cutting speeds into Job edit | Tools tab, keystrokes go to 3D view window and change the view. Annoying and confusing.


    BTW, these columns do not have meaningful headers. "mm/s" is not the quantity being input, it is the units. User is left to guess which is XY cutting speed and which is Z cutting speed. Space if tight but the unit is not the right text for the header.
    Tags:
    Steps To Reproduce: create a job
    set 3D view to isometric
    go to edit job
    select tool edit tab
    click once is one of the "mm/s" text entry boxes
    note text entry is dark blue indicating it is selected and should recv. keyboard focus
    type numeric key 6
    note 3D view jumps to different view
    type numeric key 2
    note 3D view jumps to different view
    type numeric key 8 ( out of range of view numbers )
    note digit is entered in edit box as expected.

    Clearly the keyboard events are going initially to the 3D window, it this does not catch the event it is passed to the active editbox.

    Additional Information: OS: Linux (LXDE/LXDE)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.17119 (Git)
    Build type: Release
    Branch: master
    Hash: e72b48e0cfcf4773e4b6527c74f2bac11ccff1ab
    Python version: 2.7.15
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedKingdom (en_GB)
    Attached Files:
    Notes
    (0013309)
    openBrain   
    2019-06-25 18:59   
    @freman : could you please at least precise which WB you're using ? ;)
    (0013311)
    freman   
    2019-06-25 20:16   
    Sorry, isn't Job and Job Edit specific to Path?
    (0016788)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5954.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3996 [Sketcher] Feature minor always 2019-05-31 08:09 2021-08-25 17:46
    Reporter: bzb.dev001 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Shortcut buttons for primitive shapes are not highlighted when active
    Description: In sketcher workbench. When user click on a shortcut button for primitive shapes(eg. line, arc, circle, etc), the button should change to indicate that it is currently active.
    Tags:
    Steps To Reproduce: Create new document
    create body
    create new sketch
    select plane for sketch
    click on a shortcut button for one of the sketch primitives(eg. line,arc,circle,etc)
    notice the button remains the same. The button should change to indicate that the selected primitive is currently active.
    Additional Information: OS: Ubuntu 18.04.2 LTS (LXDE/Lubuntu)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.16854 (Git) AppImage
    Build type: Release
    Branch: master
    Hash: fe0fd5512ba9a8a9c729cdc47af35bbe965050ac
    Python version: 3.7.1
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/Canada (en_CA)
    Attached Files:
    Notes
    (0016773)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5939.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3958 [Part] Bug major always 2019-05-03 03:48 2021-08-25 17:36
    Reporter: jr222 Platform: Windows  
    Assigned To: OS: Windows 10  
    Priority: normal OS Version: 10.0.17134.706  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Boolean Cut not working correctly when using arrays (polar in this case)
    Description: When doing a boolean difference between an object and an array of objects, some of the objects within the array seem to not cut correctly, while others do.

    I posted a [url= https://forum.freecadweb.org/viewtopic.php?f=3&t=36090]forum question in the Freecad forum[/url], and the problem was reproduced by most users that tested it. Some supplied workarounds, but these are not possible for more complex projects.

    This does look like a bug, as it is reproducible. It seems that the more complex the compound objects, the easier it is to reproduce.

    The example is the inner portion of a ball bearing model for 3D printing.


    Tags: array, boolean
    Steps To Reproduce: This example has the complexity required to reproduce the bug (most operations in the part workbench - parameters mentioned are changed from the default):
    1. Create a torus (r1=36mm, r2=4mm)
    2. Create a half sphere (rad=5mm, angle3=180, placement-angle=90, position.X=40mm)
    3. Use Draft Array to make a polar array from the half spheres (type=polar, number.polar=16)
    4. Fuse the torus and half-sphere-array (using boolean union)
    5. Create a smaller full sphere (rad=4.5mm, position.X=40mm)
    6. 3. Use Draft Array to make a polar array from the full smaller spheres (type=polar, number.polar=16)
    7. Cut the smaller full sphere array from the Fusion object from step 4 using Boolean difference
    8. Create a cylinder (rad=37.5mm, position.Z=-5mm)
    9. Cut the Cylinder from the "Cut" object from step 7 using Boolean difference
    Note that some of the smaller balls did not cutout the inside of the compound object.
    (in the example I copied, I changed the NumberX and NumberY values of the arrays from 2 to 1, but that I believe should not have changed the result)
    Additional Information: The model file and a screenshot of the problem are attached.

    The reproducibility of the initial simpler problem posted in the forum is "sometimes", this more complex model should result in the bug being reproduced "always".
    Attached Files: boolean-cut-with-array-not-working-2.FCStd (845,371 bytes) 2019-05-03 03:48
    https://tracker.freecad.org/file_download.php?file_id=2206&type=bug
    boolean-cut-with-array-not-working-2.PNG (163,453 bytes) 2019-05-03 03:48
    https://tracker.freecad.org/file_download.php?file_id=2207&type=bug
    image.png (57,547 bytes) 2019-10-15 12:45
    https://tracker.freecad.org/file_download.php?file_id=2374&type=bug
    Notes
    (0013077)
    jr222   
    2019-05-03 03:52   
    I re-installed Freecad 0.17 and was able to reproduce the problem in that version. i suspect this problem has been there for a while.
    I also selected major because this looks to me like a bug with substance, however, please feel free to change this, as I dont have the reference to know a major from a minor.
    (0013761)
    sariug   
    2019-10-15 12:45   
    There seem to be no problem with mine.

    OS: Ubuntu 18.04.3 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16093 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-18
    Hash: 690774c0effe4fd7b8d2b5e2fb2b8c8d145e21ce
    Python version: 2.7.15rc1
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    (0013762)
    openBrain   
    2019-10-15 17:50   
    Issue still present in 0.19 (also notice that new Draft/Array implementation breaks the example file)
    OS: Ubuntu 18.04.3 LTS (KDE/plasma)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.18502 (Git)
    Build type: Unknown
    Branch: master
    Hash: ca30dfeb27871352f0adc4dae067fd5ec7b06670
    Python version: 3.6.8
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: French/France (fr_FR)
    (0015865)
    chennes   
    2021-08-25 17:36   
    Possibly related to https://tracker.freecadweb.org/view.php?id=3938
    (0016759)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5925.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3907 [FreeCAD] Feature tweak always 2019-03-17 08:26 2021-08-25 17:26
    Reporter: brjhaverkamp Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Manipulating groups in treeview usability improvement
    Description: I have been extensively working with the Arch workbench for the past couple of weeks.

    One issue I had was that my object treeview got scattered with duplicates of object that were also items in other groups. I couldn't remove them by deleting them, because that also deletes the orignal.
    After consulting the forum, I was adviced to install the BIM workbench that has a function "Remove from group" under the left mousebutton. This works great.

    An other problem I had was that dragging and dropping objects into groups didn't always work. The target group somehow didn't accept the drop.
    However in the Arch workbench there is a Utility-> "Move to Group" function. that works very reliable.

    My usability problem now is that I have to switch between Arch and BIM to access these 2 functions when cleaning up my treeview.
    My proposal is to make this Utility submenu item available generally in the LMB menu and add the "Remove from group" function to this utility submenu. This will not only benefit the Arch and BIM workbench but also Part Design and others.
    Tags:
    Steps To Reproduce:
    Additional Information: OS: Ubuntu 18.10
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16093 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-18
    Hash: 690774c0effe4fd7b8d2b5e2fb2b8c8d145e21ce
    Python version: 2.7.15+
    Qt version: 5.11.1
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    Attached Files:
    Notes
    (0013276)
    Kunda1   
    2019-06-20 06:36   
    @brjhaverkamp please post this in a forum thread for it to get more visibility, especially since BIM development is very 'hot' right now. This may facilitate this feature being implemented.
    (0013291)
    brjhaverkamp   
    2019-06-22 06:06   
    It is discussed (amongst others) in this thread

    https://forum.freecadweb.org/viewtopic.php?f=23&t=34166&p=305040&hilit=treeview#p305040

    Indeed good to add here for completeness
    (0016734)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5899.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2916 [Path] Feature feature always 2017-02-22 06:02 2021-08-25 15:40
    Reporter: EdgarRobles Platform: Linux  
    Assigned To: OS: Ubuntu  
    Priority: normal OS Version: 16.04 LTS  
    Status: confirmed Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Add knife align up function to locate knife at begining cut precisely
    Description: You can see similar function in dxf2gcode application
    it align up the knife before begin to cut and between cut inputs.
    Tags: dragknife
    Steps To Reproduce:
    Additional Information:
    Attached Files: Mascara de soldadura.dxf (28,836 bytes) 2017-02-24 20:02
    https://tracker.freecad.org/file_download.php?file_id=1519&type=bug
    Mascara de soldadura codigo G.ngc (24,720 bytes) 2017-02-24 20:02
    https://tracker.freecad.org/file_download.php?file_id=1520&type=bug
    Notes
    (0008403)
    Kunda1   
    2017-02-22 12:37   
    @EdgarRobles Thanks for the report. Just a tip to help bug triage and expediting your request: please always try to:
    • open a forum thread before opening a ticket to generate discussion
    • if the indication from the community is to open a ticket then do so
    • link said ticket <=> thread
    • to paste the contents of Help > About FreeCAD > Copy to clipboard in to the ticket/thread
    (0008406)
    EdgarRobles   
    2017-02-22 14:20   
    Here is what i post but it is not in english
    https://forum.freecadweb.org/viewtopic.php?f=14&t=20620
    ty didn't know about triage.
    (0008407)
    Kunda1   
    2017-02-22 16:48   
    @EdgarRobles you can also ask in https://gitter.im/FreeCAD/Path
    Bug triage is when someone goes through bugs organizing them for clarity and helps get them to the correct people. ;)
    (0008415)
    sliptonic   
    2017-02-23 22:56   
    Can you describe better what kind of behavior you're looking for in the 'align' function?
    Should the program pause to let the user manually align the knife or should it add some kind of lead-in move to give the knife time to pivot.

    If it's a lead-in move, how do I determine a safe position to start from?
    (0008423)
    EdgarRobles   
    2017-02-24 19:58   
    Sure, If you try to make a dress-up knife path as fast as you start to cut it, you will see knife is not aligned at one specific direction; I think one simple solution could be say the final user align it by hand before start cutting always at the same direction.
    Other case might have to change it's between cuts for example if you have two squares
    at moment you wanted to cut the second square, it will be necessary to get down the knife and re-align (make a semi-circle to point the knife towards the first trajectory)

    I saw a little issue on the path you can see it from here: https://forum.freecadweb.org/viewtopic.php?f=14&t=20620
     in the "dragknife.png" image.
    I saw on second edge that not do knife dress-up operation; I did a second test and always it misses the second edge.
    (0008424)
    EdgarRobles   
    2017-02-24 20:02   
    This attach g code is from dxf2gcode dressup knife function, i think a example file is better than my words. xDD
    (0008476)
    mlampert   
    2017-02-28 19:29   
    Would one way to solve this would be to "drag the knife into the starting position" - if that makes any sense. Probably easiest to let the user specify a starting position from where to start dragging.

    The same is true for every independent Path. Whenever there is a rapid-move (aka the knife gets lifted off completely), there needs to be a "lead in" segment to orient the knife.
    (0008692)
    Kunda1   
    2017-03-23 23:55   
    changing to feedback to keep track of ticket.
    (0008809)
    Kunda1   
    2017-04-28 16:21   
    @sliptonic do you mind weighing in on the discussion at your earliest convenience?
    (0008938)
    sliptonic   
    2017-05-10 13:41   
    I don't have a good solution at this time. I think the most expedient solution is for the dressup to add a pause event to give time for the user to align the knife.

    Basically, after every G0 rapid, check if we are descending to the cut depth. If so, descend to just above the material, insert a M0 command, descend to cut depth, and continue. I don't know if an M0 will work on controllers other than LinuxCNC

    This logic could be implemented as another entry dressup and applied optionally to dragknife dressed operations.
    (0008965)
    Kunda1   
    2017-05-11 21:27   
    @sliptonic should I change this to a ticket as a feature request?
    (0009137)
    sliptonic   
    2017-05-25 15:51   
    The simple solution of pausing and waiting for the operator to align the knife won't work for many machine controllers that don't allow interaction. For example, Smoothie doesn't even have a pause command. I don't know of a way to safely determine an entry position where a big entry arc could be cut to guarantee starting angle.
    I think it should be left as a feature request. Maybe someone will come along with a bright idea.
    (0009147)
    Kunda1   
    2017-05-26 13:15   
    Changed ticket to Feature Request.
    (0014002)
    Kunda1   
    2020-01-06 16:36   
    Opened a thread in the Path subforum for discussion: https://forum.freecadweb.org/viewtopic.php?f=15&t=42233
    (0015864)
    Kunda1   
    2021-08-25 15:39   
    Summary by sliptonic:

    There's consensus that something is needed but no ideas about how to achieve it. For a simple single-wire profile, it's pretty easy. Let the user pick a point to start at. That doesn't work in all cases because a profile might have many wires where the tool is lifted between. What's needed is an algorithm that will consistently pick a safe starting point regardless of the profile.

    sliptonic
    (0016517)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5682.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4288 [FreeCAD] Feature minor N/A 2020-03-14 17:18 2021-08-25 01:18
    Reporter: cbruner Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Linux Mint 19.3 (X-Cinnamon/cinnamon)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.19758 (Git) AppImage
    Build type: Release
    Branch: master
    Hash: c165edd52c7f06ac09f992e5b5bf1d37661a8c0f
    Python version: 3.8.2
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: English/Canada (en_CA)
    Summary: Better Error message for No active body
    Description: Forum discussion:
    https://forum.freecadweb.org/viewtopic.php?f=3&t=44172
    Creating something in the part workbench, switching to part design selecting a face and clicking sketch gives an error about no body being present.

    Using PartDesign body (while in part design workbench), then selecting the face, and activating sketch does the same thing as what selecting face and activating sketch used to do (while in part workbench).

    So would a valid enhancement be that instead of throwing that error (which is confusing), how about when activating a sketch with a face selected, switching to partdesign workbench and doing the equivalent.

    Or... change the error message to add the text, "Perhaps use partdesign workbench/part design body to do what you are trying to do" As a newbie, I would have found this very helpful.
    Tags: #pending-PR
    Steps To Reproduce: I know that the problem is differences in versions, however, my current version .19.19... seems wrong.
    In this old tutorial (fc 14) He has created a dice with the part workbench, then goes to part design, selects a face and starts sketching on the face.
    https://youtu.be/uBKhBwSP_iM?t=244

    This makes perfect intuitive sense, as the face is the body. But my freecad complains that there is no body. Can someone explain to me why the face isn't the body, or even the cube isn't the body? and how I would properly do this tutorial with a current version of freecad? (I want to see the face while creating the dots on the dice).
    Additional Information:
    Attached Files:
    Notes
    (0015851)
    chennes   
    2021-08-25 00:51   
    If I am understanding correctly, this is addressed by PR 4949.
    (0016873)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6039.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4723 [Sketcher] Bug minor sometimes 2021-08-10 07:23 2021-08-21 16:49
    Reporter: Godwin Antony Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Windows 10 Version 2009
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24291 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-19
    Hash: 7b5e18a0759de778b74d3a5c17eba9cb815035ac
    Python version: 3.8.6+
    Qt version: 5.15.2
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: English/United States (en_US)
    Summary: sometimes sketch becomes invisible after closing the sketch.
    Description: sometimes sketch becomes invisible after closing the sketch.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0015798)
    gift   
    2021-08-10 18:35   
    Do you get a message from solver?
    You are sure, that the sketch is not overdetermined?
    Is it possible to share an example?
    (0015803)
    openBrain   
    2021-08-11 09:42   
    Please address your issue according our reporting guidelines by opening a new topic on our forum. Thx
    Also pay special attention into the guidelines on how to provide a useful report.
    (0015811)
    Godwin Antony   
    2021-08-12 04:12   
    Do you get a message from solver? - no
    You are sure, that the sketch is not overdetermined? - sure, it is not.
    Is it possible to share an example? - will share if i face this issue next time.
    (0015812)
    Godwin Antony   
    2021-08-12 04:32   
    (Last edited: 2021-08-12 05:07)
    As a firm willing to support and encourage the use of open source softwares, we are using freecad as our modelling tool.
    And could u please tell me where can i find version 0.20? @openBrain
    (0015813)
    openBrain   
    2021-08-12 06:26   
    Weekly builds
    (0015814)
    Godwin Antony   
    2021-08-12 06:53   
    Thank you!
    (0015816)
    openBrain   
    2021-08-16 14:25   
    (Last edited: 2021-08-16 14:26)
    Could you please tell us what to do with your 4 tickets 0004722 0004723 0004724 0004725 ? Should we close or would you like them to be in stand-by while you open forum threads to discuss your issues ?
    (0015838)
    Kunda1   
    2021-08-20 14:32   
    I missed this conversation. I closed those tickets because @GodwinAntony is unfamiliar with our tracker guidelines. I can re-open if it's merited.
    (0015845)
    Godwin Antony   
    2021-08-21 04:10   
    I'm sorry! those tickets can be closed as those were the issues in 19 version,
    Now I'm using 20 version and will update the issues in new tickets.
    Thank You!
    (0015846)
    openBrain   
    2021-08-21 16:49   
    NO! What are you not understanding in the guidelines seriously ? OPEN A FORUM TOPIC ! GIVE DETAILED STEPS TO REPRODUCE !!!
    I'm sorry to be rude, but your new ticket 0004731 is still in total contradiction with basic rules. I close without further processing.
    (0017079)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6248.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4593 [Arch] Bug minor always 2021-03-09 19:25 2021-08-20 15:29
    Reporter: bitacovir Platform: windows  
    Assigned To: OS: Windows  
    Priority: normal OS Version: 10  
    Status: confirmed Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 10 (10.0)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24267 (Git)
    Build type: Release
    Branch: master
    Hash: b2ca86d8d72b636011a73394bf9bcdedb3b109b7
    Python version: 3.8.8
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: English/United States (en_US)
    Summary: [Arch] Arch Stairs' rails do not recompute in FC 0.19
    Description: when you create a Arch Stairs object, rails components produce some errors and they cannot recompute in FC 0.19
    Message of Report panel:
    
    21:06:45  0 <App> Document.cpp(3527): Unnamed#Rail still touched after recompute
    21:06:45  1.8e-05 <App> Document.cpp(3527): Unnamed#Rail001 still touched after recompute
    
    I found this affect the performance of other commands in Draft WB make them slower: when I draw a line, before to display the geometry in the 3Dwindow, the program try to recompute and fails, generating the error messages. The only solution I found is to delete the rails.
    This bug is a regression compared with Arch Stair in FC 0.18.4 where you can create a stair and no errors are produced.

    Forum discussion: https://forum.freecadweb.org/viewtopic.php?p=485978#p485978
    Tags: 0.19, Arch
    Steps To Reproduce: -New file
    -Open Arch module
    -Create a Stair with Arch Stairs (click on Stair icon)
    -The new stair is generated but two error messages are shown in the report panel.
    -If you try to recompute, it will fail.
    Additional Information:
    Attached Files: freecad_3Z9TYGqlG6.png (90,673 bytes) 2021-03-09 19:25
    https://tracker.freecad.org/file_download.php?file_id=2646&type=bug
    Notes
    (0015534)
    Kunda1   
    2021-03-22 16:34   
    confirmed on the forum. Marking target as 0.20
    (0015837)
    Kunda1   
    2021-08-20 14:29   
    @paullee is there anyone that can help you with this ticket?
    (0015843)
    paullee   
    2021-08-20 15:29   
    Thanks, I am not sure. Maybe I will have a look when there is a gap.
    (0017008)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6176.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4730 [FreeCAD] Feature feature N/A 2021-08-20 08:00 2021-08-20 14:30
    Reporter: Pauvres_honteux Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: ...
    Summary: Children and/or parent to be highlighted when hovering over something in the tree/3D viewport
    Description: Forum topic:
    Children and/or parent to be highlighted when hoovering over something in the tree/3D viewport

    This is about finding a features parent and/or children in a simple way.
    Tags:
    Steps To Reproduce: N/A
    Additional Information: N/A
    Attached Files:
    Notes
    (0017083)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6252.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4729 [FreeCAD] Feature feature always 2021-08-20 07:49 2021-08-20 07:49
    Reporter: Pauvres_honteux Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: ...
    Summary: General selection principle/method throughout FreeCAD
    Description: See forum discussion: General selection method throughout FC
    Tags:
    Steps To Reproduce: N/A
    Additional Information: N/A
    Attached Files:
    Notes
    (0017082)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6251.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4728 [FreeCAD] Feature feature N/A 2021-08-20 07:34 2021-08-20 07:34
    Reporter: Pauvres_honteux Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: ...
    Summary: Local update function/button
    Description: See forum discussion: Local update function/button
    It is basically about a button to stop the update mechanism from running through everything in the document when the user so wish. And exactly what plus how that shall be implemented.
    Tags:
    Steps To Reproduce: N/A
    Additional Information: N/A
    Attached Files:
    Notes
    (0017081)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6250.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4727 [FreeCAD] Feature feature N/A 2021-08-20 05:59 2021-08-20 06:02
    Reporter: Pauvres_honteux Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: ...
    Summary: Visualisation/appearance of point/vertex
    Description: Forum discussion: Point visualisation/appearance
    Tags:
    Steps To Reproduce: N/A
    Additional Information: N/A
    Attached Files:
    Notes
    (0015830)
    Pauvres_honteux   
    2021-08-20 06:02   
    Forgot: it shall work for 3D and 2D, drawing and FEM.
    (0017080)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6249.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4716 [FreeCAD] Bug minor always 2021-07-29 09:55 2021-08-11 17:13
    Reporter: dxp.dev Platform: MacBook Pro mid-2015  
    Assigned To: OS: MacOS  
    Priority: normal OS Version: Big Sur 11.5  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: macOS 10.16
    Word size of FreeCAD: 64-bit
    Version: 0.20.25288 (Git)
    Build type: Release
    Branch: master
    Hash: bbb557aab6129efd9486d6df19f06c2976fdb7e5
    Python version: 3.9.6
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.5.2
    Locale: C/Default (C)
    Summary: With stylesheets, Scroll bar overlaps arrows in Properties tab with stylesheets, never disappears
    Description: Context : With any stylesheet (not with "no-stylesheet" theme)

    Use-case : The properties of the data can be edited (such as length with up and down arrows, pocket type with a drop down menu by clicking on the down arrow, etc.).

    Problem: The scroll bar overlaps those arrows, and when clicking on them, the scroll bar has priority and instead of modifying the properties, it just make the data window scroll.

    See attached video

    Proposed solution: The editing arrows shouldn't overlap with the scroll bar, or the scroll bar should disappear after 1/2second as in the "no-stylesheet" theme
    Tags:
    Steps To Reproduce: On FC 0.20 (git)
    • Select a stylesheet (Behave Dark, all the Dark-*, Darker-*, Light-* or proDark)
    • Open a file, apply anything to a model (pocket, pad, etc.)
    • In properties tab, clic on the drop-down arrows or up/down arrow at the right of the property you want to edit
    • Instead of clicking those arrows, scroll bar takes precedence and move the view (see attached video)
    Additional Information: FreeCAD forum topic
    Attached Files:
    Notes
    (0015784)
    chennes   
    2021-08-09 14:49   
    I can't reproduce this on Windows, so this may be a Mac-only Qt bug.

    OS: Windows 10 Version 2009
    Word size of FreeCAD: 64-bit
    Version: 0.20.25442 (Git)
    Build type: Debug
    Branch: master
    Hash: d635f03a60a7ae1e6f9d390b9cbd7bdb91692996
    Python version: 3.8.6+
    Qt version: 5.15.1
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: English/United States (en_US)
    (0015787)
    dxp.dev   
    2021-08-09 16:56   
    On the forum, user Syres couldn't reproduce on Windows either:

    On Windows as soon as the user squashes the Property panel to cause the scroll bar to appear the up/down arrows and combo box drop down arrow all shift to the left so they don't overlap (as would be expected), tested with Behave Dark stylesheet using:

    OS: Windows 7 Version 6.1 (Build 7601: SP 1)
    Word size of FreeCAD: 64-bit
    Version: 0.20.25306 (Git)
    Build type: Release
    Branch: master
    Hash: 5f5b3d9b67136edda1f6738f1a83154990f7839d
    Python version: 3.8.6+
    Qt version: 5.15.2
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: English/United Kingdom (en_GB)

    Syres
    (0015805)
    chennes   
    2021-08-11 17:13   
    I can't reproduce on:

    OS: macOS 10.15
    Word size of FreeCAD: 64-bit
    Version: 0.20.25450 (Git)
    Build type: Release
    Branch: master
    Hash: ed8e63270827afddd2f3e59cea2384af66e0f0d5
    Python version: 3.9.1
    Qt version: 5.15.2
    Coin version: 4.0.0
    OCC version: 7.5.0
    Locale: English/United States (en_US)

    Maybe fixed in recent Qt versions?
    (0017075)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6244.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4721 [FreeCAD] Bug major always 2021-08-08 18:27 2021-08-08 18:27
    Reporter: keithsloan52 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: macOS 10.15
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24276 (Git)
    Build type: Release
    Branch: (HEAD detached at 0.19.1)
    Hash: a88db11e0a908f6e38f92bfc5187b13ebe470438
    Python version: 3.8.8
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: C/Default (C)
    Summary: Trying to use Gmsh python library from FreeCAD fails on gmsh.initialize with AttributeError: dlsym(RTLD_DEFAULT, gmshInitialize)
    Description: If pip install gmsh python library under native python everything works,
    All be it my standard python3 is 3.9.5
    If I install under FreeCAD with
    pip install gmsh -t<FreeCAD python Path>
    Then from the python console I can successfully import gmsh
    But if I try gmsh.initialize() I get
    gmsh.initialize()
    19:13:10 File "/Applications/FreeCAD 0.19.1.app/Contents/Resources/lib/python3.8/site-packages/gmsh.py", line 232, in initialize
    19:13:10 lib.gmshInitialize(
    19:13:10 File "/Applications/FreeCAD 0.19.1.app/Contents/Resources/lib/python3.8/ctypes/__init__.py", line 386, in __getattr__
    19:13:10 func = self.__getitem__(name)
    19:13:10 File "/Applications/FreeCAD 0.19.1.app/Contents/Resources/lib/python3.8/ctypes/__init__.py", line 391, in __getitem__
    19:13:10 func = self._FuncPtr((name_or_ordinal, self))
    19:13:10 AttributeError: dlsym(RTLD_DEFAULT, gmshInitialize): symbol not found

    Have tried raising as an issue at gmsh github without success
    Tags:
    Steps To Reproduce: pip3 install gmsh -t<Path to valid FreeCAD library>
    from FreeCAD python Console
        import gmsh
        gmsh.initialize()
    Additional Information:
    Attached Files:
    Notes
    (0017078)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6247.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4720 [FEM] Feature feature N/A 2021-08-06 18:34 2021-08-06 20:44
    Reporter: NewJoker Platform:  
    Assigned To: berndhahnebach OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Windows 10 Version 2009
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24276 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-19
    Hash: a88db11e0a908f6e38f92bfc5187b13ebe470438
    Python version: 3.8.6+
    Qt version: 5.15.1
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: Polish/Poland (pl_PL)
    Summary: More than 3 yield points in FEM_MaterialMechanicalNonlinear
    Description: Currently only 3 yield points can be defined in FEM_MaterialMechanicalNonlinear (plasticity definition). It should be fairly simple to add a possibility to define more points so that a full stress-strain curve can be approximated. Ideally, there should be no limitation on the number of yield points at all. But if a limit can't be avoided due to coding issues then let's increase it significantly.

    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=18&t=57382

    Previous forum thread with the discussion about this limitation: https://forum.freecadweb.org/viewtopic.php?f=18&t=51756
    Tags: FEM, material
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0015776)
    Kunda1   
    2021-08-06 20:43   
    @NewJoker thanks. BTW, if you're using FEM, please make sure to use the dev version as opposed to what you reported using in this ticket 'Version: 0.19.24276 (Git)' since FEM development progresses in bursts and changes are rarely backported.
    (0017077)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6246.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4592 [Arch] Bug major always 2021-03-09 19:10 2021-08-06 16:20
    Reporter: bitacovir Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Windows 10 (10.0)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24267 (Git)
    Build type: Release
    Branch: master
    Hash: b2ca86d8d72b636011a73394bf9bcdedb3b109b7
    Python version: 3.8.8
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: English/United States (en_US)

    OS: Windows 10 (10.0)
    Word size of FreeCAD: 64-bit
    Version: 0.20.25131 (Git)
    Build type: Release
    Branch: master
    Hash: 7c519689f0d5ea78fb3292be36a857d283c05507
    Python version: 3.8.10
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.5.2
    Locale: English/United States (en_US)

    Summary: [Arch] "Move With Host" property of Arch windows does not work in FC 0.19 /0.20
    Description: In FC 0.19 when I move a Arch Wall with a nested Arch Door or Window, these elements do not move with the arch wall.
    As default, "Move With Host" property of windows is setup to "True", but it does not work.
    This bug is a regression, because the feature "Move with Host" works normally in FC 0.18.4 for arch windows nested in arch walls.

    This bug/regression has been mentioned several times in the forum:
    https://forum.freecadweb.org/viewtopic.php?f=23&t=53427
    https://forum.freecadweb.org/viewtopic.php?f=23&t=53491
    https://forum.freecadweb.org/viewtopic.php?f=23&t=53445

    Edit: This bug is also present in FC 0.20.

    Tags: 0.19, Arch
    Steps To Reproduce: In FC0.19 / 0.20
    -Open Arch Module
    -Create an Arch Wall
    -Select the wall and place an Arch window in it. (The property "Move With Host" of the window should be True).
    -Select the wall and change or move its position. The wall moves, but the window doesn't.

    Same steps in FC 0.18.4 make the wall and windows move simultaneously, as expected.
    Additional Information:
    Attached Files:
    Notes
    (0015589)
    matthijskooijman   
    2021-03-31 19:23   
    (Last edited: 2021-04-01 16:58)
    I suspect that the relevant bit of code is `get_movable_children()`. Looking there, it seems to iterate over the OutList of the wall looking for children with "MoveWithHost" set, but that seems wrong to me. Any objects that have the wall set in their "Hosts" property, will (AFAIU) appear in the InList of the wall, not the OutList?

    I quickly tried this patch:

    
    --- a/src/Mod/Draft/draftutils/groups.py
    +++ b/src/Mod/Draft/draftutils/groups.py
    @@ -297,8 +297,8 @@ def get_movable_children(objectslist, recursive=True):
         for obj in objectslist:
             # Skips some objects that should never move their children
             if utils.get_type(obj) not in ("Clone", "SectionPlane",
                                            "Facebinder", "BuildingPart"):
    -            children = obj.OutList
    +            children = obj.InList
                 if (hasattr(obj, "Proxy") and obj.Proxy
                         and hasattr(obj.Proxy, "getSiblings")
                         and utils.get_type(obj) != "Window"):
    

    Which seems to work to fix this problem. However, it also breaks the copy tool (gives src/App/Expression.cpp:3109: App::ExpressionParser::ExpressionImporter::ExpressionImporter(Base::XMLReader&): Assertion `!_Reader' failed.)

    Also, looking at the git history, it seems that this has been OutList since it was first introduced in 2014 ( FreeCAD master cb5a8079 ), so this is probably not the right fix.

    So I guess the window is supposed to be in the wall's outlist? Should it be in the Additions property? That is what commit FreeCAD master cb5a8079 suggests. But if it is in the wall's outlist and the wall is in the window's outlist, then there would be a cycle?

    Hm, I guess I do not quite understand yet how all this is supposed to work...
    (0015673)
    matthijskooijman   
    2021-05-22 14:58   
    See https://forum.freecadweb.org/viewtopic.php?f=23&t=57223 for a lot more detailed investigation about MoveWithHost and its current problems. The above suggested fix certainly is not the right approach :-)
    (0015775)
    bitacovir   
    2021-08-06 16:17   
    (Last edited: 2021-08-06 16:20)
    I changed the Severity to mayor as requested here: https://forum.freecadweb.org/viewtopic.php?f=23&t=60679
    Also this bugs is present in FC 0.20 so I edit FC version references in the original report.
    (0017007)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6175.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4717 [FreeCAD] Feature feature always 2021-07-31 01:19 2021-07-31 01:19
    Reporter: Evgeniy Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Ubuntu 20.04.2 LTS (ubuntu:GNOME/ubuntu)
    Word size of FreeCAD: 64-bit
    Version: 0.20.25281 (Git)
    Build type: Release
    Branch: master
    Python version: 3.8.10
    Qt version: 5.12.8
    Coin version: 4.0.0
    OCC version: 7.5.2
    Summary: Add ability for load ToolBar SVG icons from Python string, like as XPM
    Description: Discussion from forum

    My view of how it should look like:

    # default icon
    Icon = """
    /* SVG */
    static const char *test_icon[]={
    "<svg xmlns='http://www.w3.org/2000/svg' height='64' width='64'>",
    "<rect height='64' width='64' fill='#204a87' />",
    "</svg>"};
    """
    
    # replace fill color
    Icon.replace("fill='#204a87'","fill='#00FF00'")
    
    
    # and icon with changed colors to toolbar
    
    ... Command creation code ...
        
    def GetResources(self):
        return {"MenuText": "My Command",
            "Accel": "Ctrl+M",
            "ToolTip": "ToolTip command",
            "Pixmap"  : Icon}

    Tags: python, SVG, toolbar, UI, workbench
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0017076)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6245.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4627 [Sketcher] Bug major always 2021-04-09 18:24 2021-07-29 15:59
    Reporter: kisolre Platform:  
    Assigned To: openBrain OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Windows 8.1 Version 6.3 (Build 9600)
    Word size of FreeCAD: 64-bit
    Version: 0.20.24673 (Git)
    Build type: Release
    Branch: master
    Hash: e66ed26769ce8affe0a4ed330ff0435f4802f05e
    Python version: 3.8.6+
    Qt version: 5.15.1
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: Bulgarian/Bulgaria (bg_BG)
    Summary: When trying to create reference radius/diameter from dialog it is always created as real one.
    Description: When a dimensional constraint is created there is a "Reference" check box in the dialog, which when checked should allow creation of reference constraint without having to switch constraint creation mode before head. This does not work then creating radius/diameter constraints. The other ones (distance, angle) work as expected.
    Tags:
    Steps To Reproduce: Create an arc/circle. Try to dimension its radius. Check the "Reference" checkbox to try to create reference constraint. Confirm dialog. Real constraint is created instead.
    Additional Information: Forum thread
    Attached Files:
    Notes
    (0015625)
    openBrain   
    2021-04-19 20:06   
    Pull request
    (0017029)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6197.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4221 [TechDraw] Feature feature N/A 2019-12-10 13:09 2021-07-29 10:00
    Reporter: dxp.dev Platform: Mac  
    Assigned To: OS: MacOS  
    Priority: normal OS Version: 1.14.6  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: macOS Mojave (10.14)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.18775 (Git)
    Build type: Release
    Branch: master
    Hash: 9e93e621f9d5332114d29ea316f27aa6698eb70b
    Python version: 3.7.3
    Qt version: 5.12.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: French/Switzerland (fr_CH)
    Summary: Ability to drag and drop the circle/square defining the detail view in TechDraw
    Description: Actually:
    When adding a detail view of a part in Techdraw WB (https://www.freecadweb.org/wiki/TechDraw_NewDetail), we have to guess the coordinates of the circle/square defining the detail view to display as another element on the sheet by adjusting the values of the x,y,z anchor properties manually.

    Proposed:
    I think that adding the possibility to drag and drop the circle/square and defining its radius/dimension the same way we can drag and drop a circle/square in Sketcher WB as well as drag and drop the radius/dimension by dragging the circle/point of the square would be better.

    Advantages:
    • Faster
    • More precision
    • More user-friendly
    Tags: 0.19, TechDraw
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016850)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6016.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4698 [PartDesign] Bug minor always 2021-07-03 07:53 2021-07-26 16:22
    Reporter: chrisb Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: macOS 10.16
    Word size of FreeCAD: 64-bit
    Version: 0.20.25157 (Git)
    Build type: Release
    Branch: master
    Hash: 257cdd8f423f1530b8df6f53e242de629fee4e85
    Python version: 3.9.5
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.5.2
    Locale: C/Default (C)
    Summary: Pattern not working properly on geometric primitives
    Description: In some cases the PartDesign pattern functions don't seem to get the coordinate system of geometric primitives right. The patterned features occur then in the wrong place.
    forum discussion
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0015754)
    openBrain   
    2021-07-26 16:22   
    Just notice this is one of all things that don't work with PD primitives : mirror, ...
    Indeed it seems that primitives are by some way messing up the coordinate system.
    (0017069)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6238.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4668 [Path] Bug major always 2021-05-27 17:55 2021-07-26 07:14
    Reporter: oscar Platform: Linux  
    Assigned To: OS: Ubuntu  
    Priority: normal OS Version: 20.04  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Ubuntu 20.04.2 LTS (ubuntu:GNOME/ubuntu)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24276 (Git) AppImage
    Build type: Release
    Branch: (HEAD detached at 0.19.1)
    Hash: a88db11e0a908f6e38f92bfc5187b13ebe470438
    Python version: 3.8.8
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: Spanish/Spain (es_ES)
    Summary: planarFaceFromExtrusionEdges: sub is not defined
    Description: The method planarFaceFromExtrusionEdges() in src/Mod/Path/PathScripts/PathPocketShape.py, line 735 of current HEAD (https://github.com/FreeCAD/FreeCAD/blob/c6771853ae951f5d4fb029f3423ce2132f0ba22b/src/Mod/Path/PathScripts/PathPocketShape.py#L735), there is a variable that is not defined.
    Tags: 0.19, Path
    Steps To Reproduce: * Create an SVG with a rectangle and a circle inside
    * Import the SVG file as geometry
    * Convert both paths to sketches
    * Extrude the rectangle sketch, and make a hole on it using the circle sketch
    * Open Path workbench and try to create a pocket operation using the hole
    Additional Information: 19:46:37 Traceback (most recent call last):
      File "/tmp/.mount_freeca7dqM3T/usr/Mod/Path/PathScripts/PathUtils.py", line 60, in new_function
        res = function(*args, **kwargs)
      File "/tmp/.mount_freeca7dqM3T/usr/Mod/Path/PathScripts/PathOp.py", line 552, in execute
        result = self.opExecute(obj) # pylint: disable=assignment-from-no-return
      File "/tmp/.mount_freeca7dqM3T/usr/Mod/Path/PathScripts/PathAreaOp.py", line 392, in opExecute
        aOS = self.areaOpShapes(obj) # pylint: disable=assignment-from-no-return
      File "/tmp/.mount_freeca7dqM3T/usr/Mod/Path/PathScripts/PathPocketShape.py", line 357, in areaOpShapes
        if not self.clasifySub(subBase, sub):
      File "/tmp/.mount_freeca7dqM3T/usr/Mod/Path/PathScripts/PathPocketShape.py", line 773, in clasifySub
        (planar, useFace) = self.planarFaceFromExtrusionEdges(face, trans=True)
      File "/tmp/.mount_freeca7dqM3T/usr/Mod/Path/PathScripts/PathPocketShape.py", line 696, in planarFaceFromExtrusionEdges
        fName = sub + '_face_' + str(fCnt)
    <class 'NameError'>: name 'sub' is not defined
    Attached Files:
    Notes
    (0015688)
    Kunda1   
    2021-06-02 20:36   
    @oscar Thanks for the effort, but our guidelines are to post to the forum first. the v0.19 that you're using is already inferior since Path development is very rapid. Please test on v0.20 dev appimage from https://github.com/FreeCAD/FreeCAD-Bundle/releases/tag/weekly-builds
    (0015692)
    oscar   
    2021-06-04 05:49   
    @Kunda1 thank you for reviewing the issue! I'm sorry for not posting first in the forum, I tried, but I did not very well understand the proper place :/
    Also, note please that provided list is for the latest code (the HEAD of the master branch), and the code is still there :D

    Thanks and sorry again, I'll try to follow the rules :)
    (0015693)
    oscar   
    2021-06-04 05:53   
    @Kunda1 You are right!! I've checked the real master branch, and I see a lot of changes!! That's good! :)
    I'll clone the latest repo and try again.

    Thank you!
    (0015747)
    russ4262   
    2021-07-25 04:05   
    @oscar
    Buenas noches, señor. ¿Cómo está? Me llamo Russell y me interesa el problema que usted ha reportado aquí. ¿Todavía existe el problema con la version más actual de FreeCAD «master»? Se lo menciono porque el archivo PathPocketShape.py ya no contiene 773 líneas indicado en el texto del error publicado. También nos ayudaría si usted adjuntara un archivo sencillo de FreeCAD que produce el error.

    Hablo inglés mejor que el español.

    Gracias.
    (0015751)
    oscar   
    2021-07-26 07:14   
    (Last edited: 2021-07-26 07:14)
    @russ4262 Thank you very much for taking the time and see the issue! I've checked the latest version of the source code and, as you say, that file has been heavily refactorized! I need to test again using the latest version, and if it still fails, then I'll report back and attach a sample file.

    Thanks again!
    (0017052)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6221.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4702 [Sketcher] Feature feature N/A 2021-07-05 21:50 2021-07-05 21:51
    Reporter: NewJoker Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Windows 10 (10.0)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.22808 (Git)
    Build type: Release
    Branch: master
    Hash: 72eb41b24f12b572d55081042160954b93f4614c
    Python version: 3.6.8
    Qt version: 5.12.1
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: Polish/Poland (pl_PL)
    Summary: Object snap in sketcher
    Description: For me the most missing feature in FreeCAD is the lack of auto snapping to objects (midpoints, center points, quadrants, extensions, intersections) in sketcher.

    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=59890
    Tags: midpoint, snap
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0015729)
    NewJoker   
    2021-07-05 21:51   
    Forum thread started by another user: https://forum.freecadweb.org/viewtopic.php?f=8&t=58207
    (0017071)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6240.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4700 [Sketcher] Feature feature always 2021-07-03 22:13 2021-07-03 22:14
    Reporter: hic Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Linux Mint 19 (X-Cinnamon/cinnamon)
    Word size of FreeCAD: 64-bit
    Version: 0.20.25157 (Git) AppImage
    Build type: Release
    Branch: master
    Hash: 257cdd8f423f1530b8df6f53e242de629fee4e85
    Python version: 3.9.5
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.5.2
    Summary: Add the possibility to dimension two parallel lines
    Description: Make it possible to set the distance between two parallel lines.

    At the moment it is possible to set the distance between a point and a line or between two points. But it is impossible to set the distance between two lines.

    Additionally, automatically generate a parallelism constraint between these lines. Maybe add a warning if they are not parallel at this point.
    Tags:
    Steps To Reproduce:
    Additional Information: Link to forum discussion:

    https://forum.freecadweb.org/viewtopic.php?f=3&t=54945
    Attached Files:
    Notes
    (0017070)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6239.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4695 [Sketcher] Feature feature have not tried 2021-07-02 06:32 2021-07-02 08:36
    Reporter: paullee Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: <!--ATTENTION:
    COMPLETELY ERASE THIS AFTER PASTING YOUR
    Help > About FreeCAD > Copy to clipboard
    NOTE: just the snippet alone will do without anything else included.
    The ticket will not be submitted without it.
    -->
    Summary: [Feature] 'Hard' Block Constraint / Non-Editable Edges
    Description: [Post-new-feature-cleanup] - Chrisb's comment

    FreeCAD Forum Discussion:-
    1. Edges with Block Constraints still Moves
    2. Block Constraint


    Desirable 'Hard' Block Constraint / Non-editable Edge Behaviour

    Excerpt from above forum discussion thread :

    "Now, it seems there are 2 'intended behaviour' needs to be implemented, one is 'hard' - the previous behaviour as depicted in wiki, and the new 'soft' one :D

    I use extensively the Block Constraint in my model and in the SketchArch add-on, assuming the edge with Block Constraint would never move again :) The new user in the post I refer seems expected similar behaviour. My usescases e.g.:-

        1. The X, Y Axis and Origin never move
        2. Sometime edges in other placement / direction are needed as reference (we have Grid in architectural design)
        3. In below model, there are a few edges that are originally added making reference to edges of a Ramp
        4. They are Blocked and worked as 'External Geometry', not expected to be Driven - and Not Susceptible to 'Toponaming' problem
        5. Then I build few edges / geometry based on these reference line, those edges / geometry are driven by the Blocked Edges
        6. The thing now it become 'non-intuitive' to those used to old behaviour is that - when there are more dimensional added to the latter edges, then suddenly it would come to a moment, a turning point, that the Blocked Edge become Driven by those originally Be Driven in opposite way. (Try to illustrate in below screencaptures... the last one capture the Block Edge 'suddenly' move / 'be driven'.

    Can a 'Hard Block' / 'Absolute Block' constraint be re-provided in addition to the one with new behaviour ? :D "

    'Soft' Block Constraint Behaviour Introduced in Dec 2020

    @abdullah :
    " This is, as far as I see, the intended behaviour of the new Block constraint (introduced in December 2020).

    The working of new Block can be summarised as: "Block on a geometry constraints anything else not being constraint by another constraint".

    The old block constraint led to misleading behaviour (sometimes a dimension would be ignored while still showing the new value) and inconsistent behaviour (whether the constraint is ignored or shown as redundant/conflicting depends on the position of the dimensional constraint with respect to the block constraint in the list of constraints).

    The new block always obeys any other existing constraint (no matter whether it is located before or after in the constraint list) and fixes the rest. It is my understanding that this is the wanted behaviour."





    Tags: sketcher
    Steps To Reproduce: (see above / forum discussion with links provided)
    Additional Information:
    Attached Files:
    Notes
    (0015725)
    paullee   
    2021-07-02 08:36   
    Add [Post-new-feature-cleanup] following Chrisb's comment

    (0017067)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6236.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4691 [PartDesign] Feature feature N/A 2021-06-30 02:30 2021-06-30 02:30
    Reporter: topher217 Platform:  
    Assigned To: OS:  
    Priority: low OS Version:  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Ubuntu Core 20 (ubuntu:GNOME/ubuntu)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24276 (Git)
    Build type: Unknown
    Branch: releases/FreeCAD-0-19
    Hash: a88db11e0a908f6e38f92bfc5187b13ebe470438
    Python version: 3.8.5
    Qt version: 5.12.8
    Coin version: 4.0.0
    OCC version: 7.5.0
    Locale: English/United States (en_US)
    Summary: Performance Evalution Tool
    Description: In Solidworks there was a tool called the Performance Evaluation Tool that allowed the user to analyze what was taking up the most processing time (e.g. on startup when loading the model, on the equivalent of a recompute in FreeCAD (rebuild in Solidworkd), etc.). It would show things like which parts or features took the most time and or processing to handle such that the user could locate these things and either reduce their complexity, or some other workaround to improve performance.

    A link to the forum discussing this idea here:
    https://forum.freecadweb.org/viewtopic.php?p=513242#p513242

    A link to the documentation on Solidworks is here for reference:
    https://help.solidworks.com/2021/English/SolidWorks/sldworks/HIDD_ASSYXPERT_REBUILD_REPORT.htm?verRedirect=1

    Tags:
    Steps To Reproduce: I'm not familiar with the code base (yet), but from the little I skimmed I was thinking about this being implemented via the following items:

    1. In whatever base/parent class that defines a Part Design feature (pad, pocket, polar pattern, etc.) have some field that tracks most recent recompute time for that feature. Add this field to the Property Pane when selected in the tree view.
    2. Add a tic/tok timer or similar to the beginning and end of the recompute method from which to update the above mentioned field storing this info. Add a user-preference or other boolean to toggle this timer on/off if it slows performance.
    3. Add the ability to generate a report of some kind (pdf/spreadsheet/console log/etc.) that gathers this recompute time for each existing feature into one place. Sort these by recompute time so the user can identify which features are taking the most time to recompute.
    Additional Information:
    Attached Files:
    Notes
    (0017066)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6235.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4604 [Draft] Bug major always 2021-03-24 14:54 2021-06-29 18:22
    Reporter: tmplitmir Platform:  
    Assigned To: OS: linux  
    Priority: normal OS Version: fedora 27  
    Status: feedback Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Fedora 27 (Twenty Seven) (KDE//usr/share/xsessions/plasma)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24276 (Git) AppImage
    Build type: Release
    Branch: (HEAD detached at 0.19.1)
    Hash: a88db11e0a908f6e38f92bfc5187b13ebe470438
    Python version: 3.8.8
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: Russian/Russia (ru_RU)
    Summary: Draft. snapping mode.
    Description: snapping mode does not work. does not work at all. equally negative result in different versions. (0.16, 0.18, 0.19)
    Tags: #post-to-forum, snap
    Steps To Reproduce:
    Additional Information:
    Attached Files: snap.mp4 (498,506 bytes) 2021-03-24 14:54
    https://tracker.freecad.org/file_download.php?file_id=2657&type=bug
    Notes
    (0015539)
    Kunda1   
    2021-03-24 17:26   
    Please open a forum thread as requested in the large banner at the top of the page.
    (0015573)
    marioalexis   
    2021-03-29 16:21   
    @tmplitmir try unchecking Snap Near because it takes precedence over other snaps options (contrary to wiki ...).
    From the video, it looks like you expect to use Snap Center but you are turning it off.
    (0015719)
    marioalexis   
    2021-06-24 04:43   
    @Kunda1 I think we can close this.
    (0015722)
    jnxd   
    2021-06-29 18:22   
    Are attachments being deleted? I see the attached video is missing.
    (0017014)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6182.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4689 [FreeCAD] Bug minor always 2021-06-27 21:45 2021-06-27 21:45
    Reporter: chrisb Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: macOS 10.16
    Word size of FreeCAD: 64-bit
    Version: 0.20.25131 (Git)
    Build type: Release
    Branch: master
    Hash: 7c519689f0d5ea78fb3292be36a857d283c05507
    Python version: 3.9.5
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.5.2
    Locale: C/Default (C)
    Summary: Sketch partially vanishes on zoom in
    Description: In Sketcher parts of the still visible area vanish. Guess from Abdullah: Coin miscalculates and assumes that some parts are outside of the visible area which in fact aren't.
    Forum post.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0017065)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6234.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4688 [FreeCAD] Bug tweak always 2021-06-23 17:48 2021-06-23 17:48
    Reporter: hgraminho Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Windows 10 Version 2004
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24291 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-19
    Hash: 7b5e18a0759de778b74d3a5c17eba9cb815035ac
    Python version: 3.8.6+
    Qt version: 5.15.2
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: Portuguese/Brazil (pt_BR)
    Summary: Recomputing after unchanged task/sketch
    Description: There are certain feature types for which opening their respective task panels for edit, followed by leaving them unchanged (either by pressing cancel or esc), causes them to become marked to recompute. This causes unnecessary delays, especially for larger models.

    Comparing to version 0.18, this behavior was fixed for many of the tools, but also appeared on others, including the sketcher.

    As far as I tested (mostly PartDesign workbench), leaving or cancelling tool task pannel...
    ...generates an undesired "mark to recompute" for:
    FC 0.18: additive and subtractive pipes, mirrored feature, linear pattern and polar pattern
    FC 0.19: sketches, additive and subtractive pipes

    ...does not generate "mark to recompute" (which is fine*) for:
    FC 0.18: sketches, pad, pocket, lofts, grooves, chanfers, fillets, thickness
    FC 0.19: pad, pocket, lofts, grooves, chanfers, fillets, thickness, mirrored feature, linear pattern and polar pattern

    *however, I noticed that if there is some editable field that gets changed, then even if you change the value back and/or cancel the tool, "mark to recompute" will be generated as well. This seems to be happening for Part WB too.

    Could be happening for other workbenches as well.
    Tags:
    Steps To Reproduce: Create partdesign body.
    Create 2 simple sketches, a closed one and a path (e.g. straight line).
    Create additive pipe.
    Activate "Skip recomputes"
    Open pipe task panel (double click on it in the tree)
    Press cancel or esc.
    Note the mark for recompute icon.
    Press F5 (update)
    Enter and leave either sketch without changing it.
    Note the mark for recompute icon.
    Press F5 (update)

    Now, just for comparison, try creating a pad or any of the other features I mentioned were ok.
    Hit F5
    Open feature task panel, then cancel. Notice that mark for recompute is NOT generated.
    Now do the same but try editing something within the panel before cancel. Recompute IS generated.
    Additional Information: Forum discussion (behavior confirmed by other):
    https://forum.freecadweb.org/viewtopic.php?f=8&t=58588&p=503530#p503530

    Since this fix possibly requires changes to multiple tools and workbenches, I suggest fixing the Sketcher first, since it plays a central role for most of the users.
    Attached Files:
    Notes
    (0017064)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6233.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4685 [Path] Bug minor always 2021-06-16 16:59 2021-06-16 17:49
    Reporter: mhindi Platform: Linux  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information:
    Summary: Gcode generated by Path engrave skips some lines
    Description: https://forum.freecadweb.org/viewtopic.php?f=15&p=510599#p510599

    I produced a sketch part of which is in the attached image (sketcher_lines_bug_report.png). I created a Path Job with the sketch selected, and added an engrave operation to the job. The generated engrave path (path_engrave_bug_report.png, attached), is missing line segments from the "6" at the beginning, and the "Upsilon" (fourth character), while other characters have a correct engrave paths.
    I uploaded a file just including the "6" sketch to the forum and one of the respondents got the same result - missing the upper part of the "6". The file FreeCAD with the "6" sketch (but not the Path job, since it references a local tool) is attached.
    Tags:
    Steps To Reproduce: 1- The lines in the sketch are produced via a script that reads a Hershey font in an SVG format. The script produces "Part::Feature" objects that are then converted to a sketch, via Draft->birectional Draft to sketch icon.
    2- Select the resulting sketch
    3- Create a Job from the Path workbench.
    4- Add an engrave operation, Accept.
    5- The resulting engrave path misses some lines.
    (N.B., if the sketch is selected and converted back to individual Draft elements via (Draft->bidirectional Draft object to sketch icon) and the resulting draft objects engraved, the resulting operation produces the correct, complete figure "6".)
    Additional Information:
    Attached Files:
    Notes
    (0015713)
    mhindi   
    2021-06-16 17:08   
    (0015714)
    mhindi   
    2021-06-16 17:12   
    I get an error when I try to attach the images and the file. Something about directory not being writable. Please advise how to attach the files dragging and dropping to the upload seems not to work. (The total size is less than 2 MB.)
    (0015715)
    mhindi   
    2021-06-16 17:18   
    https://drive.google.com/file/d/1L0BXlSnecxE41kTtPY2fVwD9b5S8kuUR/view?usp=sharing, https://drive.google.com/file/d/1VwgQM76TabZu_oX3cGihCFnad0eGRn1r/view?usp=sharing
    (0015716)
    mhindi   
    2021-06-16 17:49   
    Link to the FreeCAD file containing the "6" sketch.

    https://drive.google.com/file/d/1ahe75VIeMdZQNHkvYa0kr4zZxRZ4fvbI/view?usp=sharing
    (0017063)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6232.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1416 [Sketcher] Feature feature have not tried 2014-02-16 16:08 2021-06-09 11:13
    Reporter: Pauvres_honteux Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Constraints creation "on the fly"
    Description: Hi, I have a wish of getting a constraints creation tool that consists/contains of all possible constraints commands avaible and starts running after double clicking a general constraints icon.

    Similar principle behavior as in a well known french cad program.

    I.E. after this general constraints tool has started you just click on the two lines/points you want to constrain and the following behavior is the same as now with the addition of a right click meny where one can select submatters to that specific constraint if applicable. And here's the beauty in it: you do not need to move your cursor up to and click the constraint icon for every constraint you want to create. This saves your hand from getting over strained and speeds up your work - a lot.

    To stop it running one could click the general constraints icon again or press ESC.

    Regards Pauvres_honteux
    Tags: constraints, Solver
    Steps To Reproduce:
    Additional Information: Had this in the "Open discussion" before but it was apparently the wrong place.
    Attached Files: Running_n_On_the_fly_constraints.tar.7z (598,410 bytes) 2017-06-17 07:35
    https://tracker.freecad.org/file_download.php?file_id=1655&type=bug
    Notes
    (0004688)
    Pauvres_honteux   
    2014-05-18 07:01   
    One more who finds this principle behavior to be of interest:
    http://www.freecadweb.org/tracker/view.php?id=1518
    (0009080)
    Kunda1   
    2017-05-22 13:45   
    @Abdullah OP seems to be referencing a ticket you worked on 0001518 as similar. Can you weigh in?
    (0009094)
    abdullah   
    2017-05-22 22:00   
    Well, I did the Continuous geometry mode you refer to. Jxnd did the continuous constraint creation mode (you click the constraint icon and now you select elements one after the other to which you want to apply the constraint, or pairs, or triplets depending on the constraint).

    I am not sure how that "french cad program" works. Apparently the reporter is asking for a generalisation of what jxnd did.

    I am not sure I understand the part of "a general constraints tool". If it is general, how does it know which constraint you want to apply? by guessing? The right click menu initially I thought was to change from one constraint to another, or select from a computer generated guess list. However, it says submatters, so it seems some kind fine tunning?

    A while ago I had an idea (never implemented, it will be in the forum somewhere) called "constrainator" which was guessing constraints based on the relative position of the geometry. This ticket reminded me of that.

    All in all. There is potential for improving constraint creation. Reducing the strain should be one of the main ergonomics goal of any CAD software, as a CAD user spends tons of hours in front of the computer, and it is well known that this creates all kind of health problems.

    Now, I would ask the reporter to better define what he expects from this feature request. With the current explanation there are little odds a developer will take it. Even lower that the result will match the expectations.
    (0009096)
    Kunda1   
    2017-05-23 04:38   
    @Pauvres_honteux ping
    (0009417)
    Pauvres_honteux   
    2017-06-17 07:35   
    (Last edited: 2017-06-17 11:27)
    Tried to make a movie but it got enormous in byte size, so I made a series of pictures instead.
    Could not bring the whole screen in on the pictures due to bytes limitation, but I guess icon appearance and double clicking isn't that interesting anyway in this context?
    Started the sketching tool "Polyline with arcs" to make the following:
    While clicking along in the sketch I can make an arc by "click-drag-click" as in frame 10 -> 12. Since "auto constraint" is active it also creates a tangent constraint.
    The blue lines and symbols are "running constraints", which suggests constraints at the tip of the pointer. As you can see in frame 13 it suggests a tangency constraint which I accept by left clicking once.
    Frame 40 -> 43 shows an constraint which creates a "contradictory" constraint, had to be deleted. Was done by right clicking and selecting "Delete", i.e. I didn't have to stop the "constraining mode" for the deletion.
    The green constraints where done by double clicking the "constraint button" once. After that you just "constrain away" !
    To temporarily deactivate "running constraints" you press "shift" button.
    To create just one constraint you single click the constraint button.
    Extra:
    Better selection system for constraints in Sketcher


    (0009419)
    Pauvres_honteux   
    2017-06-17 07:54   
    This "Tracker" platform adds "https://www.freecadweb.org/tracker/" in front of my inserted and intended link!
    It est, the link doesn't work at all !
    On top of the above I can't edit what I've written once it's sent!
    I'm using openSUSE Leap 42.1 with Xfce 4.12 and Firefox 52.1.1 (64-bitars).

    Anyway, copy the link "Better selection system for constraints in Sketcher", paste it in your browsers address row and remove "https://www.freecadweb.org/tracker/", then execute it.
    (0009420)
    Kunda1   
    2017-06-17 11:32   
    Sorry you're wrestling with the tracker. I fixed the URL issue all it needed was https:// as a prefix. I'll submit an upstream bug report about it. In regards to editing previous entries the tracker doesn't give that permission to 'reporters' maybe we should change that? (Ping @kkremitzki )
    Re: large size attachments you can always use an3rd party to host such a file. For movies some people use youtube. HTH
    (0009461)
    kkremitzki   
    2017-06-20 02:17   
    @Kunda1 @Pauvres_honteux Reporters should now be able to update issues.
    (0009465)
    Pauvres_honteux   
    2017-06-20 05:11   
    @kkremitzki, thank you so much for this editing possibility!
    This really opens up for reducing tracker bloating.

    PS. I removed a couple of my posts not adding anything to the issue. DS.
    (0011262)
    abdullah   
    2018-05-21 06:15   
    Thanks for the pictures. I have understood what you mean.

    Some of the concepts are similar to an old idea called "Constrinator", which was never implemented. I intended to start developing parts of that tool this year.

    I will consider your input when giving shape to that new tool.
    (0011271)
    Murmele   
    2018-05-21 17:35   
    I created a small clip which shows the dimensioning in catia:
    Youtube
    (0016417)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5582.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4357 [Part] Bug minor always 2020-06-04 09:03 2021-06-07 12:07
    Reporter: sangue Platform:  
    Assigned To: OS:  
    Priority: low OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 10
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.4 (GitTag)
    Build type: Release
    Branch: releases/FreeCAD-0-18
    Hash: 980bf9060e28555fecd9e3462f68ca74007b70f8
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: German/Switzerland (de_CH)
    Summary: Shape color is not displayed correctly after change in tree
    Description: Modifying the tree by dragging elements in, breaks the color of the shape on screen, although it's still set in the part.
    Tags: #pending-forum, colors
    Steps To Reproduce: 1. Part Module
    2. Make 5 Cubes (translate sligthly to get overlaps)
    3. Select Cube 1&2 and make Boolean Fragments 1 (BF1)
    4. Select Cube 3&4 and make Boolean Fragments 2 (BF2)
    5. Select BF1, CTRL-Select BF2 > Make boolean intersection (CUT)
    6. Select CUT > View > Set any Shape Color (red)
    7. In Treeview, drag Cube 5 into BF2 and recompute
    > CUT will be shown in default color, although CUT>View will still show the set color (red)
    Additional Information:
    Attached Files:
    Notes
    (0014462)
    openBrain   
    2020-06-04 18:11   
    @sangue : please address your issue following our reporting guidelines by opening first a topic in our forum. Thx
    We generally accept tickets when issue has been vet by the community, and especially confirmed to still exist in current development version (which you can test by yourself).
    (0014496)
    Kunda1   
    2020-06-07 14:20   
    @sangue forum thread please
    (0014516)
    sangue   
    2020-06-08 07:53   
    Yep. Just couldn't add another post earlier, cause forum didn't let me. It's here now:
    https://forum.freecadweb.org/viewtopic.php?f=19&t=47394
    (0016902)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6069.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4681 [FreeCAD] Feature feature N/A 2021-06-06 08:42 2021-06-06 08:42
    Reporter: Pauvres_honteux Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: N/A
    Summary: Allow non solid entities to be linked into Bodies in an automagic way.
    Description: Forum discussion: Allow non solid entities to be linked into Bodies in an automagic way.

    This request is about making the workflow less clickprone (more automagic and stable?) and therefor speeding up the creation process significantly.
    Tags:
    Steps To Reproduce: N/A
    Additional Information: N/A
    Attached Files:
    Notes
    (0017062)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6231.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4680 [FreeCAD] Feature feature N/A 2021-06-06 08:31 2021-06-06 08:31
    Reporter: Pauvres_honteux Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: N/A
    Summary: NURBS to be ruled by curves and adjoining surfaces
    Description: Forum discussion: NURBS to be ruled by curves and adjoining surfaces

    This is a request to make NURBS obey user created boundry curves and adjoining (ruling) surfaces, the day NURBS surfaces get implemented.

    Nota bene: Face/surface edges does not qualify as curves!
    Tags:
    Steps To Reproduce: N/A
    Additional Information: N/A
    Attached Files:
    Notes
    (0017061)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6230.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4679 [FreeCAD] Feature feature N/A 2021-06-06 08:12 2021-06-06 08:12
    Reporter: Pauvres_honteux Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: N/A
    Summary: A visible and selectable master zero/coordinate system
    Description: Forum discussion: File zero / Master zero.

    This will form the basis for future creation of rock solid models and assemblies.

    Some people may want to be able to continue working with todays "move and place", so for them an on/off switch of some sort may be required. Unless they try this new and smarter approach and become converts? =OD
    Tags:
    Steps To Reproduce: N/A
    Additional Information: N/A
    Attached Files:
    Notes
    (0017060)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6229.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4678 [FreeCAD] Feature feature N/A 2021-06-06 07:47 2021-06-06 07:47
    Reporter: Pauvres_honteux Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: N/A
    Summary: Tool/function to create a point on extrema of users choice
    Description: Forum discussion: Point on extrema.

    This feature will create a point at the extrema on a line, curve, surface or solid of users choice and in a direction of users choice and stay connected to that direction in such a way it recalculates the extrema if/when direction changes, e.g. the line indicating direction changes.
    Tags:
    Steps To Reproduce: N/A
    Additional Information:
    Attached Files:
    Notes
    (0017059)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6228.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4676 [FreeCAD] Feature minor always 2021-06-05 06:08 2021-06-06 06:37
    Reporter: TedM Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information:
    Summary: Not have Std_DuplicateSelection/Std_Copy automatically check dependencies
    Description: Currently, when doing Std_DuplicateSelection (Edit->duplicate selected object) or Std_Copy (Edit->copy) on PartDesign body(ies) or feature(s), the Object Selection dialog box has the selected objects as well as dependencies all checked. In my opinion, you almost never want to copy dependencies. In fact, copying dependencies which are features of another body (e.g. a sketch is created from a master sketch in another body by Sketcher_Carbon_Copy), this results in PD features outside of any body.

    Manually going through the object list to uncheck objects not specifically selected before starting the operation is tedious and error prone. Conversely, if only the original objects are automatically checked, it is easy to go through and check everything else.

    Assuming that we don't want to change the current default behavior (even though I personally think the current behavior is most often wrong), I'd suggest a button in the dialog box to "uncheck dependencies" and possibly a button "check dependencies".

    Also useful would be a configuration parameter to set the default behavior.
    Tags:
    Steps To Reproduce:
    1. Open new document and switch to Part Design WB.
    2. Create a body and sketch with a circle in the center and close the sketch.
    3. Pad the sketch.
    4. Make only the sketch visible.
    5. Create a second body and sketch.
    6. Make sure construction lines is toggled off, click Carbon Copy and control-click the visible sketch. Close the sketch.
    7. Pad this sketch.
    8. Double-click the second body to deactivate it and single-click to select that body.
    9. Edit->duplicate selection. The select objects dialog box has, in addition to the contents of Body001, XY_Plane and Sketch from the original body. Click OK.
    10. We now have Body002 which is a copy of Body001 EXCEPT that Sketch001 references Sketch002 instead of Sketch. Also Sketch002 (a copy of Sketch) and XY_Plane002 are floating outside of any body.
    Additional Information:
    Attached Files:
    Notes
    (0015695)
    TedM   
    2021-06-05 06:12   
    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=3&t=59098
    (0015696)
    TedM   
    2021-06-05 06:13   
    I am currently unable to upload my sample file. I'm getting the following:

    APPLICATION ERROR 0000503

    Invalid upload path. Directory either does not exist or not writable to webserver.

    Please use the "Back" button in your web browser to return to the previous page. There you can correct whatever problems were identified in this error or select another action. You can also click an option from the menu bar to go directly to a new section.
    (0015697)
    TedM   
    2021-06-06 01:24   
    I have placed the sample file in the 10th message of the linked thread. The file earlier in the thread will also work, it's just a tiny bit more complex.
    (0015702)
    Pauvres_honteux   
    2021-06-06 06:37   
    Hmm, to me this sounds like a version of 4502: Automate Link and ShapeBinder

    I.e. just copy, then decide for a pasting option: with link, without link (as is) or dead.
    (0017058)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6227.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4672 [Sketcher] Bug major have not tried 2021-05-31 10:39 2021-06-02 20:32
    Reporter: wst Platform:  
    Assigned To: OS:  
    Priority: high OS Version:  
    Status: feedback Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Windows 10 Version 2009
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24276 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-19
    Hash: a88db11e0a908f6e38f92bfc5187b13ebe470438
    Python version: 3.8.6+
    Qt version: 5.15.1
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: Dutch/Belgium (nl_BE)
    Summary: Datum 10,00 m for the constraint with index 6 is invalid
    Description:
    1. create a new file > new part > open sketcher.
    2. draw a vertical line (vertical constraint)
    3. add a vertical length constraint of 4200 mm
    4. draw a new horizontal line from the bottom point to the right (horizontal constraint)
    5. add a horizontal length constraint of 10000 mm (10m)

    You will receive: "Datum 10,00 m for the constraint with index 6 is invalid.


    
    12:28:18  Traceback (most recent call last):
      File "<string>", line 1, in <module>
    <class 'ValueError'>: Datum 10,00 m for the constraint with index 6 is invalid
    12:28:18  App.getDocument('Naamloos').getObject('Sketch').setDatum(6,App.Units.Quantity('10000.000000 mm'))
    12:28:30  Traceback (most recent call last):
      File "<string>", line 1, in <module>
    <class 'ValueError'>: Datum 10,00 m for the constraint with index 6 is invalid
    12:28:30  App.getDocument('Naamloos').getObject('Sketch').setDatum(6,App.Units.Quantity('10000.000000 mm'))
    


    Tags:
    Steps To Reproduce:
    1. create a new file > new part > open sketcher.
    2. draw a vertical line (vertical constraint)
    3. add a vertical length constraint of 4200 mm
    4. draw a new horizontal line from the bottom point to the right (horizontal constraint)
    5. add a horizontal length constraint of 10000 mm (10m)
    Additional Information: Windows 10 latest update
    Attached Files:
    Notes
    (0015687)
    Kunda1   
    2021-06-02 18:56   
    @wst can you reproduce on v0.20 dev? https://github.com/FreeCAD/FreeCAD-Bundle/releases/tag/weekly-builds
    (0017054)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6223.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4674 [FreeCAD] Feature crash always 2021-06-01 23:30 2021-06-01 23:32
    Reporter: jose-giraldez Platform:  
    Assigned To: OS:  
    Priority: high OS Version:  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information:
    Summary: FreeCAD cannot execute in Surface Pro X ARM based 64-bit syste
    Description:
    Your text to link here...

    Even though Microsoft's Surface Pro X, which is ARM based architecture, Windows 10 ARM, still can execute all x86 software by using internal x86 emulator.
    It works for most software so far, with minor exceptions... I guess FreeCAD 0.19 is an exception can cannot execute in Windows 10 ARM

    After Apple annoucement in 2020 and other major OEM (DELL, HP, ETC) laptops are migrating to ARM architecture.
    It is time FreeCAD fixes compatibility issues with Windows ARM.
    Tags:
    Steps To Reproduce: Install FreeCAD 0.19.x
    Execute FreeCAD
    Windows gives error "Cannot execute program"
    Additional Information:
    Attached Files:
    Notes
    (0015683)
    jose-giraldez   
    2021-06-01 23:31   
    https://forum.freecadweb.org/viewtopic.php?f=3&t=52193
    (0015684)
    jose-giraldez   
    2021-06-01 23:32   
    https://forum.freecadweb.org/viewtopic.php?f=3&t=52193
    (0017056)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6225.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4673 [Sketcher] Bug minor always 2021-06-01 05:49 2021-06-01 05:50
    Reporter: chrisb Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: macOS 10.16
    Word size of FreeCAD: 64-bit
    Version: 0.20.24825 (Git)
    Build type: Release
    Branch: master
    Hash: ccc4151b3020969450325466e385850783795325
    Python version: 3.9.2
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.5.1
    Locale: C/Default (C)
    Summary: Undetected redundant constraint
    Description: Description and file ar in this forum post.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0017055)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6224.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3603 [TechDraw] Feature minor always 2018-09-19 13:26 2021-05-31 18:31
    Reporter: ceremcem Platform:  
    Assigned To: OS:  
    Priority: low OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Preserve sketch colors in DXF exports
    Description: According to this, TechDraw currently does not support colored exports. I'm creating this post for further searches.

    Rationale
    While creating a laser cut output by using a unfold sketch of a bent sheet metal, it's important to set the bending lines to different colors, and also different colors for laser marking (if there is any) etc. These are set properly in 3D design but when I create the projection, they are not kept as is.

    Forum post
    https://forum.freecadweb.org/viewtopic.php?f=35&t=31042
    Tags: colors, DXF, export
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0011795)
    ceremcem   
    2018-09-19 13:27   
    Sorry, this is related with TechDraw, not PartDesign
    (0016642)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5807.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1436 [Sketcher] Feature feature N/A 2014-02-23 18:03 2021-05-25 10:42
    Reporter: bejant Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.13  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Sketcher: Break a Line and Add a Point onto a Line
    Description: A forum user requested two new features which seem useful:
    1. Break a line into two segments, leaving a gap where the user clicked between the two new segments. I'll add that the default gap should be user selectable.
    2. Add a point onto a line.
    From the following forum thread:
    http://forum.freecadweb.org/viewtopic.php?f=8&t=5928#p47176
    Tags:
    Steps To Reproduce:
    Additional Information: Feature request #1 reminds me of a little lisp routine named brk.lsp that I used to use daily in AutoCAD. I did a web search and believe the following code is the proper routine, maybe it will be of help (or maybe not).

    (defun c:brk(/ os pt1 pt2)
      (setvar "CMDECHO" 0)
      (setq os (getvar "osmode"))
      (setvar "osmode" 512)
      (setq pt1 (getpoint "\nPick object to be broken : "))
      (setvar "osmode" 33)
      (setq pt2 (getpoint "\nBreak point : "))
      (setvar "osmode" 0)
      (command "break" pt1 "f" pt2 "@")
      (setvar "osmode" os)
      (princ)
    )
    Attached Files:
    Notes
    (0015677)
    aviket   
    2021-05-25 10:42   
    This feature is already partially present in draft module of 0.19
    (0016419)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5584.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4594 [FreeCAD] Bug minor always 2021-03-10 20:31 2021-05-23 14:55
    Reporter: dudo Platform: Arch Linux  
    Assigned To: OS: Linux  
    Priority: normal OS Version:  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Arch Linux
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.20.24407 (Git)
    Build type: Release
    Branch: master
    Hash: 9f937f765d9c811535018110618056883b258837
    Python version: 3.9.2
    Qt version: 5.15.2
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: English/United States (en_US)
    Summary: Grid is transparent in respect to the window
    Description: Grid lines, instead of being filled with color, are filled with whatever is "below" the FreeCAD window, eg. desktop wallper, other windows, etc.

    https://forum.freecadweb.org/viewtopic.php?f=3&t=56509

    https://streamable.com/4xedi5

    https://i.imgur.com/dVKiDaB.png
    Tags: Coin3d
    Steps To Reproduce:
    Additional Information: This is using fully up to date Arch Linux, using git version of FreeCAD, running under wayland / sway
    Attached Files:
    Notes
    (0015498)
    dudo   
    2021-03-11 01:16   
    It seems to be related to blending, like every mesh that's rendered with some kind of transparency shows the bug in action

    https://streamable.com/0qavx3

    (Additionally, note the z-fighting issues, unrelated I guess)
    (0015499)
    dudo   
    2021-03-11 17:34   
    On the same system under Xorg it works all right, no transparency issues, so this could be wayland specific
    (0015501)
    Kunda1   
    2021-03-11 19:47   
    (Last edited: 2021-03-11 19:48)
    What graphics card/display driver are you using? Have you read the known issues as chrisb mentions in the forum thread?
    (0015502)
    dudo   
    2021-03-12 01:18   
    I've read the known issues but couldn't find any that would describe this behavior. The driver is Intel/MESA.

    
    ~> glxinfo | grep OpenGL
    OpenGL vendor string: Intel Open Source Technology Center
    OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 4000 (IVB GT2)
    OpenGL core profile version string: 4.2 (Core Profile) Mesa 20.3.4
    OpenGL core profile shading language version string: 4.20
    OpenGL core profile context flags: (none)
    OpenGL core profile profile mask: core profile
    OpenGL core profile extensions:
    OpenGL version string: 3.0 Mesa 20.3.4
    OpenGL shading language version string: 1.30
    OpenGL context flags: (none)
    OpenGL extensions:
    OpenGL ES profile version string: OpenGL ES 3.0 Mesa 20.3.4
    OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
    OpenGL ES profile extensions:
    ~> lspci | grep VGA
    00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
    
    (0015576)
    dannixon   
    2021-03-29 17:02   
    I am also seeing this issue using FreeCAD 0.19.
    It happens with both Weston and wlroots based compositors and not at all under Xorg/Xwayland.
    I'll also add that setting a solid background color also causes the entire render area to be affected, not just transparent areas.

    I do notice the following error which is only seen when running under Wayland:
    Coin warning in glxglue_isdirect(): Couldn't get current GLX context.
    (0015675)
    skewty   
    2021-05-23 14:43   
    This also affects Fedora 34 Gnome so Platform field should perhaps be adjusted accordingly.
    What I see in Fedora 34 is the part background color, when set to solid is completely transparent. Oddly this does not occur on the gradient setting.
    A work-around for this is thus to set both gradient colors to be the same (looks like a solid color but isn't transparent).

    I am also getting odd Qt menu placement issues in Wayland. For example:
    • File menu opens to the left outside window bounds.
    • Edit menu opens to the top outside window bounds.

    Additionally the splash screen is not centered when it opens for me.

    Could these all be related to a screen size / boundary call (upstream in Qt most likely) not working correctly in Wayland?
    (0015676)
    skewty   
    2021-05-23 14:55   
    
    [scott@fedora ~]$ glxinfo | grep OpenGL
    OpenGL vendor string: Intel
    OpenGL renderer string: Mesa Intel(R) UHD Graphics (CML GT2)
    OpenGL core profile version string: 4.6 (Core Profile) Mesa 21.1.1
    OpenGL core profile shading language version string: 4.60
    OpenGL core profile context flags: (none)
    OpenGL core profile profile mask: core profile
    OpenGL core profile extensions:
    OpenGL version string: 4.6 (Compatibility Profile) Mesa 21.1.1
    OpenGL shading language version string: 4.60
    OpenGL context flags: (none)
    OpenGL profile mask: compatibility profile
    OpenGL extensions:
    OpenGL ES profile version string: OpenGL ES 3.2 Mesa 21.1.1
    OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
    OpenGL ES profile extensions:
    [scott@fedora ~]$ lspci | grep VGA
    00:02.0 VGA compatible controller: Intel Corporation CometLake-U GT2 [UHD Graphics] (rev 02)
    [scott@fedora ~]$ 
    
    (0017009)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6177.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4659 [FreeCAD] Bug trivial always 2021-05-18 01:39 2021-05-18 01:39
    Reporter: samantha-uk Platform: Macbook Intel  
    Assigned To: OS: OSX Catalina  
    Priority: normal OS Version: 10.15.7  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information:
    Summary: Select Color -> Pick Screen Color cannot select a colour outside the dialog window
    Description: When using Select Color -> Pick Screen Color, the selection pointer is restricted to sampling inside the dialog box.


    This contrasts with the Spreadsheet color picker where the eyedropper tool can sample anywhere on the screen.
    Tags: UI
    Steps To Reproduce: Fire up the Select Color dialog from Preferences or Property View/view and select the Pick Screen Color feature.
    The cursor will not move outside the dialog boundary.
    Additional Information: Contrast with the similar activity from spreadsheet workbench, which seems to use a different approach.
    Attached Files:
    Notes
    (0017049)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6218.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4651 [Part] Bug minor always 2021-05-01 11:51 2021-05-13 16:59
    Reporter: Daniele75 Platform:  
    Assigned To: OS: Windows 10 Home  
    Priority: high OS Version: 20H2  
    Status: feedback Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: I discovered the problem as initially I had version 18 installed on one pc, then on another I installed version 19.
    Seeing the problem with the 19 I tried both versions on the same pc, first replacing it with the previous one then trying to use them both in the same pc at the same time.
    Summary: Problem in using the sweep function
    Description:
    I found a bug when making springs that occurs in version 19, while up to 18 it worked smoothly.

    Tags:
    Steps To Reproduce: 1° new file
    2° goto "Part" ambient
    3° creates parametric geometric primitives
    4° Propeller
    5° set dimension: pitch 0,75 ; height 3mm ; radius 1,3mm
    6° Create Propeller ( Ok )
    7° goto "Sketcher" ambient
    8° Create new Sketcher
    9° Select XZ floor
    10° Create circle
    11° Set constraints... radius 0,2mm ; height from y axis 0mm ; distance from x axis 1,3mm ( same than radius of propeller )
    12° close
    13° goto "Part" ambient
    14° select Sweep utilities
    15° Select Sketch from list available profiles
    16° bring to selected profiles
    17° select all the propeller in the draw ( black to green color )
    18° check create solid + frenet
    19° OK


    the sweep obtained is corrupted.

    Additional Information:
    Attached Files:
    Notes
    (0015662)
    openBrain   
    2021-05-13 16:59   
    @Daniele75 : please address your issue according our reporting guidelines by opening a new topic on our forum. Thx
    (0017043)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6211.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4655 [Arch] Bug minor always 2021-05-04 17:04 2021-05-13 16:55
    Reporter: bitacovir Platform:  
    Assigned To: OS: Windows  
    Priority: normal OS Version: 10  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information:
    Summary: [Arch] Double click on door/window opens BIM wokbench
    Description: When I double click on Arch door/window, in the combo view panel, FreeCAD switches to BIM wokbench. If you are in any workbench, it'll change to BIM with the double click (tested on 0.19.2 and 0.20)

    Forum discussion:
    https://forum.freecadweb.org/viewtopic.php?f=23&t=58362
    Tags: 0.19, Arch
    Steps To Reproduce: Open Arch workbench
    Create a Arch wall
    Insert an Arch Window in the wall
    Double click on the window object in the combo view panel
    The workbench changes to BIM workbench (that I have installed).
    Additional Information:
    Attached Files:
    Notes
    (0017046)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6215.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4248 [Sketcher] Feature trivial always 2020-01-15 19:58 2021-05-11 21:20
    Reporter: leoheck Platform: x86_64  
    Assigned To: OS: Ubuntu  
    Priority: high OS Version: 18.04/19.04/19.1  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: This is what I am using right now.

    OS: Ubuntu 19.10 (ubuntu:GNOME/ubuntu)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.
    Build type: Release
    Python version: 3.7.5
    Qt version: 5.12.4
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/United States (en_US)
    Summary: Shorctut for Transform
    Description: I use the "Transform" action to move objects very often. This action does not have a shortcut. It will represent a really good improvement to have this shortcut implemented.

    I posted this some time ago in the Forum too.
    https://forum.freecadweb.org/viewtopic.php?f=8&t=38258&hilit=shortcut

    I would suggest something like Ctrl+Shit+T (or something with T, because it is easier to remember) for example. Working at least in Part Workbench and Part Design Workbench.
    Tags: shortcuts
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0014089)
    Kunda1   
    2020-01-16 16:58   
    @leoheck why are you marking this ticket Product Version 0.18 when you are using 0.19 ? Please use the correct version next time. Thank you
    (0014090)
    leoheck   
    2020-01-16 18:28   
    I use Freecad in a bunch of computers. On my personal computer, I am using Freecad 0.19. But since it is a small feature request it would be nice to implement it in 0.18 as well if possible. I am trying to change it. It took me about 10 minutes just to understand how to reply to your message.
    (0014091)
    leoheck   
    2020-01-16 18:30   
    Ah, you already fixed it. Alright, thanks.
    (0015660)
    heewa   
    2021-05-11 21:19   
    (Last edited: 2021-05-11 21:20)
    Looks like this has been fixed on the 0.20 release (with PR 0004678). I verified that it works for me on a build from master. A simple merge to the 0.19 branch should fix it for that release as well.
    (0016857)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6023.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1208 [FreeCAD] Feature minor always 2013-08-10 18:54 2021-05-09 20:42
    Reporter: bejant Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.13  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Parts Appear as Shells Instead of Solids When Viewed by Clipping Plane
    Description: FreeCAD version is actually 0.14 (0.14 presently is not selectable from Product Version box).

    I do not know if the parts are actually solids that appear as shells, of if the parts really are hollow shells. Link to forum thread:


    http://forum.freecadweb.org/viewtopic.php?f=3&t=4371
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0007714)
    Kunda1   
    2017-01-13 13:29   
    Some developments with coin3d has made this a possiblity: Please see http://forum.freecadweb.org/viewtopic.php?f=3&t=4371&start=10#p94838
    (0012818)
    berndhahnebach   
    2019-03-01 21:32   
    related https://forum.freecadweb.org/viewtopic.php?f=8&t=18188
    (0015658)
    dstarke   
    2021-05-09 20:42   
    Create a rectangular filled face in the Draft workbench and use that with the "Slice apart" tool of the Part workbench also results in a solid clipping plane.
    See https://www.xsim.info/articles/FreeCAD/en-US/HowTo/Cut-a-solid-with-a-plane.html
    (0016405)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5570.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4657 [FreeCAD] Bug minor always 2021-05-04 20:17 2021-05-06 13:55
    Reporter: mcv100 Platform: Windows  
    Assigned To: OS: Windows 10  
    Priority: normal OS Version: 1909  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Windows 10 Version 1909
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24291 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-19
    Hash: 7b5e18a0759de778b74d3a5c17eba9cb815035ac
    Python version: 3.8.6+
    Qt version: 5.15.2
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: English/Netherlands (en_NL)
    Summary: Vertices turn black with box selection when no constraints are visible in first new sketch
    Description: I'm seeing a strange issue in the Sketcher, where all vertices (including the origin) turn black after a box selection, unless there are constraint symbols visible. I can reproduce this issue consistently and very easily, even on a fresh 0.19.2 install with all preferences reset.

    Just make a new file, go into part design, new body, new sketch and make a box selection. I see the origin turn black instantly (even if it was selected), unless there were constraints visible it seems.

    I cannot reproduce this issue on a new body, new sketch if the file already contains other bodies. Only in a fresh file does this happen for me.

    Forum link:
    https://forum.freecadweb.org/viewtopic.php?f=3&t=58314&p=501224

    [DEV EDIT] more reports on the forum :
    https://forum.freecadweb.org/viewtopic.php?f=3&t=57744
    https://forum.freecadweb.org/viewtopic.php?f=12&t=55260
    Tags:
    Steps To Reproduce:
    1. Make new file
    2. Go into part design
    3. Make new body
    4. Start a new sketch
    5. Make a box selection
    6. See origin turn black
    Additional Information:
    Attached Files:
    Notes
    (0017047)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6216.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4654 [FreeCAD] Bug minor always 2021-05-04 16:20 2021-05-05 07:45
    Reporter: SeppoTu Platform: Table PC  
    Assigned To: OS: Windows 10 Pro  
    Priority: normal OS Version: 20H2  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Windows 10 Version 2009
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24276 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-19
    Hash: a88db11e0a908f6e38f92bfc5187b13ebe470438
    Python version: 3.8.6+
    Qt version: 5.15.1
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: Finnish/Finland (fi_FI)
    Summary: Problem to rotate 3D-view with 3D-mouse
    Description: Center of rotation is not updated in perspective view mode, during transfer with 3D-mouse.
    In perspective view mode the normal mouse operations sets rotating center in correct postion.
    Using 3D-mouse the rotation center is not updated. This makes it very difficult to use 3D-mouse in prespective view mode.
    Tested with 3DConnexion's SpacePilot Pro.
    Tags: 3dconnexion, mouse, rotate, Win
    Steps To Reproduce: 1. Open FreeCAD.
    2. Create new part (cube).
    4. Change view mode to perspective view.
    5. Rotate cube with 3D-mouse. Rotation center is in cube's center.
    6. Move cube away from it's original position by using 3D-mouse.
    7. Rotate cube again with 3D-mouse. Rotation center has not transferred with the cube.
       Instead rotation center is still at the old location.
    8. Rotate cube with normal mouse. Cube jumps to to it's original location (rotation center) before it starts rotate.
    Additional Information:
    Attached Files:
    Notes
    (0015650)
    SeppoTu   
    2021-05-05 07:45   
    Correction to reproduction:
    In reproduce step 6, I ment to say that: zoom the view with 3D-mouse, not that cube it self has to move.
    (0017045)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6214.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4652 [Path] Bug minor always 2021-05-04 06:52 2021-05-04 07:03
    Reporter: dubstar_04 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: <!--ATTENTION:
    COMPLETELY ERASE THIS AFTER PASTING YOUR
    Help > About FreeCAD > Copy to clipboard
    NOTE: just the snippet alone will do without anything else included.
    The ticket will not be submitted without it.
    -->
    Summary: Drilling Operation missing move to operation start depth.
    Description: The drilling operation is missing a move to operation start depth

    ########## Example Output ##########
    G0 Z35.000000
    G90
    G1 X0.000000 Y0.000000 Z12.000000 <---- This line is missing
    G99
    G81 R33.000000 X0.000000 Y0.000000 Z0.000000
    G80
    G0 Z33.000000
    G81 R33.000000 X0.000000 Y0.000000 Z0.000000
    G80
    G0 Z33.000000
    G0 Z35.000000
    ########## Example Output ##########

    Forum Link: https://forum.freecadweb.org/viewtopic.php?f=15&t=58306
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0017044)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6212.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4646 [Arch] Bug minor always 2021-04-27 13:49 2021-04-27 13:49
    Reporter: bitacovir Platform:  
    Assigned To: OS: windows  
    Priority: normal OS Version: 10  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Windows 10 Version 1909
    Word size of FreeCAD: 64-bit
    Version: 0.20.24587 (Git)
    Build type: Release
    Branch: master
    Hash: 1f62d4666102d8efd4d8f3ba58a1037456a3bcfb
    Python version: 3.8.6+
    Qt version: 5.15.1
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: English/United States (en_US)
    Summary: [Arch] "Show Fill" in ArchView-TechDraw no longer works
    Description: It seems Show Fill set to True no longer works for ArchWall in TechDraw with ArchView.
    Forum discussion for more information: https://forum.freecadweb.org/viewtopic.php?f=23&t=57534
    Bug in FC 0.19 and 0.20
    Maybe assign this to Yorik.
    Tags: 0.19, Arch
    Steps To Reproduce:
    Additional Information:
    Attached Files: Test_ TechDraw-ArchView_ ArchWall_05_ No Fill Bug.FCStd (48,102 bytes) 2021-04-27 13:49
    https://tracker.freecad.org/file_download.php?file_id=2681&type=bug
    Notes
    (0017040)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6208.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4641 [Sketcher] Feature feature always 2021-04-24 12:14 2021-04-24 12:14
    Reporter: jmaustpc Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Ubuntu 20.04.2 LTS (KDE/plasma)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.Stable PPA
    Build type: Release
    Branch: unknown
    Hash: 9e3b630bbfb6807e93eeffb655e6c20f218644fc
    Python version: 3.8.5
    Qt version: 5.12.8
    Coin version: 4.0.0
    OCC version: 7.5.1
    Locale: English/Australia (en_AU)
    Summary: Sketcher Clone - extend to allow substitution of dimensional constraints between different geometry items
    Description: Sketcher Clone will currently substitute a dimensional constraint on a single geometry element with a "equals" constraint on the matching geometry element in the clone.

    The request is to extend this so that it will work when that dimensional constraint is between two different geometry elements.

    Tags:
    Steps To Reproduce: For example a Horizontal distance constraint applied to the top line of a rectangle will be an Equals constraint on the top line of the rectangle in the clone. However currently if the horizontal distance constraint for the same rectangle was applied between each of the top points of the two vertical side lines of the rectangle, then the same Horizontal constraint will be applied to the clone rectangle rather than an equals, therefore requiring editing every instance of the clone and original if an edit is required.

    Forum topic
    https://forum.freecadweb.org/viewtopic.php?f=3&t=57915

    An example file is attached to this ticket, it is the same file as one of the files in my post to that same topic in the link above.
    Additional Information:
    Attached Files: copy_clone_tests_sketcher_constrained_only_between_geometry2.FCStd (9,841 bytes) 2021-04-24 12:14
    https://tracker.freecad.org/file_download.php?file_id=2678&type=bug
    Notes
    (0017037)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6205.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4640 [FreeCAD] Feature feature N/A 2021-04-21 12:33 2021-04-22 14:51
    Reporter: nukeRomancer Platform:  
    Assigned To: OS:  
    Priority: immediate OS Version:  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: <!--ATTENTION:
    COMPLETELY ERASE THIS AFTER PASTING YOUR
    Help > About FreeCAD > Copy to clipboard
    NOTE: just the snippet alone will do without anything else included.
    The ticket will not be submitted without it.
    -->
    Summary: interactive controls in the viewport for all / most ( where applicable ) tools that have numeric values / inputs
    Description: interactive controls in the viewport for all / most ( where applicable ) tools that have numeric values / inputs

    this would be a MASSIVE improvement to the general workflow

    https://forum.freecadweb.org/viewtopic.php?p=496292#p496292

    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0015641)
    Pauvres_honteux   
    2021-04-22 14:51   
    Some good examples of how user interacting stuff can be made, begins at 28 minutes
    (0017036)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6204.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1294 [FreeCAD] Feature minor have not tried 2013-10-31 10:21 2021-04-21 18:10
    Reporter: wmayer Platform:  
    Assigned To: wmayer OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Configure light sources
    Description: http://catiadoc.free.fr/online/basug_C2/basugbt1701.htm
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0013409)
    Kunda1   
    2019-08-10 16:59   
    relevant: https://forum.freecadweb.org/viewtopic.php?f=10&t=9663&p=326080#p326080
    (0015633)
    Kunda1   
    2021-04-21 18:10   
    @realthunder has implemented this in his LinkStage3 branch, here's the initial post he made about it: https://forum.freecadweb.org/viewtopic.php?f=10&t=9663&start=60#p394930
    (0016410)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5575.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4637 [Part] Bug minor always 2021-04-17 22:25 2021-04-17 22:38
    Reporter: chrisb Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: macOS 10.16
    Word size of FreeCAD: 64-bit
    Version: 0.20.24612 (Git)
    Build type: Release
    Branch: master
    Hash: f525904c1be10a0f55aa3502151c2c55e5054259
    Python version: 3.9.2
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.5.1
    Locale: C/Default (C)
    Summary: Part Create shape from mesh: sewing tolerance not editable
    Description: With a plain vanilla config the sewing tolerance cannot be changed to a value below 1.0.
    It is necessary to change the settings in Preferences->Import-Export-MeshFormats at least once. Then the preset value is used and can be changed.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0015613)
    chrisb   
    2021-04-17 22:38   
    We have seen something similar with Draft->Scale, where the factor couldn't be changed to fractional numbers.
    (0017034)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6202.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4633 [FreeCAD] Bug crash always 2021-04-13 19:21 2021-04-13 19:21
    Reporter: 56jimalexander Platform:  
    Assigned To: OS:  
    Priority: high OS Version:  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information:
    OS: Windows 10 (10.0)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24212 (Git)
    Build type: Release
    Branch: master
    Hash: 3d227cf7179c00e57f2733f947b4b1b0368d219a
    Python version: 3.8.8
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: English/United States (en_US)
    Summary: .19 release crashes on creating certain surfaces
    Description: Original post with confirmation: https://forum.freecadweb.org/viewtopic.php?f=3&t=57538

    This problem is well documented in the referenced post.
    I am not able to upload the file (.2mb) here but it is available in the reference post.
    Tags:
    Steps To Reproduce: See provided link
    Additional Information:
    Attached Files:
    Notes
    (0017032)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6200.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4632 [Path] Bug minor always 2021-04-13 10:04 2021-04-13 10:04
    Reporter: monkeydog Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: (freecad-0.19-0.3.20201125gita50ae33557.fc33.2.x86_64)
    OS: Fedora 33 (Workstation Edition) (GNOME/gnome)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.Unknown
    Build type: Unknown
    Python version: 3.9.0
    Qt version: 5.15.1
    Coin version: 4.0.0a
    OCC version: 7.5.0
    Locale: English/Australia (en_AU)
    Summary: 3d surface covers model instead of selected faces
    Description: When selecting all outside edges of a shape for a single 3D surfacing operation, the entire model gets 3D surfaced; Expectation is just the selected edges are 3D surfaced.

    Associated thread: https://forum.freecadweb.org/viewtopic.php?f=15&t=56981
    Tags:
    Steps To Reproduce: Add all outside edges of a shape to by applied within a single 3D surface operation and apply.
    Additional Information: The attached images demonstrate that the inclusion of face 7 to the 3d surface operation to complete the outside perimeter causes the entire model to be 3D surfaced.
    Further commentary on the images may be found in the original thread https://forum.freecadweb.org/viewtopic.php?f=15&t=56981
    Attached Files: phone.FCStd (159,657 bytes) 2021-04-13 10:04
    https://tracker.freecad.org/file_download.php?file_id=2666&type=bug
    Screenshot from 2021-03-23 21-42-11.png (108,483 bytes) 2021-04-13 10:04
    https://tracker.freecad.org/file_download.php?file_id=2667&type=bug
    Screenshot from 2021-03-23 21-40-05.png (108,041 bytes) 2021-04-13 10:04
    https://tracker.freecad.org/file_download.php?file_id=2668&type=bug
    Screenshot from 2021-03-23 21-39-39.png (102,486 bytes) 2021-04-13 10:04
    https://tracker.freecad.org/file_download.php?file_id=2669&type=bug
    Notes
    (0017031)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6199.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3340 [Draft] Bug block always 2018-02-07 12:44 2021-04-12 06:14
    Reporter: wmayer Platform:  
    Assigned To: yorik OS:  
    Priority: high OS Version:  
    Status: assigned Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Massive memory leak in Draft
    Description: When using e.g. the dimension tool and hovering over a shape causes a huge memory leak. A user reported that the total memory consumption went up to 11 GB (!!!)
    Tags:
    Steps To Reproduce:
    Additional Information: https://forum.freecadweb.org/viewtopic.php?f=10&t=26784
    Attached Files:
    Notes
    (0011023)
    yorik   
    2018-03-08 15:15   
    This is now reduced as much as we can on the FreeCAD side I think. There is still some memory leak somewhere in pivy, though. But this has ow been minimized as much as possible.

    I suggest we either close this now, as there is AFAICS not much more we can do in the FreeCAD code itself, or leave it open, removing the 0.17 target, in case someone wants to dig into the pivy code later, as after all, it has become more or less our baby (or Looo's :) ) now...

    In any case I'll remove the 0.17 tag
    (0011025)
    wmayer   
    2018-03-08 15:50   
    Out of curiosity what makes you believe that there is a leak in pivy?
    (0011026)
    yorik   
    2018-03-08 17:32   
    Try this https://forum.freecadweb.org/viewtopic.php?f=10&t=26784&start=20#p216270
    (0011027)
    wmayer   
    2018-03-08 20:19   
    See this: https://forum.freecadweb.org/viewtopic.php?f=10&t=26784&start=30#p219240
    (0012668)
    yorik   
    2019-02-16 22:27   
    This one fell far below my radar... In any case the problem is not big anymore, more several optimizations to do, so better to reschedule for 0.19...
    (0014547)
    carlopav   
    2020-06-14 21:17   
    @yorik, what's the status of this? is that something that could be done now?
    (0014548)
    yorik   
    2020-06-15 08:13   
    It needs testing again, basically. I have not observed this anymore, but it needs to be metered precisely to make sure.
    (0014554)
    carlopav   
    2020-06-15 17:17   
    I think i've observed a huge augmenting of memory used when changing from 2d to 3d and back into 2d several times on the dimension object... Do you experience the same?
    (0014816)
    Kunda1   
    2020-10-10 12:53   
    (Last edited: 2020-10-10 12:53)
    Is this the memory leak solved in FreeCAD master ab4ab444 ?
    thread: https://forum.freecadweb.org/viewtopic.php?f=15&t=50583
    (0014817)
    Kunda1   
    2020-10-10 12:58   
    Tracking in https://forum.freecadweb.org/viewtopic.php?f=8&t=51016
    (0015610)
    wmayer   
    2021-04-12 06:14   
    When building FreeCAD with -fsanitize=address then this build reports that an SoSeparator isn't deleted. The node contains an SoCoordinate3 and an SoLineSet.
    The amount of memory is only a few KB.
    (0016596)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5761.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4630 [PartDesign] Bug minor always 2021-04-11 15:59 2021-04-11 15:59
    Reporter: BloodyRain2k Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Windows 7 Version 6.1 (Build 7601: SP 1)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24276 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-19
    Hash: a88db11e0a908f6e38f92bfc5187b13ebe470438
    Python version: 3.8.6+
    Qt version: 5.15.1
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: English/United States (en_US)
    Summary: Can't use a linked Sketch for Lofting
    Description: I tried to create something that cuts a hole through a sketch profile into the same sketch but mirrored.
    So I've linked the sketch and then flipped it, assuming I can just loft from the original to the linked copy, but it won't do that.
    Tags: Loft, Sketch
    Steps To Reproduce: Create primitive, create sketch, link sketch, try to loft from sketch to linked copy.

    Example file included.
    Additional Information:
    Attached Files: Linked_Loft.FCStd (17,612 bytes) 2021-04-11 15:59
    https://tracker.freecad.org/file_download.php?file_id=2665&type=bug
    Notes
    (0017030)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6198.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4615 [Part] Feature feature N/A 2021-04-05 09:24 2021-04-11 15:17
    Reporter: Pauvres_honteux Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: Not applicable for this request.
    Summary: Surface to surface tangency via a common curve
    Description: Forum discussion: Surface to surface tangency
    Request for development of the possibility to create a tangent surface with respect to another surface sharing a common curve.
    The curve shall be the parent of both surfaces.
    No approximation of curves or surfaces is allowed.

    Make file "Arbitrary four-sided surface" to work according to what is stated above:
    Arbitrary four-sided surface
    Tags: toponaming
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0015594)
    Kunda1   
    2021-04-05 11:09   
    (Last edited: 2021-04-05 11:20)
    Looks like there has been some effort already by wmayer in
    (0015595)
    Pauvres_honteux   
    2021-04-05 11:52   
    @Kunda1, you do realize you've linked to the same thread as I did? Hence I already know all that and have tested it and it does not work for the requested "Surface to surface tangency via a common curve".
    The way it works as of now is via an surface edge and that makes the model extreamly affected by topo naming, no matter how good Realthunders algo works. Please reread the topic and try to understand how one create rock solid, linked, geometry. That is, via a common curve as a parent for both surfaces.
    (0015596)
    Kunda1   
    2021-04-05 13:35   
    @Pauvres_honteux Yes, I do realize that. My intention was to summarize by linking to the code that has already been contributed. This way, devs have a summary of what's been done on the source code side of things.
    (0017021)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6189.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4624 [Part] Bug major always 2021-04-08 00:01 2021-04-09 14:26
    Reporter: DocFingo Platform: Core i5-8350U (x64, 8GB RAM)  
    Assigned To: OS: Windows 10 Enterprise  
    Priority: normal OS Version: 10.0.19042  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Windows 10 Version 2009
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24276 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-19
    Hash: a88db11e0a908f6e38f92bfc5187b13ebe470438
    Python version: 3.8.6+
    Qt version: 5.15.1
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: English/Germany (en_DE)
    Summary: Thickness fails on simple shapes (BRep_API command not done) - regression from 0.19.24267
    Description: Thickness operations with Arc or Tangent join types fail on predominantly concave shapes.
    Message is BRep_API: command not done. This happens for any positive Thickness value.

    Changing join type to Intersection solves the issue, but does not yield the desired part.

    This is a potential regression from 0.19.24267 where the issue seemed to be (mostly?) fixed, see reproduction steps below.

    A Thickness problem in conjunction with OCC 7.5 was previously reported here by user AlStu, with forum discussions here.
    However OCC 7.5 is present in both OCC has been upgraded from 7.3 in 0.19.24267 to 7.5 in 0.19.24276, both show different results.
    Tags:
    Steps To Reproduce: Part workbench: Make a simple extrusion from a sketch with concave outer shape.
    Apply Thickness while selecting the top face. Try different Join types.

    To test the potential regression from 0.19.24267, open the attached FCstd file.
    Press F5 to recompute the solution.
    0.19.24267 -> Thickness is computed successfully except for the sharp-edged shape.
    0.19.24276 -> Thickness (Arc/Tangent join type) fails for 3 out of 4 shapes. Deleting and re-applying thickness yields BRep_API: command not done
    Additional Information: This is the previous 0.19.24267 version I used for the comparison:
    OS: Windows 10 (10.0)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24267 (Git)
    Build type: Release
    Branch: master
    Hash: b2ca86d8d72b636011a73394bf9bcdedb3b109b7
    Python version: 3.6.8
    Qt version: 5.12.1
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/Germany (en_DE)
    System Description
    Attached Files: ThicknessTestShapes.FCStd (118,170 bytes) 2021-04-08 00:01
    https://tracker.freecad.org/file_download.php?file_id=2662&type=bug
    Notes
    (0017028)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6196.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4620 [Sketcher] Feature minor have not tried 2021-04-07 05:36 2021-04-07 05:36
    Reporter: abdullah Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Ubuntu 20.04.2 LTS (MATE/mate)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.
    Build type: Release
    Branch: unknown
    Hash: e8566f22bbeb0b7204e3c45519d0963e8881100b
    Python version: 3.8.5
    Qt version: 5.12.8
    Coin version: 4.0.0
    OCC version: 7.5.1
    Summary: Check implementation of ::setDatum
    Description:
    https://github.com/FreeCAD/FreeCAD/pull/4264#issuecomment-766913064
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0017026)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6194.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4619 [Sketcher] Bug minor have not tried 2021-04-07 05:25 2021-04-07 05:25
    Reporter: abdullah Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Ubuntu 20.04.2 LTS (MATE/mate)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.
    Build type: Release
    Branch: unknown
    Hash: e8566f22bbeb0b7204e3c45519d0963e8881100b
    Python version: 3.8.5
    Qt version: 5.12.8
    Coin version: 4.0.0
    OCC version: 7.5.1
    Summary: Internal alignment constraints should not be reported as redundant
    Description:
    An internal alignment constraint can be redundant with other constraints, but it is never the one to be removed.
    It may be possible to improve the algorithm suggesting redundant constraints, so that it does not suggest removing internal alignment constraints.

    https://github.com/realthunder/FreeCAD/issues/97
    Tags:
    Steps To Reproduce: Unfortunately no file at this moment. If somebody comes along with one file, please upload it here.
    Additional Information:
    Attached Files:
    Notes
    (0017025)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6193.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4618 [PartDesign] Feature minor always 2021-04-06 07:25 2021-04-06 11:49
    Reporter: BloodyRain2k Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Windows 7 Version 6.1 (Build 7601: SP 1)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24276 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-19
    Hash: a88db11e0a908f6e38f92bfc5187b13ebe470438
    Python version: 3.8.6+
    Qt version: 5.15.1
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: English/United States (en_US)
    Summary: Better edge selection for Part Sweep
    Description: I've been working a lot with the Part Sweep of the Part Design WB recently and I've started to feel that adding edges of objects shouldn't be as cumbersome as it currently is.

    For example is it not possible to preselect the wanted edges and THEN click the "Add Edge" button to add them, nor is it possible to just keep adding them because the button gets "released" after each edge added.
    It might not sound like much, but I've had to redo the same Sweep a dozen times while working on my oddly shaped part shown below, because eventually something in the feature order went wrong and I had to delete and later redo the Sweep.

    Edit: I also just remembered that the DEL key doesn't work for either the edges nor the profiles used in transition mode.
    It's shown in the context menu, but pressing the key doesn't register.




    On a sidenote: it would be also great if there would be a Compound Filter for just keeping the edges selected when creating it as a path.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0017024)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6192.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4614 [Assembly] General feature N/A 2021-04-05 08:30 2021-04-05 13:43
    Reporter: Pauvres_honteux Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: ... does not apply on this request.
    Summary: Request for a separate Assembly file format
    Description: Basically this request is to make REAL assemblies possible AND to make it possible to manage large scale corporations files with a database/existing PDM-system.
    See https://forum.freecadweb.org/viewtopic.php?f=20&t=52431&sid=f77a79b296e07ce9a752194851f541ac
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0015598)
    Kunda1   
    2021-04-05 13:42   
    Moved to Assembly category

    Heads-up @Pauvres_honteux can you be more mindful about categorizing the tickets you open. It saves bug triagers a lot of time.
    (0017020)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6188.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4617 [FEM] Feature minor N/A 2021-04-05 10:36 2021-04-05 13:37
    Reporter: Pauvres_honteux Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: Not applicable to this request.
    Summary: GUI for creating "virtual elements"
    Description: See forum discussion: Virtual elements

    In FEM world so called virtual elements are heavily used to reduce the amount of raw calculation power needed for any given simulation.
    Example: imagine an already created engine block where your boss tells you to create an engine mount that can withstand a specific amount of G-forces. When you iterate through your different designs of that engine mount you must check them for strength AND at the same time check the engine block for strength in that area. To not stall your computer each and every time you must do these FEM calculations you will cut out the fastening portion for the engine mount from the engine block and utilize "virtual elements" to replace the rest of the engine block. This reduce the number of nodes calculculate and therefor reduce the strain on your computer, hence significantly reduce calculation time. Engine block stiffnes at the cut boundaries will given to you by your calculation specialist department and these values are set to the virtual elemnts.
    The same principle goes for any calculation that can be simplified. Even for telecom masts!
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0015597)
    Kunda1   
    2021-04-05 13:37   
    @Pauvres_honteux shouldn't this be in the FEM category?
    (0017023)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6191.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4616 [PartDesign] Feature feature N/A 2021-04-05 09:50 2021-04-05 11:05
    Reporter: Pauvres_honteux Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: Not applicable for this request.
    Summary: Request for a "Replacement command" in PartDesign
    Description: See forum discussion: Feature request - Replacement command
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0015593)
    Kunda1   
    2021-04-05 11:04   
    (Last edited: 2021-04-05 11:05)
    Changed severity to 'Feature'
    Moved ticket from 'Part' to 'PartDesign'
    (0017022)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6190.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4603 [Arch] Bug minor always 2021-03-24 11:28 2021-04-01 17:08
    Reporter: bitacovir Platform: Windows  
    Assigned To: OS: Windows  
    Priority: normal OS Version: 10  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Windows 10 Version 1909
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.20.24451 (Git)
    Build type: Release
    Branch: master
    Hash: 9c8685c20cd70553d85940c2ba93ade69f38171d
    Python version: 3.8.6+
    Qt version: 5.15.1
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: English/United States (en_US)

    OS: Windows 10 (10.0)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24267 (Git)
    Build type: Release
    Branch: master
    Hash: b2ca86d8d72b636011a73394bf9bcdedb3b109b7
    Python version: 3.8.8
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: English/United States (en_US)
    Summary: Draft_Wire: Ctrl+Z does not work in FC 0.19
    Description: 'Ctrl+Z' does not work inside the Draft_Wire command. Pressing the panel button works, but not the keyboard shortcut.

    In FC 0.18.4 'Ctrl+Z' works.

    Forum discussion: https://forum.freecadweb.org/viewtopic.php?f=23&t=56805

    Tags: 0.19, Draft, undo
    Steps To Reproduce: Open Draft WB
    Click on Draft polyline tool
    After two or three clicks try Ctrl+Z. Nothing happens (It should delete last point).
    Additional Information:
    Attached Files:
    Notes
    (0017013)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6181.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4611 [FreeCAD] Bug minor always 2021-03-30 17:51 2021-03-30 20:09
    Reporter: drmacro Platform: PC  
    Assigned To: OS: Ubuntu  
    Priority: normal OS Version: 20.04  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information:
    OS: Ubuntu 20.04.2 LTS (XFCE/ubuntustudio)
    Word size of FreeCAD: 64-bit
    Version: 0.20.24640 (Git)
    Build type: Unknown
    Branch: master
    Hash: afa40aa0493309013e2e0dc5199523ef1f4c046c
    Python version: 3.8.5
    Qt version: 5.12.8
    Coin version: 4.0.0
    OCC version: 7.5.1
    Locale: English/United States (en_US)
    Summary: Export of .obj files inconsistant between Wavefront and Alias Mesh
    Description: Forum thread: https://forum.freecadweb.org/viewtopic.php?f=3&t=57195

    When exporting an assembly:
    Wavefront export appears to ignore the deviation property of a feature. Alias mesh uses the deviation value.
    Wavefront export adds the feature name to the item in the export, exporting multiple items. Alias mesh exports a single monolithic item
    Tags: OBJ
    Steps To Reproduce: Create an assembly (I used A2+)
    set the deviation value on features to differ values.
    Select features export with Wavefront selected.
    Select same features, export with Alias Mesh

    Import each .obj file in Blender.
    Additional Information:
    Attached Files:
    Notes
    (0017019)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6187.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4235 [TechDraw] Feature minor always 2019-12-26 08:06 2021-03-29 17:18
    Reporter: svbol Platform: x86 32-bit  
    Assigned To: OS: Linux Mint  
    Priority: normal OS Version: 18.3  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Linux Mint 18.3 Sylvia (XFCE/xfce)
    Word size of OS: 32-bit
    Word size of FreeCAD: 32-bit
    Version: 0.19.
    Build type: Release
    Python version: 3.5.2
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: Russian/RussianFederation (ru_RU)
    Summary: TechDraw: "Format Spec" field not changed automaticaly
    Description: Problem:
    After change field "Use Global Decimals" or "Alternate Decimals" on TechDraw Setting page number of decimals on existing pages not change.
    Field "Format Spec" not changed after I change Settings.

    Solve:
    Change field "Format Spec" manually or automatic.
    1. For manually mode - need add button "Apply to existing pages" to Setting page (this button have Sketcher's Setting page).
    2. For automatic mode - digit "4" in "%.4f" must be change to needed digit from setting.
    Tags: #post-to-forum
    Steps To Reproduce: 1. Create Page of TechDraw with dimensions,
    2. Change "TechDraw" - "TechDraw Dimensions" ("Use global decimals" or "Alternate Decimals"),
    3. Dimensions of page have old Number of Decimals.
    Additional Information:
    Attached Files: Apply_Scetcher.png (54,132 bytes) 2019-12-26 08:06
    https://tracker.freecad.org/file_download.php?file_id=2417&type=bug
    TD_Setting.png (100,954 bytes) 2019-12-26 08:36
    https://tracker.freecad.org/file_download.php?file_id=2418&type=bug
    Notes
    (0013943)
    openBrain   
    2019-12-26 12:01   
    @svbol : please open a topic thead on our forum (Techdraw subforum) according reporting guidelines (big yellow box). You'll get assistance there. Thx
    (0013951)
    Kunda1   
    2019-12-29 13:34   
    @svbol please post the thread URL back in this ticket so we can track it. Thanks.
    (0013956)
    svbol   
    2019-12-29 14:58   
    (Last edited: 2019-12-29 15:00)
    Thank you.
    I think about this task many time.
    And change description of this problem.
    For best resolve - need change "%.4f" to "%.3f" ("3" from Setting) in field "Format Spec" for every dimensions in present TechDraw pages.

    On forum
    https://forum.freecadweb.org/viewtopic.php?f=35&t=42019

    (0015580)
    Kunda1   
    2021-03-29 17:18   
    Workaround: https://forum.freecadweb.org/viewtopic.php?f=35&t=42019&p=492286#p356585
    (0016852)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6018.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4363 [FreeCAD] Feature feature always 2020-06-06 17:13 2021-03-29 17:15
    Reporter: unalcalde Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: feedback Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Ubuntu 20.04 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16146 (Git) AppImage
    Build type: Release
    Branch: (HEAD detached at 0.18.4)
    Hash: 980bf9060e28555fecd9e3462f68ca74007b70f8
    Python version: 3.6.7
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: Spanish/Spain (es_ES)
    Summary: Frozen views are not stored in the project
    Description: If you save some interested views of your project, are not saved in the project and are lost when close.

    It would be interesting they were saved with the project.

    Tags: #pending-forum
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0014513)
    openBrain   
    2020-06-07 17:34   
    @unalcalde : please address your issue following our reporting guidelines by opening first a topic in our forum. Thx
    We generally accept feature request only when it has been discussed and refined with the community.
    (0015578)
    Kunda1   
    2021-03-29 17:14   
    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=57227
    (0016904)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6071.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3198 [Sketcher] Feature minor N/A 2017-09-27 07:31 2021-03-27 19:48
    Reporter: jrt Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.16  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Displaying name instead of value in Sketcher constraint
    Description: See discussion thread: https://forum.freecadweb.org/viewtopic.php?f=3&t=24611

    The idea is to be able to choose to display name, or other symbol, instead of the value of a constraint in either sketcher, 3D view etc.
    Tags: constraints
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016564)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5729.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4609 [FreeCAD] Bug minor always 2021-03-27 17:37 2021-03-27 17:43
    Reporter: uwestoehr Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Windows 10 Version 2009
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24276 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-19
    Hash: a88db11e0a908f6e38f92bfc5187b13ebe470438
    Python version: 3.8.6+
    Qt version: 5.15.1
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: German/Germany (de_DE)
    Summary: What's this? is broken for the Std and sketcher toolbar icons
    Description: Using the brand new FreeCAD 0.19.1 I notice that the "What's this" feature
    https://wiki.freecadweb.org/Std_WhatsThis
    does not work for the Std toolbar buttons (https://wiki.freecadweb.org/Std_Base)

    But it works fine for e.g. all toolbar buttons of the PartDesign, Part, Mesh, FEM WB.

    It is however also broken for the Sketch WB.

    I tried to fix this according to how bug 0004330 was fixed but failed.

    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=3&t=56891
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0017018)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6186.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4606 [PartDesign] Bug minor always 2021-03-25 06:08 2021-03-27 11:47
    Reporter: jhelmine Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Ubuntu 20.10 (ubuntu:GNOME/ubuntu)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24212 (Git) AppImage
    Build type: Release
    Branch: master
    Hash: 3d227cf7179c00e57f2733f947b4b1b0368d219a
    Python version: 3.8.6
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: Finnish/Finland (fi_FI)
    Summary: Part Design Pad tool do not work in linux AppImage 24212 works in Windows 0.20 24489 (git)
    Description: Hello,

    Example were padding do not work in prebuild 24212 Linux version but works on Windows, compiled from git 24489.
    Test file in http://jhelmine.kapsi.fi/3D/LedKehysVaunuun_test.FCStd (same included to report also).


    Tags: #pending-forum, appimage
    Steps To Reproduce: To repeat error open file LedKehysVaunuun_test.FCStd.
    First use "Part Design" then activate Body001Yläpallo.
    Click Sketch006RuuvinRunko and click Pad this sketch.
    Padding to normal direction do not show anything else than outlines in already made body. Reverse direction padding adds structure.

    Windows version (0.20 from master) works as expected and I can continue. Before error situation parameters in spreadsheet ("data") was changed and paddings and pockets removed. Changing data.PallonD (text "Pallon halkaisija") to small value like 50 or less makes error situation, multiple bodies. This was done before error but correcting to back do not help.
    Additional Information: Padding tested in:
    FreeCAD_0.19-24212-Linux-Conda_glibc2.12-x86_64.AppImage
    FreeCAD_0.19-23578-Linux-Conda_glibc2.12-x86_64.AppImage
    Attached Files: LedKehysVaunuun_test.FCStd (40,482 bytes) 2021-03-25 06:08
    https://tracker.freecad.org/file_download.php?file_id=2658&type=bug
    Notes
    (0015551)
    Kunda1   
    2021-03-27 10:25   
    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=57132
    (0015556)
    Kunda1   
    2021-03-27 11:47   
    Per @looo this looks like a discrepancy between OCCT 7.4.0 and 7.5.0
    (0017016)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6184.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4596 [FreeCAD] Bug minor always 2021-03-14 14:39 2021-03-27 11:27
    Reporter: pilhuhn Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: macOS 10.15
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.20.24434 (Git)
    Build type: Release
    Branch: master
    Hash: 8ec3766b00d672c15ce050d6a29a5d76f5602153
    Python version: 3.9.0
    Qt version: 5.15.2
    Coin version: 4.0.0
    OCC version: 7.5.0
    Locale: German/Germany (de_DE)
    Summary: UserAppData dir on macOS is wrong.
    Description: See https://forum.freecadweb.org/viewtopic.php?f=22&t=7104
    Tags: #pending-PR, macOS
    Steps To Reproduce: See 1st entry in the above forurm thread.
    Additional Information:
    Attached Files:
    Notes
    (0015524)
    Kunda1   
    2021-03-15 21:49   
    (Last edited: 2021-03-27 11:26)
    FreeCAD Pull Request 4620
    (0015525)
    pilhuhn   
    2021-03-16 06:22   
    (Last edited: 2021-03-27 11:27)
    See also https://github.com/FreeCAD/FreeCAD/pull/4623 which is related.
    (0017011)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6179.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4602 [Path] Bug major always 2021-03-23 17:10 2021-03-27 10:20
    Reporter: Colin_W Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Debian GNU/Linux 10 (buster) (KDE//usr/share/xsessions/plasma)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24276 (Git) AppImage
    Build type: Release
    Branch: (HEAD detached at 0.19.1)
    Hash: a88db11e0a908f6e38f92bfc5187b13ebe470438
    Python version: 3.8.8
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: English/United Kingdom (en_GB)
    Summary: Vcarve path cuts air above the part
    Description: https://forum.freecadweb.org/viewtopic.php?f=15&t=56990

    When creating a Vcarve path from a shapestring the generated path is created above the surface,
    bug confirmed with mlampert.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files: vcarve-test.FCStd (104,117 bytes) 2021-03-23 17:10
    https://tracker.freecad.org/file_download.php?file_id=2655&type=bug
    vcarve-test.png (26,429 bytes) 2021-03-23 17:10
    https://tracker.freecad.org/file_download.php?file_id=2656&type=bug
    Notes
    (0015550)
    Kunda1   
    2021-03-27 10:20   
    Confirmed in the forum thread.
    (0017012)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6180.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4608 [Sketcher] Bug minor always 2021-03-26 23:29 2021-03-26 23:29
    Reporter: chrisb Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: macOS 10.16
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24276 (Git)
    Build type: Release
    Branch: (HEAD detached at 0.19.1)
    Hash: a88db11e0a908f6e38f92bfc5187b13ebe470438
    Python version: 3.8.8
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: C/Default (C)
    Summary: Solver doesn't determine state of sketch correctly
    Description: In the example shown in the forum post the solver doesn't detect the state of already fixed lines properly.

    This bug is difficult to reproduce due to the size of the example and should just be tested after other fixes.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0017017)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6185.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4605 [FEM] Bug feature always 2021-03-24 17:17 2021-03-24 17:17
    Reporter: Jee-Bee Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: <!--ATTENTION:
    COMPLETELY ERASE THIS AFTER PASTING YOUR
    Help > About FreeCAD > Copy to clipboard
    NOTE: just the snippet alone will do without anything else included.
    The ticket will not be submitted without it.
    -->
    Summary: FEM ignore Force / Pressure constraints during *FREQUENCY calculation
    Description: During a frequency calculation things like masses, forces etc change the result on *FREQUENCY calculation. But these things are ignored in FreeCAD.
    Tags: calculix, FEM
    Steps To Reproduce:
    1. Create base part (for example beam
    2. Add fixed constraint on end point
    3. add force constraint on other end in direction of the beam
    4. Run writer
    5. check inp file for output. it isn't there
    Additional Information: See: http://feacluster.com/CalculiX/ccx_2.13/doc/ccx/node8.html
    See: https://forum.freecadweb.org/viewtopic.php?f=18&t=20392

    See calculix example: http://feacluster.com/CalculiX/ccx_2.13/doc/ccx/input_deck_viewer.php?input_deck=beamf2.inp
    Attached Files:
    Notes
    (0017015)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6183.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3933 [FEM] Feature feature always 2019-04-13 07:52 2021-03-21 11:18
    Reporter: joha2 Platform:  
    Assigned To: berndhahnebach OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Meshing should be non blocking or at least has a progress bar/log output
    Description: Referring to the forum thread https://forum.freecadweb.org/viewtopic.php?f=18&t=35480

    joha2:

    The meshing with gmsh or netgen or other external meshers is blocking. Is it possible to perform these subprocesses in a non-blocking manner or at least - if this is not possible - with a process indicator and a cancel button?

    bernd:

    very good point. Same on import of large ifc files. For ccx or gmsh it is simple. Since they are external programms, just kill them. This is not smart but works quite well. For netgen some break button would be cool.

    joha2:

    Yes, killing gmsh would be possible. But when I perform the meshing of a complicated part, I never know what gmsh actually does (some logging would be nice) or whether it is frozen. Further meshing of a part is independent from other things you can do in FreeCAD. Therefore it would be nice to execute gmsh independently from the rest of FreeCAD. Some cancel button is possible, but some intermediate feedback is maybe not so trivial.

    bernd:

    In the regard of gmsh you are totally right. I have had a look into this myself some time ago. Feel free to make a bug report and asign it to me. Something in the regard of process logging for gmsh.
    Tags: FEM
    Steps To Reproduce: * Select Part workbench
    * Create part (e.g. Cube)
    * Select FEM workbench
    * Mesh part (GMSH) with MaximumLength 0.001
    * Wait a looooong time
    Additional Information: Not applicable
    Attached Files:
    Notes
    (0013030)
    joha2   
    2019-04-18 21:19   
    I just compiled the gmsh binary with cmake -DENABLE_OPENMP=1 -DENABLE_MPI=1. This improves the speed of the process by using gmsh -nt $(nproc) [I don't know the windows equivalen]. For large meshes, it might be useful to save the mesh to a .med file instead of .unv. What do you think @bernd?
    (0015533)
    Kunda1   
    2021-03-21 11:18   
    CC @berndhahnebach
    (0016748)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5914.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4352 [FreeCAD] Bug minor always 2020-05-29 02:31 2021-03-21 11:17
    Reporter: hobbes1069 Platform: ALL  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: Master as of 2020-05-28
    Summary: CMake Install process needs revamping
    Description: I've posted about this some time ago (i.e. 2011) either to the bug tracker or the forums but that's irrelevant now. It looks like there have been some changes in 0.19 prerelease that seem to move in the right direction but the work is incomplete. My current spec file for Fedora no longer installs files to the correct location and my old method of dumping almost everything into /usr/lib{,64}/freecad no long functions.

    Having a fully compliant FHS install is long overdue and while I can't find the specific messages anymore, it was promised some time ago.

    I am submitting this to the issue tracker in hopes of getting the attention it deserves, and part of that is offering my time to help fix it ONLY if there is sufficient interest from the developers. To be honest, I don't have time for this. I'm working on cutting back on my Fedora packaging duties due to $LIFE and $DAYJOB, but I really don't like the way things are right now and am willing to make the short term sacrifice, but again, only if it is taken seriously.

    1. For the love of god, please use CMake's GNUInstallDirs module. This will take care of all *Nix systems and maybe others.

    2. Unless the libraries produced by FreeCAD are intended for TRULY shared (ie.e. public) consumption, they belong in a private subdir, i.e., /usr/lib{,64}/freecad on RPM (FHS compliant systems), but really all you have to do is append /freecad to CMAKE_INSTALL_LIBDIR if you use GNUInstallDirs, it takes care of the odd Debian tuple location for libraries.

    Certainly the libraries not prefixed with "lib" can't go into /usr/lib{,64}.

    There are 93 instances of CMAKE_INSTALL_LIBDIR being used directly based on current master:

    $ grep -ro CMAKE_INSTALL_LIBDIR | wc -l
    93

    My recommendation would be instead of sed'ing these all to "CMAKE_INSTALL_LINDIR/freecad" is to replace them with "FREECAD_INSTALL_LIBDIR" and default them to the correct location in one of the helper macros.

    3. If you do this, CMake is smart enough to know if the RPATH needs to be set or not, negating the need for all the manual RPAH handling.

    4. All no-arch data does belong in /usr/share, but it ALSO needs to be in a "freecad" subdirectory. Currently if I don't override it a lot of stuff is dumped directly into /usr/share, like some of the Mod python files.

    It can be handled similarly to 0000002. Also, I haven't dug into it enough to know it's not being done correctly but stuff in /usr/share REALLY needs to be noarch. Meaning it's EXACTLY the same if its i686, x86_64, ppc64le, s390x, arm, etc.

    Now that I actually cut out the install portion of the build log and sorted it. It's not quite as bad as I thought, but my premis still stands. I'll attach the install portion so you can see where things are being installed when no override is being specified on the command line.
    Tags: cmake
    Steps To Reproduce:
    Additional Information: Side topic:
    Maybe it matters for other platforms but I don't understand the overriding the output location of binaries and libraries in cMake/FreeCadMacros.cmake. By default they are created in the same directory they are configured in and CMake can track this just fine.
    Attached Files: freecad-install.txt (175,253 bytes) 2020-05-29 02:31
    https://tracker.freecad.org/file_download.php?file_id=2474&type=bug
    FreeCAD_installation_locations.txt (87,345 bytes) 2020-07-01 09:18
    https://tracker.freecad.org/file_download.php?file_id=2502&type=bug
    Notes
    (0014437)
    hobbes1069   
    2020-05-29 13:44   
    Ok, after several build attempts yesterday trying to beat the package back into submission I got more than a little frustrated. With fresh eyes I found GNUInstallDirs buried in "cMake/FreeCAD_Helpers/ConfigureCMakeVariables.cmake".

    It's also in "src/XDGData/CMakeLists.txt" which I would say would be inappropriate to include two different places but my guess this is an attempt to override the PREFIX in the former location:

            set(CMAKE_INSTALL_PREFIX "/usr/lib${LIB_SUFFIX}/freecad" CACHE PATH "Installation root directory")

    I believe this is only necessary because all of the Mod/ installs use the relative install path "Mod/<module>" which will only be installed relative to the PREFIX.

    Also, I misspoke in the original post, noarch data if it's executable code still belongs in /usr/lib, not /usr/share, which IS for noarch data, just not noarch code such as pure python.

    Evaluating the install location portion of

    
    macro(ConfigureCMakeVariables)
        # ================================================================================
        # Output directories for install target
    
        if(WIN32)
            set(CMAKE_INSTALL_PREFIX ${CMAKE_BINARY_DIR}/install CACHE PATH "Installation root directory")
            set(CMAKE_INSTALL_BINDIR bin CACHE PATH "Output directory for executables")
            set(CMAKE_INSTALL_DATADIR data CACHE PATH "Output directory for data and resource files")
            set(CMAKE_INSTALL_INCLUDEDIR include CACHE PATH "Output directory for header files")
            set(CMAKE_INSTALL_DOCDIR doc CACHE PATH "Output directory for documentation and license files")
            # Don't set it without manual adoption of LibDir variable in src/App/FreeCADInit.py
            set(CMAKE_INSTALL_LIBDIR lib CACHE PATH "Output directory for libraries")
        else()
            set(CMAKE_INSTALL_PREFIX "/usr/lib${LIB_SUFFIX}/freecad" CACHE PATH "Installation root directory")
            include(GNUInstallDirs)
        endif()
    

    1. In this case creating all the cache variables for WIN32 is superfluous as GNUInstallDirs would set cache variables to the exact same values in all cases except the _PREFIX which could be easily modified.

    2. Referenced above, the old issue of dumping everything into /usr/lib{,64}. Please correct me if I'm wrong, but again, the only reason I can find for this is all the stuff in src/Mod not using a proper install location ${CMAKE_INSTALL_LIBDIR}.

    By default GNUInstallDirs marks all the variables as advanced but it's trivial to expose the locations that FreeCAD actually uses.
    (0014440)
    hobbes1069   
    2020-05-29 22:31   
    Ok, so even though I wasn't going to do it I did anyway. I have a patch ready for master but I still have a few things to tweak. I've got everything installing correctly except:

    
       Installed (but unpackaged) file(s) found:
       /usr/Ext/PySide/QtCore.py
       /usr/Ext/PySide/QtGui.py
       /usr/Ext/PySide/QtSvg.py
       /usr/Ext/PySide/QtUiTools.py
       /usr/Ext/PySide/__init__.py
       /usr/Ext/freecad/gui/RemoteDebugger.py
       /usr/Ext/freecad/gui/RemoteDebugger.ui
       /usr/Ext/lazy_loader/__init__.py
       /usr/Ext/lazy_loader/lazy_loader.py
       /usr/share/doc/FreeCAD/ThirdPartyLibraries.html
       /usr/share/doc/FreeCAD/freecad.qch
       /usr/share/doc/FreeCAD/freecad.qhc
       /usr/share/icons/hicolor/16x16/apps/freecad.png
       /usr/share/icons/hicolor/32x32/apps/freecad.png
       /usr/share/icons/hicolor/48x48/apps/freecad.png
       /usr/share/icons/hicolor/64x64/apps/freecad.png
       /usr/share/icons/hicolor/scalable/mimetypes/application-x-extension-fcstd.svg
       /usr/share/pixmaps/freecad.xpm
    

    I fixed the icon stuff so it's really just the top stuff.

    1. Why are the translations (I assume that's what the qch and qhc files are) installing to /usr/doc? That doesn't make any sense.

    2. The Ext stuff is still not installing to a freecad subdir even though the helper macro that adds it is added before src/Ext is executed in the main CMakeLists.txt.

    in src/Ext/freecad/CMakeLists.txt, FREECAD_LIBRARY_INSTALL_DIR is set to CMAKE_INSTALL_LIBDIR, which should already be /usr/lib{,64}/freecad but it's not working...
    
    if (WIN32)
            set(FREECAD_LIBRARY_INSTALL_DIR ${CMAKE_INSTALL_BINDIR})
    else()
            set(FREECAD_LIBRARY_INSTALL_DIR ${CMAKE_INSTALL_LIBDIR})
    endif()
    

    Almost there!
    (0014443)
    hobbes1069   
    2020-05-30 13:33   
    Well I mentioned this bug in the pull request but it doesn't look like it's been picked up yet...

    https://github.com/FreeCAD/FreeCAD/pull/3525

    There's still some non-script stuff being installed to /usr/lib{,64}/freecad/Mod I'll work on that when I have a little more time.
    (0014456)
    vocx   
    2020-06-02 16:21   

    Why are the translations (I assume that's what the qch and qhc files are) installing to /usr/doc? That doesn't make any sense.

    hobbes1069

    These files are not translation files, they are compiled HTML files. They comprise the offline documentation that can be opened with FreeCAD, and need Qt assistant to be installed, I think.
    (0014457)
    hobbes1069   
    2020-06-02 16:25   
    (Last edited: 2020-06-03 17:26)
    I figured that out later, I still question if they should get installed into /usr/doc, which is typically for plain text, markdown, rtf, files. Since they are compiled I would consider them to be a Qt resource file and should go somewhere in /usr/share/freecad.
    (0014607)
    PrzemoF   
    2020-07-01 09:18   
    Default file locations on fedora linux.
    (0014608)
    PrzemoF   
    2020-07-01 09:18   
    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=10&t=47159
    (0016900)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6067.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3600 [PartDesign] Feature minor always 2018-09-16 15:41 2021-03-15 21:47
    Reporter: normandc Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Improve PartDesign Transformation features performance
    Description: PartDesign Transformation features (linear/polar pattern, mirrored, MultiTransform) are extremely slow when the number of occurrences is high. Surely there is a way to improve performance, because Draft Array can create multiple occurrences a lot faster.

    Forum topics to be linked later, as I can't find any relevant one at the moment.

    Test file may be added later as well, please attach if you have one.
    Tags:
    Steps To Reproduce:
    Additional Information: 0003527 is a good usecase
    Attached Files:
    Notes
    (0015523)
    Kunda1   
    2021-03-15 21:47   
    @davidosterberg would you be interested in looking at this?
    (0016641)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5806.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3725 [FreeCAD] Bug major always 2018-12-12 09:15 2021-03-13 21:37
    Reporter: mnv Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: feedback Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Changing of the transparency parameter on Radeon GPU
    Description: I got problem with changing transparency parameter with FreeCAD based on Qt5.
    You can see result of the applying transparency value for model on the attachment screenshot.
    This problem was reproduced on AMD Radeon HD7700, AMD Radeon HD6670 and AMD Radeon R9 380.
    Graphic drivers were updated on the last available version.
    Tags: #pending-forum, display
    Steps To Reproduce: 1. Run FreeCAD
    2. Open any model
    3. Select part of model or full model
    4. Change Transparency value
    Additional Information: FreeCAD About Info:
    OS: Windows 10
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.15299 (Git)
    Build type: Release
    Branch: master
    Hash: 5217b245b4f98cf1e3f63ecfe20e379fe4923d80
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    Attached Files: EnginePart.png (124,492 bytes) 2018-12-12 09:15
    https://tracker.freecad.org/file_download.php?file_id=2070&type=bug
    Notes
    (0012266)
    Kunda1   
    2018-12-12 23:48   
    Please post a link to this ticket on the forum to discuss with the community
    (0012270)
    mnv   
    2018-12-14 09:21   
    https://forum.freecadweb.org/viewtopic.php?f=3&t=32787
    (0015510)
    Kunda1   
    2021-03-13 21:36   
    @mnv is this solved in a higher version of Qt5 ?
    (0016680)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5845.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4445 [FreeCAD] Bug crash always 2020-09-26 23:46 2021-03-13 21:29
    Reporter: mrjohnc Platform:  
    Assigned To: Kunda1 OS:  
    Priority: none OS Version:  
    Status: resolved Product Version:  
    Product Build: Resolution: fixed  
    Projection: none      
    ETA: none Fixed in Version: 0.19  
        Target Version: 0.20  
    FreeCAD Information: OS: KDE Flatpak runtime
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.14555 (Git shallow)
    Build type: Release
    Branch: (HEAD detached at 783e134)
    Hash: 783e1346c7a078f5265c3f0c6a927d09a8c1fe70
    Python version: 3.7.4
    Qt version: 5.14.2
    Coin version: 4.0.0
    OCC version: 7.3.0
    Locale: English/United States (en_US)
    Summary: FreeCAD menus and buttons very slow (Linux version) on ChromeOS (GPU Acceleration must be enabled)
    Description: FreeCAD menus and buttons don't work respond very slowly on Linux version run on ChromeOS, this is true for installing through FlatHub, Snapstore and Appimage. Sometimes the menus change when you mouse over them so you can't click on anything, sometimes the blue background turns grey, flashing when the mouse moves. When the app first opens it is possible to select the menu options but they often don't seem to do anything. In an earlier version of Prusa Slicer I had a similiar issue but it seems that it was resolved.
    Tags: ChromeOS
    Steps To Reproduce: Install FreeCAD 0.18 using snap, flathub or appimage
    Open and try to use
    Additional Information:
    Attached Files:
    Notes
    (0014768)
    mrjohnc   
    2020-09-27 08:14   
    Just to add, when I try to use parts of the UI eg creating a new body parts of the UI disappear like the view controls and everything in the application box. Once I've tried to do this often FreeCAD stops responding and once closed when I try to repopen I just get a black screen and have to restart my laptop
    (0014769)
    mrjohnc   
    2020-09-27 09:33   
    OK, it looks like the issue is being caused by GPU acceleration, disabling GPU acceleration for Linux apps means it runs. I'm not sure how to include this as a fix
    (0014770)
    mrjohnc   
    2020-09-27 09:34   
    You can turn off GPU support by disabling chrome://flags/#crostini-gpu-support
    (0014771)
    Kunda1   
    2020-09-27 11:19   
    @mrjohnc, Thanks for the heads up. This is good to know.
    A favor, next time please follow our tracker guidelines (yellow banner, top of page). It helps us with dealing with triage immensely. As you can see we are currently only accepting v0.19 bugs. Is this then something that can be replicated on v0.19?
    Try it quickly via AppImage

    CC @chrisb (we may need to add this to Known Issues thread)
    (0014772)
    mrjohnc   
    2020-09-27 11:48   
    Hi @Kunda1

    Thanks, I can confirm that the issues remain with 0.19 when GPU acceleration enabled although they're not quite as bad its still not usable. Again disabling GPU acceleration is a workaround
    (0014810)
    openBrain   
    2020-10-09 21:27   
    @mrjohnc : could you please paste the full information about the 0.19 version your tried ? Thx
    (0014923)
    Kunda1   
    2020-10-22 11:26   
    @mrjohnc ping
    (0014925)
    Kunda1   
    2020-10-22 11:31   
    Updated ticket to reflect v0.19 only
    (0014926)
    mrjohnc   
    2020-10-22 11:45   
    @openBrain and @Kunda1 thanks, its the latest version available on Flathub as of now. I'm happily using it with GPU acceleration turned off, I'm unsure if its an issue with the OS, Linux support is still in Beta. My suggestion would just be to have some guidance on ChromeOS installation with a little not to say 'if you have issues with the interface turn off GPU acceleration in chrome://flags
    (0014927)
    Kunda1   
    2020-10-22 15:45   
    @mrjohnc where do you propose we should display this note so ChromeOS users see it?
    BTW, the problem goes away with GPU acceleration then? *confused*
    (0014931)
    mrjohnc   
    2020-10-22 16:50   
    (Last edited: 2020-10-22 16:52)
    @Kunda1

    I think that instructions should live here
    https://wiki.freecadweb.org/Install_on_Unix

    And then maybe a small note on this page in the Linux section on the downloads page saying something like 'including Chromebooks with Linux support' https://www.freecadweb.org/downloads.php

    The Chromebook instructions could be something like this, are you able to add it?

    ==Chromebooks with Linux support==
    FreeCAD can be installed on Intel based Chromebooks with Linux support (link https://www.chromium.org/chromium-os/chrome-os-systems-supporting-linux)

    # Enable Linux support (https://support.google.com/chromebook/answer/9145439?hl=en-GB)
    # Enable Flatpak installation using the terminal (https://flatpak.org/setup/Chrome%20OS/)
    # Install FreeCAD via Flathub using the command line instructions (https://flathub.org/apps/details/org.freecadweb.FreeCAD)
    # Find FreeCAD in your Linux Apps folder

    Note: there is an issue with some Chromebooks which causes UI problems in FreeCAD, this can be solved by disabling Linux GPU acceleration in Chrome Flags (chrome://flags/#crostini-gpu-support)

    ----

    There are some other ways to achieve installing it but this is the one with the least steps and most simple for new users.
    (0014932)
    Kunda1   
    2020-10-22 19:27   
    @kkremitzki what do you think? Should we put this on the site and/or the Github release page ?
    (0014937)
    kkremitzki   
    2020-10-22 23:08   
    Sure, if there are platform-specific instructions needed, it seems pretty reasonable to expand the "For distro-specific instructions..." sentence on the downloads page to specifically mention them, as Chromebooks are extensively used in education.
    (0015127)
    Kunda1   
    2020-12-12 12:52   
    @sgrogan please update the 0.19 Release page mentioning Chromebook support. Here's the suggested text (please modify as you see fit)
    
    #### Chromebook
    
    We understand through our forum users that FreeCAD can successfully run on Chromebooks. The only caveat known to us is the need to enable GPU acceleration (Ticket [0004445](https://tracker.freecadweb.org/view.php?id=4445)) within FC. 
    
    (0015209)
    mrjohnc   
    2021-01-15 23:55   
    @Kunda1 sorry to miss this before, I think this is good, please can you add it?
    (0015392)
    Kunda1   
    2021-02-20 18:01   
    pinged @sgrogan via the forum. Hope he gets it this time ;)
    (0015395)
    Kunda1   
    2021-02-20 20:39   
    sgrogan has added a note to the release page. Closing this ticket.
    (0015407)
    mrjohnc   
    2021-02-21 10:50   
    correcting message
    (0015408)
    mrjohnc   
    2021-02-21 10:53   
    (Last edited: 2021-02-21 10:57)
    @Kunda1, I just spotted an error in the message you suggested, it only works if you disable GPU acceleration, not enable it, it should read (adding a few more instructions)

    Chromebook

    We understand through our forum users that FreeCAD can successfully run on Chromebooks which have Linux support https://support.google.com/chromebook/answer/9145439?hl=en-GB The only caveat known to us is the need to disable GPU acceleration via chrome://flags/#crostini-gpu-support The easiest way to install it is to enable Flatpak https://flatpak.org/setup/Chrome%20OS/ and then install using this link https://flathub.org/apps/details/org.freecadweb.FreeCAD
    (0015412)
    Kunda1   
    2021-02-21 11:36   
    (Last edited: 2021-02-21 11:42)
    Sorry, @mrjohnc, lots going on ATM. Thanks for the orientation.

    @sgrogan please copy/paste (again) this corrected version to 0.19_pre Release page

    
    ## Chromebook
    
    We understand through our forum users that FreeCAD can successfully run on Chromebooks which have [Linux support](https://support.google.com/chromebook/answer/9145439?hl=en-GB). The only caveat known to us is the need to disable GPU acceleration via `chrome://flags/#crostini-gpu-support` The easiest way to install it is to enable [Flatpak](https://flatpak.org/setup/Chrome%20OS/) and then install using this [link](https://flathub.org/apps/details/org.freecadweb.FreeCAD)
    
    (0015507)
    Kunda1   
    2021-03-13 21:29   
    Ok, sorry for the delay! Too much going on. I've updated the release page to reflect the correct message.
    https://github.com/FreeCAD/FreeCAD/releases/tag/0.19_pre

    Resolving
    (0016940)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6107.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4589 [FreeCAD] Bug minor always 2021-03-08 02:18 2021-03-13 21:21
    Reporter: edwilliams16 Platform: Mac  
    Assigned To: OS: OSX  
    Priority: normal OS Version: 10.13.6  
    Status: confirmed Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: macOS High Sierra (10.13)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24267 (Git)
    Build type: Release
    Branch: master
    Hash: b2ca86d8d72b636011a73394bf9bcdedb3b109b7
    Python version: 3.8.8
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: C/Default (C)
    Summary: Edit|Placement generates the wrong Center when object is already translated.
    Description:

     Discussed in https://forum.freecadweb.org/viewtopic.php?f=3&t=56393

     
    Tags:
    Steps To Reproduce:   Create a nominal part box.
      In the properties, set position_y to 30 mm
      Open Edit|Placement
      Click on "Center of Mass"
      Choose x-axis
      Try various angles and note that the body translates as well as rotating about an axis through the CG.

     Note that the documentation and user expectation would expect only that the axis of rotation would shift from the box origin to through the CG.
     The problem is that the "Center" should be relative to the box's local origin and should not have the translation added in. In the code, the "position" needs to be subtracted from the CG location so it is relative.

      The same error occurs when using the "selected points" dialog. The point locations need to have the position vector subtracted from them to create the center.

     From https://wiki.freecadweb.org/Placement#Using_.22Center.22_to_Control_Axis_of_Rotation

    "Now consider the case of selecting 2 points. You would select the 2 desired points, and then click the Selected points button. The coordinates of the midpoint between the 2 selected points get placed into the X, Y, and Z spinboxes within the Center section. Now any rotation done on the object will be about this center of rotation."

      except this isn't what happens if the object is already translated...
    Additional Information:
    Attached Files:
    Notes
    (0017004)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6172.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4595 [Arch] Bug minor always 2021-03-13 15:05 2021-03-13 15:05
    Reporter: bitacovir Platform: Windows  
    Assigned To: OS: Windows  
    Priority: normal OS Version: 10  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Windows 10 (10.0)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24267 (Git)
    Build type: Release
    Branch: master
    Hash: b2ca86d8d72b636011a73394bf9bcdedb3b109b7
    Python version: 3.8.8
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: English/United States (en_US)
    Summary: [Arch] Arch External Reference does not load windows nested in walls
    Description: Arch External Reference does not display windows nested in walls, inside an Arch BuildingPart, in FC 0.19
    This is a regression, because the External Reference works normally in FC 0.18.4

    Forum discussions where this bug is reported:
    https://forum.freecadweb.org/viewtopic.php?f=23&t=56467
    https://forum.freecadweb.org/viewtopic.php?f=23&t=56566
    Tags:
    Steps To Reproduce: -Open Arch Module.
    -Create an Arch wall
    -Place an Arch window in the wall
    -Put the wall in an Arch BuildingPart
    -Save the file.
    -Open a new file.
    -Create an Arch Reference object.
    -In the reference panel select the previous file and the Arch BuildingPart object.
    -The reference object only shows in the 3Dwindow the wall with the hole, without the window.
    Additional Information:
    Attached Files: freecad_C3QgU3mwh0.png (80,253 bytes) 2021-03-13 15:05
    https://tracker.freecad.org/file_download.php?file_id=2647&type=bug
    Notes
    (0017010)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6178.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4591 [Sketcher] Bug minor always 2021-03-09 12:28 2021-03-09 12:28
    Reporter: chrisb Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: macOS 10.15
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24267 (Git)
    Build type: Release
    Branch: master
    Hash: b2ca86d8d72b636011a73394bf9bcdedb3b109b7
    Python version: 3.8.8
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: C/Default (C)
    Summary: Solver doesn't report redundancy correctly
    Description: When multiple redundancies exist, the solver reports only partially redundant constraints and not fully redundant ones.
    Forum Discussion
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0017006)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6174.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4590 [Sketcher] Bug minor always 2021-03-09 12:23 2021-03-09 12:23
    Reporter: chrisb Platform:  
    Assigned To: abdullah OS:  
    Priority: low OS Version:  
    Status: assigned Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: macOS 10.15
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24267 (Git)
    Build type: Release
    Branch: master
    Hash: b2ca86d8d72b636011a73394bf9bcdedb3b109b7
    Python version: 3.8.8
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: C/Default (C)
    Summary: Hiding of constraints can be wrong when more than one constraint exists for the same pair of geometric elements.
    Description: When more than one constraint exists for the same pair of geometric elements, then it's only the last one which controls all visibilities in 3D view.
    Forum discussion
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0017005)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6173.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4488 [Arch] Bug minor always 2020-11-10 17:36 2021-03-08 10:01
    Reporter: AndrewA Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Debian GNU/Linux bullseye/sid (XFCE/xfce)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.22960 (Git) AppImage
    Build type: Release
    Branch: master
    Hash: c5a4b01d2e4218bcc0eb6650337650a6c65ef0e4
    Python version: 3.8.6
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: English/United Kingdom (en_GB)
    Summary: Roof Overhang not removed by Arch:Remove Component
    Description: On the Roof:GarageEast the Structure has been removed using the Remove Component, however the overhang has been left.


    https://forum.freecadweb.org/viewtopic.php?f=23&t=52035
    Tags:
    Steps To Reproduce: Draw a polyline and produce a roof.
    Produce a solid that intersects.
    Use Arch:Remove Component to cut the roof.

    The Overhang is left
    Additional Information:
    Attached Files:
    Notes
    (0015494)
    Roy_043   
    2021-03-08 10:01   
    This issue has already been fixed:
    https://github.com/FreeCAD/FreeCAD/pull/4054
    (0016959)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6126.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4587 [FreeCAD] Bug crash sometimes 2021-03-05 08:35 2021-03-07 21:46
    Reporter: PainTER4711 Platform: PC  
    Assigned To: OS: Ubuntu 20.10  
    Priority: normal OS Version: 20.10  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Ubuntu 20.04.2 LTS (MATE/mate)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24267 (Git) AppImage
    Build type: Release
    Branch: master
    Hash: b2ca86d8d72b636011a73394bf9bcdedb3b109b7
    Python version: 3.8.6
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: German/Germany (de_DE)
    Summary: Freecad crashes after starting new File
    Description: When i try to start a new drawing and use the Field "new", Freecad crashes.
    Tags: #pending-forum, 0.19, appimage
    Steps To Reproduce: Start Freecad
    Click "New ..."
    Additional Information: A crash after trying to create a new file:


    $ ./FreeCAD_0.19-24267-Linux-Conda_glibc2.12-x86_64.AppImage 
    FreeCAD 0.19, Libs: 0.19R24267 (Git)
    © Juergen Riegel, Werner Mayer, Yorik van Havre and others 2001-2021
    FreeCAD is free and open-source software licensed under the terms of LGPL2+ license.
    FreeCAD wouldn't be possible without FreeCAD community.
      #####                 ####  ###   ####  
      #                    #      # #   #   # 
      #     ##  #### ####  #     #   #  #   # 
      ####  # # #  # #  #  #     #####  #   # 
      #     #   #### ####  #    #     # #   # 
      #     #   #    #     #    #     # #   #  ##  ##  ##
      #     #   #### ####   ### #     # ####   ##  ##  ##
    
    Program received signal SIGSEGV, Segmentation fault.
    #0  /lib/x86_64-linux-gnu/libc.so.6(+0x46210) [0x7f40025b3210]
    #1  /lib/x86_64-linux-gnu/libdrm_nouveau.so.2(+0x4c0c) [0x7f3ffcc85c0c]
    0000002  /lib/x86_64-linux-gnu/libdrm_nouveau.so.2(+0x5291) [0x7f3ffcc86291]
    0000003  /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so(+0xa7ff43) [0x7f3ff7323f43]
    0000004  /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so(+0xa8003b) [0x7f3ff732403b]
    0000005  /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so(+0x9ca3c8) [0x7f3ff726e3c8]
    0000006  /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so(+0x15bc79) [0x7f3ff69ffc79]
    0000007  0x7f4002fc2a91 in QPlatformBackingStore::composeAndFlush(QWindow*, QRegion const&, QPoint const&, QPlatformTextureList*, bool) from /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/libQt5Gui.so.5+0x46f
    0000008  /tmp/.mount_FreeCAR4zAIv/usr/plugins/platforms/../../lib/libQt5XcbQpa.so.5(+0x54ca4) [0x7f3ffe56dca4]
    0000009  /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/libQt5Widgets.so.5(+0x17ccec) [0x7f40032dccec]
    0000010  /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/libQt5Widgets.so.5(+0x17de6a) [0x7f40032dde6a]
    0000011  /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/libQt5Widgets.so.5(+0x17ed2b) [0x7f40032ded2b]
    0000012  /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/libQt5Widgets.so.5(+0x17efaf) [0x7f40032defaf]
    0000013  0x7f40032efdd4 in QWidgetPrivate::syncBackingStore() from /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/libQt5Widgets.so.5+0x66
    0000014  0x7f40032ffcd9 in QWidget::event(QEvent*) from /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/libQt5Widgets.so.5+0x91f
    0000015  0x7f40033aa34f in QMainWindow::event(QEvent*) from /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/libQt5Widgets.so.5+0xdd
    0000016  0x7f40051cafcc in Gui::MainWindow::event(QEvent*) from /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/libFreeCADGui.so+0x7c
    0000017  0x7f40032d47f2 in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/libQt5Widgets.so.5+0xdc
    0000018  0x7f40032da31d in QApplication::notify(QObject*, QEvent*) from /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/libQt5Widgets.so.5+0x1ac9
    0000019  0x7f4004dbf169 in Gui::GUIApplication::notify(QObject*, QEvent*) from /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/libFreeCADGui.so+0x89
    0000020  0x7f4002aae606 in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/libQt5Core.so.5+0x86
    0000021  /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/libQt5Widgets.so.5(+0x17f695) [0x7f40032df695]
    0000022  /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/libQt5Widgets.so.5(+0x17fd53) [0x7f40032dfd53]
    0000023  0x7f40033013a3 in void QWidgetPrivate::repaint<QRect>(QRect) from /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/libQt5Widgets.so.5+0x7d
    0000024  0x7f40032f3270 in QWidget::repaint() from /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/libQt5Widgets.so.5+0x24
    0000025  0x7f40033d0df3 in QProgressBar::setValue(int) from /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/libQt5Widgets.so.5+0xe5
    0000026  /tmp/.mount_FreeCAR4zAIv/usr/lib/WebGui.so(+0x2639c) [0x7f3f684d839c]
    0000027  0x7f4002ac4a18 in QMetaObject::activate(QObject*, int, int, void**) from /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/libQt5Core.so.5+0x6c0
    0000028  0x7f3fd2ac4cdd in QWebEngineView::loadProgress(int) from /tmp/.mount_FreeCAR4zAIv/usr/plugins/designer/../../lib/libQt5WebEngineWidgets.so.5+0x31
    0000029  0x7f4002ac494d in QMetaObject::activate(QObject*, int, int, void**) from /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/libQt5Core.so.5+0x5f5
    0000030  0x7f3fd2abc181 in QWebEnginePage::loadProgress(int) from /tmp/.mount_FreeCAR4zAIv/usr/plugins/designer/../../lib/libQt5WebEngineWidgets.so.5+0x31
    0000031  /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/libQt5Core.so.5(+0x1ca9ba) [0x7f4002acb9ba]
    0000032  0x7f4002ac3533 in QObject::event(QEvent*) from /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/libQt5Core.so.5+0x5b
    0000033  0x7f40032d47f2 in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/libQt5Widgets.so.5+0xdc
    0000034  0x7f40032da31d in QApplication::notify(QObject*, QEvent*) from /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/libQt5Widgets.so.5+0x1ac9
    0000035  0x7f4004dbf169 in Gui::GUIApplication::notify(QObject*, QEvent*) from /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/libFreeCADGui.so+0x89
    0000036  0x7f4002aae606 in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/libQt5Core.so.5+0x86
    0000037  0x7f4002adc8a4 in QTimerInfoList::activateTimers() from /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/libQt5Core.so.5+0x24c
    0000038  /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/libQt5Core.so.5(+0x1dbf54) [0x7f4002adcf54]
    #39  /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/./libglib-2.0.so.0(g_main_context_dispatch+0x27d) [0x7f3fff9fb98d]
    #40  /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/./libglib-2.0.so.0(+0x54c21) [0x7f3fff9fbc21]
    0000041  /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/./libglib-2.0.so.0(g_main_context_iteration+0x31) [0x7f3fff9fbcc1]
    0000042  0x7f4002add0e8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/libQt5Core.so.5+0x5e
    0000043  0x7f4002aab019 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) from /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/libQt5Core.so.5+0x187
    0000044  0x7f4002aaee8f in QCoreApplication::exec() from /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/libQt5Core.so.5+0xfd
    0000045  0x7f4004d356b1 in Gui::Application::runApplication() from /tmp/.mount_FreeCAR4zAIv/usr/bin/../lib/libFreeCADGui.so+0x1631
    0000046  /tmp/.mount_FreeCAR4zAIv/usr/bin/freecad(+0x37cd) [0x55af7532c7cd]
    0000047  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x7f40025940b3]
    0000048  /tmp/.mount_FreeCAR4zAIv/usr/bin/freecad(+0x4559) [0x55af7532d559]
    
    Attached Files: grafik.png (3,201 bytes) 2021-03-05 08:35
    https://tracker.freecad.org/file_download.php?file_id=2644&type=bug
    Notes
    (0015490)
    chennes   
    2021-03-05 18:20   
    Have you posted about this in the forums? Based on the location of the crash (inside libdrm_noeveau) this has the smell of a graphics card driver problem. What card and driver are you using?
    (0015492)
    PainTER4711   
    2021-03-07 09:12   
    Hi,
    No, i didn't post in the Forum. Somehow i overlooked the first point - sorry.
    I was confused because the 0.18 is working fine.

    Should i do this instead or additional to this issue?

    $ lspci -nnk | grep "VGA\|'Kern'\|3D\|Display" -A2
    08:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1)
        Subsystem: ASUSTeK Computer Inc. GM206 [GeForce GTX 960] [1043:8528]
        Kernel driver in use: nouveau

    Thank you,
    Stephan
    (0015493)
    chennes   
    2021-03-07 17:18   
    It looks like there is at least one other person experiencing this, why don't you add your info to this forum discussion:
    https://forum.freecadweb.org/viewtopic.php?f=4&t=56394

    If we can find out what you have in common that will give devs a chance to debug.
    (0017003)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6171.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3647 [TechDraw] Feature feature N/A 2018-10-22 18:54 2021-03-07 11:20
    Reporter: vocx Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Allow for easy editing of TechDraw elements by double clicking
    Description: To create a View, the user selects a 3D object, and then uses the TechDraw_NewView, or the TechDraw_NewProjGroup. Further options of the View can only be changed from the Property view panel, including the direction of the projection, the scale, and the elements included in the View.

    Currently, to change which elements form part of the View, the user must edit the "Source" property; it opens a dialog with many elements, including "None (Remove link)". This is a tedious way of selecting which elements are part on the View, in particular if the document has hundreds or thousands of different elements to choose from.

    A better way of selecting elements is the way the Arch workbench does it: double clicking the element in the tree view displays a dialog to add or remove elements from the 3D viewport or from the tree view itself.

    Double clicking the View element should probably also allow for changing the direction of projection and the scale.

    This editing by double-clicking can also be used for other TechDraw elements, for example, the Template of the page, the Arch Section View, Dimensions, Hatches, etc. Double clicking the Template should open a dialog to select an SVG template; double clicking the Arch Section View should open a dialog to select an Arch_SectionPlane in the document; double clicking the Dimension should open a dialog to chenge its properties; double clicking a Hatch should open a dialog to select the SVG hatch.

    Some elements can already be edited by double clicking, like the TechDraw_GeomHatch, and the Projection Group.

    Discussion and images https://forum.freecadweb.org/viewtopic.php?f=35&t=31655
    Tags:
    Steps To Reproduce:
    Additional Information: OS: Ubuntu 18.04.1 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.14995 (Git)
    Build type: Release
    Branch: master
    Hash: 7b866816785ac1ca9787b63d4bff12873bb3a593
    Python version: 2.7.15rc1
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    Attached Files:
    Notes
    (0012084)
    vocx   
    2018-10-22 19:03   
    This feature request is also related to issue 3646. The projection direction could be defined by double clicking an already placed View object, and changing the properties in a dialog.
    (0016657)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5822.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3646 [TechDraw] Feature feature N/A 2018-10-21 17:04 2021-03-07 11:20
    Reporter: vocx Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Allow manual entry of the main direction (the front) for a ProjectionGroup
    Description: If a body's face is selected, and the user creates a ProjectionGroup, the projection direction is normal to that face. If no face is selected, the projection uses the 3D camera angle.

    However, Sketches don't have a face so if the user tries to create a projection normal to that Sketch, he has to rely on adjusting the camera first before calling the ProjectionGroup tool.

    An option to manually define the main direction (the front) of the ProjectionGroup could be added, so that selecting a face, or changing the 3D camera is not necessary.

    The feature was first requested in the old TechDraw repository https://github.com/WandererFan/FreeCAD-TechDraw/issues/65

    Now it's in the forum https://forum.freecadweb.org/viewtopic.php?f=35&t=31041
    Tags:
    Steps To Reproduce:
    Additional Information: OS: Ubuntu 18.04.1 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.14995 (Git)
    Build type: Release
    Branch: master
    Hash: 7b866816785ac1ca9787b63d4bff12873bb3a593
    Python version: 2.7.15rc1
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    Attached Files:
    Notes
    (0012544)
    uwestoehr   
    2019-01-28 16:16   
    This issue also popped up in this discussion:
    https://forum.freecadweb.org/viewtopic.php?f=35&t=33776&p=282993#p282993
    (0016656)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5821.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4378 [PartDesign] Bug crash always 2020-06-18 16:09 2021-03-03 11:51
    Reporter: cappu Platform: linux  
    Assigned To: OS: Xubuntu  
    Priority: normal OS Version: 20.04  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Ubuntu 20.04 LTS (XFCE/xubuntu)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.21654 (Git) AppImage
    Build type: Release
    Branch: master
    Hash: ddf0cf3136a6c5a459abae4bf1f9c714f6f45c86
    Python version: 3.8.2
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: English/United States (en_US)
    Summary: Crash after changing a pocket-size
    Description: Crash after changing a size-parameter in a sketch and close sketch (cpu gets 100% load and memory runs full)
    I am not sure if ths issue is found before as I do not know how to name it.
    But on my PC it is very simple to reproduce.
    Tags: #pending-forum, 0.19, crash, Part Design
    Steps To Reproduce: 1) open RegalBuero (copy).FCStd
    2) change WS to part-design
    3) open last sketch043: RegalBuero/P2_KeinteilBoxen../B8_BodenHinten001/Seitenloecher/Sketch043

    4) In this sketch043 change the very right-side hight-parameter from 32,8 to 33mm
    5) close the sketch
    6) look on cpu and RAM. On my PC CPU become 100% load (after aprox 5sec) and RAM starts slowly overflow (approx 30sec left until complete overflow)

    Additional Information: I use appimage file.
    If size of hight-parameter is less than 33 mm, no problems occur. 33mm and bigger seems to be a problem which is not catch in code.
    I created this 3d-model last week and updated appimage-version 1 time. With current version of FreeCad and at least one version before the issue occurs on my PC.
    Hope you can reproduce it on your PC.
    Attached Files: image.png (5,953 bytes) 2020-06-27 11:06
    https://tracker.freecad.org/file_download.php?file_id=2496&type=bug
    Screenshot_2020-06-27_13-20-42.png (19,618 bytes) 2020-06-27 11:22
    https://tracker.freecad.org/file_download.php?file_id=2497&type=bug
    Notes
    (0014588)
    Kunda1   
    2020-06-26 17:09   
    @cappu where is the forum thread (as per our bugtracker guidelines)?
    Please open one next time before opening a ticket. Please open a thread now and link back to this ticket. Also add the forum thread to this ticket so we can track it.
    (0014589)
    Kunda1   
    2020-06-26 17:10   
    Also there is no file (RegalBuero (copy).FCStd) attached to this ticket to test
    (0014596)
    cappu   
    2020-06-27 10:58   
    Hello,
    Thanks for taking care.
    Please find attached file (hope it works now)
    No thread at the moment because in description it is description it is described if clearly a bug, it can be directly added here. But I will create a forum thread...
    I tried today with latest version, and crash still happens on my PC

    OS: Ubuntu 20.04 LTS (XFCE/xubuntu)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.21764 (Git) AppImage
    Build type: Release
    Branch: master
    Hash: ccea55a65512d37081d708d6f504d0c4d182a9e0
    Python version: 3.8.2
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: English/United States (en_US)

    Best regars
    (0014597)
    cappu   
    2020-06-27 11:06   
    Hm, looks like I do something wrong at adding the file. Filesize 1,6MB. No error. Green bar under file.

    But when I go over the attached file is says:
    html> <head><title>413 Request Entity Too Large</title></head> <body bgcolor="white"> <center><h1>413 Request Entity Too Large</h1>
    (0014598)
    cappu   
    2020-06-27 11:07   
    I already removed most parts of the model. Is there a different way to add the file?
    (0014599)
    cappu   
    2020-06-27 11:22   
    Tried to create a forum thread. But here an error comes when trying to add the file.
    (see screenshot)
    But without file, it does not make sense to talk about (Description: On Increasing a pocket size, computer crashes??? ).
    Is there a possibility to send you the model?
    (0014600)
    cappu   
    2020-06-27 12:50   
    Datei siehe

    https://www.magentacloud.de/lnk/ahAhDTWN
    (0014601)
    cappu   
    2020-06-27 13:21   
    Forum Link: https://forum.freecadweb.org/viewtopic.php?f=19&t=48101
    (hope it is the correct forum. I have not found one to verify bugs)
    (0014614)
    Kunda1   
    2020-07-02 18:07   
    Related partial fix: FreeCAD master 31b1ad87
    (0015478)
    Kunda1   
    2021-03-03 11:51   
    Trying to add attachment
    (0016910)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6077.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    495 [FreeCAD] Bug feature always 2011-11-27 05:56 2021-03-02 23:17
    Reporter: normandc Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Inconsistent translations for workbench names
    Description: Currently in latest FreeCAD source, translation for workbench names is inconsistent:

    - Some workbenches toolbar names are translated (in View --> Toolbars menu)
    - Some workbench specific menu names are translated, some aren't. For example, when the workbench selector is set to a specific workbench, the workbench menu name is not translated. The Raytracing menu name is in English (but its contents are translated). But if in complete workbench mode, then most of the workbench menus are translated.
    - In the workbench selector, the workbench names are not translated.

    This should require some consideration.

    I realize that translating the workbench names is a delicate matter as it could complicate communication on the forums with users of other languages. But I believe that a wholly translated interface is preferable, as some English names don't have signification to users of other languages. (For example: the distinction between Draft and Drawing can be lost on French users)
    Tags: locale, translation
    Steps To Reproduce:
    Additional Information: I'll try to post screenshots shortly.
    Attached Files: FC_complete.png (46,473 bytes) 2011-11-29 02:06
    https://tracker.freecad.org/file_download.php?file_id=145&type=bug
    FC_draft_workbench.png (45,620 bytes) 2011-11-29 02:07
    https://tracker.freecad.org/file_download.php?file_id=146&type=bug
    FC_Draft_toolbar.png (85,111 bytes) 2011-11-29 02:07
    https://tracker.freecad.org/file_download.php?file_id=147&type=bug
    Notes
    (0001357)
    Jriegel   
    2011-11-27 18:00   
    We have different levels of translations. Thats IMO not a bug.
    Besides there is a string not showing up on crowdin, that would be a bug!

    Otherwise its a encouragement for the translaters and I will close this "bug" ;)
    (0001362)
    normandc   
    2011-11-27 18:16   
    Please explain what you mean by different levels of translation.

    Right now, I have workbench menu names showing either in French or in English depending on if I've set the complete workbench, or if the workbench selector is set to a specific workbench. Then the workbench selector itself is not translated. How is that no a bug? And why isn't a single string used for the 3 use cases?
    (0001364)
    yorik   
    2011-11-27 19:12   
    I think workbench names are specified in their InitGui file, which is why they are not taken into account by the translation system. Since workbenches are activated/deactivated by name internally, changing this will require serious changes in the code. Sincerely I'm not sure it's worth the work...

    Their contents (toolbars, menu entries, etc) on the other hand, is taken into account by translation mechanisms and should be 100% translated. If something is missing (provided all crowdin strings are translated of course), indeed it is a bug (probably some string internally which isn't using a translation function). I suggest you make a list here with what you see that isn't translated, we'll need to go one by one...

    But I'm not sure it's a showstopper for 0.12... There will probably be more than a couple, and at this rate that release will never be out ;) My opinion is more to see translations as a work in progress, and refine progressively...
    (0001365)
    normandc   
    2011-11-27 19:43   
    What I want to make sure of is to get a sense of the direction we go. If we decide that workbench names should not (or cannot) be translated, then I will have to revert all the translations where I have translated them. And that includes the Wiki documentation...

    So that to prevent inconsistencies in v0.12...
    (0001373)
    normandc   
    2011-11-29 02:21   
    I finally made screen captures.

    I used the Draft module as an example.

    First one shows the Complete workbench with all the workbench menus translated. Draft menu here is called "Planche à dessin".

    Second one shows the Draft workbench interface. Both the Draft menu and the workbench selector show "Draft" instead of "Planche à dessin". This is an inconsistency in my opinion.

    The third one shows that the Draft toolbar name is indeed translated. At this point I didn't know what to do anymore so I named it "Outils Draft" for the time being.

    I'd rather have the name "Planche à dessin" put everywhere but I can understand if this can't be done in v0.12. But I would like to know if it'll be possible later though. As I said otherwise I'll have to change the wiki French translation accordingly.

    So, should this be considered a bug? feature request?

    P.S. Yorik, since it's your module you may also not like the chosen name? It was first named that way by mrchep and I thought it fitting, and easy to visualize its purpose by French users.
    (0001375)
    yorik   
    2011-11-29 12:08   
    Normally in latest revision all appearences of "Draft" in menus can be translated. Check if the crowdin stuff is OK, then I'll add them again to the sources. For the other workbenches we need to see which ones don't translate correctly.

    For me the name is fine, being Draft or Planche à dessin...

    But one thing I'll not be able to change is how the workbench names appear in the workbenches dropdown box. If this will be possible in the future or not is more up to Jürgen or Werner, and it would probably require some heavy changes to the source code...
    (0002728)
    Jriegel   
    2012-12-20 22:15   
    I will move the Workbench selector to a menu structure for the most common
    workbenches. So we have a translation and more information...
    (0005734)
    yorik   
    2015-01-25 16:09   
    There are still inconsistencies in translations ("Draft" is not translated equally on crowdin (sometimes "Planche à dessin", sometimes "Ébauche" , sometimes "Draft"), same problem in other languages too...

    But outside that problem all python-generated menus appear now to be correctly translated.

    The only thing missing is to translate the WB selector itself. I believe this is possible (in Gui/Actions.cpp, class WorkbenchComboBox), it looks like the individual actions that compose the selector are always get/set by their objectName, so there would be no problem in setting their displayed text to something else, but I'm not too sure where to get the translations...
    (0009205)
    Kunda1   
    2017-05-30 23:48   
    @yorik is this still the case?
    (0009206)
    Kunda1   
    2017-05-30 23:49   
    @normandc can you recheck this please when you have a moment?
    (0009225)
    yorik   
    2017-05-31 16:38   
    Yes it is still the case, workbench names are not trasnlated in the workbench selector. I think there was a discussion about that on the forum in the past...
    (0009327)
    Kunda1   
    2017-06-10 04:53   
    @yorik I searched the forum but no joy. Do you mind trying to find this thread and associating it to this ticket?
    (0009356)
    yorik   
    2017-06-13 17:24   
    Cannot find it back... I guess it was spread over several discussions...
    (0009359)
    Kunda1   
    2017-06-13 21:49   
    @yorik do you think this should make it in to 0.17?
    (0009360)
    yorik   
    2017-06-14 01:21   
    I don't know how to handle this, so I couldn't say...
    (0009366)
    Kunda1   
    2017-06-14 12:44   
    Opened new forum thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=22936&p=178016
    (0011420)
    Kunda1   
    2018-06-13 13:25   
    Unassigning Jriegel
    (0015474)
    MaurinoWeb   
    2021-03-02 22:13   
    (Last edited: 2021-03-02 22:15)
    Hello everybody
    I allowed myself to comment here thanks to the invitation of @Kunda1 in this post https://forum.freecadweb.org/viewtopic.php?f=8&t=56067
    I am a simple FreeCAD user and my comment is of the same level, this message is only the my modest opinion...

    I believe that in FreeCAD the names of the WB must remain in English which is the main language chosen, this avoids confusion and does not disperse users that follow tutorials in other languages​​... for example blender has did an "extreme" choice to use only english, but it worked!
    The choice in FreeCAD to translate all languages ​​has more style, but if we also translate the names of the WB, in my opinion, we lose the benefits and increase the work of the translators without obtaining any advantages in return (I translated very little and I don't write as a translator, it's just my thought).

    What are the benefits of translating WB names? Personally I see few and of minimal importance, but I also see some disadvantages...

    --> Bi-lingual users will not be so quick in change WB when they switch languages ​​in FreeCAD, and this will annoy at the beginning and even after.
    --> Beginner mono-language users following a tutorial of another language will have more difficulty of the normal.
    --> Wiki SEO optimization can be less targeted and less efficient (to check, maybe just more SEO work to avoid it?)
    --> The results of the search engines will be dispersed in the translations of the WB names, with the risk that the user, in addition to translating the "search phrase", must also remember to translate the most important word, the "WB name" this does not help. (to check, maybe just more SEO work to avoid it?) same thing if a user wants to ask for help in the English forum.
    --> All written or recorded tutorials to date will be out of date.
    --> All the linguistic habits achieved up to now regarding WB will be lost, for which PRO?

    I realize that they are "small" disadvantages, but they increase "confusion"... Even today several FreeCAD users complain about the confusion, some love FreeCAD, but they say it anyway... so we should avoid adding more, even if minimal.

    I agree that this "confusion" often does not exist, and it is only the user who remains attached to the old experiences, or maybe is only used to the "ready meals" of commercial software, but nothing can be done about this.

    I can change my mind about anything I've written if it's wrong, I hate beliefs and love the benefit of the doubt, so if something escapes me I'll be happy to understand it, thank you.

    I apologize for the bad English, written with the help of google translated.
    A greeting and thanks for all the work done to date, you are great!
    (0015475)
    MaurinoWeb   
    2021-03-02 23:17   
    An example that concerns only the SEO with the changes of WB names.
    Recently the name of the part design workbench has been translated into Italian in "ambiente disegnopezzo"

    I find it smart to translate "workbench" but the rest(wb names) should be a fixed word, so the user has the help of the translated "workbench" to understand choise what is, but the WB names is part of the FreeCAD fixed terminology and will soon learn.

    Now looking at html of the view-source:https://wiki.freecadweb.org/PartDesign_Workbench/it
    you can see that in the <title> tag there is no term as in the url, this is not recommended.
    it is also not recommended to change the <title> since it is an official documentation, now if we write in google "ambiente part design" in the "search result" still has the "old" title (ambiente part design) while duckduckgo has already been updated (ambiente disegnopezzo), soon google will update too.
    We are not helping the search engines, so one day it could better position a site with a seo-friendly html and find the official documentation under the results, in English no, but in other languages ​​it could happen and these changes do not help.

    So imagining all the WB names translated, I confirm my concern that in all languages ​​other than English there will be scattered rankings with different "key phrases" in search engines... this won't help over time.

    a greeting
    (0016383)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5548.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4584 [Path] Bug minor sometimes 2021-03-01 20:35 2021-03-01 20:35
    Reporter: mlampert Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: see forum
    Summary: Path Tag dressup can store a float but expect a Quantity later on
    Description: see forum discussion.
    Tags:
    Steps To Reproduce: https://forum.freecadweb.org/viewtopic.php?f=15&t=56156
    Additional Information: n/a
    Attached Files:
    Notes
    (0017002)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6170.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4580 [Sketcher] Bug minor always 2021-02-28 15:37 2021-02-28 15:37
    Reporter: garya Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: FreeBSD 11.4-RELEASE-p6 (XFCE/xfce)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.b2ca86d8d
    Build type: Release
    Python version: 3.7.9
    Qt version: 5.15.2
    Coin version: 4.0.0
    OCC version: 7.5.0
    Locale: C/Default (C)
    Summary: Sketcher does not report error
    Description: See discussion on
    help forum
    In the development version of the code at which this is being reported, this bug *does actually report the error*, but that is only because of extra code @chrisb pushed a workaround for another issue which will not be fixed in 0.19. When that bug is fixed, this bug will reappear.
    So this bug is being reported to not lose the issue.
    Tags:
    Steps To Reproduce: - load the file Bug_Sketcher_NotRedundant_2_5_simplified.FCStd
    - edit sketch Sk_Diamond
    - set length of Edge2 to 0.4mm
    -> The diamond shape collapses on itself, the top two legs folding down onto the bottom
       This is a violation of the L2_nrm_L3 constraint
    -> solver reports 1 DOF
    -> Report View shows
      Updating geometry: Error build geometry(2): Both points are equal
      Invalid solution from SQP(augmented system) solver
    - close sketcher
    -> an error is reported for the sketch.
    Additional Information: from @chrisb:
    2) The not reporting the situation directly. With the latest master the error is reported directly as conflicting (one case appearing to defy the principle of causality in which the fix preceeds the bug report, though it is not really the case). This was "fixed" because a couple of days ago I pushed a "work-around" for another issue. The workaround includes executing an extra solve that should not be necessary, but it is because of a bug that will not be fixed in 0.19. The extra solve coincidentally also "fixes" the reporting. However, when this workaround is reverted because a proper solution is found for the bug in 0.20, this bug will appear again. So here it might makes sense to have a separate ticket for the reporting, not to lose the information on how to reproduce it.
    Attached Files:
    Notes
    (0017001)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6169.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4579 [Sketcher] Bug minor always 2021-02-28 15:21 2021-02-28 15:21
    Reporter: garya Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: FreeBSD 11.4-RELEASE-p6 (XFCE/xfce)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.b2ca86d8d
    Build type: Release
    Python version: 3.7.9
    Qt version: 5.15.2
    Coin version: 4.0.0
    OCC version: 7.5.0
    Locale: C/Default (C)
    Summary: Sketch (diamond shape) collapses on itself and ignores some constraints
    Description: Forum discussion:
      https://forum.freecadweb.org/viewtopic.php?f=3&t=56029&sid=cae9731349d24c2a6929a890bf2208b6
    Tags: sketcher, Solver
    Steps To Reproduce: - load the file Bug_Sketcher_NotRedundant_2_5_simplified.FCStd
    - edit sketch Sk_Diamond
    - set length of Edge2 to 0.4mm
    -> The diamond shape collapses on itself, the top two legs folding down onto the bottom
       This is a violation of the L2_nrm_L3 constraint
    -> solver reports 1 DOF
    -> Report View shows
      Updating geometry: Error build geometry(2): Both points are equal
      Invalid solution from SQP(augmented system) solver
    - close sketcher
    -> an error is reported for the sketch.
    Additional Information:
    Attached Files: Bug_Sketcher_NotRedundant_2_5_simplified.FCStd (4,108 bytes) 2021-02-28 15:21
    https://tracker.freecad.org/file_download.php?file_id=2639&type=bug
    Notes
    (0017000)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6168.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4577 [FreeCAD] Bug minor have not tried 2021-02-27 15:20 2021-02-27 15:20
    Reporter: StefanBruens Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: openSUSE Tumbleweed (KDE//usr/share/xsessions/plasma5)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.Unknown
    Build type: Release
    Python version: 3.8.7
    Qt version: 5.15.2
    Coin version: 3.1.3
    OCC version: 7.5.1
    Locale: English/United States (en_US)
    Summary: Use normalized signatures in QObject::connect when new-style is not possible
    Description: QObject::connect uses normalized signatures when connecting signals to get rid of ambiguities.

    Using non-normalized signatures has a runtime overhead (at connect time, not signal emission).

    In general, new-style (functor) connects should be preferred, but there may be cases when late binding is preferred (i.e. when the exact type of the target QObject is not known at compile time).
    Tags:
    Steps To Reproduce:
    Additional Information: https://marcmutz.wordpress.com/effective-qt/prefer-to-use-normalised-signalslot-signatures/
    Attached Files:
    Notes
    (0016999)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6167.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4575 [Arch] Bug minor random 2021-02-25 15:30 2021-02-26 12:12
    Reporter: AndrewA Platform:  
    Assigned To: yorik OS:  
    Priority: low OS Version:  
    Status: confirmed Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Debian GNU/Linux bullseye/sid (XFCE/xfce)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24212 (Git) AppImage
    Build type: Release
    Branch: master
    Hash: 3d227cf7179c00e57f2733f947b4b1b0368d219a
    Python version: 3.8.6
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: English/United Kingdom (en_GB)
    Summary: Window from sketch produces incorrect hole
    Description:

    When putting a window in a roof, the hole often works, but at times it produces the wrong hole.

    https://forum.freecadweb.org/viewtopic.php?f=23&t=56018&p=481865#p481865
    Tags:
    Steps To Reproduce: To create the window I had a standard window in first, then changed the sketch to a custom one.
    Often this works fine, as the example attached did until I made it higher,then all changes to the image seem to not do anything. I cannot reliably reproduce the behaviour, although it has happened before.

    Additional Information: This is a minor bug as there is a work around, see the forum post above
    Attached Files: Greenhouse_BugReport.FCStd (241,060 bytes) 2021-02-25 15:30
    https://tracker.freecad.org/file_download.php?file_id=2638&type=bug
    Notes
    (0015440)
    Kunda1   
    2021-02-26 12:12   
    Assigning to yorik
    (0016997)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6165.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3922 [FreeCAD] Bug major always 2019-03-29 16:19 2021-02-23 18:59
    Reporter: ArnoVersfeld Platform: Intel® Core™ i7-3770 CPU @ 3.40G  
    Assigned To: OS: Ubuntu  
    Priority: urgent OS Version: 18.04.2  
    Status: feedback Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Preferences, General, Units, user system MKS(m/kg/s/degree) displaying dimensions as millimetres and not metres
    Description: I installed FreeCAD and set the Preferences as shown in the summary.
    When I go to Arch, Draft or Drawing workbench and draw a simple image like a square then use the dimension tool I get a display in millimetres and not metres. I closed FreeCAD.
    I deleted the file in the .FreeCAD folder namely user.cfg and cookies and opened FreeCAD again and got the same results.
    I uninstalled FreeCAD from the system and reinstalled it after again deleting the files in the FreeCAD folder and got the same results, namely, "display in millimetres and not metres".
    When I go to the combo view of a rectangle that I've drawn the Height is 8,00 mm and the Length 12,00 mm these dimensions should be 0,80 m and 1,20 m.
    Tags: units
    Steps To Reproduce: When I go to Arch, Draft or Drawing workbench and draw a simple image like a square then use the dimension tool I get a display in millimetres and not metres. I closed FreeCAD.
    I deleted the file in the .FreeCAD folder namely user.cfg and cookies and opened FreeCAD again and got the same results.
    I uninstalled FreeCAD from the system and reinstalled it after again deleting the files in the FreeCAD folder and got the same results, namely, "display in millimetres and not metres".
    When I go to the combo view of a rectangle that I've drawn the Height is 8,00 mm and the Length 12,00 mm these dimensions should be 0,80 m and 1,20 m.
    Additional Information: Contents of the user.cfg file:
    
    <?xml version="1.0" encoding="UTF-8" standalone="no" ?>
    <FCParameters>
    
      <FCParamGroup Name="Root">
        <FCParamGroup Name="BaseApp">
          <FCParamGroup Name="LogLevels">
            <FCInt Name="Default" Value="2"/>
          </FCParamGroup>
          <FCParamGroup Name="Preferences">
            <FCParamGroup Name="General">
              <FCText Name="FileOpenSavePath">/home/arno</FCText>
              <FCText Name="AutoloadModule">StartWorkbench</FCText>
              <FCBool Name="ShowSplasher" Value="1"/>
              <FCBool Name="PythonWordWrap" Value="1"/>
              <FCInt Name="ToolbarIconSize" Value="24"/>
            </FCParamGroup>
            <FCParamGroup Name="Units">
              <FCInt Name="UserSchema" Value="1"/>
              <FCInt Name="Decimals" Value="2"/>
              <FCInt Name="FracInch" Value="8"/>
            </FCParamGroup>
            <FCParamGroup Name="Macro">
              <FCBool Name="LocalEnvironment" Value="1"/>
              <FCText Name="MacroPath">/home/arno/.FreeCAD/Macro</FCText>
              <FCBool Name="RecordGui" Value="1"/>
              <FCBool Name="GuiAsComment" Value="1"/>
              <FCBool Name="ScriptToPyConsole" Value="1"/>
              <FCBool Name="ScriptToFile" Value="0"/>
              <FCText Name="ScriptFile">FullScript.FCScript</FCText>
            </FCParamGroup>
            <FCParamGroup Name="Mod">
              <FCParamGroup Name="OpenSCAD"/>
              <FCParamGroup Name="Import">
                <FCParamGroup Name="hSTEP">
                  <FCBool Name="ReadShapeCompoundMode" Value="1"/>
                </FCParamGroup>
              </FCParamGroup>
              <FCParamGroup Name="Start">
                <FCText Name="AutoloadModule">StartWorkbench</FCText>
                <FCUInt Name="BackgroundColor1" Value="1331197183"/>
                <FCUInt Name="BackgroundTextColor" Value="4294703103"/>
                <FCUInt Name="PageColor" Value="4294967295"/>
                <FCUInt Name="PageTextColor" Value="255"/>
                <FCUInt Name="BoxColor" Value="3722305023"/>
                <FCUInt Name="LinkColor" Value="65535"/>
                <FCUInt Name="BackgroundColor2" Value="2141107711"/>
                <FCText Name="Template"></FCText>
                <FCText Name="BackgroundImage"></FCText>
                <FCText Name="ShowCustomFolder"></FCText>
                <FCBool Name="InWeb" Value="0"/>
                <FCBool Name="InBrowser" Value="1"/>
                <FCBool Name="ShowNotes" Value="0"/>
                <FCBool Name="ShowExamples" Value="1"/>
                <FCBool Name="closeStart" Value="0"/>
                <FCBool Name="DoNotShowOnOpen" Value="0"/>
                <FCBool Name="ShowForum" Value="0"/>
                <FCBool Name="UseStyleSheet" Value="0"/>
                <FCBool Name="NewFileGradient" Value="0"/>
                <FCText Name="FontFamily"></FCText>
                <FCInt Name="FontSize" Value="13"/>
              </FCParamGroup>
              <FCParamGroup Name="Draft">
                <FCFloat Name="dxfScaling" Value="1.000000000000"/>
                <FCFloat Name="maxsegmentlength" Value="5.000000000000"/>
                <FCBool Name="dxfShowDialog" Value="0"/>
                <FCBool Name="dxfUseLegacyImporter" Value="0"/>
                <FCBool Name="dxfAllowDownload" Value="0"/>
                <FCBool Name="dxftext" Value="0"/>
                <FCBool Name="dxfImportPoints" Value="0"/>
                <FCBool Name="dxflayout" Value="0"/>
                <FCBool Name="dxfstarblocks" Value="0"/>
                <FCBool Name="dxfGetOriginalColors" Value="0"/>
                <FCBool Name="joingeometry" Value="0"/>
                <FCBool Name="groupLayers" Value="0"/>
                <FCBool Name="dxfStdSize" Value="0"/>
                <FCBool Name="dxfUseDraftVisGroups" Value="0"/>
                <FCBool Name="importDxfHatches" Value="0"/>
                <FCBool Name="renderPolylineWidth" Value="0"/>
                <FCBool Name="DiscretizeEllipses" Value="1"/>
                <FCBool Name="dxfmesh" Value="0"/>
                <FCBool Name="dxfExportBlocks" Value="1"/>
                <FCBool Name="dxfproject" Value="0"/>
                <FCBool Name="dxfCreatePart" Value="1"/>
                <FCBool Name="dxfCreateDraft" Value="0"/>
                <FCBool Name="dxfCreateSketch" Value="0"/>
                <FCText Name="TeighaFileConverter"></FCText>
                <FCFloat Name="svgDiscretization" Value="0.000000000000"/>
                <FCInt Name="svgstyle" Value="0"/>
                <FCInt Name="svg_export_style" Value="0"/>
                <FCBool Name="svgDisableUnitScaling" Value="0"/>
                <FCBool Name="SvgLinesBlack" Value="1"/>
                <FCBool Name="ocaareas" Value="0"/>
                <FCText Name="snapModes">111111111101111</FCText>
                <FCInt Name="precision" Value="6"/>
                <FCFloat Name="tolerance" Value="0.050000000000"/>
                <FCText Name="ClonePrefix"></FCText>
                <FCText Name="constructiongroupname">Construction</FCText>
                <FCInt Name="UiMode" Value="1"/>
                <FCInt Name="defaultWP" Value="0"/>
                <FCBool Name="Verbose" Value="1"/>
                <FCBool Name="copymode" Value="1"/>
                <FCBool Name="selectBaseObjects" Value="0"/>
                <FCBool Name="UsePartPrimitives" Value="0"/>
                <FCBool Name="fillmode" Value="1"/>
                <FCBool Name="focusOnLength" Value="0"/>
                <FCUInt Name="constructioncolor" Value="746455039"/>
                <FCInt Name="gridEvery" Value="10"/>
                <FCInt Name="gridSize" Value="100"/>
                <FCFloat Name="gridSpacing" Value="1.000000000000"/>
                <FCInt Name="modsnap" Value="1"/>
                <FCInt Name="modalt" Value="2"/>
                <FCInt Name="modconstrain" Value="0"/>
                <FCBool Name="showSnapBar" Value="1"/>
                <FCBool Name="hideSnapBar" Value="0"/>
                <FCBool Name="alwaysSnap" Value="1"/>
                <FCBool Name="grid" Value="1"/>
                <FCBool Name="alwaysShowGrid" Value="1"/>
                <FCInt Name="linewidth" Value="2"/>
                <FCInt Name="HatchPatternResolution" Value="128"/>
                <FCText Name="svgDashedLine">0.09,0.05</FCText>
                <FCText Name="svgDashdotLine">0.09,0.05,0.02,0.05</FCText>
                <FCText Name="svgDottedLine">0.02,0.02</FCText>
                <FCText Name="template"></FCText>
                <FCText Name="patternFile"></FCText>
                <FCInt Name="snapStyle" Value="0"/>
                <FCBool Name="saveonexit" Value="0"/>
                <FCBool Name="showPlaneTracker" Value="0"/>
                <FCBool Name="preserveFaceColor" Value="0"/>
                <FCBool Name="preserveFaceNames" Value="0"/>
                <FCUInt Name="color" Value="255"/>
                <FCUInt Name="snapcolor" Value="4294967295"/>
                <FCInt Name="dimPrecision" Value="2"/>
                <FCFloat Name="textheight" Value="0.200000000000"/>
                <FCFloat Name="extlines" Value="0.300000000000"/>
                <FCFloat Name="extovershoot" Value="0.000000000000"/>
                <FCFloat Name="dimovershoot" Value="0.000000000000"/>
                <FCFloat Name="arrowsize" Value="0.100000000000"/>
                <FCFloat Name="dimspacing" Value="0.050000000000"/>
                <FCText Name="textfont"></FCText>
                <FCText Name="FontFile"></FCText>
                <FCInt Name="dimstyle" Value="0"/>
                <FCInt Name="dimsymbol" Value="0"/>
                <FCInt Name="dimorientation" Value="0"/>
                <FCBool Name="showUnit" Value="1"/>
              </FCParamGroup>
              <FCParamGroup Name="Arch">
                <FCText Name="ifcRootElement">IfcProduct</FCText>
                <FCText Name="ifcSkip"></FCText>
                <FCInt Name="ifcImportModeArch" Value="0"/>
                <FCInt Name="ifcImportModeStruct" Value="0"/>
                <FCBool Name="ifcShowDialog" Value="0"/>
                <FCBool Name="ifcDebug" Value="0"/>
                <FCBool Name="ifcCreateClones" Value="1"/>
                <FCBool Name="ifcSeparateOpenings" Value="0"/>
                <FCBool Name="ifcGetExtrusions" Value="0"/>
                <FCBool Name="ifcSplitLayers" Value="0"/>
                <FCBool Name="ifcPrefixNumbers" Value="0"/>
                <FCBool Name="ifcMergeMaterials" Value="0"/>
                <FCBool Name="ifcImportProperties" Value="0"/>
                <FCBool Name="ifcFitViewOnImport" Value="0"/>
                <FCBool Name="ifcExportAsBrep" Value="0"/>
                <FCBool Name="ifcUseDaeOptions" Value="0"/>
                <FCBool Name="ifcJoinCoplanarFacets" Value="0"/>
                <FCBool Name="ifcStoreUid" Value="1"/>
                <FCBool Name="ifcSerialize" Value="0"/>
                <FCBool Name="ifcExport2D" Value="1"/>
                <FCBool Name="IfcExportFreeCADProperties" Value="0"/>
                <FCBool Name="ifcCompress" Value="1"/>
                <FCBool Name="DisableIfcRectangleProfileDef" Value="0"/>
                <FCInt Name="ColladaSegsPerEdge" Value="1"/>
                <FCInt Name="ColladaSegsPerRadius" Value="2"/>
                <FCFloat Name="ColladaScalingFactor" Value="1.000000000000"/>
                <FCFloat Name="ColladaTessellation" Value="1.000000000000"/>
                <FCFloat Name="ColladaGrading" Value="0.300000000000"/>
                <FCInt Name="ColladaMesher" Value="0"/>
                <FCBool Name="ColladaSecondOrder" Value="0"/>
                <FCBool Name="ColladaOptimize" Value="1"/>
                <FCBool Name="ColladaAllowQuads" Value="0"/>
                <FCInt Name="MaxComputeAreas" Value="20"/>
                <FCInt Name="ReferenceCheckInterval" Value="60"/>
                <FCFloat Name="ConversionTolerance" Value="0.001000000000"/>
                <FCFloat Name="CutLineThickness" Value="2.000000000000"/>
                <FCFloat Name="SymbolLineThickness" Value="0.600000000000"/>
                <FCFloat Name="patternScale" Value="0.010000000000"/>
                <FCText Name="archHiddenPattern">30, 10</FCText>
                <FCText Name="BimServerUrl">http://localhost:8082</FCText>
                <FCBool Name="autoJoinWalls" Value="1"/>
                <FCBool Name="joinWallSketches" Value="0"/>
                <FCBool Name="archRemoveExternal" Value="0"/>
                <FCBool Name="applyconstructionStyle" Value="0"/>
                <FCBool Name="MoveWithHost" Value="0"/>
                <FCBool Name="ConversionFast" Value="1"/>
                <FCBool Name="ConversionFlat" Value="0"/>
                <FCBool Name="ConversionCut" Value="1"/>
                <FCBool Name="ShowVRMDebug" Value="0"/>
                <FCBool Name="BimServerBrowser" Value="0"/>
                <FCBool Name="surveyUnits" Value="1"/>
                <FCInt Name="WindowTransparency" Value="85"/>
                <FCInt Name="StairsSteps" Value="17"/>
                <FCFloat Name="WallWidth" Value="200.000000000000"/>
                <FCFloat Name="WallHeight" Value="3000.000000000000"/>
                <FCFloat Name="StructureLength" Value="100.000000000000"/>
                <FCFloat Name="StructureWidth" Value="100.000000000000"/>
                <FCFloat Name="StructureHeight" Value="1000.000000000000"/>
                <FCFloat Name="RebarDiameter" Value="6.000000000000"/>
                <FCFloat Name="RebarOffset" Value="30.000000000000"/>
                <FCFloat Name="WindowWidth" Value="1000.000000000000"/>
                <FCFloat Name="WindowHeight" Value="1000.000000000000"/>
                <FCFloat Name="WindowThickness" Value="100.000000000000"/>
                <FCFloat Name="StairsLength" Value="4500.000000000000"/>
                <FCFloat Name="StairsWidth" Value="1000.000000000000"/>
                <FCFloat Name="StairsHeight" Value="3000.000000000000"/>
                <FCFloat Name="PanelLength" Value="1000.000000000000"/>
                <FCFloat Name="PanelWidth" Value="1000.000000000000"/>
                <FCFloat Name="PanelThickness" Value="10.000000000000"/>
                <FCFloat Name="PipeDiameter" Value="50.000000000000"/>
                <FCBool Name="WallSketches" Value="1"/>
                <FCUInt Name="WallColor" Value="3604403967"/>
                <FCUInt Name="StructureColor" Value="2527705855"/>
                <FCUInt Name="RebarColor" Value="3111475967"/>
                <FCUInt Name="WindowColor" Value="556614399"/>
                <FCUInt Name="WindowGlassColor" Value="1572326399"/>
                <FCUInt Name="PanelColor" Value="3416289279"/>
                <FCUInt Name="ColorHelpers" Value="674321151"/>
              </FCParamGroup>
              <FCParamGroup Name="Part">
                <FCParamGroup Name="General"/>
                <FCParamGroup Name="IGES"/>
                <FCParamGroup Name="STEP"/>
              </FCParamGroup>
            </FCParamGroup>
            <FCParamGroup Name="Document">
              <FCBool Name="CreateNewDoc" Value="0"/>
              <FCInt Name="CompressionLevel" Value="3"/>
              <FCBool Name="UsingUndo" Value="1"/>
              <FCInt Name="MaxUndoSize" Value="20"/>
              <FCBool Name="SaveTransactions" Value="0"/>
              <FCBool Name="TransactionsDiscard" Value="0"/>
              <FCBool Name="SaveThumbnail" Value="0"/>
              <FCBool Name="AddThumbnailLogo" Value="1"/>
              <FCBool Name="CreateBackupFiles" Value="1"/>
              <FCInt Name="CountBackupFiles" Value="1"/>
              <FCBool Name="DuplicateLabels" Value="0"/>
              <FCInt Name="prefLicenseType" Value="0"/>
              <FCText Name="prefLicenseUrl">http://en.wikipedia.org/wiki/All_rights_reserved</FCText>
              <FCText Name="prefAuthor"></FCText>
              <FCBool Name="prefSetAuthorOnSave" Value="0"/>
              <FCText Name="prefCompany"></FCText>
              <FCBool Name="RecoveryEnabled" Value="1"/>
              <FCBool Name="AutoSaveEnabled" Value="1"/>
              <FCInt Name="AutoSaveTimeout" Value="15"/>
            </FCParamGroup>
            <FCParamGroup Name="Bitmaps">
              <FCParamGroup Name="Theme"/>
            </FCParamGroup>
            <FCParamGroup Name="View">
              <FCText Name="NavigationStyle">Gui::CADNavigationStyle</FCText>
              <FCInt Name="OrbitStyle" Value="1"/>
              <FCInt Name="AntiAliasing" Value="0"/>
              <FCInt Name="CornerNaviCube" Value="1"/>
              <FCInt Name="MarkerSize" Value="9"/>
              <FCBool Name="ZoomAtCursor" Value="1"/>
              <FCBool Name="InvertZoom" Value="1"/>
              <FCBool Name="DisableTouchTilt" Value="1"/>
              <FCFloat Name="ZoomStep" Value="0.200000000000"/>
              <FCBool Name="DragAtCursor" Value="0"/>
              <FCBool Name="CornerCoordSystem" Value="1"/>
              <FCBool Name="ShowFPS" Value="0"/>
              <FCBool Name="UseVBO" Value="0"/>
              <FCBool Name="ShowNaviCube" Value="1"/>
              <FCBool Name="UseAutoRotation" Value="0"/>
              <FCFloat Name="EyeDistance" Value="5.000000000000"/>
              <FCBool Name="EnableBacklight" Value="0"/>
              <FCUInt Name="BacklightColor" Value="4294967295"/>
              <FCInt Name="BacklightIntensity" Value="100"/>
              <FCBool Name="Perspective" Value="0"/>
              <FCBool Name="Orthographic" Value="1"/>
              <FCText Name="NewDocumentCameraOrientation">Top</FCText>
              <FCUInt Name="BackgroundColor" Value="336897023"/>
              <FCUInt Name="BackgroundColor2" Value="859006463"/>
              <FCUInt Name="BackgroundColor3" Value="2543299327"/>
              <FCUInt Name="BackgroundColor4" Value="1869583359"/>
              <FCBool Name="Simple" Value="0"/>
              <FCBool Name="Gradient" Value="1"/>
              <FCBool Name="UseBackgroundColorMid" Value="0"/>
              <FCBool Name="EnablePreselection" Value="1"/>
              <FCBool Name="EnableSelection" Value="1"/>
              <FCUInt Name="HighlightColor" Value="3789624575"/>
              <FCUInt Name="SelectionColor" Value="481107199"/>
              <FCFloat Name="PickRadius" Value="5.000000000000"/>
            </FCParamGroup>
            <FCParamGroup Name="OutputWindow">
              <FCBool Name="checkLogging" Value="0"/>
              <FCBool Name="checkWarning" Value="1"/>
              <FCBool Name="checkError" Value="1"/>
              <FCUInt Name="colorText" Value="255"/>
              <FCUInt Name="colorLogging" Value="65535"/>
              <FCUInt Name="colorWarning" Value="4289331455"/>
              <FCUInt Name="colorError" Value="4278190335"/>
              <FCBool Name="RedirectPythonOutput" Value="1"/>
              <FCBool Name="RedirectPythonErrors" Value="1"/>
            </FCParamGroup>
            <FCParamGroup Name="DockWindows">
              <FCParamGroup Name="TreeView">
                <FCBool Name="Enabled" Value="1"/>
              </FCParamGroup>
              <FCParamGroup Name="PropertyView">
                <FCBool Name="Enabled" Value="1"/>
              </FCParamGroup>
              <FCParamGroup Name="DAGView">
                <FCBool Name="Enabled" Value="0"/>
              </FCParamGroup>
            </FCParamGroup>
            <FCParamGroup Name="TreeView">
              <FCUInt Name="TreeEditColor" Value="4294902015"/>
              <FCUInt Name="TreeActiveColor" Value="3873898495"/>
            </FCParamGroup>
            <FCParamGroup Name="PropertyView"/>
            <FCParamGroup Name="Editor">
              <FCBool Name="EnableLineNumber" Value="1"/>
              <FCBool Name="EnableFolding" Value="1"/>
              <FCInt Name="TabSize" Value="4"/>
              <FCInt Name="IndentSize" Value="4"/>
              <FCBool Name="Tabs" Value="1"/>
              <FCBool Name="Spaces" Value="0"/>
              <FCUInt Name="Text" Value="0"/>
              <FCUInt Name="Bookmark" Value="16776960"/>
              <FCUInt Name="Breakpoint" Value="4278190080"/>
              <FCUInt Name="Keyword" Value="65280"/>
              <FCUInt Name="Comment" Value="11141120"/>
              <FCUInt Name="Block comment" Value="2694882304"/>
              <FCUInt Name="Number" Value="65280"/>
              <FCUInt Name="String" Value="4278190080"/>
              <FCUInt Name="Character" Value="4278190080"/>
              <FCUInt Name="Class name" Value="4289331200"/>
              <FCUInt Name="Define name" Value="4289331200"/>
              <FCUInt Name="Operator" Value="2694882304"/>
              <FCUInt Name="Python output" Value="2863300352"/>
              <FCUInt Name="Python error" Value="4278190080"/>
              <FCUInt Name="Current line highlight" Value="3772833792"/>
              <FCInt Name="FontSize" Value="10"/>
              <FCText Name="Font">Ubuntu</FCText>
            </FCParamGroup>
            <FCParamGroup Name="MainWindow">
              <FCBool Name="TiledBackground" Value="0"/>
            </FCParamGroup>
            <FCParamGroup Name="DAGView"/>
            <FCParamGroup Name="RecentFiles">
              <FCInt Name="RecentFiles" Value="4"/>
            </FCParamGroup>
            <FCParamGroup Name="Browser"/>
          </FCParamGroup>
          <FCParamGroup Name="Macro"/>
          <FCParamGroup Name="Workbench"/>
          <FCParamGroup Name="MainWindow">
            <FCParamGroup Name="Toolbars">
              <FCBool Name="File" Value="1"/>
              <FCBool Name="Workbench" Value="1"/>
              <FCBool Name="Macro" Value="1"/>
              <FCBool Name="View" Value="1"/>
              <FCBool Name="Structure" Value="1"/>
              <FCBool Name="Navigation" Value="0"/>
              <FCBool Name="Draft tray" Value="0"/>
            </FCParamGroup>
            <FCParamGroup Name="DockWindows">
              <FCBool Name="Std_ReportView" Value="0"/>
              <FCBool Name="Std_TreeView" Value="1"/>
              <FCBool Name="Std_PropertyView" Value="0"/>
              <FCBool Name="Std_SelectionView" Value="1"/>
              <FCBool Name="Std_CombiView" Value="1"/>
              <FCBool Name="Std_PythonView" Value="0"/>
            </FCParamGroup>
          </FCParamGroup>
          <FCParamGroup Name="Workbenches"/>
        </FCParamGroup>
        <FCParamGroup Name="Tux">
          <FCParamGroup Name="NavigationIndicator">
            <FCBool Name="Compact" Value="0"/>
            <FCBool Name="Tooltip" Value="1"/>
          </FCParamGroup>
          <FCParamGroup Name="PersistentToolbars">
            <FCParamGroup Name="User">
              <FCParamGroup Name="StartWorkbench"/>
              <FCParamGroup Name="ArchWorkbench"/>
            </FCParamGroup>
            <FCParamGroup Name="System">
              <FCParamGroup Name="StartWorkbench"/>
              <FCParamGroup Name="ArchWorkbench"/>
            </FCParamGroup>
          </FCParamGroup>
        </FCParamGroup>
      </FCParamGroup>
    
    </FCParameters>
    
    Attached Files:
    Notes
    (0012976)
    Kunda1   
    2019-03-29 21:41   
    @ArnoVersfeld thank you. It's better to post to the forum first (per our guidelines at the top of the page).
    @chrisb care to weigh in ?
    (0013016)
    Kunda1   
    2019-04-06 19:49   
    @ArnoVersfeld please post your Help > About FreeCAD > Copy to clipboard
    (0013333)
    Kunda1   
    2019-07-05 21:08   
    fixed typos in title
    (0013334)
    Kunda1   
    2019-07-05 21:09   
    ping @ArnoVersfeld
    (0013485)
    Kunda1   
    2019-08-29 23:26   
    @chrisb is there an already open issue or known issue related to this ticket ?
    (0015357)
    chrisb   
    2021-02-16 07:58   
    No forum discussion, not tested in 0.19, no file, only preferences shown as XML and no screenshot? Hard to validate.
    (0015428)
    wmayer   
    2021-02-23 18:59   
    If you choose MKS in the unit preferences and create a standard box afterwards it shows 10mm x 10mm x 10mm. The reporter probably expects 0.01m x 0.01m x 0.01m
    (0016741)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5906.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4574 [PartDesign] Bug minor always 2021-02-20 22:41 2021-02-21 16:58
    Reporter: dg1727 Platform: Linux  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: Version: 0.19pre from freecad-daily PPA
    Hash: ed02d1bbddaa6daeedfe766b2ce33e88f4b22f93
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Summary: PartDesign Boolean Cut: attempted translation along X-axis causes unexpected rotation
    Description: PartDesign Boolean Cut: attempted translation along X-axis causes unexpected rotation
    Tags:
    Steps To Reproduce: Open FreeCAD.

    Enable the axis cross.

    In the following steps, after each time a solid is made (those steps are marked with a "*"), adjust the view scale & angle (preferably to an oblique view) so you can tell the shape, location, & orientation of what was made.

    In the Part Design workbench, create a Body (the default name is Body).

    Within that Body, create a sketch in the XZ plane.

    Draw a 10mm x 10mm square whose lower-left corner is at (X = 10 mm, Z = 10 mm).

    Exit the sketcher.

    In the tree view, select Body. In the properties windowpane below the tree view, on the Data tab, enter a value for Placement > Position > x of 50 mm.

    (*) Revolve the sketch, leaving the default parameters, which use the vertical sketch axis as the revolution axis. This produces a square-cross-section toroid. The default name is "Revolution."

    Create a new Body (the default name is Body001).

    Within this Body, create a sketch in the XY plane.

    Draw a 10mm-diameter circle whose center is at (X = 65 mm, Y = 15 mm).

    Exit the sketcher.

    (*) Pad the sketch by 30 mm. (Keep the other parameters at default.) This makes a cylinder shape which appears to intersect the toroid.

    In the treeview, make Body active. (Right-click > "Toggle active body")

    Start a Boolean operation.

    In the taskpane for the Boolean, set the Boolean operation to Cut.

    In the taskpane, select "Add body." Then use the 3D view to select the cylinder shape (Body001).

    Even before you click OK, the toroid (actually the result of the Boolean, a different object than the original toroid) will appear, unexpectedly rotated 90 degrees about the X axis.
    Additional Information: The same issue also seems to happen (I didn't use exactly the same steps to duplicate it) on v0.18.4, with the same versions of Coin & OpenCASCADE.

    There aren't any errors in the terminal, nor in the FreeCAD logfile.
    Attached Files:
    Notes
    (0015397)
    Kunda1   
    2021-02-21 01:48   
    Please paste full About info
    @dg1727 Please first open a forum thread per our forum guidelines. Thank you
    (0015411)
    Kunda1   
    2021-02-21 11:31   
    @dg1727 ping
    (0015413)
    dg1727   
    2021-02-21 12:56   
    https://forum.freecadweb.org/viewtopic.php?f=8&t=55853

    OS: Linux
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19pre from freecad-daily PPA
    Build type: Release
    Branch: unknown
    Hash: ed02d1bbddaa6daeedfe766b2ce33e88f4b22f93
    Python version: Same issue on 2 widely different Python versions
    Qt version: irrelevant to this issue
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: [redacted]
    (0015414)
    dg1727   
    2021-02-21 13:02   
    It seems that the issue happens only if the first PartDesign Body (object name "Body" in the procedure above) is a solid of revolution. (Using a Pad, for instance, doesn't cause the issue.)
    (0015415)
    wmayer   
    2021-02-21 13:09   
    Confirmed with:

    OS: Ubuntu 18.04.5 LTS (XFCE/xubuntu)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.24188 (Git)
    Build type: Debug
    Branch: master
    Hash: 385efeeb589dc2b6c3046ace9c9df23a996ced0c
    Python version: 3.6.9
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: German/Germany (de_DE)
    (0016996)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6164.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1181 [FreeCAD] Feature feature N/A 2013-07-14 17:47 2021-02-20 22:45
    Reporter: project4 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: trunk  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Adding an option to fill a the surface with image or other methods to show a thread-like shape
    Description: I saw in other applications that it's common to fill the surface with an image that looks like a thread on parts.
    That simplifies the object since there will be much less details than modeling the threads on a bolt or nut.

    Other ideas to use an image on a part is to apply a material on it.
    I think I saw somewhere that material is one of the big features for FreeCad, so I'm sure there will be much more work done in that direction, but the threading appearance is not related to that, so I hope you could add at least that property to the part designer.

    Thanks.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0003411)
    wmayer   
    2013-07-16 12:01   
    Do you talk about texture mapping?
    (0003413)
    project4   
    2013-07-16 15:19   
    Yes, I think that's how it's called.
    But I'm talking about one specific case for the threading and not every possible image to be used as a texture.
    (0003415)
    shoogen   
    2013-07-17 03:00   
    This could be useful for knurling as well.
    (0003433)
    ulrich1a   
    2013-07-30 06:04   
    There is a need to mark holes or bolts, which have a thread, in some way. Because if we want to have a drawing of a part with a thread, we also want the thread shown on the drawing with its characteristic drawing style.
    This method is named "cosmetic thread" in solidworks. It is shown for example at this page: http://help.solidworks.com/2013/English/SolidWorks/sldworks/c_cosmetic_threads.htm
    I think there should also a way to have this in a step file, but I could not find any useful information.
    (0007882)
    Kunda1   
    2017-01-19 15:27   
    Changing status back to new since OP responded.
    (0015396)
    Kunda1   
    2021-02-20 22:45   
    @davidosterberg how much does this ticket related to Helix ?
    (0016402)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5567.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4124 [Sketcher] Bug minor random 2019-09-11 20:43 2021-02-20 17:33
    Reporter: dimitar Platform: Windows  
    Assigned To: OS: Windows  
    Priority: normal OS Version: 10  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Sketcher angle produces errors when units set in m/kg/degree
    Description: Sketcher Angle produces errors when in meters constantly when creating angle constraints. As per the forum below, it seems to be an imprecision issue.

    Even, as in the suggestion of the forum, creating enabling advanced solver, and enabling sketch size multiplier, the issue persists.

    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=3&t=37716&hilit=angle
     
    Tags: #pending-forum, units
    Steps To Reproduce: 1. Create a sketch
    2. Create 2 lines a good distance away from the sketch origin
    3. Add angle constraint
    4. Leave the sketch
    5. Adjust the angle constraint in the sketch properties
    6. Sometimes the sketch fails to recompute throwing an Sketcher Invalid Constraint Index 22 or just an Error or Error 3.
    Additional Information: OS: Windows 10
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16117 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-18
    Hash: dbb4cc6415bac848a294f03b80f65e888d531742
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedKingdom (en_GB)
    Attached Files: edgeAngleError.FCStd (13,889 bytes) 2019-09-11 20:43
    https://tracker.freecad.org/file_download.php?file_id=2324&type=bug
    angled constraints issues.FCStd (18,534 bytes) 2019-09-12 00:26
    https://tracker.freecad.org/file_download.php?file_id=2325&type=bug
    FreeCAD_Dv3e0Ajbbs.png (29,945 bytes) 2019-09-13 17:05
    https://tracker.freecad.org/file_download.php?file_id=2328&type=bug
    FreeCAD_wjaJcbFmgB.png (20,931 bytes) 2019-09-13 17:05
    https://tracker.freecad.org/file_download.php?file_id=2329&type=bug
    constraints issue.FCStd (15,072 bytes) 2019-09-13 17:05
    https://tracker.freecad.org/file_download.php?file_id=2330&type=bug
    Notes
    (0013582)
    dimitar   
    2019-09-12 00:26   
    I've started another thread with a fresh example. In the attached file, if the spreadsheet number gets changed, the angle sometimes adjusts itself, sometimes it doesn't.

    https://forum.freecadweb.org/viewtopic.php?f=3&t=39276
    (0013592)
    dimitar   
    2019-09-13 17:05   
    i've just experienced this behavior with a radius constraint. I suspect it must be a rounding issue due to the fact that I am working in meters. In the following example, if i change the radius from 70m to 50m, i get the following error, also, if i go down to what it gives me and then try to go back up I also get and invalid constraints with index 8.
    (0015391)
    Kunda1   
    2021-02-20 17:33   
    Moved to Sketcher category

    @abdullah care to take look?
    (0016820)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5986.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    922 [FreeCAD] Feature major always 2012-12-20 17:05 2021-02-20 14:08
    Reporter: Jriegel Platform:  
    Assigned To: realthunder OS:  
    Priority: high OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: major rework      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Topological Naming
    Description: Group issue for all issues regarding Topological Naming. All bugs and features will be collected under this issue and targeted by the Naming Project:

    http://www.freecadweb.org/wiki/Naming_project

    Tags: toponaming
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0004577)
    berndhahnebach   
    2014-04-26 17:32   
    link on new wiki
    http://www.freecadweb.org/wiki/index.php?title=Naming_project
    (0008890)
    Kunda1   
    2017-05-05 12:11   
    Assigning to @jnxd since his project was accepted for GSOC 2017
    (0012919)
    mihai.dumitresq   
    2019-03-16 13:22   
    What's the latest status on topological naming?
    (0012924)
    Kunda1   
    2019-03-16 16:49   
    @mihai.dumitresq currently the best prospects look like in realthunder's link3/Assembly3 brnaches. You can find the discussion on the Forum: https://forum.freecadweb.org/viewtopic.php?f=10&t=27278
    (0017148)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6317.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    876 [PartDesign] Feature minor have not tried 2012-11-14 18:16 2021-02-20 13:55
    Reporter: wmayer Platform:  
    Assigned To: realthunder OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Topological naming interface
    Description: http://forum.freecadweb.org/viewtopic.php?f=10&t=2980
    Tags:
    Steps To Reproduce:
    Additional Information: Downgraded and assigned to jnxd
    Attached Files:
    Notes
    (0002573)
    wmayer   
    2012-11-21 09:47   
    Some more information from pythonocc:
    http://www.pythonocc.org/resources/meshing/pythonocc-and-smesh/
    (0002741)
    jrheinlaender   
    2012-12-21 09:32   
    Just a reminder that I submitted a draft implementation for a topological naming interface on github jrheinlaender/TNaming

    https://github.com/jrheinlaender/FreeCAD/tree/jrheinlaender/TNaming
    (0004959)
    normandc   
    2014-08-17 20:02   
    I don't know who can edit the bug description but since then the forum was migrated out of SF. So the updated link to the forum topic should be http://forum.freecadweb.org/viewtopic.php?f=10&t=2980
    (0015383)
    Kunda1   
    2021-02-20 13:55   
    @realthunder is this a dupe of 0000922 ?
    (0017147)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6316.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3050 [FEM] Feature feature N/A 2017-05-27 09:57 2021-02-20 12:55
    Reporter: berndhahnebach Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: reopened  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FEM, constraint pressure, make it work on face meshes too.
    Description: The pressure constraint (FemConstraintPressure) should work on face meshes too. Ccx supports this.

    But we'll face a problem here:
    How do we get the information if a FEM mesh face is in the same direction like the geometrical face normal (the normal of the reference shape)?

    For more information see forum thread: https://forum.freecadweb.org/viewtopic.php?f=18&t=21872
    Tags: constraints, FEM
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0009177)
    berndhahnebach   
    2017-05-28 10:49   
    A first implementation has been merged into master. But it is a start only. The FEMMesh faces should not have flipped normals and group data is needed too. See the forum thread linked in description for more informations.

    https://github.com/FreeCAD/FreeCAD/commit/7ed786cf863f5b11de55c6d4c7c8ce3e753bd5ce
    (0011786)
    berndhahnebach   
    2018-09-18 06:37   
    issue 0003313 has further informations.
    (0011790)
    berndhahnebach   
    2018-09-18 06:44   
    (Last edited: 2018-09-18 06:44)
    closed by misstake, thus reopened

    (0014525)
    berndhahnebach   
    2020-06-12 05:29   
    (Last edited: 2020-06-12 05:31)
    related: https://forum.freecadweb.org/viewtopic.php?f=18&t=47497
    (0014526)
    berndhahnebach   
    2020-06-12 05:32   
    https://github.com/FreeCAD/FreeCAD/blob/6271887cc656d8571000de2f4e06df2be8d84105/src/Mod/Fem/femmesh/meshtools.py#L1586
    (0016534)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5699.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3977 [PartDesign] Bug major always 2019-05-15 21:32 2021-02-18 14:31
    Reporter: openBrain Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Fillet feature fails on solid obtained by revolution
    Description: Fillet function fails on particular part obtained by revolution. It correctly works on same part obtained by other function(s).
    Tags: fillet
    Steps To Reproduce: Attached file demonstrates the bug with one part where filleting fails (obtained by Revolution) and one where it succeeds (obtained by Pad).
    More precisely, on the working model, the 4 inner edges of the "crest" can be filleted, while only 2 are in the faulty design. Trying to fillet the other 2 will fail or even freeze FC.
    Additional Information: Forum thread
    ---
    OS: Ubuntu 18.04.2 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.1.
    Build type: Release
    Python version: 2.7.15rc1
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: French/France (fr_FR)
    Attached Files: bug_fillet_revolution.FCStd (49,409 bytes) 2019-05-15 21:32
    https://tracker.freecad.org/file_download.php?file_id=2221&type=bug
    Notes
    (0016766)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5932.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4570 [FreeCAD] Feature tweak always 2021-02-16 18:53 2021-02-16 18:53
    Reporter: Huldar Platform:  
    Assigned To: OS:  
    Priority: low OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Windows 10
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.4 (GitTag)
    Build type: Release
    Branch: releases/FreeCAD-0-18
    Hash: 980bf9060e28555fecd9e3462f68ca74007b70f8
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedKingdom (en_GB)
    Summary: Change workbench dropdown menu size along with toolbar icons
    Description: I posted to the forum first, here is the link Forum post.

    The feature request I want to make is that the workbench dropdown menu scales in size along with the toolbar icons when you change them through
    Edit>Preferences>General>Size of toolbar icons

    That's all :)
    Thanks.
    Tags:
    Steps To Reproduce: Go to
    Edit>Preferences>General>Size of toolbar icons
    Additional Information:
    Attached Files:
    Notes
    (0016995)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6163.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4568 [FEM] Bug major always 2021-02-15 16:21 2021-02-15 16:21
    Reporter: Jee-Bee Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: <!--ATTENTION:
    COMPLETELY ERASE THIS AFTER PASTING YOUR
    Help > About FreeCAD > Copy to clipboard
    NOTE: just the snippet alone will do without anything else included.
    The ticket will not be submitted without it.
    -->
    Summary: FEM can't mesh a linked object
    Description: The FEM Mesh don't accept non-shaped objects.
    The result is that linked bodies can't be used as input for creating a mesh.
    Tags:
    Steps To Reproduce: n.a.
    Additional Information: see topic: https://forum.freecadweb.org/viewtopic.php?f=18&t=53372
    Attached Files:
    Notes
    (0016994)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6162.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4084 [FreeCAD] Bug minor always 2019-08-08 18:35 2021-02-15 16:14
    Reporter: Jee-Bee Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: placement within a body breaks after a clone from non origin position
    Description: The Clone of the PartDesign Body don't give the result as may expected from what the Clone should do(In my opinion).
    However my proposal could be broader interpreted as PartDesign... my issue is with PartDesign.

    What is the situation:
    Outside PartDesign all objects have a relation with Origin(general one).
    In PartDesign normally you start with a Part OR Body. The Part have a relation with the PartOrigin. The Body have relation with PartOrigin OR Origin. The PartDesign Shape have a relation with BodyOrigin OR PartOrigin?
    From now on i describe everything with the PartDesign Body as i discovered it with that. I assume the issue is the same with PartDesign Part.
    When i make a Shape inside my Body the Shape have a relation with the BodyOrigin. When i change the Placement of the Body (moving), the relation between the Object and the BodyOrigin are constant(don't change). This is off course what i want!
    Now a second instance of the same Body is needed. I can create a new Body and go trough all the steps as did before and give it a new Placement. This is Error prone so I create a Clone.
    Now comes the Bug in my opinion. The Clone create a new Body as expected but the relation between the Object and the BodyOrigin aren't preserved!
    In the Clone the Shape have exactly the same Position as the original Shape. The BodyOrigin is at the general Origin and the Placement is [0,0,0] (for the example i ignored Rotation!).


    According to Crisb this is inherent the way FC handles Boolean AND Clone Objects.
    In PartWB i understand that. with every Boolean function deciding what origin is choosed(master+slave/calculation/...) Yes i understand(a bit).
    But PartDesign is another workflow. All Shapes have a relation to their origin from where they are created... So when Cloneing the Body means that the Shape and his relation to his BodyOrigin are preserved!

    My proposal is to modify the PartDesign Clone so that Shape + BodyOrigin (+ Placement) are Preserved.
    Tags: Clone, Part Design
    Steps To Reproduce: - start new document
    - (go to part design)
    - create body
    - create object in body (the object has a position/ relation regarding the coordinate system of the body)
    - move body around
    - create clone from body
    internal coordinate system of the body from clone is different than the internal coordinate system of the original body.
    The clone internal coordinate system
    Additional Information: Link to Topic: https://forum.freecadweb.org/viewtopic.php?f=8&t=38295
    Attached Files: clone_partdesign_bug.FCStd (10,978 bytes) 2019-08-08 18:35
    https://tracker.freecad.org/file_download.php?file_id=2281&type=bug
    Notes
    (0016808)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5974.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4560 [FEM] Feature feature N/A 2021-02-11 11:07 2021-02-15 05:56
    Reporter: Jee-Bee Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: acknowledged Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: <!--ATTENTION:
    COMPLETELY ERASE THIS AFTER PASTING YOUR
    Help > About FreeCAD > Copy to clipboard
    NOTE: just the snippet alone will do without anything else included.
    The ticket will not be submitted without it.
    -->
    Summary: use multiple mesh in analysises
    Description: ATM it is not possible to solve analysises with multiple meshes
    Tags:
    Steps To Reproduce: -
    Additional Information: https://forum.freecadweb.org/viewtopic.php?p=476836
    Attached Files:
    Notes
    (0015345)
    berndhahnebach   
    2021-02-15 05:54   
    (Last edited: 2021-02-15 05:55)
    BTW: it is possible to solve tie constraints with gaps in the surface. All bodies have to be meshed in the same huge mesh.

    But still ... The use of multiple meshes would be an great enhancement.
    (0016991)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6159.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3924 [FreeCAD] Bug minor always 2019-04-04 14:52 2021-02-11 17:13
    Reporter: Geoplace Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Text (Annotation) moves greatly when placement edited.
    Description: The place where the Text (annotation) are shown is disproportionately modified even when the placement has been edited by 1mm.

    The placement edition of one Text note affects others notes, even when you edit a windows placement it also distorts Text showed in the 3D space.

    OS: Windows 8.1
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16093 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-18
    Hash: 690774c0effe4fd7b8d2b5e2fb2b8c8d145e21ce
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Tags:
    Steps To Reproduce: 1.- Open FreeCAD v18 . Switch to Arch workbench.
    2.- Create a Rectangle and make face false. (Being in the default top view)
    3.- Create Text (Annotations) one at each corner of the rectangle.
    4.- Use the wall tool in the rectangle to get walls.
    5.- Use windows tool and insert one at the front wall.
    6.- Change the windows (or text) placement parameter by opening it from the properties/data window and edit for example de X axis by 1mm. Clic Apply or OK.
    7.- Now the texts go far away, at least 3 of them. The recompute don’t fix its shown positions.
    Additional Information: The text placement parameters stay the same. Lucky when we save and reopen the file its Texts takes the correct place.

    The same happen in the Linux OpenSuse Version 0.18. And Windows v 0.19.
    OS: Windows 8.1
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.16267 (Git)
    Build type: Release
    Branch: master
    Hash: ddb335cfe057336f1958d68126bb0471328d735c
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0

    It's an annoying bug because when you have a larger file that takes times to load, the open-close workaround to see the correct result would waste a lot more time.

    Here is the link to the forum with steps with images:
    https://forum.freecadweb.org/viewtopic.php?f=8&t=35307

    Here is a test file you just need do the step 6 to see the bug.
    Attached Files: Prueba Annoation Windows wall-wind.FCStd (45,819 bytes) 2021-02-11 17:13
    https://tracker.freecad.org/file_download.php?file_id=2619&type=bug
    Notes
    (0015324)
    Kunda1   
    2021-02-11 17:13   
    Re-added attachment as the previous one was corrupted somehow.
    (0016743)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5908.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3998 [PartDesign] Feature minor always 2019-06-01 14:30 2021-02-08 22:01
    Reporter: abdullah Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Fillet tool not showing which edge/face fails
    Description: Fillet tool sometimes fails, but it doesn't indicate which one of the elements to fillet is the one that is failing.
    Tags: fillet
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016774)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5940.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4558 [Path] Feature minor N/A 2021-02-08 16:45 2021-02-08 16:45
    Reporter: sliptonic Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.20  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: <!--ATTENTION:
    COMPLETELY ERASE THIS AFTER PASTING YOUR
    Help > About FreeCAD > Copy to clipboard
    NOTE: just the snippet alone will do without anything else included.
    The ticket will not be submitted without it.
    -->
    Summary: Helix operation should handle conical use-cases
    Description: Current helix operation can only handle cylindrical holes. It should also handle conical holes.

    Tags:
    Steps To Reproduce:
    Additional Information: Ideally, it would have a very similar interface to the new additive/subtractive helix sweep in PD. Even better, it should autoconfigure based on the selected geometry.
    Attached Files: 2021-02-08_10-37.png (61,741 bytes) 2021-02-08 16:45
    https://tracker.freecad.org/file_download.php?file_id=2613&type=bug
    Notes
    (0016990)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6158.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4323 [FreeCAD] Bug minor always 2020-04-24 21:23 2021-02-07 22:08
    Reporter: cadandre Platform: PC  
    Assigned To: OS: Windows  
    Priority: normal OS Version: 10  
    Status: feedback Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 10
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.4 (GitTag)
    Build type: Release
    Branch: releases/FreeCAD-0-18
    Hash: 980bf9060e28555fecd9e3462f68ca74007b70f8
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: German/Germany (de_DE)
    Summary: Import of any .dae (Collada)-file fails
    Description: According to
    https://wiki.freecadweb.org/index.php?title=Extra_python_modules#pyCollada

    FreeCAD on Windows should be able to open/import .dae-files
    Quote:
    'Windows

    On Windows since 0.15 pycollada is included in both the FreeCAD release and developer builds so no additional steps are necessary.'

    Nevertheless every import of .dae-files (Open as well as Import) fails (see screenshot attached). If somebody tells me where to find the errormessage at the bottom of the screenshot, I could provide it.
    Tags: #post-to-forum, 0.18
    Steps To Reproduce: open/import any .dae-file
    Additional Information:
    Attached Files: dae_import_fails.png (24,952 bytes) 2020-04-24 21:23
    https://tracker.freecad.org/file_download.php?file_id=2461&type=bug
    ExampleCollada.dae (15,833 bytes) 2021-02-07 21:41
    https://tracker.freecad.org/file_download.php?file_id=2611&type=bug
    Notes
    (0014371)
    openBrain   
    2020-04-24 22:38   
    @cadandre : please address your issue according our reporting guidelines by opening a topic in our forum. Thx
    (0015303)
    chennes   
    2021-02-07 21:41   
    Here's an example DAE file for testing.
    (0015304)
    chennes   
    2021-02-07 22:08   
    I am able to load the example file under the following:
    OS: Windows 10 Version 2004
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.23971 (Git)
    Build type: Release
    Branch: master
    Hash: a3fb41502b079a86175e6a414d82956a48bab4e2
    Python version: 3.8.6+
    Qt version: 5.15.1
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: English/United States (en_US)
    (0016884)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6050.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4332 [FreeCAD] Bug minor always 2020-05-01 16:17 2021-02-07 21:23
    Reporter: AlStu Platform: Acer Aspire V, 8GB/512GB SSD  
    Assigned To: OS: Windows  
    Priority: normal OS Version: 10 Home, kept up  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 10 (10.0)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.20655 (Git)
    Build type: Release
    Branch: master
    Hash: e8e67e8c5ebbc9f9ed9ea67aba5b891969595ece
    Python version: 3.8.2
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: English/Canada (en_CA)
    Summary: Thickness limitation on curved geometry
    Description: On file 04-29b, Thickness works well: It is a boat Body with longitudinal symmetry. On PartDesign WB, it is made by lofting through 3 sketches. The sketches are on the same XZ plane but displaced by Y and Z Attachments. Each sketch has 3 lines and an arc. Thickness is Reversed true and Intersection true.

    On file 04-29c, Thickness fails: The Body is identical to above except that on 1 ("Rib mid") of the 3 sketches, 2 lines have been replaced by very shallow arcs. The arcs are so shallow that they visually appear straight. In more detail, Thickness works up to 3.60mm and fails at 3.70mm and above. The Report says "<App> Document.cpp(3715): Failed to recompute Nonsuch_04_29c#Thickness: BRep_API: command not done".

    I first asked on the forum here and was told to change from v0.18 to v0.19 and that worked for the file 04-29b. I later asked on the forum here and have not had a reply. I used PartDesign WB but still fails on Part WB. I have tried many variations in the geometry and settings, none improve the 3.60mm max Thickness limitation, most cause complete failure.
    Tags:
    Steps To Reproduce: Because of the sweeping shape of the curves involved to create this issue, easiest to just test on the attached files, 04-29c is the one which fails. They have already had AdditiveLoft. Select Face 2 (the top face) and try to Make a Thick Solid tool above 3.60mm.
    Additional Information: My fallback would be to make a plug and use binary subtraction, but that is a pain and the Thickness limitation will still exist.
    System Description Two displays
    Attached Files: Nonsuch 04-29b.FCStd (253,437 bytes) 2020-05-01 16:17
    https://tracker.freecad.org/file_download.php?file_id=2465&type=bug
    Nonsuch 04-29c.FCStd (292,874 bytes) 2020-05-01 16:17
    https://tracker.freecad.org/file_download.php?file_id=2466&type=bug
    bug_thikness.FCStd (22,731 bytes) 2020-06-07 13:18
    https://tracker.freecad.org/file_download.php?file_id=2484&type=bug
    Notes
    (0014492)
    sfornengo   
    2020-06-07 10:43   
    Thickness is becoming unusable, always saying "BRep_API: command not done" or "BRep_Tool:: TopoDS_Vertex hasn't gp_Pnt" even with very small thickness eg 0.1mm
    (0014494)
    sfornengo   
    2020-06-07 13:18   
    Here is the most simple geometry demonstrating thickness fail.
    Try to make a thickness, selecting the face with no fillet to get a simple cap results in "BRep_API: command not done"
    (0015301)
    chennes   
    2021-02-07 21:23   
    For the record, this is still failing for me with OCC 7.5:
    OS: Windows 10 Version 2004
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.23971 (Git)
    Build type: Debug
    Branch: master
    Hash: a3fb41502b079a86175e6a414d82956a48bab4e2
    Python version: 3.8.6+
    Qt version: 5.15.1
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: English/United States (en_US)
    (0016889)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6055.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4521 [FreeCAD] Feature major always 2020-12-24 14:11 2021-02-07 11:18
    Reporter: DrC Platform: HP laptop  
    Assigned To: OS: Windows 10  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 10 (10.0)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.23141 (Git)
    Build type: Release
    Branch: master
    Hash: 0eba78d40096720f7a637a9a73c382a08b820bca
    Python version: 3.8.6
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: English/United Kingdom (en_GB)
    Summary: When joining a polygon to the end of an arc a tangent is implied
    Description: This feature seems to activate at imperceptible movement of the mouse or stylus. It results in an arbitrary tangent side added at whatever length fits the algorithm arbitrating between the gratuitous tangent and the new side.

    A more user friendly approach might be to require a mouse click to define the tangent length.
    Tags: #post-to-forum, 0.19, Poly-line, UI
    Steps To Reproduce: See my previous report - number to follow.
    Additional Information: See my previous report - number to follow.
    Attached Files:
    Notes
    (0015179)
    DrC   
    2020-12-24 14:18   
    Previous report was

    0004520: Doubleclick when drawing a polygon seems to results in an unresolvable double point.
    (0015243)
    Kunda1   
    2021-01-31 12:09   
    Forum thread please
    (0015273)
    DrC   
    2021-02-05 05:38   
    Sorry - there was no thread to attach this to. I had a bug mid-job and needed to get it down while I could still remember how it happened.

    I probably shouldn't even be here because I'm not a developer and not a professional bug fixer (any more) but merely trying to use FreeCad. Trouble is I feel an obligation to tell you about as bug when I see it even when (as it always will be) it's mid job and I'm doing something new.

    A section headed 'report all bugs here' in the forum might help me - but would it help you?

    I really need it to be a one step process unless you can't replicate it.
    (0015274)
    DrC   
    2021-02-05 06:28   
    https://forum.freecadweb.org/viewtopic.php?f=3&t=5236&p=474546#p474546
    (0015283)
    chennes   
    2021-02-07 03:39   
    I believe the OP means "polyLINE" rather than "polyGON" -- the effect is that there is an extra segment to your polyline if your cursor is positioned too close to the arc. The logic behind this construction eludes me. IMO, the OP is right, I don't think it should behave like this: I suspect it is an actual bug rather than a feature misbehaving, but this is probably something for @abdullah to look into.
    (0015287)
    DrC   
    2021-02-07 11:18   
    Confirm - polyLINE

    Apologies.

    Software I grew up with drew 'polygons' this way.
    (0016976)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6144.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4554 [PartDesign] Bug major always 2021-02-07 09:08 2021-02-07 09:08
    Reporter: GeoffG Platform: Linux  
    Assigned To: OS: Kubuntu  
    Priority: normal OS Version: 20.04  
    Status: new Product Version: 0.19  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version:  
    FreeCAD Information: OS: Ubuntu 20.04.2 LTS (KDE/plasma)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.23756 (Git) AppImage
    Build type: Release
    Branch: master
    Hash: 9c6e9184930a52b165a0b7274e3a45d1006bfe67
    Python version: 3.8.6
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: English/Australia (en_AU)
    Summary: Loft tool "Closed" option not working
    Description: I have created a model that contains five circle sketches arranged so that the solid can be closed using the Closed option. Unfortunately the Closed option does nothing in this case. The model file containing the sketches and resultant AdditiveLoft has been attached.

    I have raised this in the forum and others have indicated that this is a bug.

    The forum topic is: https://forum.freecadweb.org/viewtopic.php?f=3&t=55253
    Tags:
    Steps To Reproduce: (I apologise if I'm being too descriptive for such a simple process)

    1. Delete the existing AdditiveLoft
    2. Select the 5 sketches in order from top to bottom.
    3. Activate them by pressing the space bar
    4. Switch to Part Design workbench
    5. Initiate the Loft tool
    6. Toggle on the Closed option

    Nothing happens. There are no error messages either.
    Additional Information: I don't know if its useful but I have attached a screenshot of the versions of the graphical environment and processor that I'm using.
    Attached Files: Closed Loft.FCStd (46,831 bytes) 2021-02-07 09:08
    https://tracker.freecad.org/file_download.php?file_id=2609&type=bug
    Computing Environment.png (56,036 bytes) 2021-02-07 09:08
    https://tracker.freecad.org/file_download.php?file_id=2610&type=bug
    Notes
    (0016988)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6156.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3183 [FreeCAD] Feature feature always 2017-09-12 21:04 2021-02-06 06:50
    Reporter: KarenRei Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Graceful handling of self-intersections when creating part from imported mesh
    Description: Currently, self-intersections are anethema to FreeCAD. Unfortunately, meshes from external sources frequently have self-intersection. For example, if one makes a 2d surface in blender, then applies a "solidify" modifier to add thickness, the modifier will often have minor self intersection around sharp corners.

    It's common for many other programs I've used to deal gracefully with self-intersection because it's such a common issue. For example, if I upload a model with self intersection for 3d printing with iMaterialize, they convert it into a solid without complaints; the only constraints are the obvious - no non-manifold edges (aka, it must be "watertight").

    Even if you don't personally see value on this feature (or trust me that it would be well appreciated), adding it would at the very least save you the time of people seeking help about them on the forum ;)
    Tags: constraints
    Steps To Reproduce: Load any model with self-intersection. I'll make one for you if you'd rather :)
    Additional Information: OS: "Fedora release 24 (Twenty Four)"
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.11828 (Git)
    Build type: Unknown
    Branch: master
    Hash: 71130d09ed57c03c03bbbc0ef49e94a590f6ddd4
    Python version: 2.7.13
    Qt version: 4.8.7
    Coin version: 3.1.3
    OCC version: 6.8.0.oce-0.17
    Locale: Icelandic/Iceland (is_IS)
    Attached Files: tmp.dae (10,947 bytes) 2017-09-13 19:18
    https://tracker.freecad.org/file_download.php?file_id=1727&type=bug
    Notes
    (0010112)
    Kunda1   
    2017-09-13 12:13   
    Quick question, why is your version of FC 0.17 using an inferior version of OCC? Should be at least 7.1
    Also please upload an example file to expedite things for testers.
    Have you discussed this on the forum at all?
    (0010119)
    KarenRei   
    2017-09-13 19:18   
    I don't even know what OCC is. My install process was simply "dnf install freecad" on a stock Fedora 24 system.

    Yes, this has been discussed quite a few times on the forum, as it's a common complication when importing meshes.

    Attaching a sample model with self intersection. :)
    (0010122)
    wmayer   
    2017-09-13 20:21   
    What is a "minor self intersection"? is there also a "major self intersection"? And the model you uploaded is this a "minor" or a "major" self-intersection?
    (0010123)
    KarenRei   
    2017-09-13 20:40   
    It doesn't really matter; that was just an example of self intersection. "Minor" self intersection would be self intersection that is "adjective: lesser, as in size, extent, or importance, or being or noting the lesser of two"

    Any algorithm for self intersection should work for all self intersection, regardless of how much there is, should it not?
    (0016560)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5725.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3092 [FreeCAD] Feature feature always 2017-06-21 07:53 2021-02-06 06:50
    Reporter: PaFe Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Rescaling sketch at first dimensional constraint
    Description: In Solidworks there is quite a good feature that consists in rescaling all the sketch keeping the same proportions when adding the first dimensional contraint. Other dimensions are still uncostrainted, only rescaled. This is very useful because the drawer, drawing the very first sketch of a part, usually doesn't care about dimensioning but only about proportions of a shape. If the first dimensions of the uncostrainted sketch are very different from the final constrainted ones, the first dimensional constraint will "explode" all the sketch. The feature is to avoid this. Is it possible to add something similar in freecad?
    Tags: constraints
    Steps To Reproduce:
    Additional Information: OS: Ubuntu 17.04
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.11310 (Git)
    Build type: None
    Branch: master
    Hash: d28bae3f52b3e7cf959e8b9f7bcff264f95db191
    Python version: 2.7.6
    Qt version: 4.8.6
    Coin version: 4.0.0a
    OCC version: 7.1.0
    Attached Files:
    Notes
    (0009474)
    Kunda1   
    2017-06-21 10:18   
    (Last edited: 2017-06-21 10:23)
    @PaFe as per https://freecadweb.org/wiki/tracker#Requesting_features please open a forum thread to discuss with the community. Thx!

    (0009483)
    PaFe   
    2017-06-21 15:00   
    @Kunda1 So sorry! Here it is the Forum https://forum.freecadweb.org/viewtopic.php?f=19&t=23049
    (0016548)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5713.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3073 [FreeCAD] Feature feature random 2017-06-05 16:12 2021-02-06 06:50
    Reporter: Escain Platform: PC  
    Assigned To: OS: Linux Debian  
    Priority: none OS Version: Jessie 8.8  
    Status: confirmed Product Version: 0.16  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: "Labels & Attributes" tree mix-up randomly elements
    Description: What I do:
    I have several files, with several objects inside each. Elements are commonly default parts, sketchs and many boolean operations between.

    I select elements in one file, Ctrl+C to copy and select "No" to get a simple copy.

    In the other file, I paste with Ctrl+V

    What happens:
    For the few 10 elements, usually all is fine, after, the tree (where I paste) start to mix elements:
    - Files name is replace by "Unnamed"
    - Objects become sub-elements of others where they are unrelated
    - Objects disappear
    - Objects name start to point other objects in the view (e.g. I had a "Coin" for comparative size. The element "Coin" suddenly where pointing to my main part).

    Apart of that, I want to congratulate you for this wonderful software!! I love it.
    Tags:
    Steps To Reproduce: It seem random, it happens often, but I did not found a clear step-by-step.
    Additional Information: OS: Debian GNU/Linux 8.8 (jessie)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.16.
    Build type: None
    Python version: 2.7.9
    Qt version: 4.8.6
    Coin version: 4.0.0a
    OCC version: 6.8.0.oce-0.17
    Attached Files:
    Notes
    (0009296)
    Kunda1   
    2017-06-06 18:40   
    Please open a forum thread and bi-directionally connect ticket <=> thread
    (0009299)
    Kunda1   
    2017-06-06 18:48   
    @yorik is that well known click/drag tree bug?
    (0009301)
    yorik   
    2017-06-06 20:27   
    No, never seen that before...
    (0009325)
    Kunda1   
    2017-06-10 04:45   
    Forum thread opened: https://forum.freecadweb.org/viewtopic.php?f=8&t=22874
    (0009352)
    Kunda1   
    2017-06-12 22:00   
    Per @wmayer in the forum thread, I've changed this ticket from bug to feature
    (0016544)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5709.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3069 [FreeCAD] Feature feature have not tried 2017-06-04 07:08 2021-02-06 06:50
    Reporter: attesz86 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Persistent Clipping Plane
    Description: Feature request for a Clipping Plane feature that does not need to be closed when executing other operations.
    Tags: clipping plane
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016541)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5706.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3039 [FreeCAD] Feature feature N/A 2017-05-18 11:09 2021-02-06 06:50
    Reporter: Kunda1 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Importer for Autodesk Inventor files
    Description:

    by jmplonka » Thu Feb 09, 2017 3:26 pm
    Hello!
    I'm currently working on an importer for Autodesk (R) Inventor (R) files. Simply because my son has a license from school and it will end in 2 years ;)
    Current status:
    * Inventor files are OLE2 files
    * iProperties can be imported and some of them can be attached to the FreeCAD files.
    * embeded Excel workbooks are added to FreeCAD document.
    Next Steps:
    * display sketches with lines, etc.
    * The AddOn requres therefore the python packages for xlrd, xlutils and xlwt
    The project is currently located on https://github.com/jmplonka/InventorLoader
    Any help (eg. retrieving the coordinates or the names of objects) is highly welcome.

    jmplonka
    Tags:
    Steps To Reproduce:
    Additional Information: Forum thread: https://forum.freecadweb.org/viewtopic.php?f=22&t=20575
    Attached Files:
    Notes
    (0016532)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5697.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2966 [FreeCAD] Feature minor have not tried 2017-03-14 14:10 2021-02-06 06:50
    Reporter: Milkroundsoftware Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Rotate View on Screen
    Description: Hi,
    I have been working CAD during 1976-85 at BAe Systems at Brough where I was the main designer of the MAXIS wireframe system. OK old hat by todays systems but the old feeling of wanting always to change the view remains. I feel like a man without hands!

    When using FreeCad yes you can do it but it is a pain... you have to think about how.

    The MAXIS system had a Rotation Icon (it was on a tablet) but could easily be located on the XYZ marker at the bottom RHC of the FreeCad screen. The two key bits of information are the direction of rotation taken from the DX & DY from the XYZ origin and the degree of rotations taken from SQRT(DX*DX + DY*DY) **3 (distance from origin cubed). This allows both small and large rotations.
    A Rotate screen Z icon is also needed.

    A similar tablet based icon allowed move left-right/up-down.

    We also had commands to look down edges or between two points.

    I hope you don't see this as a critism.

    Steve Hall
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016523)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5688.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2794 [FreeCAD] Feature minor have not tried 2016-11-25 08:16 2021-02-06 06:50
    Reporter: herrdeh Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: enable "document window" (flat lines, wireframes, points, shaded) for keyboard shortcuts
    Description: According to this thread (http://forum.freecadweb.org/viewtopic.php?t=14336), it's not easily possible to change the flat lines / wireframes / etc... display style within the keyboard shortcuts editor. I'm using this feature way to rarely and frequently get into troble for that reason. I'd love a shortcut for that toggle!
    Tags: keyboard, shortcuts
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0007488)
    herrdeh   
    2016-11-25 10:38   
    There is a macro which quite does what I want:
    http://www.freecadweb.org/wiki/index.php?title=Macro_Toggle_Drawstyle

    But it's not so easy to handle, expecially when it comes to non-English versions of FC.
    (0016509)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5674.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2410 [FreeCAD] Feature feature N/A 2016-01-17 21:20 2021-02-06 06:50
    Reporter: piffpoof Platform: Macintosh  
    Assigned To: OS: Mac OS X  
    Priority: normal OS Version: 10.6.8  
    Status: new Product Version: 0.15  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Set Visibility/Invisibility of object that requires manual intervention (not simply Space bar)
    Description: When working with constructions objects, or dimension objects, there are times when it is desireable to mark them as Hidden (or Invisible). The Visibility parameter in the View tab (value equals True/False) allows this. The limitation is that when a Group or compound object has it's Visibility toggled (using the space bar) then the lower level objects can become visible.

    This request is to make a level of Visibility available through the View tab that is not effected by the space bar. Instead it would require the user to actually toggle that Visibility manually. The effect would be similar to the code:
    FreeCADGui.ActiveDocument.getObject(ShapeNameObj.Name).Visibility = False
    FreeCADGui.ActiveDocument.getObject(ShapeNameObj.Name).Visibility = True

    This would allow objects such as construction or dimensional to remain Hidden (or Invisible) until the user manually switches them to Visible. In the mean time the user can toggle the Visibility of a compound object, a Group or the complete Object Collection in the workspace using the space bar. And not have the undesired objects be made Visible.
    Tags:
    Steps To Reproduce:
    Additional Information: There was a forum thread about this
    http://forum.freecadweb.org/viewtopic.php?f=3&t=13431
    System Description OS: Mac OS X
    Word size: 64-bit
    Version: 0.14.3703 (Git)
    Branch: releases/FreeCAD-0-14
    Hash: c6edd47334a3e6f209e493773093db2b9b4f0e40
    Python version: 2.7.5
    Qt version: 4.8.6
    Coin version: 3.1.3
    SoQt version: 1.5.0
    OCC version: 6.7.0
    Attached Files:
    Notes
    (0016474)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5639.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2173 [FreeCAD] Feature feature N/A 2015-06-26 17:43 2021-02-06 06:50
    Reporter: galou_breizh Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Pythonic vs. non-pythonic
    Description: I think the Python interface could be improved and be made more pythonic.

    An example:
    Gui.ActiveDocument.ActiveView.getCamera()
    and
    Gui.ActiveDocument.ActiveView.setCamera()
    could be replaced by a property
    Gui.ActiveDocument.ActiveView.Camera.

    For example:
    c = ActiveDocument.ActiveView.Camera
    ActiveDocument.ActiveView.Camera = '#Inventor V2.1 ascii ....'
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016465)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5630.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2077 [FreeCAD] General minor have not tried 2015-05-01 00:58 2021-02-06 06:50
    Reporter: tanderson69 Platform: amd64  
    Assigned To: OS: Kubuntu  
    Priority: normal OS Version: 14.10  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Assembly Merge: update tree view upon active object change
    Description: http://forum.freecadweb.org/viewtopic.php?f=20&t=10735
    Tags:
    Steps To Reproduce:
    Additional Information:
    System Description OS: Ubuntu 14.10
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.15.4427 +22 (Git)
    Branch: *
    Hash: *
    Python version: 2.7.8
    Qt version: 4.8.6
    Coin version: 4.0.0a
    OCC version: 6.8.0.oce-0.17-dev
    Attached Files:
    Notes
    (0016461)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5626.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2022 [FreeCAD] Feature feature N/A 2015-03-22 22:15 2021-02-06 06:50
    Reporter: shoogen Platform:  
    Assigned To: OS:  
    Priority: low OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Profile shift for involute gear
    Description: Add profile shift to the involute gear feature in the PartDesign Workbench.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016453)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5618.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1968 [FreeCAD] Feature minor have not tried 2015-02-16 15:26 2021-02-06 06:50
    Reporter: swill Platform:  
    Assigned To: OS: Ubuntu Server  
    Priority: normal OS Version: 14.04  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: importDXF (v1.38) how to change DXF export format
    Description: I see this in the code:

    self.acadver=' 9\n$ACADVER\n 1\nAC1009\n'
    """DXF AutoCAD-Release format codes:
    AC1021 2008, 2007
    AC1018 2006, 2005, 2004
    AC1015 2002, 2000i, 2000
    AC1014 R14,14.01
    AC1012 R13
    AC1009 R12,11
    AC1006 R10
    AC1004 R9
    AC1002 R2.6
    AC1.50 R2.05
    """

    How do I change this to, say, 'AC1015' so I can export a DXF file with the units of measure included in the exported file?

    My export code currently looks like this:
    import importDXF
    importDXF.export(FreeCAD.ActiveDocument.Objects, "%s/%s.dxf" % (config['app']['export'], data_hash))

    Thanks...
    Tags: DXF
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0005803)
    yorik   
    2015-02-17 14:52   
    This is unfortunately not so simple... There are a LOT of differences between DXF formats, much more than simply changing that value. All the header format is different after AC1009.

    This means basically that to support above versions, we need to recode entirely a very big part of the exporter. This cannot be done easily or quickly...
    (0005804)
    swill   
    2015-02-17 15:17   
    Ok. I had a suspicion this was going to be the case. Right now my clients have been able to open the resulting DXF files with LibreCAD and then just exporting them again as a DXF and they are updated to a newer version of DXF with units included.

    Do you happen to have any references I can review which gives more clarity into the differences? If I can get a strong enough grasp on what has to change I may be able to extend the functionality to support a more recent version of DXF. I think that packaging the units into the export was added in R2000 (according to one of the guys I have been working with).

    If I can scope out the amount of work to add support for this, it may be something I can take on. My project has been taking most of my free time, but this would be very valuable for my project.
    (0005805)
    yorik   
    2015-02-17 18:12   
    Ah, if you are willing to work a bit on this, this would be very precious. One of the first task needed would be exactly what you are mentioning: Gathering info about what is different between versions. I'm afraid it's no simple task, I have never been able to find clear info on the subject.

    The DXF libray we use for export is something we borrowed from Blender, it might also be time to recode it for good... We've also more less a plan to redo in C++ to gain better performance...
    (0005806)
    yorik   
    2015-02-17 18:14   
    Note, too, that you might find an intermediate solution: Have a look at how DWG export works with the Teigha converter utility. You might achieve the same result, but converting to a higher version of DXF instead of DWG...
    (0005807)
    swill   
    2015-02-17 18:36   
    Ok, thanks Yorik. I can start to look into what is needed for a total rewrite of the DXF export functionality, but I probably can't take that on right now. I will start by trying to understand what the moving parts are and what would need to be done.

    The Teigha converter utility may be a good option to get support in a relatively short term. I currently am not able to run Teigha on my server because I don't have X installed, but that is an easier problem to solve than rewriting all the DXF export functionality. :)

    Thanks for your input.
    (0007892)
    Kunda1   
    2017-01-20 01:48   
    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=10&t=20069
    (0016448)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5613.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1901 [FreeCAD] Feature minor always 2015-01-06 19:42 2021-02-06 06:50
    Reporter: triplus Platform: Linux  
    Assigned To: ickby OS: Ubuntu  
    Priority: normal OS Version: 14.04  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Add MSAA 6x option
    Description: Older graphic hardware (Radeon R300g) supports up to MSAA 6x and having the possibility to select MSAA 6x under preferences would be great.

    Side note: adding information to preferences GUI FreeCAD restart is needed when changing Anti-Aliasing mode probably wouldn’t hurt.
    Tags:
    Steps To Reproduce:
    Additional Information: On Linux it is possible to force MSAA 6x mode for mentioned hardware like this:

    export GALLIUM_MSAA=6
    freecad
    Attached Files:
    Notes
    (0005583)
    ickby   
    2015-01-08 06:49   
    Adding MSAA6x should be not a big issue, however, it may be a good idea to check which option is available in the hardware and only present those. I would need to investigate this.

    The restart thing is only in current development version, 0.14 stable changes the AntiAliasing without restart. I have a few ideas how to change that, but that needs investigating.

    I will takle both issues when my UI work is done, that may take a while
    (0005589)
    wmayer   
    2015-01-08 10:46   
    ickby I hope you don't mind if I assign it to you then.
    (0005596)
    ickby   
    2015-01-08 12:50   
    no, actually I wanted to do this too, somehow forgot that :)
    (0005600)
    triplus   
    2015-01-08 18:29   
    If some (standard) way of checking hardware/driver available MSAA modes exist it for sure would be great for FreeCAD to only show available modes. For example as mentioned hardware does not support MSAA 8x setting this option produces the same result as if mode none was selected. No "radeon: Acquired access to AA optimizations." is printed to stdout.

    User could get confused thinking MSAA does not work at all or thinking it might be FreeCAD bug. In reality hardware does not support MSAA 8x but MSAA modes up to 6x works just fine.

    If there is no (standard) way of checking hardware/driver available MSAA modes exist i am guessing having 2x, 4x, (6x) and 8x will still work for majority of FreeCAD users just fine and don't spend to much time on this.

    Changing Anti-Aliasing mode without restarting FreeCAD again that would be great and that should be priority when you decide to work on this again.

    Cheers.
    (0010125)
    wmayer   
    2017-09-14 13:44   
    http://blog.qt.io/blog/2015/09/21/using-modern-opengl-es-features-with-qopenglframebufferobject-in-qt-5-6/
    https://stackoverflow.com/questions/24738638/how-to-determine-the-maximum-number-of-supported-multisample-samples
    https://docs.blender.org/manual/ja/dev/preferences/system.html
    (0016444)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5609.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1699 [FreeCAD] Feature feature N/A 2014-08-19 02:55 2021-02-06 06:50
    Reporter: bejant Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.14  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Allow Wrapping of 2D Objects, Draft ShapeString, Onto Non-Linear Surfaces
    Description: It seems that users often want the ability to wrap 2D objects and text so it follows a curved surface. One such forum post is here:
    http://forum.freecadweb.org/viewtopic.php?f=3&t=7384

    It could also be helpful if the user could select a + or - distance from the 3D face for the wrap.
    Tags: shapestring
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0004965)
    normandc   
    2014-08-19 03:01   
    Wrapping 2D geometry on surfaces would be useful for more than text. It is a standard surfacing tool.
    (0004973)
    yorik   
    2014-08-19 15:40   
    But I'm afraid it's not very easy to achieve...
    (0004974)
    bejant   
    2014-08-19 18:50   
    Sorry, but I goofed. I mentioned 2D objects in the title but only mentioned text in the description. Also, the last sentence in the description should read:

    "It could also be helpful if the user could select a + or - distance FROM the 3D face for the wrap."
    (0008733)
    Kunda1   
    2017-03-29 18:13   
    Linked to 0000897
    (0016428)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5593.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1666 [FreeCAD] Feature minor always 2014-08-04 11:22 2021-02-06 06:50
    Reporter: triplus Platform: Linux  
    Assigned To: OS: Ubuntu  
    Priority: normal OS Version: 14.04  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Respect symbolic links
    Description: Based on discussion in this feature request:

    http://www.freecadweb.org/tracker/view.php?id=1665#c4918
    Tags: #lowhangingfruit, Qt, Qt5
    Steps To Reproduce: 1.) Create new folder and save test .fcstd file in this folder
    2.) Create symbolic link to test .fcstd file (ln -s) from different directory
    2.) Open the file in FreeCAD by clicking on just created symbolic link
    3.) Modify the file and save the changes

    Expected behaviour:

    FreeCAD saves the changes at original test .fcstd file location. Backup files are saved to original test .fcstd file location.

    Current behaviour:

    FreeCAD saves the changes at symbolic link test .fcstd file location. Backup files are saved to symbolic link test .fcstd file location.
    Additional Information:
    Attached Files:
    Notes
    (0005254)
    triplus   
    2014-10-25 22:55   
    For future reference if anybody will try to tackle this area and to provide symbolic links support for FreeCAD this is how Qt Creator deals with symbolic links:

    https://qt.gitorious.org/qt-creator/qt-creator/commit/a8ee92a53ba4b1c4c7e2c34db27ee44ed7e9c585

    Relevant discussion (don't rewrite symlink on save, rewrite target instead):

    https://qt.gitorious.org/qt-creator/qt-creator/merge_requests/399
    (0008604)
    Kunda1   
    2017-03-10 23:14   
    @triplus can you find a more up-to-date source? since Qt seems to have moved their repo.
    (0010064)
    Sam   
    2017-09-03 00:07   
    Forum thread: Issues 1665 & 1666; Symbolic links & backups
    (0016427)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5592.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1587 [FreeCAD] Feature minor have not tried 2014-06-20 16:47 2021-02-06 06:50
    Reporter: quick61 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: trunk  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Sweep On Multiple Paths
    Description: Reference - http://forum.freecadweb.org/viewtopic.php?f=22&t=6842

    Add ability to make a sweep defined by more than one path.

    Additional references:

    http://forum.freecadweb.org/viewtopic.php?f=22&t=6842#p55261

    http://forum.freecadweb.org/viewtopic.php?f=22&t=6842#p55266

    http://forum.freecadweb.org/viewtopic.php?f=22&t=6842#p55267
    Tags: sweep
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0006088)
    wmayer   
    2015-04-27 07:42   
    http://opencascade.blogspot.de/2009/12/surface-modeling-part4.html
    (0016424)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5589.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1415 [FreeCAD] Feature minor have not tried 2014-02-16 15:58 2021-02-06 06:50
    Reporter: Pauvres_honteux Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Multi core/thread support
    Description: Hi, I'm not sure if FC currently is utilizing multiple cores/threads simultaneously, but it would be of huge benefit for the future when one could, at least in theory, move a feature (point, line, plane) in the resulting body and see the whole result updated in real time.

    E.G. a casting whos shape depends upon an irregular hole pattern.
    Or upon step changing a common draft angle parameter reflects its impact in real time.
    Or moving holes and depressions in sheet metal and see the result in real time really enhances your understanding of that specific part you're working on.

    And your customers will get a better understanding of how a particular change/demand will impact the end result which in the end cut costly time - a lot.

    Regards Pauvres_honteux
    Tags: multithreading
    Steps To Reproduce:
    Additional Information: Had this in the "Open discussion" before but it was apparently the wrong place.
    Attached Files:
    Notes
    (0004281)
    Pauvres_honteux   
    2014-02-23 18:22   
    This might be a starting point for learning parallel computing?
    http://www.parallella.org/Introduction/

    Regards Pauvres_honteux
    (0004283)
    wmayer   
    2014-02-23 20:40   
    For parallel computing Qt already offers e.g. the (low-level) QThread class, QThreadPool or the high-level API QtConcurrent which we make use here and there.

    The problem is not that we don't know how to parallelize it's more the lack of OCC to support it. At the moment there are only a few algorithms that are ready to use in separate threads.
    (0004690)
    shoogen   
    2014-05-18 16:46   
    One improvemnt would be, that a recompute only blocks when applying changes to the GUI (changing QT elements or the scenegraph) and not while performing computations inside OCCT.
    (0004693)
    Pauvres_honteux   
    2014-05-19 02:52   
    (Last edited: 2017-05-06 21:15)
    Hi Shoogen, I get a feeling there's a vital word (for me) missing in your comment [0001415:0004690] "...only blocks when applying..." ? Should there have been a word before or after "blocks" ?

    (0004903)
    wbraun   
    2014-07-31 08:24   
    (Last edited: 2014-07-31 08:28)
    From my experience in an engineering company routinely working with complex models containing many parts, I strongly support parallel processing. The commercial CAD systems I know are all more or less single threaded Windows applications. As Processors these days no longer get faster, but have more cores instead, the only way to significantly improve productivity of CAD when working with complex projects seems to be to go parallel.
    With Linux effortlessly scaling from an Arduino to supercomputers and an eight core workstation being available for 500 €, a truly parallel computing CAD system running on Linux could be a killer.
    My experience with the commercial systems was that upgrading a several year old version on several year old PCs to the current version with carefully single-thred-performance-optimized PCs did not result in a noticeable performance increase. Loading and processing times of complex assemblies remained unchanged. A huge investment for nothing and very frustrating.

    (0008162)
    Kunda1   
    2017-02-02 01:07   
    Linked 0002750
    (0016416)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5581.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1391 [FreeCAD] Feature feature N/A 2014-02-07 05:25 2021-02-06 06:50
    Reporter: normandc Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.14  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Allow editing of multiple sketches at the same time
    Description: Currently, it is not possible to edit two sketches at the same time. To edit a second sketch, the user has to close the first sketch.

    It would be very useful to allow editing of more than one sketch at the same time.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0004164)
    mrlukeparry   
    2014-02-08 00:34   
    I am just wondering if this is just to do with sketcer or might be related in general to ViewProvider::setEdit()?

    If I remember there is specific dialogue warning if you try to open another sketch editor.
    (0016415)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5580.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1347 [FreeCAD] Feature feature always 2014-01-07 21:08 2021-02-06 06:50
    Reporter: bejant Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.13  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Reduce Rendering Time of Complex Objects
    Description: Reduce rendering time of complex objects resulting in faster Rotate, Pan, Zoom.

    This feature request is from the following forum thread:
    http://forum.freecadweb.org/viewtopic.php?f=3&t=5307
    Tags: slow
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0007645)
    Kunda1   
    2017-01-11 19:53   
    wmayer writes in http://forum.freecadweb.org/viewtopic.php?f=3&t=5307#p42308
    > Here the point is if you are in sketch edit mode and modify it the dependent features like pad, pocket or whatever shouldn't update automatically.

    > The request of andre is to reduce rendering time when you rotate or pan inside the 3d view because there we have for each little movement a complete redraw of the scene. For very complex objects this can be quite time consuming.

    > In the Mesh module we have implemented a way to reduce rendering time. If you have a mesh with more than 100,000 triangles then panning or rotation auto-flips to a point display. I have meshes with more than 5,000,000 triangles and panning/rotation is sufficiently fast.
    (0016412)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5577.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1095 [FreeCAD] Feature feature unable to reproduce 2013-04-12 15:40 2021-02-06 06:50
    Reporter: nikospap Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: trunk  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Free Flight View (inspection Tool)
    Description: Most of us have played First Person Shooters games.

    When you are not taking part in the battle,
    you become a "spectator",
    and can move around in the 3D world,
    in some sort of free flight mode.

    Depending on the game you might...
    a. flight/view through walls, as if you were a ghost
    b. have to go around objects (e.g. walls) as if you are a 3D being yourself.

    Having the following scenarios in mind,
    I thing option b, would work better for FreeCad.

    What's the purpose of it?

    To inspect what you have created.

    Let's say, you've created a set of interconnecting pipes,
    and want to see how the liquid would flow in them.
    With this tool you could travel in the pipes as if you were the liquid yourself.

    Or you might want to create a house.
    With this tool you could flight around within the rooms,
    pretending to be a person walking in the house.

    ________________

    More...
    I would even go as far as suggesting the use of the standard, FPS, keyboard shortcuts,
    that many people are familiar with.
    Meaning, of course, WSAD.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0003062)
    yorik   
    2013-04-13 01:40   
    Honestly I see little point on trying to do that in FreeCAD, when it is simple to export your work to an application more suited for that kind of thing, like Blender.
    (0003063)
    nikospap   
    2013-04-13 11:52   
    So what if you want to change something in your work.
    Wouldn't that mean going back to Freecad,
    make the change,
    then export again,
    then open, again, with Blender,
    and then inspect again?

    Depending on what you might want to create,
    how many times will you have to go back and forth
    between these programs?

    That doesn't seem very practical.
    (0004861)
    nikospap   
    2014-07-28 06:42   
    (Last edited: 2014-07-28 06:48)
    Please, check the second video on the following link,
    where, in the John Deere factory,
    they have created a virtual, 3D copy of the production line.
    Amongst others, they use what I refer to as a "Free Flight View"
    to inspect the production process, and make the necessary changes,
    before they even start the production!

    http://tinyurl.com/ky7cvkf

    (0005367)
    bejant   
    2014-12-11 14:37   
    This post is to provide links to similar FreeCAD developments.

    In the John Deere video nikospap referenced it looks like the user is wearing an Oculus Rift (or some similar VR device) and dev jriegel is working on support for this:
    http://forum.freecadweb.org/viewtopic.php?f=9&t=7715

    Additionally, FreeCAD forum member JMG has done something similar to a free flight view and has posted in the Users Showcase. It allows the user to define a path on which the camera travels, and then moves the camera along that path.
    http://forum.freecadweb.org/viewtopic.php?f=24&t=8437
    (0005411)
    DeepSOIC   
    2014-12-20 00:24   
    +1.
    I've seen the feature in Serious Editor and I used it... only!
    The standard CAD navigation is very usable for not-too-concave objects. But for exploring internal cavities that might be invisible from outside, free flight view is very handy. It's extremely hard to place the camera into a deep hole in an object with standard navigation.
    (0016398)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5563.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1089 [FreeCAD] Bug minor always 2013-04-08 08:51 2021-02-06 06:50
    Reporter: luigirin Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.13  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Robot Tools are not correctly placed when robot has another placement
    Description: If I place a robot on a placement different from the origin frame and then i place connect a tool, this one is placed as if the robot was in the origin position. If I connect first the tool and then I move the robot with a placement the toll goes in their original position.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016397)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5562.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    850 [FreeCAD] Feature minor N/A 2012-09-28 02:26 2021-02-06 06:50
    Reporter: jrheinlaender Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Write own and better version of BRepFeat_MakePrism
    Description: This will resolve the following problems:

    1. BRepFeat_MakePrism does not always give correct results when the UpToFace is not planar (and sometimes it even makes a difference whether the UpToFace is convex or concave!!!)

    2. BRepFeat_MakePrism with option "2" cannot generate a correct SubShape for Pocket/UpToFirst because the subtracted material is completely inside the support - so there is no added material

    3. And if we define AddShape and SubShape as reflecting not the added/subtracted material but the design intent (see separate thread I started) then we also will not be able to use BRepFeat_MakePrism any more

    and will fix the following bugs:
    0000775
    0000766

    Tags:
    Steps To Reproduce:
    Additional Information: Planned for 0.14
    Attached Files:
    Notes
    (0008735)
    Kunda1   
    2017-03-29 18:50   
    @wmayer please advise on the status of this ticket. Thanks!
    (0016393)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5558.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    798 [FreeCAD] Feature feature N/A 2012-07-19 11:37 2021-02-06 06:50
    Reporter: shoogen Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.12  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Allow to redefine the standard views
    Description: Allow to choose from diffrent possibilties to orient the standard views.
    One should be able to choose the normal axis, positive or negative orientation, and 0°,90°,180° and 270° degrees of rotation. Which leads to 3x2x4 24 choices.
    An alternative way to select the orientation is to quantisize the current/saved camera view to the nearest choice.
    As in other CAD software the front view should be the reference.
    An additional way would be a offer list of suggested, well known coordinates conventions, like the (X:Out,Y:Right,Z:Up) for Land vehicles and the FreeCAD Ship Module or (X:Out,Y:Left,Z:Down) for other craft. Or Autocad default (X:Right,Y:In,Z:Up) and Soldiworks default (X:Right,Y:Up,Z:Out)
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0002303)
    shoogen   
    2012-07-23 12:09   
    Currently the quaternions are hard coded in src/Gui/View3DPy.cpp. A possible implementation would be to save the rotation to the new TOP surface as a property of the DOCUMENT. That rotation would than the multiplies with the hard coded one.
    (0016391)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5556.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    69 [FreeCAD] Feature minor have not tried 2010-01-29 12:08 2021-02-06 06:50
    Reporter: wmayer Platform:  
    Assigned To: wmayer OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Python debugger
    Description: Add a Python debugging facility to FreeCAD.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0002765)
    wmayer   
    2012-12-29 16:37   
    (Last edited: 2013-01-02 11:06)
    External resources:
    http://hapdebugger.sourceforge.net/

    http://pydev.org/download.html
    http://pydev.org/manual_101_root.html
    http://pydev.org/manual_adv_remote_debugger.html

    http://winpdb.org/
    http://winpdb.org/docs/embedded-debugging/

    (0002834)
    wmayer   
    2013-01-09 17:42   
    (Last edited: 2013-01-09 18:06)
    See also:
    QScriptEngineDebugger
    QScriptEngine
    QScriptEngineAgent

    https://github.com/hpfem/agros2d/commit/e92e5b8f8fef3b9eb13e81a9d79d21139a36b161
    https://github.com/hpfem/agros2d/blob/master/src/pythonlab/pythonengine.h

    (0008814)
    Kunda1   
    2017-04-28 19:41   
    Proposed Python editor/debugger workbench: https://forum.freecadweb.org/viewtopic.php?f=10&t=21898
    (0009745)
    Kunda1   
    2017-07-12 18:29   
    Updates to debugger: https://forum.freecadweb.org/viewtopic.php?f=10&t=21898&start=10#p182177
    (0016375)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5540.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3904 [FreeCAD] Bug minor always 2019-03-13 08:19 2021-02-06 06:50
    Reporter: carlopav Platform:  
    Assigned To: OS:  
    Priority: low OS Version:  
    Status: confirmed Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Draft _ Delete objects while command is active
    Description: Draft _ Delete objects while command is active
    Tags: Draft
    Steps To Reproduce: set "when drawing lines set focus on Lenght instead of X coordinate" preference
    Draft
    Draw a line
    Activate a command like move
    Press "del"
    The entity is deleted and the command crash
    Additional Information: https://forum.freecadweb.org/viewtopic.php?f=23&t=34771
    Attached Files:
    Notes
    (0012911)
    Kunda1   
    2019-03-15 22:23   
    Confirmed in the forum thread
    (0016731)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5896.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3798 [FreeCAD] Feature tweak always 2019-01-26 11:19 2021-02-06 06:50
    Reporter: markus51 Platform:  
    Assigned To: OS:  
    Priority: low OS Version:  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Improve the "Sketch select" dialog of the "Map a sketch to a face" commando
    Description: When you have a lot of sketches, then it isn't easy to find
    the wanted sketch in the "Sketch select" dialog of the
    "Map a sketch to a face" commando.

    1.) Increase the size of the dropdown list of the combobox to see more sketches (a double size will be goot)
    2.) Add a check box "Alphabetical sort", when this box is selected then the entries in the
    dropdown list of the combobox will be sorted.
    3.) Add an edit field "Filter", when this field isn't empty only entries those contains the filter text are shown in the list of the combobox.
    4.) It will be good when the "Sketch select" dialog remembers the last settings (Filter+Sort) of the last call.
    Tags:
    Steps To Reproduce: 1.) Goti "Pard Desingn"
    2.) Select a plane on your model
    3.) Press "Map a sketch to a face" in the toolbar
    Additional Information:
    Attached Files:
    Notes
    (0012549)
    Kunda1   
    2019-01-29 18:11   
    Where is the forum post discussing this with the community?
    Please follow the tracker guidelines. Thanks you for your comprehension
    (0012719)
    markus51   
    2019-02-21 19:04   
    I have implemened this feature in my private version.

    It is faster to do such improvements by my own, than discuss it on this forum !
    (0012721)
    uwestoehr   
    2019-02-22 00:16   
    > I have implemented this feature in my private version.

    It would be nice if FC and user like me could benefit from this. Could you therefore open a forum thread and make a pull request so that your improvement could go in?
    (0012725)
    Kunda1   
    2019-02-22 12:03   
    @markus51 "Alone you go faster. Together we go farther"
    (0016709)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5874.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3772 [FreeCAD] General minor always 2019-01-14 11:32 2021-02-06 06:50
    Reporter: wwwutz Platform: PC  
    Assigned To: OS: Windows  
    Priority: normal OS Version: 7  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Base::Console().Warning() Color almost unreadable on status bar with standard color theme
    Description: When
    Base::Console().Warning()
    is called, the text color changes to 'orange' which is hard to read on white, but almost impossible to read on grey background.
    See attached screen crop.

    Suggested fix: make it black. [ colour visual impaired people would be pleased 8-) ]
    Tags:
    Steps To Reproduce: generate a Warning() to be logged 8-)
    Additional Information: OS: Windows 7
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.15619 (Git)
    Build type: Release
    Branch: master
    Hash: 7d8e5662648b794b5c93e28835a2bf5c1fddffec
    Python version: 2.7.14
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.2.0
    Locale: German/Germany (de_DE)
    Attached Files: freecad-warning-color.png (19,275 bytes) 2019-01-14 11:32
    https://tracker.freecad.org/file_download.php?file_id=2095&type=bug
    Notes
    (0012609)
    Kunda1   
    2019-02-10 15:54   
    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=34124
    (0016695)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5860.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3760 [FreeCAD] Feature feature N/A 2019-01-05 13:16 2021-02-06 06:50
    Reporter: Kunda1 Platform:  
    Assigned To: OS:  
    Priority: low OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Feature: Errors in sketches could be propagated up the tree
    Description: This FR comes out of 0003545 and a forum discussion


    It would be great if errors in sketches could be propagated up the tree, i.e. if a sketch contains an error, so should the enclosing feature, the enclosing body, ... . This is even more important for Part WB objects with their deep nesting.

    chrisb
    Tags:
    Steps To Reproduce:
    Additional Information: This ticket closes 0003545
    Attached Files:
    Notes
    (0016692)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5857.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3741 [FreeCAD] Bug major always 2018-12-18 20:57 2021-02-06 06:50
    Reporter: HardyW Platform: iMac  
    Assigned To: OS: macOS  
    Priority: normal OS Version: Mojave  
    Status: feedback Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: [macOS] Wrong coordinate calculation / visualisation when using Retina display
    Description: The drawn elements are wrongly shown relative to a background image when tracing elements of the image. This error only occurs on Retina displays!
    Tags: HiDPI, macOS, retina
    Steps To Reproduce: Create a new document, switch to image mode and import an image. Switch to draft mode to trace the outlines of an image.
    Additional Information: Example screen print attached.
    Attached Files: Bildschirmfoto 2018-12-18 um 21.55.45.png (1,298,185 bytes) 2018-12-18 20:57
    https://tracker.freecad.org/file_download.php?file_id=2078&type=bug
    LowResMode.jpg (193,258 bytes) 2019-01-05 15:03
    https://tracker.freecad.org/file_download.php?file_id=2088&type=bug
    Notes
    (0012310)
    Kunda1   
    2018-12-19 09:33   
    0003738:0012306
    (0012379)
    Kunda1   
    2019-01-05 11:43   
    @blacey care to weigh in?
    (0012392)
    blacey   
    2019-01-05 15:03   
    (Last edited: 2019-01-05 15:03)
    There are a number of issues related to HiDPI monitors in FreeCAD regardless of the underlying OS. https://forum.freecadweb.org/search.php?st=0&sk=t&sd=d&sr=posts&keywords=HIDPI&start=20 Some improvements were implemented during the Qt4->Qt5 transition but several are not simple fixes because supporting frameworks, such as Coin 3D, do not natively support HiDPI resolutions.

    On macOS, the most effective work-around is to run FreeCAD in low-res support by using Finder->Get Info on /Applications/FreeCAD.app and enable the "Open in Low Resolution" option.

    (0016685)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5850.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3710 [FreeCAD] Feature feature N/A 2018-12-01 06:53 2021-02-06 06:50
    Reporter: normandc Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Placement should remember "Apply incremental changes" checkbox setting
    Description: I always use the Placement utility with the "Apply incremental changes" checkbox ticked. For many users it makes the Placement utility easier to manage. Unfortunately the checkbox has to be ticked every time the utility is launched.

    There should be a parameter so that this setting is remembered.

    Feature request registered in the "FreeCAD" project as this tool is not in a specific module.
    Tags:
    Steps To Reproduce:
    Additional Information: OS: Ubuntu 18.04.1 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.15287 (Git)
    Build type: Release
    Branch: master
    Hash: 792bb8282a475905a233905a07060640456f3128
    Python version: 2.7.15rc1
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: French/Canada (fr_CA)
    Attached Files:
    Notes
    (0016675)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5840.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3637 [FreeCAD] Feature feature always 2018-10-12 17:20 2021-02-06 06:50
    Reporter: freedman Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: At FreeCAD startup; Add options to change the initial camera view and window size in Sketcher.
    Description: Add options for Sketcher to use when FreeCAD initially starts and no file has been opened.

    https://forum.freecadweb.org/viewtopic.php?f=8&t=31000

    To summerize, there are two issues, both with starting a sketch for the first time.
    1) This text from a post stated well:
    "offer a setting in Preferences --> Display to set the initial view to one of the standard views (top, right, front, left, axonometric...), but change the default from top to axonometric."

    2) This text from a post stated well:
    " the zoom is waaay to close. The whole width of the screen is about 2 mm. Suitable for designing the tiniest of parts". My screen measures 2.5 x 1.5, very small also.

    #1 above could be very helpful to the new user, they would get a much better idea of the 3D workspace.
    Thanks
    Tags:
    Steps To Reproduce:
    Additional Information: OS: Windows 7
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.14786 (Git)
    Build type: Release
    Branch: master
    Hash: 75acfe898f97d213647b0b93032287e48a31abfe
    Python version: 2.7.14
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.2.0
    Locale: English/UnitedStates (en_US)
    Attached Files:
    Notes
    (0012012)
    freedman   
    2018-10-12 17:26   
    The first line of the description should say "Add options for Sketcher to use when FreeCAD initially starts and no file has been opened.
    (0012019)
    Kunda1   
    2018-10-13 12:27   
    @freedman added
    (0016654)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5819.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3594 [FreeCAD] Feature feature N/A 2018-09-14 19:46 2021-02-06 06:50
    Reporter: rawrpenguinzombies Platform:  
    Assigned To: OS:  
    Priority: none OS Version:  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: DXF Export Units Toggle
    Description: OS: Windows 7
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.13528 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-17
    Hash: 5c3f7bf8ec51e2c7187789f7edba71a7aa82a88b
    Python version: 2.7.14
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.2.0
    Locale: English/UnitedStates (en_US)

    So this is the information off of my work build, but my personal PC is running FreeCAD on Arch Linux.

    https://forum.freecadweb.org/viewtopic.php?f=3&t=30829
    Here is link to the forum page.

    The feature I am requesting is an addition to the DXF export menu that allows the user to toggle the exported file in inches or in millimeters. Here in the US we now use both on a day to day basis in production and this would greatly expedite DXF export.
    Tags: DXF, units
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0011743)
    Kunda1   
    2018-09-14 19:55   
    Related to 0003494
    (0016640)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5805.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3554 [FreeCAD] Bug minor always 2018-08-06 16:50 2021-02-06 06:50
    Reporter: bzipitidoo Platform: PC  
    Assigned To: OS: Linux  
    Priority: normal OS Version: kernel 4.11.8  
    Status: feedback Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: fillet fails on cut torus
    Description: Been using python scripting to make parts. Fillet is finicky. Sometimes it works. Sometimes it gives an error message:

    Part.OCCError: BRep_API: command not done

    and the fillet fails. It can fail on a simple piece, but work on a more complicated shape that is other shapes fused with the simple piece.

    Investigating, the simplest fail I found so far is a cut down torus-- sliced in half like a bagel, then cut in half again. See the included python script.
    Tags: Part
    Steps To Reproduce:
    #makeFillet fails in this python script:
    
    import math
    import Part
    from FreeCAD import Base
    
    DEG2RAD = math.pi/180.0
    rd = 72
    origin = Base.Vector(0,0,0)
    znorm = Base.Vector(0,0,1)
    xnorm = Base.Vector(1,0,0)
    
    boxcorner = Base.Vector(-rd*2,-rd*2,-rd*2)
    cutbox = Part.makeBox(rd*4,rd*2,rd*4,boxcorner,znorm)
    
    fulltorus = Part.makeTorus(rd-4,4,origin,xnorm,0,360)
    halftorus = fulltorus.cut(cutbox)
    
    basecyl = Part.makeCylinder(rd+2,9,origin,xnorm)
    halftorus = halftorus.cut(basecyl)
    
    #This fillet fails
    filletht = halftorus.makeFillet(0.2, halftorus.Edges)
    Additional Information: OS: "PCLinuxOS"
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.13528 (Git) AppImage
    Build type: None
    Branch: releases/FreeCAD-0-17
    Hash: 5c3f7bf8ec51e2c7187789f7edba71a7aa82a88b
    Python version: 2.7.6
    Qt version: 4.8.6
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    Attached Files: 0003554.FCStd (7,716 bytes) 2018-10-04 09:14
    https://tracker.freecad.org/file_download.php?file_id=2008&type=bug
    Notes
    (0011599)
    Kunda1   
    2018-08-07 12:01   
    @bzipitidoo please test this on 0.18dev as well (there is an appimage). Also please, per our guidelines (yellow banner at the top) post to our forums before opening a ticket.
    (0011601)
    bzipitidoo   
    2018-08-07 13:29   
    I tested this script with makeFillet on version 0.18.14220 and 0.18_Conda Appimages. The problem with makeFillet is present in both 0.18 versions.
    (0011602)
    Kunda1   
    2018-08-07 15:36   
    please open a forum thread and post this ticket to it to start a discussion. thanks
    (0011692)
    normandc   
    2018-09-02 21:47   
    For the Python challenged, an actual FreeCAD document would be nice. I'm an experienced CAD user, I can troubleshoot models, but I need a model to do it - a python script might as well be Mandarin to me. I don't speak Mandarin. And running the aforementioned script produces zero visible result in the 3D view.
    (0011915)
    wmayer   
    2018-10-04 09:15   
    Attached is a project file with the half torus. Now go to Part, select the fillet tool and select all edges. Use a radius of 0.2.
    (0012143)
    Kunda1   
    2018-11-07 00:51   
    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=32087
    (0012170)
    normandc   
    2018-11-11 05:37   
    (Last edited: 2018-11-11 05:38)
    The problem seems to be with the inner circular edge of the half torus. Without it, all other edges fillet successfully.

    A workaround is to cut the torus slightly bigger or smaller than half. If the minor radius of the torus is 4mm, cut 0.001 from the midplane, either side works - all fillets succeed.

    I would surmise that this is an OCC issue...

    OS: Ubuntu 18.04.1 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.15169 (Git)
    Build type: Release
    Branch: master
    Hash: 7d197ce829600e308dd0e85aeb1a4ac9376ff286
    Python version: 2.7.15rc1
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: French/Canada (fr_CA)

    (0016634)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5799.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3536 [FreeCAD] Bug tweak always 2018-07-09 15:47 2021-02-06 06:50
    Reporter: Stonehenge81 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Sketcher Issue while using Windows high constrast mode
    Description: When in Windows High Contrast mode, the sketcher doesn't work as expected. When trying on a sketch, items are not visible until you either exist the sketcher or select an already existing line.

    When selecting a sketch line, it is not highlighting correctly.

    I have tried selecting different stylesheets, but the issue persists.

    These issues go away when Windows is not in high contrast mode.
    Tags: sketcher, Win
    Steps To Reproduce: - Place Windows into High Contrast mode. (left-alt + left-shift + PrintScreen).
    - Create a new sketch
    - Draw line / rectange
    Additional Information: OS: Windows 10
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.13522 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-17
    Hash: 3bb5ff4e70c0c526f2d9dd69b1004155b2f527f2
    Python version: 2.7.14
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.2.0
    Locale: English/UnitedStates (en_US)
    Attached Files:
    Notes
    (0011507)
    Kunda1   
    2018-07-09 18:35   
    (Last edited: 2018-07-09 18:52)
    @Stonehenge81 Can you recreate with 0.18dev ?
    Also please open a forum thread and link this ticket to it (+ add the thread URL to this ticket)

    (0011972)
    Kunda1   
    2018-10-08 14:18   
    @Stonehenge81 please respond

    CC @GeneFC can you please try to recreate this ?
    (0011973)
    Stonehenge81   
    2018-10-08 15:09   
    I downloaded the latest .18dev and I still experience the same issue.

    After further investigation, I noticed that the sketch (not freecad application) is unresponsive. The same unresponsiveness can be noticed when in the viewing plan. Trying to zoom in / out or rotate is extremely sluggish.

    Also, this issue, happening on an Intel system, does not happen on another computer, which is an AMD system. I'm not sure if there is any correlation, but thought I would mention it.
    (0011976)
    Kunda1   
    2018-10-08 15:38   
    @Stonehenge81 Thanks for the response. Can you post the actual v0.18dev Help > About FreeCAD > Copy to clipboard info in this ticket please?
    (0011977)
    Stonehenge81   
    2018-10-08 15:49   
    Of course, sorry for the very delayed initial reply. Also, I posted my issues on the Forum. I'll add the link once it has been approved.

    OS: Windows 10
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.14928 (Git)
    Build type: Release
    Branch: master
    Hash: 3d833e52df450cb98c1dacd0a3d17b439217a4c0
    Python version: 2.7.14
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.2.0
    Locale: English/UnitedStates (en_US)
    (0011980)
    Kunda1   
    2018-10-08 22:48   
    Confirmed bug on the forum thread
    (0012441)
    wmayer   
    2019-01-16 15:12   
    https://forum.freecadweb.org/viewtopic.php?t=31425
    (0016632)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5797.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3414 [FreeCAD] Feature feature N/A 2018-03-31 09:23 2021-02-06 06:50
    Reporter: silopolis Platform: Intel x86_64  
    Assigned To: OS: Debian 9 "Stretch" Linux  
    Priority: normal OS Version: 4.9  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Add "X-Ray" display mode
    Description: Hi,

    As suggested by @zbigg in the forum here https://forum.freecadweb.org/viewtopic.php?f=8&t=27049, having a display mode as the X-Ray one found in Sketchup would be very beneficial in a number of situations.

    Adding the possibility to snap to otherwise hidden geometries would surely ice the cake :)
    Tags:
    Steps To Reproduce:
    Additional Information:
    System Description
    Attached Files:
    Notes
    (0011337)
    Kunda1   
    2018-05-31 17:33   
    See
    https://forum.freecadweb.org/viewtopic.php?f=8&t=27049&start=10#p224664
    and
    https://forum.freecadweb.org/viewtopic.php?f=22&t=20698&hilit=x+ray&start=120#p234462
    (0012423)
    nhomar   
    2019-01-12 22:51   
    Hello.

    It is also necessary on Draft, and IMHO it is a bug not a feature.

    Snap should be available in the hidden elements from the view if not it is almos impossible to move one object in reference to the other, (Even with snap grid activated, the grid itself is hidden also).

    Thanks in advance for this tool.
    (0016615)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5780.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3405 [FreeCAD] Feature feature always 2018-03-27 03:31 2021-02-06 06:50
    Reporter: pager48 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Permit users to select any closed contour within a sketch
    Description: This will enable them to pad/pocket closed sketch contours residing in a single sketch, currently FC forces users to make a multitude of sketches to acheive the same result, it would be far more efficient to permit selection of closed contours of interest rather than making multitude of sketches.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016613)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5778.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3400 [FreeCAD] Feature feature always 2018-03-26 23:16 2021-02-06 06:50
    Reporter: pager48 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Enable showing planes from model body
    Description: It would be optimal to show planes when working with a part and selecting
    Body --> origin --> some plane
    then hitting space to show/hide
    currently they cannot be shown or hidden.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016612)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5777.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3399 [FreeCAD] Feature feature always 2018-03-26 23:08 2021-02-06 06:50
    Reporter: pager48 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Implement dimension tool
    Description: Currently freecad requires a user to select appropriate constraint tool to constrain an object. This is because no dimension tool exists, such a tool would automatically detect object type and apply appropriate constraint rather than causing user to select appropriate constraint tool every time they want to constrain an object. The dimension tool should remain enabled to permit user to dimension as many items as desired thus not having to toggle the tool for every item they need to constrain.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016611)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5776.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3397 [FreeCAD] Feature feature always 2018-03-26 22:55 2021-02-06 06:50
    Reporter: pager48 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Permit Linear pattern feature to follow guide curves
    Description: Currently it only supports following straight references, would be optimal for it to follow curved references.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0011059)
    pager48   
    2018-03-26 23:32   
    This will likely end up as a new tool.
    (0016609)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5774.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3395 [FreeCAD] Feature feature have not tried 2018-03-26 22:32 2021-02-06 06:50
    Reporter: pager48 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Turn vertex into 3D spheres with gradient coloring for optimal identification
    Description: Currently freecad has vertex points displayed as a 2D solid color. They are rather difficult to distinguish and even at times to select. The suggestion here would be to turn it into a mini 3D sphere with a gradient so its not one solid color. It identification as a vertex point would be optimal and give users an easier time dealing with them. Permit users to vary sphere size in options dialog as well.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016608)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5773.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3305 [FreeCAD] Feature feature have not tried 2018-01-08 20:10 2021-02-06 06:50
    Reporter: Kunda1 Platform:  
    Assigned To: OS:  
    Priority: low OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: QGIS + Civil Engineering integration in to FreeCAD
    Description: Thread that is tracking these topics can be found at https://forum.freecadweb.org/viewtopic.php?f=8&t=22390
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016593)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5758.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3290 [FreeCAD] Feature feature N/A 2017-12-26 12:38 2021-02-06 06:50
    Reporter: looo Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Port PySide imports to pyqt-abstraction-layer
    Description: For Qt5 we are currently using the PySide api for PySide2. This results in conflicts when used with other python libraries which depends on qt-bindings. (qt-console, spyder, matplotlib)
    qtpy [1] seems to offer a good abstraction layer which will also simplify the porting for future versions of Qt.

    [1] https://github.com/spyder-ide/qtpy#description
    Tags: pyside, Qt5
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016589)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5754.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3268 [FreeCAD] Feature major always 2017-11-21 09:31 2021-02-06 06:50
    Reporter: herrdeh Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: [feature] surface cleaner or smooth surface tool (e.g. Mesh WB's "close holes")
    Description: I'm doing mainly plastic parts, which have a shell and some internals, internals are mainly made with boxes for enforcement purpose. As plastic parts should have nice smooth rounded shapes - and boxes tend to be rectangular, the internals always will jut out of the outer surface.

    There are various methods to "sand down" these edges and outstands, we discussed this issue here: German forum thread - but it always is quite some work, and it can cause quite some trouble.

    The Mesh WB has got a nice feature "close holes" - maybe some thoughts from the code could be used for that purpose. I'd be happy to have a "surface cleaner" or "smooth surface" tool to get out of these complications

    Cheers,
    Wolf
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016583)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5748.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3219 [FreeCAD] Feature minor have not tried 2017-10-24 12:12 2021-02-06 06:50
    Reporter: Eneen Platform:  
    Assigned To: OS:  
    Priority: low OS Version:  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: [proposal] Add option to disable turntable rotation constraint
    Description: Turntable horizontal and vertical rotation constraint is really nifty feature, but it would be nice to be able to turn it off - muscle memory when going back and forth to blender adopts really long. Simple tickbox "Enable turntable constraints" below "Zoom at cursor" and "invert zoom" would make it perfect.
    Tags: constraints
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0010347)
    Kunda1   
    2017-10-24 16:24   
    As the yellow banner at the top of the bugtracker asks, please open a forum thread for this proposal to discuss with community. Then bidirectionally paste thread<->ticket or else what happens is ticket rot. Thanks!
    (0010350)
    Eneen   
    2017-10-25 08:59   
    Thx!
    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=25039
    (0016568)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5733.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3072 [FreeCAD] Feature minor N/A 2017-06-05 14:42 2021-02-06 06:50
    Reporter: keithsloan52 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Please add a function exportDXF to TopoShape
    Description: TopoShape supports the following functions.

    exportBrep, exportIges, exportStep, exportSTL

    What I really need is exportDXF.

    Thanks
    Tags: DXF, export
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0009295)
    Kunda1   
    2017-06-06 18:38   
    Is there a forum thread related so this can get more exposure?
    (0010229)
    Kunda1   
    2017-10-01 20:02   
    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=24709
    (0010361)
    yorik   
    2017-10-27 19:40   
    There is no way currently to export a TopoShape to DXF, the 3D solid geometry definition inside a DXF files are encoded as proprietary ACIS/SAT data, which we have no way to implement (it is undocumented).

    I don't think there is much here that can be done...
    (0016543)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5708.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2686 [FreeCAD] Feature feature N/A 2016-08-31 04:39 2021-02-06 06:50
    Reporter: Pauvres_honteux Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Container for points, lines, planes and surfaces
    Description:  I'd like to propose a new container (name: Geometry?) were we store anything related to; points, lines, planes and surfaces. But not anything solid related.

    This container would allow linking to/from anything within it. There will NOT be a result of the container itself. The container shall NOT have any hierark dependency to any other "geometry" containers. It will have more resemblence with a folder in an archive. Moreover it shall NOT be possible to link to the container itself.

    These containers must be freely reorganized within the visible tree and with respect to each other, visability vise.
    Tags: containers, lines, Part Design, planes, points, surfaces
    Steps To Reproduce:
    Additional Information: This picture might help a bit:
    https://catiatutor.com/images/stories/bestpractises1/image001.jpg
    Attached Files:
    Notes
    (0007300)
    Pauvres_honteux   
    2016-08-31 04:47   
    (Last edited: 2017-01-28 21:00)
    Forum discussion:
    http://forum.freecadweb.org/viewtopic.php?f=8&t=17214

    (0010806)
    Kunda1   
    2018-01-21 13:28   
    Ticket referenced also in https://forum.freecadweb.org/viewtopic.php?f=8&t=17630&start=10#p210712
    (0011535)
    Pauvres_honteux   
    2018-07-18 09:12   
    I'm adding this discussion Datum entity vs Body
    (0016497)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5662.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2462 [FreeCAD] Feature minor N/A 2016-03-02 11:15 2021-02-06 06:50
    Reporter: piffpoof Platform: Macintosh  
    Assigned To: OS: Mac OS X  
    Priority: normal OS Version: 10.6.8  
    Status: new Product Version: 0.15  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Manage Object Display Order in Tree View
    Description: This feature request is especially pertinent to models involving large numbers of objects.

    Under current versions of FreeCAD there is no option to specify in which order the objects shall be listed. Often an operation on an object will result in the resultant object (i.e. the outcome) being placed at the bottom of the object list. If the operation (e.g. Cut) is deleted than then objects previously held within the Cut are placed either at the end of the object list or at the the end of the Group (if the objects are within a Group). Where to look for the results of your operation? It is not always predictable.

    With large collections of objects, methods to manage the objects are required. One method is by creating Groups and placing objects within them. Yet with large object collections even the number of objects in a Group can be daunting. Especially if operations can remove objects from Groups.

    When working with a large number of objects such behaviour can be very annoying. Objects being worked with can be placed at the bottom of the object list, often off the screen.

    There are numbers of potential solutions to this, I've a generic approach here:

    Right-click in Tree View to Select Object Listing Order
    The user could right-click to select one of the following sort orders:
    - as is (i.e. the way FreeCAD lists objects in 0.14 and 0.15)
    - alphabetic
    - user determined order (i.e. user drags objects to desired place in the list)

    If the ability to sort objects alphabetically were available through a right-click menu option, then the user would at least know where in the list of objects to direct his attention to locate an object.
    Tags:
    Steps To Reproduce:
    Additional Information: As an example, with initial testing of the Open Street Map data importation by Microelly2, over 500 buildings can be imported. Obviously these can all be placed into a Group named "Buildings" but the problem simply happens again within the Group. With the current versions of FreeCAD the objects are listed in the order of creation, and then the ordered can be modified by certain object operations. So looking for Building 357 requires searching the complete list of 500 buildings
    forum thread is http://forum.freecadweb.org/viewtopic.php?f=8&t=13882&start=20#p111397
    System Description OS: Mac OS X
    Word size: 64-bit
    Version: 0.14.3703 (Git)
    Branch: releases/FreeCAD-0-14
    Hash: c6edd47334a3e6f209e493773093db2b9b4f0e40
    Python version: 2.7.5
    Qt version: 4.8.6
    Coin version: 3.1.3
    SoQt version: 1.5.0
    OCC version: 6.7.0
    Attached Files:
    Notes
    (0006878)
    piffpoof   
    2016-03-02 17:41   
    (Last edited: 2017-11-06 13:11)
    Thanks for detecting the duplicate Yorik - I didn't find that one.

    I have read Shawn's feature request (0002124) and it is basically the same as this one. I also read Werner's reply.

    In reading Shawn's feature request, I think he makes a good point in that such an ordering is standard in commercial packages (at least those I have worked with, I can't speak for all packages). I would also point out that scaling FreeCAD to large projects (large in the sense of being comprised from a large number of objects) is not going to be easy unless some presentation layer is introduced to manage GUI presentation of the object structures.

    (0006889)
    normandc   
    2016-03-06 20:25   
    But Shawn underscores the difficulty of adding such functionality. Safeguards must be added to prevent the end user from borking his model. In short: the system must not allow the user to reorder a feature to place it on top of a feature it's based on. This is no easy task to implement IMHO.

    One thing that will help with large projects is the work in the PartDesign-Next branch, and eventually Assembly wb allowing multiple document types.
    (0010391)
    Kunda1   
    2017-11-06 13:18   
    (Last edited: 2017-11-06 13:20)
    Merging part of 0001730
    See 0001730:0005481 and 0001730:0009438
    Ultimately this issue relies a lot on Topological Naming which has been an ongoing issue for a long time.
    http://www.freecadweb.org/wiki/Naming_project

    (0011393)
    Kunda1   
    2018-06-10 13:25   
    @realthunder responds in https://forum.freecadweb.org/viewtopic.php?f=20&t=25712&start=520
    (0016478)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5643.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2039 [FreeCAD] Feature tweak always 2015-04-07 15:10 2021-02-06 06:50
    Reporter: larsen Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.14  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Use default selection for exports
    Description: When nothing is selected and the user wants to export, FreeCAD shows a warning message. IMHO it would be useful to automatically export the latest entry from the tree.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0011934)
    Kunda1   
    2018-10-05 23:47   
    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=31377
    (0016456)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5621.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1971 [FreeCAD] Feature feature N/A 2015-02-17 10:25 2021-02-06 06:50
    Reporter: shoogen Platform:  
    Assigned To: wmayer OS:  
    Priority: high OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Boolean Operations With Multiple Arguments
    Description: Use the Boolean Operations With Multiple Arguments for the MultiFusion and MultiCommon Featues.
    Make them available from python.
    http://dev.opencascade.org/index.php?q=node/1060
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0005811)
    shoogen   
    2015-02-19 07:42   
    It seems that this is not suitable to be used for MutliCommon Features.
    The Cut function might be useful in PartDesign array Features.
    (0005899)
    shoogen   
    2015-03-21 22:12   
    http://tracker.dev.opencascade.org/view.php?id=25966 in response to http://forum.freecadweb.org/viewtopic.php?f=3&t=10225
    (0016449)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5614.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1954 [FreeCAD] Bug minor always 2015-02-08 15:31 2021-02-06 06:50
    Reporter: rockn Platform: Linux Ubuntu  
    Assigned To: wmayer OS: 14.04  
    Priority: normal OS Version: 64 bits  
    Status: assigned Product Version: 0.15  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Set colors doesn't work on objects that have edit mode reimplemented
    Description: It seem that Set colors is not working on objects that have their edit mode reimlemented (Arch, Draft, etc)
    Tags: colors
    Steps To Reproduce: Create an Arch Object (Wall, Structure...)
    Right clic on it in the tree view
    Clic on set colors
    Instead of having the task panel to change colors per faces the component task widget is open.
    Additional Information: OS: Ubuntu 14.04.1 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.15.4527 (Git)
    Branch: master
    Hash: 0da2e4c45a9a259c26abd54c2a35393e1c15696f
    Python version: 2.7.6
    Qt version: 4.8.6
    Coin version: 4.0.0a
    OCC version: 6.7.1.oce-0.16
    System Description
    Attached Files:
    Notes
    (0006736)
    jmaustpc   
    2016-01-20 14:00   
    (Last edited: 2016-01-20 14:01)
    In current master from today, "Set colours..."

    works for Draft Clone

    does not for Draft Array which give the error message "this object is not editable"

    Sets an Arch wall into task "Components of this object" and so does Arch Structure and Arch stairs.

    Building does not have "set colours" in its context menu at all.


    OS: Ubuntu 12.04.5 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.16.6240 (Git)
    Build type: Debug
    Branch: master
    Hash: fa42bc451ab6933a441d7be3680c1d17a25c33e8
    Python version: 2.7.3
    Qt version: 4.8.2
    Coin version: 3.1.3
    OCC version: 6.9.1.oce-0.18-dev

    (0006780)
    yorik   
    2016-01-31 18:15   
    I had a better look at this now, the "set colors" dialog uses the different edit modes system (setEdit() can receive a number, allowing the object to have several different edit modes.

    This is defined in Mod/Part/ViewProviderExt.cpp L694

    However, although that system works in python too (setEdit can receive a number), there is apparently no system to fall back to the C++ setEdit if the python setEdit returns False. (Gui/ViewProviderPythonFeature.cpp L415). If the python setEdit exists, the C++ setEdit is never called, no matter the returned value, unless I'm wrong...

    I thought about mimicking the ViewProviderExt above (adding a "return Gui::ViewProviderDocumentObject::setEdit(ModNum);" if the python setEdit returns False) but it's apparently not the right way to do.

    I'll investigate further
    (0007849)
    Kunda1   
    2017-01-17 20:01   
    Forum thread: http://forum.freecadweb.org/viewtopic.php?f=10&t=19989
    (0007874)
    wmayer   
    2017-01-19 13:04   
    At the moment the whole "edit modes" framework is broken by design. When setting up an edit mode for a view provider then two methods are involved:
    1. setupContextMenu where a QAction can be added to a QMenu
    2. setEdit(int) where an int of the actual edit mode is passed

    The difficulty is that inside setupContextMenu a unique integer should be set to the QAction which is still unique when a method invokes the same method of the parent class. And inside setEdit a view provider must know the edit mode numbers it must handle.

    With the current implementation when a sub-class wants to handle the edit modes of the base class it must know its implementation.

    When thinking about it I guess it would work if setupContextMenu returns an int which is the number of edit modes it handles. Then the sub-class would know from which value to start with.
    setEdit should then also return an int and depending on its value a sub-class knows if the base class handled it already.

    Example (in pseudo code):
    
    int BaseClass::setupContextMenu(menu)
      // add two modes
      int id = 0;
      QAction* act1 = menu->addAction(...);
      act1->setData(QVariant(id++));
      QAction* act2 = menu->addAction(...);
      act2->setData(QVariant(id++));
      return id; // id = 2
    
    int SubClass::setupContextMenu(menu)
      int id = BaseClass::setupContextMenu
      QAction* act1 = menu->addAction(...);
      act1->setData(QVariant(id++));
      QAction* act2 = menu->addAction(...);
      act2->setData(QVariant(id++));
      QAction* act3 = menu->addAction(...);
      act3->setData(QVariant(id++));
      return id; // id = 5
    

    
    int BaseClass::setEdit(ModNum)
     if ModNum < 2:
       // handle it
      return ModNum - 2; // the 2 is the number of modes this view provider handles
    
    int SubClass::setEdit(ModNum)
      if ModNum < 0 // the base class handled it
         return ModNum;
      if ModNum < 3:
        // handle it
      return ModNum - 3;
    

    The only important point is that a programmer has to take care to use the correct values in setEdit to be consistent with setupContextMenu. But he doesn't have to know about the implementation of the base class any more.
    (0010236)
    Kunda1   
    2017-10-02 04:42   
    Related to 0000477
    (0016446)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5611.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1818 [FreeCAD] Bug minor always 2014-11-07 14:20 2021-02-06 06:50
    Reporter: microelly2 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version: 0.14  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Bool Op representation error
    Description: A Pocket on a Box or the bool difference of two part::Box:

    two of the orthogonal views in the 3D windows have errors
    hidden inner edges are shown!


    The case pad - pocket works fine.
    Tags: #pending
    Steps To Reproduce: see the example file
    go through all ortho views
    Additional Information:
    Attached Files: error_inner_faces.fcstd (14,923 bytes) 2014-11-07 14:20
    https://tracker.freecad.org/file_download.php?file_id=859&type=bug
    Notes
    (0005288)
    quick61   
    2014-11-07 19:46   
    (Last edited: 2014-11-07 19:49)
    I think this error is being caused by a forked model. A properly constructed model does not show this problem. See the dependency graph of the attached file.

    What is being seen visually in the 3D view is not the same that is seen mathematically inside FreeCAD when projecting the 2D view from a forked model.

    (0005289)
    microelly2   
    2014-11-07 23:08   
    No, its not the fork, I have packed two cases into one file

    if you delete the pocket so that there are only the two cubes and the cut the representation error ist still there.

    the same if you delete the outer path.


    the error occurs already in the case cut: box - box
    (on my computer:

    OS: Ubuntu 14.04.1 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.15.4159 (Git)
    Branch: master
    Hash: fa3a2a0d3a7a0a619ab6323e236376bb43636e79
    Python version: 2.7.6
    Qt version: 4.8.6
    Coin version: 4.0.0a
    OCC version: 6.7.1
    (0005290)
    quick61   
    2014-11-07 23:57   
    Switch your "View from: X +ve" to "View from: X -ve" and leave "Axis aligned right: Y +ve"
    (0007893)
    Kunda1   
    2017-01-20 01:53   
    @microelly2 does 0001818:0005290 help ?
    (0008057)
    Kunda1   
    2017-01-28 13:49   
    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=10&t=20312
    (0008085)
    normandc   
    2017-01-29 17:11   
    (Last edited: 2017-01-29 17:11)
    What quick61 suggests is for the creation of 2D projected views in the Drawing workbench. The problem in this bug report relates to the 3D view. It still persists in current master when switching to a standard view. But doing a zoom "Fit All" corrects the issue and it no longer appears afterwards.

    OS: Ubuntu 14.04.5 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.9822 (Git)
    Build type: None
    Branch: master
    Hash: 0df4af4ba5e6edce825af6ecf6d024c704292633
    Python version: 2.7.6
    Qt version: 4.8.6
    Coin version: 4.0.0a
    OCC version: 6.8.0.oce-0.17

    (0008322)
    Kunda1   
    2017-02-16 14:27   
    (Last edited: 2017-02-16 14:29)
    Issue still persists in:
    OS: Ubuntu 14.04.5 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.10091 (Git)
    Build type: None
    Branch: master
    Hash: 3076b5938f3af5b7a3375c6aa8471bbacb9d6c4a
    Python version: 2.7.6
    Qt version: 4.8.6
    Coin version: 4.0.0a
    OCC version: 6.8.0.oce-0.17
    ref: https://forum.freecadweb.org/viewtopic.php?f=10&t=20312#p160229

    (0008323)
    Kunda1   
    2017-02-16 16:07   
    https://youtu.be/pCDEJtFC6rs <== screencast showing issue
    (0016437)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5602.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1792 [FreeCAD] Feature minor have not tried 2014-10-20 17:32 2021-02-06 06:50
    Reporter: quick61 Platform: All  
    Assigned To: OS: All  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Move Export 3D SVG From Export To Tools Menu
    Description: Export 3D SVG is a capture of the 3D view and does not facilitate the selection of individual objects within the document. Thus, 3D SVG export does not behave the same way as the other export formats do, including Flattened SVG.

    Therefor 3D SVG export has more in common with the Tools > Save picture function than it does with actual export functions.
    Tags: #pending
    Steps To Reproduce:
    Additional Information: FreeCAD Forum thread - http://forum.freecadweb.org/viewtopic.php?f=3&t=8099
    Attached Files:
    Notes
    (0016434)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5599.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1778 [FreeCAD] Feature feature N/A 2014-10-08 10:15 2021-02-06 06:50
    Reporter: shoogen Platform:  
    Assigned To: OS:  
    Priority: none OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: side-by-side and top-and-bottom stereo modes
    Description: Support for Side-by-Side Horizontal and Top-and-Bottom stereoscopy modes.

    Tags: stereoscopy, UI
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0005204)
    shoogen   
    2014-10-08 10:17   
    to be used with consumer tv sets.
    (0016432)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5597.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1589 [FreeCAD] Feature feature N/A 2014-06-23 04:38 2021-02-06 06:50
    Reporter: Pauvres_honteux Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: feedback Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Points, curves and surfaces
    Description: I'd like to propose a workbench for points, curves and surfaces similar to (preferably better than) what you have in the big french program.
    Tags:
    Steps To Reproduce:
    Additional Information: With such a wb one can create anything, there are no limits what so ever once you got that. Ok, time maybe.
    By the way, anyone here using that big french program at work?
    Attached Files:
    Notes
    (0010205)
    Kunda1   
    2017-09-27 17:19   
    Does OP mean something like NURBS ?
    ping @chrisb
    (0011970)
    Kunda1   
    2018-10-08 14:15   
    @Pauvres_honteux please respond
    (0011982)
    Pauvres_honteux   
    2018-10-09 05:27   
    Hi Kunda, I am having a complete surface workbench in mind. Nurbs would be a subpart of that workbench. Same goes for points and lines/curves.
    As of now it's not possible since all datums are forced "behind bars", i.e. forced to be children of the Body container. (Datums being the absolute foundation of/for everything else)
    So I guess we have to wait for that be fixed first. Hopefully it's not a big thing to fix?
    (0011988)
    Kunda1   
    2018-10-09 12:15   
    @Pauvres_honteux no idea. Please start a thread on the forum about this to deepen the discussion. Please link this ticket to it and vice versa. Thanks
    (0016425)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5590.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1141 [FreeCAD] Feature feature N/A 2013-05-28 12:32 2021-02-06 06:50
    Reporter: pfirszt Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: acknowledged Product Version: trunk  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Honeycomb, internal bone structure and bamboo
    Description: With the rise of 3D printing (cost related to volume/weight) it would be nice to have some tools to create structures like [1] honeycomb, [2] internal bone structure and [3] bamboo like structure
    [1] A "sheet" on honeycomb with parametric cell size and wall thickness could be used for boolean operation.
    [2] a lot off different size bubbles, bubbles don't overlap and size of a bubble depends on the distance from wall - closer to the wall -> smaller bubble. Something like a sponge, but with a "twist".
    [3] in a pipe: thin internal walls with smooth translation into the main pipe wall - http://www.midwestbamboo.com/images/node_removal.JPG

    1 and 3 can be made using existing tools, but 2 would require a lot of work to get a good result.
    Tags: #tobeclosed
    Steps To Reproduce:
    Additional Information:
    Attached Files: IMG_20180306_141628.jpg (199,359 bytes) 2018-03-06 13:20
    https://tracker.freecad.org/file_download.php?file_id=1849&type=bug
    IMG_20180306_141635.jpg (162,672 bytes) 2018-03-06 13:20
    https://tracker.freecad.org/file_download.php?file_id=1850&type=bug
    Notes
    (0003252)
    Jriegel   
    2013-06-26 13:01   
    Yes would be a nice feature, But I have no time for it....
    (0004155)
    bejant   
    2014-02-06 03:07   
    (Last edited: 2014-02-06 03:09)
    I think reasonable approximations could be done with modeling some types of 3D tessellations of the M.C. Escher kind: http://www.mcescher.com/gallery/symmetry/

    For case (2)above a model of a solid Box with spherical voids inside could be modeled. The trick would be to locate the voids intersected by an edge of the box in a like manner such that when the boxes are arrayed face to face those hollow spheres align with the hollow sphere of the arrayed box next to it (for each of six faces). The location of the hollow spheres that are contained wholly inside the box does not need to be precise. These boxes would be arrayed to fully encase one's model, then the boolean intersection tool could be applied to remove that portion of the 3D array outside of the model. The thickness of the model shell would fill in those voids common to the shell, and the model interior would contain the "bubbles". The user could scale the cube model to suit his / her needs, so maybe a handful of different models would be needed, each having different solid to void ratios (densities).

    Similarly, this could be done for cases (1) and (3) above but (3) would probably be more like smooth straws instead of bamboo with nodes, plates, and internodes:
    http://halfsidebamboo.info/http:/halfsidebamboo.info/wordpress/96/bamboo-plant-parts-i/

    So couldn't this be achieved by some type of model library rather than coding?

    (0004161)
    mrlukeparry   
    2014-02-08 00:17   
    we deal with lattice structures in our Research Group - although more to do with optimisation. I am not exactly sure how they are exactly handled as I am sure we use custom algorithms which use unit cells that form part of the tessellation.

    I am not confident boundary-surface representation is the best solution with these especially exporting to STL with tolerances and also numerous problems with minimum wall thickness from what I've heard and is often machine specific.

    It'd be interesting anyway if someone on was interested in tackling this.
    (0009082)
    Kunda1   
    2017-05-22 14:05   
    Honeycomb - https://forum.freecadweb.org/viewtopic.php?t=11008
    (0011016)
    herrdeh   
    2018-03-06 13:20   
    I think, this gets more and more important with 3D-printers getting so cheap that even I could afford one...

    I had a little success by abusing cura's support lattice feature and setting the "distance-to-walls" parameters to 0. And you can configure quite a lot in cura. The cura-support-lattice-abuse has some disadvantages:

    • you cannot create holes in your lattice and empty space intended to be left empty is likely to be stuffed with lattice
    • getting out the support lattice can be difficult and will leave more remainings
    • you cannot create different lattice structures for support (when printing) and enforcement of your part. But you want to have as little as necessary for support - and likely much more for enforcement.

    So, this feature should be implemented in FreeCAD.
    Couldn't we borrow some code (or concepts at least) from cura? - The support lattice feature seems to be quite elaborate there...

    Here was some discussion in German on that issue.

    Attached photos of abused cura support lattice parts. Not pretty, but amazingly firm.
    (0011349)
    Kunda1   
    2018-06-03 15:26   
    Also relevant:
    FCHoneycombMaker macro: https://forum.freecadweb.org/viewtopic.php?f=22&t=29073
    (0012231)
    pfirszt   
    2018-12-02 15:50   
    Relevant python script for FreeCAD : https://reprapltd.com/fibre/
    (0012233)
    Kunda1   
    2018-12-03 12:08   
    Not sure where this should go? Probably in the FreeCAD-macros repo..right ?
    (0012234)
    pfirszt   
    2018-12-03 12:13   
    I guess it's a good idea.
    (0012240)
    Kunda1   
    2018-12-05 13:25   
    Mentioned in https://github.com/FreeCAD/FreeCAD-macros/issues/6
    (0016399)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5564.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    573 [FreeCAD] Feature feature unable to reproduce 2012-01-17 20:09 2021-02-06 06:50
    Reporter: pperisin Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.12  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Macro editing FCMacro file - 4 improvements
    Description: Hi,

    I have three improvements suggestion that would help people in scripting

    1 - auto indent - if the line I'm writting something in has i.e. 6 spaces before first character, when I press enter I go to the next line but at it's beginning. I would like to have 6 spaces automatically added when I press enter in this case.

    2 - multi line editing - The easiest way to explain this one is if you open some document in notepad++. then press ALT key and select multiple lines. you will see how it selects in a row+column like way. Also, when you have stuff selected this way, writting anything will add those characters to all those selected lines.

    3 - code completition and a list that appears after you press '.' - like the one in python console

    4 - Find and replace text
    Regards,
    Petar
    Tags: #lowhangingfruit, macros, split ticket
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0001586)
    pperisin   
    2012-01-18 06:00   
    oh, another one - Find and replace text
    (0008171)
    Kunda1   
    2017-02-02 14:15   
    Reminder sent to: mandeep7
    Do you have any interest working on these features at all ?
    (0008826)
    Kunda1   
    2017-04-29 12:54   
    Check out @mumme work in https://forum.freecadweb.org/viewtopic.php?f=10&t=21898
    (Also attached 0000069 to this ticket)
    (0016386)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5551.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    503 [FreeCAD] Feature minor have not tried 2011-11-30 07:15 2021-02-06 06:50
    Reporter: wmayer Platform:  
    Assigned To: wmayer OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Measurement framework
    Description: Forum thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=1965
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0002327)
    Jriegel   
    2012-08-23 09:19   
    We need a bit more for a "Framework" :)
    I would put that in the code snipped of the Wiki...
    (0002894)
    wmayer   
    2013-02-11 13:40   
    http://forum.freecadweb.org/viewtopic.php?f=10&t=3549&start=20
    (0003331)
    wmayer   
    2013-07-05 07:26   
    (Last edited: 2014-01-08 20:10)
    http://forum.freecadweb.org/viewtopic.php?f=3&t=4225&start=10

    (0004033)
    mrlukeparry   
    2014-01-08 20:12   
    The Drawing Module I am working on has the facility for measurements and basic statistics that could be extended. This is in a separate module Measure and has python bindings too.
    (0005755)
    wmayer   
    2015-02-01 17:02   
    http://forum.freecadweb.org/viewtopic.php?f=8&t=9561&p=77531#p77531
    (0010292)
    wmayer   
    2017-10-11 13:14   
    https://forum.freecadweb.org/viewtopic.php?f=22&t=24835
    (0011660)
    Kunda1   
    2018-08-26 00:34   
    (Last edited: 2018-08-26 00:36)
    Hey @easyw-fc does Manipulator WB address this ?

    Edit: fixed old sourceforge phpBB url in the ticket summary to point to correct thread.

    (0016384)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5549.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    494 [FreeCAD] Feature minor always 2011-11-27 05:37 2021-02-06 06:50
    Reporter: normandc Platform:  
    Assigned To: wmayer OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Objects names in Label & Attributes Tree View should be translatable
    Description: Currently, all the GUI tools can be localized in other languages than English, either in menus or the toolbars. But the names of the objects created with these tools, in the Tree view under Labels & Attributes remain in English.

    It would avoid confusion to users and enhance the user experience if those objects' names could be translated as well.

    EDIT: So, to be clear, this ticket is about translating default names for items to the local language on object creation. ( 0000494:0006953 )
    This ticket is not about being able to translate said items post object creation.
    Tags: #lowhangingfruit, translation
    Steps To Reproduce:
    Additional Information: EDIT: Also, at this time, only Part Primitive labels are translatable. All other FreeCAD objects are missing:
    Arch,
    Draft,
    PartDesign, and so on.
    Attached Files:
    Notes
    (0001356)
    Jriegel   
    2011-11-27 17:56   
    Its perfectly possible to set the Label property with a translated
    text in the command which create the object.
    But we have to take into account that then its hard to exchange
    document with other people... They will see names which means nothing to them...

    I would not do it for the 0.12!
    (0001359)
    normandc   
    2011-11-27 18:09   
    (Last edited: 2011-11-27 18:12)
    I hadn't thought of that.

    I wonder if those object text strings could be translated on the fly like the rest of the GUI? That they would appear in the language set in FreeCAD?

    If I recall, that's how Solid Edge works, but I haven't used a French version of the software for a couple of years. I believe that the features names would be translated in the software locale, but I can't be sure.

    Still, as it is, the users create features of which names mean nothing to them if they don't have a working knowledge of English.

    (0006948)
    ian.rees   
    2016-04-06 07:01   
    Just trying to think through how this might work:

    1) French user creates Cylindre and Cylindre001 in a new file, saves it and sends to English user
    2) English user opens file and sees Cylinder and Cylinder001
    3) English user fuses Cylinder and Cylinder001 together, to create Fusion. Re-saves file and sends back to French user.

    What does the French user see when they open the document and expand the object in it?

    If the French user opens the file from the English user and saves it again without explicitly modifying anything, do we want the file to change?

    Another user makes a drawing of an engine, and calls an object in it "Cylinder". Does that object's name get translated when the file is shared in other languages?

    One corner case: If I'm using English FreeCAD and make a document with an object named "Cylindre" and another named "Cylinder" and send it to a French user, I think we need to make sure that Cylinder gets translated to Cylindre001. AFAIK object names need to be unique.
    (0006950)
    wmayer   
    2016-04-06 12:50   
    IMO, it's sufficient to translate the text on object creation and leave it afterwards as is. This means if an English user gets the project of a French user he will get the French text.

    Also advanced users usually change the default label to something more meaningful and such text cannot be translated into another language anyway.
    (0006951)
    ian.rees   
    2016-04-06 21:29   
    OK, so should we close this ticket then? From what I understand, the primitives are now translated on creation, though haven't confirmed myself. http://forum.freecadweb.org/viewtopic.php?f=10&t=10497&start=30
    (0006952)
    normandc   
    2016-04-06 22:09   
    I agree with wmayer. I will add that even if you were to open a FreeCAD file made by somebody else with labels in a language you don't understand, you always have the icons to tell you the type of object. Back when I wrote this report, it was not the case.

    But why close the ticket? At this time, only Part Primitive labels are translatable. All other FreeCAD objects are missing: Arch, Draft, PartDesign, and so on. Therefore most of the job is not even done yet.
    (0006953)
    ian.rees   
    2016-04-06 22:19   
    Ahh, I got a bit confused by the example in the forum where everything is translated. So, I thought the bug was about translating names after they're created, not about creating things with localised names.

    So, to be clear, this ticket is about translating default names for items to the local language.
    (0006954)
    normandc   
    2016-04-06 22:22   
    Yes, that's it.
    (0007837)
    Kunda1   
    2017-01-17 11:55   
    I updated the 'Description' and 'Additional Information' of this ticket for more clarity.
    What Workbenches are left to be translated? We can keep track of them in the 'Additional Information' field
    (0010957)
    normandc   
    2018-02-13 02:59   
    As per my 2016-04-06 comment: all of them apart from Part primitives.
    (0012021)
    normandc   
    2018-10-13 20:36   
    Removed "I don't know if this would be possible for 0.12 release..." from description as this obviously didn't make it. And 7 years later with a boatload of new commands added since 2011, this will be a MUCH BIGGER job.
    (0016382)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5547.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    5 [FreeCAD] Feature minor have not tried 2009-09-28 09:17 2021-02-06 06:50
    Reporter: Jriegel Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: acknowledged Product Version: 0.8  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Navigator
    Description: The Navigator is a kind of Manipulator to move FreeCAD objects visually.
    Its basically inspired by the Catia V5 Compass.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0000483)
    pperisin   
    2011-01-04 14:06   
    Hi,

    NaroCAD has similar thing. It is called gizmo:

    http://www.youtube.com/watch?v=Djd6LqdOEvM&NR=1
    http://www.youtube.com/watch?v=TCRO8xxojnU&feature=related

    Regards
    Petar Perisin
    (0011423)
    Kunda1   
    2018-06-13 13:27   
    Unassigning Jriegel
    (0016372)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5537.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4142 [FreeCAD] Feature feature N/A 2019-09-24 09:21 2021-02-06 06:50
    Reporter: Kunda1 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Start WB could report more details when highlighting an FCStd file
    Description: sliptonic makes a great point in his YT clip [1] about the StartWB adding the ability to report more information on a file when highlighting or hovering over it.

    [1] https://youtu.be/uKD6sGdci4Y?t=189

    The whole segment starts at https://youtu.be/uKD6sGdci4Y?t=53
    Another interesting part https://youtu.be/uKD6sGdci4Y?t=114
    Tags: Start Workbench
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016826)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5992.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4133 [FreeCAD] Bug major have not tried 2019-09-17 04:08 2021-02-06 06:50
    Reporter: bug_reporter_00342 Platform: Linux  
    Assigned To: OS: Ubuntu  
    Priority: normal OS Version: 18.04.3 LTS  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Sometimes face / sketch exports to flattened svg or dxf incorrectly
    Description: I've been seeing this bug very occasionally I believe since 0.16, seemingly at random. Trying to export a particular sketch as a flattened svg or dxf truly flattens the constituent paths such that they lie on top of each other when they should not. It may be that the paths are being projected along the wrong (90deg) axis to produce the exported vector image.
    Trying to export a clone or facebinder of the relevant sketch then exporting produces the same results.
    Tags: #pending-forum, DXF, export, SVG
    Steps To Reproduce: Open attached FCStd file, try to export Sketch002 as Flattened SVG or DXF. View exported file in Inkscape or similar, visually compare to original sketch.

    For reference, Sketch001 exports fine. Rotating the body of Sketch002 by 90deg to lie parallel to the plane of Sketch001 does not solve the issue.

    Tried in 0.17, 0.18, and 0.19 Daily with the same results.
    Additional Information: OS: Ubuntu 18.04.3 LTS (ubuntu:GNOME/ubuntu)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.
    Build type: Release
    Python version: 3.6.8
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    Attached Files: cant_export_Sketch002.FCStd (40,528 bytes) 2019-09-17 04:08
    https://tracker.freecad.org/file_download.php?file_id=2346&type=bug
    Notes
    (0013615)
    bug_reporter_00342   
    2019-09-17 17:21   
    Workaround is to pad the sketch, export the pad as a STEP file, open the STEP file in a new FreeCAD document, recreate the original sketch by tracing out the face using external geometry, then export the new sketch as SVG or DXF.

    This workaround does not support sketches that cannot currently be padded, such as those which would produce multiple solids.
    (0013616)
    Kunda1   
    2019-09-17 20:13   
    Thanks for posting. Do you mind (per the guidelines in the yellow banner at the top of the page) to post this issue to the forum to get the attention of the community. Thank you.
    (0013636)
    bug_reporter_00342   
    2019-09-19 00:14   
    (Last edited: 2019-09-19 00:14)
    Yep, no worries, I'll make a forum post. I did see the yellow banner, but the text by the Description text field currently reads:
        
    Read this before reporting and make a forum thread asking for help first if you aren't sure it's a bug!
    I was pretty confident that this is a bug, so I posted without the forum thread. Perhaps the text could be changed if a forum post is always desired.

    (0013640)
    Kunda1   
    2019-09-19 02:53   
    @bug_reporter_00342
    Thanks for posting to the forum, in the future please x-post the url back to the ticket so we can track the thread from the ticket. thanks

    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=3&t=39441
    (0013690)
    Kunda1   
    2019-09-27 10:48   
    Apparently, similiar discussion at https://forum.freecadweb.org/viewtopic.php?f=3&t=33708
    (0016824)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5990.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4073 [FreeCAD] Bug major always 2019-07-30 03:40 2021-02-06 06:50
    Reporter: Orcaman42 Platform: MacOSX  
    Assigned To: OS: 10.15  
    Priority: normal OS Version: 10.15  
    Status: feedback Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: [MacOSX Catalina] Unable to save (most likely due to security permissions)
    Description: If you close the start page, then try to save a file, No save as window opens. Looking at thee file history there's nothing there that the file even previously existed either.

    I don't think asking for help will work since users don't really safe files outside of using command S or the File menu.
    Tags: macOS
    Steps To Reproduce: Make a new file, draw something. Close the start window & save your document. No Save As window opens, no save happens. Search for a file "Untitled.FCStd" & nothing.
    Additional Information: OS: macOS 10.15
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16131 (Git)
    Build type: Release
    Branch: (HEAD detached at 0.18.3)
    Hash: 3129ae4296e40ed20e7b3d460b86e6969acbe1c3
    Python version: 3.6.7
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    Attached Files:
    Notes
    (0013394)
    Kunda1   
    2019-07-30 12:51   
    @Orcaman42 cant reproduce. How do you draw something without changing to another workbench (I'm still in Start WB). Also, next time please open a forum thread before opening a ticket (per our guidelines in the large yellow banner at the top of the page)

    OS: Manjaro Linux
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16131 (Git)
    Build type: Release
    Branch: makepkg
    Hash: 3129ae4296e40ed20e7b3d460b86e6969acbe1c3
    Python version: 3.7.3
    Qt version: 5.13.0
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/United States (en_US)
    (0013407)
    JuM1697   
    2019-08-08 19:44   
    Hi!
    I can confirm that issue. And I might know the reason: With MacOS Catalina Apple asks you to give every Application permissions to access your folders to read/write files. Usually a prompt opens and asks for adjustment of the security settings when the application is trying to access files for the first time. This prompt doesn't appear!

    OS: macOS 10.15
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16131 (Git)
    Build type: Release
    Branch: (HEAD detached at 0.18.3)
    Hash: 3129ae4296e40ed20e7b3d460b86e6969acbe1c3
    Python version: 3.6.7
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: German/Germany (de_DE)
    (0013413)
    Kunda1   
    2019-08-12 17:06   
    @JuM1697 please create a forum thread in the Help subforum referencing this ticket for discussion.
    (0013418)
    JuM1697   
    2019-08-12 18:50   
    Okay, done!
    (0013421)
    chrisb   
    2019-08-12 21:03   
    This is the forum discussion thread.
    (0013680)
    Kunda1   
    2019-09-24 09:27   
    (Last edited: 2019-09-24 09:27)
    another thread sprung up: https://forum.freecadweb.org/viewtopic.php?f=4&t=39587

    (0016805)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5971.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4046 [FreeCAD] Bug minor always 2019-07-02 12:50 2021-02-06 06:50
    Reporter: openBrain Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Implementation flaw in View/Show all objects
    Description: The command "Show all objects" found in View -> Visibility not always makes visible the last operation in a PartDesign Body.

    Forum thread
    Tags: 0.18, GUI
    Steps To Reproduce:
    1. Open the attached file
    2. Select View -> Visibility -> Show all objects => 'Draft' is incorrectly made visible instead of 'Pad003'
    Additional Information:
    OS: Ubuntu 18.04.2 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.1.
    Build type: Release
    Python version: 2.7.15rc1
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: French/France (fr_FR)

    OS: Ubuntu 18.04.2 LTS (KDE/plasma)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19. // 2019/06/29
    Build type: Release
    Python version: 3.6.8
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: French/France (fr_FR)

    OS: Windows 8.1
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.17171 (Git)
    Build type: Release
    Branch: master
    Hash: d19470a9711ea604f3ca6c93e46afadf64d5bb87
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: Bulgarian/Bulgaria (bg_BG)
    Attached Files: allVisibleBug.FCStd (22,139 bytes) 2019-07-02 12:50
    https://tracker.freecad.org/file_download.php?file_id=2253&type=bug
    Notes
    (0016797)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5963.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4014 [FreeCAD] Bug major always 2019-06-10 12:13 2021-02-06 06:50
    Reporter: openBrain Platform:  
    Assigned To: sgrogan OS:  
    Priority: immediate OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Build number & hash are no more available on daily build (Linux)
    Description: Build number & hash that identifies FreeCAD release are no more available in Linux daily builds.
    Windows builds seems to not have the same problem.
    ---
    Forum thread (FR)

    Dedicated thread opened
    Tags:
    Steps To Reproduce:
    1. Open FreeCAD
    2. Click on "Help" -> "About FreeCAD" -> "Copy to clipboard"
    3. Paste anywhere you want
    Additional Information: Example with latest daily build as of today :
    OS: Ubuntu 18.04.2 LTS (KDE/plasma)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.
    Build type: Release
    Python version: 3.6.7
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: French/France (fr_FR)
    Attached Files:
    Notes
    (0013170)
    openBrain   
    2019-06-10 12:14   
    I tagged it with high importance/priority as it's a really useful function at forum discussions.
    (0013172)
    Kunda1   
    2019-06-10 17:34   
    Punting to @sgrogan
    (0013298)
    openBrain   
    2019-06-22 16:27   
    Priority --> Urgent according this thread
    (0013299)
    Kunda1   
    2019-06-22 18:49   
    @kkremitzki Can this be fast tracked ?
    (0013301)
    kkremitzki   
    2019-06-23 05:27   
    @Kunda1 I don't have the bandwidth to try to find a solution for this right now, but I am keeping an eye on the issue to help implement it once a solution is found, or if anyone has questions about the current build automation.
    (0016779)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5945.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4002 [FreeCAD] Feature feature N/A 2019-06-06 00:23 2021-02-06 06:50
    Reporter: ifohancroft Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: [Feature Request] Revit rotation stop on Scroll Release
    Description: Currently, rotation in Revit navigation style works the following way:

    1. To rotate, start moving the mouse while holding Shift+Scroll.
    2. If you release just Shift and you keep moving - you are no longer rotating. You are panning.
    3. If you release just the Scroll and you keep moving - you are still rotating.
    4. To stop rotating, you need to release both Shift and Scroll.

    I am coming from Blender and while the Revit mode works the way I have setup my Blender config, the details above confuse me very much and using both FreeCAD and Blender it would feel more comfortable for them to have them work the same way.

    Here's what changes I am suggesting to the steps above and why they would be helpful in practice:

    1. To rotate, start moving the mouse while holding Shift+Scroll <- This one stays the same.
    2. If you release just Shift and you keep moving - you are still rotating. <- No need to having to hold shift forever once you've entered rotation mode. You can let go of it.
    3. If you release just the Scroll and you keep moving - you are moving the mouse freely (no rotation, no panning) <- This is the main idea and main change I would like to see. The idea behind is so that you can readjust your mouse and by pressing scroll again you continue your rotation.
    4. To stop rotating, you need to release both Shift and Scroll <- This is like it currently is, also it is like the proposed 0000003 but then you don't press scroll again and you let go of Shift so it's not really a separate step in a way.

    TL;DR: When you release just Scroll during rotation, you should be able to move the mouse freely instead of continue to be in rotation mode.
    Ideally, also: When you release just Shift, you should still be in rotation mode.

    I think No.2 from the proposed changes (being able to still rotate while letting go of Shift) may affect the following:
    Currently, if you are panning and you start holding shift, now you are rotating. I believe implementing 0000002 from the suggested changes may stop this form working this way.

    Forum post
    Tags: keyboard, mouse, navigation, rotate
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0013145)
    ifohancroft   
    2019-06-06 00:27   
    Above, where it says 0000003 or 0000002 that's meant to mean point 2 or 3 of the points mentioned. (Maybe we need the ability to edit our tickets after we've posted them.
    (0016776)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5942.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3999 [FreeCAD] Bug major always 2019-06-02 03:23 2021-02-06 06:50
    Reporter: ifohancroft Platform: x86_64  
    Assigned To: OS: Fedora  
    Priority: normal OS Version: 29  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Toolbars get disabled on file open if 'Close & switch on opening file' is enabled
    Description: Summary:

    If you set FreeCAD's option 'Switch workbench after loading' to 'Part Design' and enable the option 'Close & switch on opening file', when you open a FreeCAD project file by double clicking on the file, when FreeCAD starts, the toolbars 'File, 'Workbench', 'Macro', 'View', 'Structure' and 'Navigation' wil be disabled.

    You can see the toolbars for a second when FreeCAD starts and then dissapear (the whole second row of toolbars and those that are on the first row, dissapear as well. Tested with more than one FreeCAD project file.

    System info:
    Fedora 29 64 bit with XFCE as a desktop environment
    uname -a output: Linux localhost.localdomain 5.0.17-200.fc29.x86_64 #1 SMP Mon May 20 15:39:10 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
    Tags: file, options, preferences, start, toolbar, UI, workbench
    Steps To Reproduce: 0. Backup your FreeCAD config files to not lose your current configuration
    1. Open FreeCAD
    2. Go to Edit -> Preferences -> Start
    3. Change 'Switch workbench after loading' from 'Start' to 'Part Design' (haven't tested if selecting a workbench different than 'Part Design' makes a difference
    4. Enable the option 'Close & switch on opening file' (this is irregardless of whether the option 'Close start page after loading' is enabled or not)
    5. Hit ok (or apply and ok, it doesn't matter)
    6. Close FreeCAD
    7. Find a FreeCAD project file in your files using your file manager and double click it (or I guess single click if you have set your file manager to use single click for file opening)
    8. You will see the toolbars in question for a second and then you will see them dissapear. (Now, since the Navigation toolbar isn't usually present/enabled in Part Design anyway, you can verify that it also dissapears as well as you first check the Start workbench and see it is enabled there, if after you reproduce the bug you go to Start again, you will see it is also one of the disabled toolbars)
    9. To reproduce the bug again or to reset FreeCAD's enabled toolbars, delete everything in both $HOME/.FreeCAD and $HOME/.config/FreeCAD (haven't tested which config files keeps the toolbars options and the Start options) Keep in mind that deleting those files will reset every FreeCAD setting for your user.
    Additional Information: OS: "Fedora release 29 (Twenty Nine)"
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.Unknown (0.18.2 according to the Fedora repo package info)
    Build type: Unknown
    Python version: 3.7.3
    Qt version: 4.8.7
    Coin version: 3.1.3
    OCC version: 6.9.1.oce-0.18
    Locale: English/UnitedStates (en_US)
    (It was installed from the Fedora repo via DNF)
    Attached Files:
    Notes
    (0013136)
    Kunda1   
    2019-06-02 12:33   
    Thank you for the ticket. Some orientation on how to use our bugtracker: read the giant yellow banner at the top of the page. We ask you to open a forum thread first to discuss your issue on the forum before opening a ticket. Many issues are solved this way. Also please do not create tags if they don't exist.

    Now please create a forum thread and cross link ticket<->thread so we can track this issue's progress. Thank you for your comprehension.

    FYI, you are using an out of date version of 0.18 that isn't py3/qt5 and has obsolete dependencies.
    (0013141)
    ifohancroft   
    2019-06-03 01:18   
    (Last edited: 2019-06-03 07:03)
    I am sorry. I did read the How to submit bugs but thought making a post is only required for feature requests.
    I had a checkmark on 'Existing tags' so I thought that it wouldn't let me set a tag if it doesn't exist. I will create a thread as soon as I get on my pc.
    The version is the latest from the Fedora repo and it was in-fact updated the other day but I am after all one Fedora version behind. I will look into building FreeCAD from source.
    Forum post
    P.S. Bug still present in FreeCAD 0.19 compiled from git following the out of source build compile guide in CompileOnUnix

    OS: "Fedora release 29 (Twenty Nine)" (XFCE/xfce)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.16886 (Git)
    Build type: Unknown
    Branch: master
    Hash: ed47e962d2c821bf1792889f6d7bdf457dcf6c9e
    Python version: 2.7.15
    Qt version: 4.8.7
    Coin version: 3.1.3
    OCC version: 6.9.1.oce-0.18
    Locale: English/UnitedStates (en_US)

    P.P.S. In the ticket description, where I've written 'Test with more than one FreeCAD project file.' it should be 'Tested with more than one FreeCAD project file.'

    (0013227)
    Kunda1   
    2019-06-17 06:12   
    @ifohancroft so is this still an issue because you were using python2 instead of py3 ?
    (0013256)
    ifohancroft   
    2019-06-18 17:05   
    @Kunda1 Yes. It is still a problem, even with the Appimage:

    OS: Fedora 29 (Twenty Nine)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16117 (Git) AppImage
    Build type: Release
    Branch: (HEAD detached at 0.18.2)
    Hash: dbb4cc6415bac848a294f03b80f65e888d531742
    Python version: 3.6.7
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    (0016775)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5941.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3994 [FreeCAD] Bug crash always 2019-05-30 19:20 2021-02-06 06:50
    Reporter: RICCARDO Platform:  
    Assigned To: OS:  
    Priority: urgent OS Version:  
    Status: feedback Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: zoom unstable
    Description: cambia visuale in automatico, sparisce tutto dopo qualche secondo, perde il centro schermo

    English:
    changes view automatically, disappears after a few seconds, loses the screen center
    Tags:
    Steps To Reproduce: aprire file esempio
    fare scorrere il mouse sullo schermo
    si nota la scomparsa dell'immagine, e la rotazione parziale del Gestore visuale 3d in alto a dx

    English:
    open example files
    slide the mouse on the screen
    note the disappearance of the image, and the partial rotation of the visual 3D manager at the top right
    Additional Information: OS: Windows 7
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16110 (Git)
    Build type: Release
    Branch: (HEAD detached at upstream/releases/FreeCAD-0-18)
    Hash: f7dccfaa909e5b9da26bf50c4a22ccca9bb10c40
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: Italian/Italy (it_IT)
    Attached Files:
    Notes
    (0013231)
    Kunda1   
    2019-06-17 06:46   
    @RICCARDO Can you reproduce this on 0.19_pre ?
    Also please follow our guidelines (big yellow banner at the top of this page). Please also use english language in the bug reports. Thank you
    (0013451)
    Kunda1   
    2019-08-22 20:31   
    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=38759
    (0013455)
    Kunda1   
    2019-08-23 00:22   
    @RICCARDO no example files were attached.
    (0016771)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5937.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3990 [FreeCAD] Bug minor always 2019-05-28 18:31 2021-02-06 06:50
    Reporter: bzb.dev001 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Placement dialog fails after click on 3d view
    Description: When the Placement dialog is opened, clicking on 3d view and using the number key to select a different view, causes the dialog box to be inoperative. Ie. changing values in the Placement dialog does not correspond to positional changes in the solid in 3d view.

    reference discussion: https://forum.freecadweb.org/viewtopic.php?f=3&t=36665
    Tags:
    Steps To Reproduce: Create Body
    Create a sketch
    Create Pad feature on sketch.
    Click on Body in Combo view
    Open Placement dialog
    changing translation values for x,y,z show solid moving in 3d view...This is expected
    click on some area in 3d view
    now change translation values for x,y,z...Notice the solid does not move to correspond to new specified position
    Changing any value in both the Translation section, Center section and Rotation section of dialog does nothing

    If I were to click on "selected points" button, a notification message is shown. Once I click on the "ok" button to close it, changing the values in Center section of Placement dialog cause the solid to move. This is unexpected.
    Additional Information: OS: Ubuntu 18.04.2 LTS (LXDE/Lubuntu)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.16718 (Git) AppImage
    Build type: Release
    Branch: master
    Hash: cfd04ac6afa091f5c4f18e94756bd58fb6d66806
    Python version: 3.7.1
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/Canada (en_CA)
    Attached Files:
    Notes
    (0013126)
    Kunda1   
    2019-05-29 19:33   
    confirmed by chrisb in the forum thread
    (0016770)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5936.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3966 [FreeCAD] Feature feature N/A 2019-05-12 21:34 2021-02-06 06:50
    Reporter: sliptonic Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Support switching the inputfield unit scheme per control explicitly in Python
    Description: I would like to be able to set the unit scheme for an inputfield on a form independent of what the user has selected for their global preference.
    Tags:
    Steps To Reproduce:
    Additional Information: https://forum.freecadweb.org/viewtopic.php?f=10&t=36330&sid=ef4c25d766469e16b55051bf43b4209c
    Attached Files:
    Notes
    (0016763)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5929.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3948 [FreeCAD] Bug major always 2019-04-27 10:56 2021-02-06 06:50
    Reporter: seppelw Platform: x86 64 Bit  
    Assigned To: OS: Windows  
    Priority: normal OS Version: 7 and 10  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Part-Container: Moved Part container with objects, shapeblinder links to nothing
    Description: When having Objects within a moved part-container, it is not possible to create a shapebinder that is automatically linked to the object implicitly moved by the part-container.

    https://forum.freecadweb.org/viewtopic.php?f=3&t=35938
    Tags:
    Steps To Reproduce:
     1) Add 3 Solids, Cube, Cylinder, Cone
     2) Place each in an individual part
     3) Move the parts
     4) Add a new Body
     5) Add Facebinders to the Objects
    Result) The Facebinder is not linked tot he object in the part-container.

    Additional Information:
    Attached Files: Bug.FCStd (13,772 bytes) 2019-04-27 10:56
    https://tracker.freecad.org/file_download.php?file_id=2200&type=bug
    Bug.png (167,769 bytes) 2019-04-27 10:56
    https://tracker.freecad.org/file_download.php?file_id=2201&type=bug
    Notes
    (0013065)
    Kunda1   
    2019-04-27 11:50   
    Please always add you Help > About FreeCAD > Copy to clipboard info to any ticket, per our guidelines (yellow banner top of page)
    (0013342)
    seppelw   
    2019-07-14 19:28   
    OS: Windows 10
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16093 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-18
    Hash: 690774c0effe4fd7b8d2b5e2fb2b8c8d145e21ce
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: German/Germany (de_DE)
    (0013347)
    openBrain   
    2019-07-15 16:46   
    @seppelw this version is outdated (even in the 0.18 branch) so no real interest to confirm bug with it.
    For ones landing here, you can give a try to PlacementAbsolufy Macro that will reset Part containers to origin of Global Coordinate System while preserving objects position.
    (0016755)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5921.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3947 [FreeCAD] Bug major always 2019-04-27 10:49 2021-02-06 06:50
    Reporter: seppelw Platform: x86 64 Bit  
    Assigned To: OS: Windows  
    Priority: high OS Version: 7 and 10  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Part-Container: Moved Part-Container do not effect contained objects
    Description: FreeCAD is not able to handle Objects in moved Part-Container and always refers to the origin of the object in the container.


    https://forum.freecadweb.org/viewtopic.php?f=3&t=35938
    Tags:
    Steps To Reproduce: Bug:

     1) Add 3 Solids, Cube, Cylinder, Cone
     2) Place each in an individual part
     3) Move the parts
     4) Set the current working plane to the face of the Cube
     Result) FreeCAD is not able to work with Part-container

     There is no reason why that should happen.
    Additional Information:
    Attached Files: Bug_2.FCStd (8,217 bytes) 2019-04-27 10:49
    https://tracker.freecad.org/file_download.php?file_id=2198&type=bug
    Bug_2.png (221,917 bytes) 2019-04-27 10:49
    https://tracker.freecad.org/file_download.php?file_id=2199&type=bug
    Notes
    (0013060)
    seppelw   
    2019-04-27 11:08   
    P.S. As openBrain concluded: .....the pity is that FC misses the feature of being able to work inside an active part container.
    (0013067)
    seppelw   
    2019-04-27 13:08   
    Part-containers with it's placement should allow nesting and the actual position in space of the actual object should be calculated accordingly(derived).

    For visualization that is the case, when moving the part-container the displayed solid in it moves according to the move of the part-container. However, when it comes to shape-binders, working-planes etc. the behaviour does not match the display-position/behaviour, it is implemented differently, the functions use a wrong position.

    The display is correct but the functions such as working-plane, shape-binders use a falsely calculated position, different from the display breaking the WYSIWYG concept.
    (0013343)
    seppelw   
    2019-07-14 19:28   
    OS: Windows 10
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16093 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-18
    Hash: 690774c0effe4fd7b8d2b5e2fb2b8c8d145e21ce
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: German/Germany (de_DE)
    (0016754)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5920.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3920 [FreeCAD] Feature feature N/A 2019-03-27 09:02 2021-02-06 06:50
    Reporter: Jee-Bee Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: change orientation views related to XYZ planes
    Description: I would request a option to change the direction of the views
    default front is x to the right and z to the top.
    but in some use cases or norms the default directions are different.
    It would be great to change these views according to what is needed.

    I also created a topic in case of discussion. see https://forum.freecadweb.org/viewtopic.php?f=8&t=35257

    I added 3 pictures as solutions in CREO and in inventor
    Tags: GUI, navigation, navigation cube, UI
    Steps To Reproduce: not applicable
    Additional Information: I added 3 pictures as solutions in CREO and in inventor
    Attached Files: creo_set_view_1.PNG (9,847 bytes) 2019-03-27 09:02
    https://tracker.freecad.org/file_download.php?file_id=2167&type=bug
    creo_set_view_2.PNG (14,754 bytes) 2019-03-27 09:02
    https://tracker.freecad.org/file_download.php?file_id=2168&type=bug
    inventor_set_view.PNG (43,342 bytes) 2019-03-27 09:02
    https://tracker.freecad.org/file_download.php?file_id=2169&type=bug
    Notes
    (0016740)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5905.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3740 [FreeCAD] Bug tweak always 2018-12-18 20:51 2021-02-06 06:50
    Reporter: HardyW Platform: iMac  
    Assigned To: OS: macOS  
    Priority: normal OS Version: Mojave  
    Status: confirmed Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: [macOS] Editing item by double-clicking opens other project window
    Description: When editing an item by double clicking onto the item in the tree structure always the first project window, respectively the start page, is activated.
    Tags:
    Steps To Reproduce: Open FreeCAD and create a new document without closing the start page. Switch to draft mode and draw something. Finish drawing.
    Double click onto an item in the element tree to start editing. The start page is being activated. A mouse click on the document page (to switch pages) reveals that the "double clicked" element is in edit mode.
    Additional Information:
    Attached Files:
    Notes
    (0012311)
    Kunda1   
    2018-12-19 09:33   
    0003738:0012306
    (0012312)
    chrisb   
    2018-12-19 09:58   
    (Last edited: 2018-12-19 09:59)
    With the setup as described above I have drawn a line. Don't know what "finish editing" means in the error report.
    Double clicking enters editing mode as it should.

    OP: please try on a non retina display and don't flood the bug tracker without discussions in the forum.

    OS: Mac OS X
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.13541 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-17
    Hash: 9948ee4f1570df9216862a79705afb367b2c6ffb
    Python version: 2.7.14
    Qt version: 5.10.1
    Coin version: 4.0.0a
    OCC version: 7.2.0
    Locale: German/Germany (de_DE)

    (0012323)
    HardyW   
    2018-12-19 21:34   
    This bug is independent from the type of display. It occurs on either display (checked on a non Retina display again and before submitting this bug).

    PS: "Finish editing" means that a line is drawn (at the beginning the I observed the bug by drawing a polyline / dwire). I still had this example in my mind.
    PPS: Which forum do you like to use for the discussion? "Open discussion"?

    OS: Mac OS X
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.13541 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-17
    Hash: 9948ee4f1570df9216862a79705afb367b2c6ffb
    Python version: 2.7.14
    Qt version: 5.10.1
    Coin version: 4.0.0a
    OCC version: 7.2.0
    Locale: English/Germany (en_DE)
    (0012338)
    Kunda1   
    2018-12-24 12:35   

    PPS: Which forum do you like to use for the discussion? "Open discussion"?

    HardyW
    Yes, please.
    (0012364)
    Kunda1   
    2019-01-04 18:39   
    @HardyW please link the forum thread in to this ticket. thank you
    (0012610)
    Kunda1   
    2019-02-10 16:05   
    Forum discussion thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=34125
    (0016684)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5849.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3673 [FreeCAD] Bug tweak always 2018-11-07 14:05 2021-02-06 06:50
    Reporter: deejay2 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: HIDPI related bug where text doesn't fit grey box in "Documents" when the software starts.
    Description: HIDPI is more and more used with > 1080p monitors like 4K. It basically downscales the resolution without actually lowering the monitor resolution. It results in crisper image without the tinyzation of everything on a small but high resolution monitor.

    Best explained here:
    https://support.system76.com/articles/hidpi-multi-monitor/

    QT5 actually supports HIDPI quite well and it will make FreeCAD usable on workstations using HIDPI (at last!) :) The problem(s) that remain(s) (Maybe I'll find more later) is in the Start page "Document" tab. Each thumbnail is in a gray box with text underneath. The text doesn't fit in the grey box so it makes the welcome to FreeCAD exeperience a bit frightening.

    Tags: HiDPI
    Steps To Reproduce: Use hidpi with a 4K monitor. For me it's easy to do with POP!_OS which derivates from Ubuntu. You just go in gnome settings->Peripherals->Monitors, Enable HIDPI and scale to 200%.

    I used the FreeCAD_pre AppImage.
    Additional Information:
    Attached Files: Capture d’écran de 2018-11-07 09-05-05.png (279,444 bytes) 2018-11-07 14:05
    https://tracker.freecad.org/file_download.php?file_id=2038&type=bug
    Capture d’écran de 2019-03-02 22-10-01.png (646,649 bytes) 2019-03-03 03:12
    https://tracker.freecad.org/file_download.php?file_id=2146&type=bug
    CaptureFreeCad.PNG (1,923,721 bytes) 2019-04-06 19:13
    https://tracker.freecad.org/file_download.php?file_id=2174&type=bug
    CaptureFreeCad-2.PNG (77,789 bytes) 2019-04-06 19:46
    https://tracker.freecad.org/file_download.php?file_id=2175&type=bug
    Capture2.PNG (43,442 bytes) 2019-04-06 19:46
    https://tracker.freecad.org/file_download.php?file_id=2176&type=bug
    Capture3.PNG (42,277 bytes) 2019-04-06 19:46
    https://tracker.freecad.org/file_download.php?file_id=2177&type=bug
    Notes
    (0012149)
    deejay2   
    2018-11-07 20:03   
    OS: Pop!_OS 18.04 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.15150 (Git) AppImage
    Build type: Release
    Branch: master
    Hash: fe8f172ce1f725cbc5e7a1538beaaac6a6529ec2
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: French/Canada (fr_CA)
    (0012154)
    Kunda1   
    2018-11-09 00:17   
    @deejay please open a thread on the forums to discuss this with the community
    (0012165)
    Kunda1   
    2018-11-10 16:07   
    forum thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=32159
    (0012824)
    deejay2   
    2019-03-03 03:12   
    Here's another screenshot showing effect of hidpi on preferences.
    (0013007)
    gweb   
    2019-04-06 19:13   
    This isn't only restricted to "documents". Here is a screenshot of my start page with a HiDPI scaling of 250% on V0.17 on Windows. Notice that not only the text doesn't fit in the boxes, but also the background is not stretched to fit the window
    (0013015)
    gweb   
    2019-04-06 19:46   
    A few more instances of places where text or images don't fit correctly with HiDPI scaling
    (0013017)
    Kunda1   
    2019-04-06 19:51   
    @gweb we aren't addressing 0.17 anymore. Please test on 0.19dev
    https://github.com/FreeCAD/FreeCAD/releases/tag/0.19_pre
    (0013234)
    Kunda1   
    2019-06-17 07:32   
    Still lots of HiDPI bugs: https://www.freecadweb.org/tracker/search.php?tag_string=HiDPI
    (0016666)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5831.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3446 [FreeCAD] Feature minor have not tried 2018-04-25 13:54 2021-02-06 06:50
    Reporter: microelly2 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: a python method to convert a Shape into a point cloud without extra dialog but parameter
    Description:
    see
    https://forum.freecadweb.org/viewtopic.php?f=22&t=28366#p229963
    Tags: Mesh
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016620)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5785.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3254 [FreeCAD] Feature minor always 2017-11-11 11:56 2021-02-06 06:50
    Reporter: Kunda1 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Wrong paths to fonts occur when you exchange models between different systems. An 'Embed' option would be useful
    Description: If a font that is used in FC file is missing on a system that the file wasn't created on, FC throws errors as described in th forum thread
     
    Workaround is copying the font file into a local directory on the other system, set the font in Preferences->Draft->TextAndDimensions and use relative paths.
    Tags: #lowhangingfruit, Bountysource Potential, export, font, packaging
    Steps To Reproduce:
    Additional Information: Original Forum thread: https://forum.freecadweb.org/viewtopic.php?p=198905#p198775
    Dedicated forum thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=29504&p=241658#p241658
    Please discuss in the above 'dedicated' forum thread
    Attached Files:
    Notes
    (0012462)
    yorik   
    2019-01-18 21:54   
    Supposing this is about draft shapestrings...

    Indeed the font file is needed to rebuild the correct geometry. Therefore it makes sense to have it embedded. It's a rather simle change (change App::PropertyFile with PropertyFileIncluded) however, if we have many shapestrings, each of them will embed a copy of the font file in the file.. That might be annoying. Not sure what would be a best path here...
    (0012600)
    normandc   
    2019-02-09 20:27   
    Guys, there's a potential license issue here. What if the font that was used has a license that prohibits the user from distributing it?
    (0012604)
    Kunda1   
    2019-02-10 15:33   
    @normandc IMO, this is the users responsiblity. Take Scribus for example, I don't recall Scribus having this functionality, and it is a FOSS Desktop Publishing program.
    (0012612)
    normandc   
    2019-02-10 17:16   
    Are you saying that Scribus doesn't offer the option to embed fonts in documents? If that's so, well, maybe this is related.
    (0013488)
    Kunda1   
    2019-08-30 11:10   
    More related discussion on this topic at https://forum.freecadweb.org/viewtopic.php?f=8&t=38643&start=40#p330424
    (0016581)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5746.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3157 [FreeCAD] Feature minor have not tried 2017-08-11 20:55 2021-02-06 06:50
    Reporter: Sam Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Expose makeLoft smoothing algorithm, max degree, and parametrization type to the user.
    Description: I was having some issues with a loft that produced and unexpected outcome. I don't think I'm alone.

    Over in the forum, at Unexpected Klein bottle during PDN loft, there has been some discussion about this. The interesting words start at the end of this post.

    [quote=Chris_G]
    I looked at the source code.
    The makeLoft function uses OCC BRepOffsetAPI_ThruSections that offers these control functions ( smoothing algorithm, setting the max degree, setting the parametrization type).
    So it may be good to have them implemented in the loft tool ?
    [/quote]

    Followed up by Joyas


    It would add more options when Loft takes its own path and forgets the user's intention.

    Sometimes you draw a nice set of sections using the same sketch (with different sizes and orientations), you think that everything will go well, but... loft prefers to cross itself between two of these sections. :cry:

    https://freecadweb.org/wiki/Part_Loft_Technical_Details

    Joyas
    When number of profiles exceeds 9, interpolation degree is dropped to 3. This switchover can substantially reduce wiggling.

    "max degree" could be implemented in a simple way: default (9 or more ---> 3), infinite and a integer number.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0013545)
    Kunda1   
    2019-09-05 21:26   
    Created a dedicated forum thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=39121
    (0016557)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5722.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2927 [FreeCAD] Bug minor always 2017-02-26 05:49 2021-02-06 06:50
    Reporter: ian.rees Platform:  
    Assigned To: ian.rees OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Mac application bundler doesn't track library versions
    Description: I've run in to an issue on my own machine, where the linker finds a newer version of a library than the one that ends up getting copied in to the application bundle. This causes the older library to not be loaded by dyld when the bundle is launched, which can cause a range of problems.

    There are several (and, to me at least, some are non-obvious) places in the existing script that need to take library versions in to account. After mucking around with it script for a few hours to find the source of my problem, I'm thinking that it'll be best to re-write the part that creates the graph of dependencies.

    (note to self: Local branch is 20170225-bundle-tool)
    Other changes:
      * dir_filter in main() needs to be more Python version-agnostic
      * before calling otool, etc on libraries mentioned, the script should ensure that the library actually exists, and respond accordingly.
    Tags: #post-to-forum, macOS, packaging
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0013546)
    Kunda1   
    2019-09-05 21:41   
    Dedicated forum thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=39122
    (0016518)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5683.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1967 [FreeCAD] Feature feature N/A 2015-02-14 22:05 2021-02-06 06:50
    Reporter: shoogen Platform:  
    Assigned To: shoogen OS:  
    Priority: none OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Fuzzy Boolean Operations
    Description: make use of Fuzzy Boolean Operations
    http://dev.opencascade.org/index.php?q=node/1056
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0005920)
    shoogen   
    2015-03-22 22:21   
    git://github.com/5263/FreeCAD dev-fuzzyboolean

    The development has stalled. Please feel free to test and comment. I would like to wait with the integration until the problem with corrupted input shapes (comment-520) is solved.
    (0013495)
    openBrain   
    2019-08-31 10:57   
    As of today, fuzzy boolean operations are available in the Defeaturing WB.
    (0016447)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5612.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    336 [FreeCAD] Feature minor have not tried 2011-04-14 06:10 2021-02-06 06:50
    Reporter: fantamas Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: acknowledged Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Add a feature recognition tool
    Description: When reverse engineering is required, it will be very easy if you can create editable features from point cloud files, stl files or step files.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0000836)
    Jriegel   
    2011-05-17 10:48   
    We have planes for that (Point module), but have no time for such things
    in the near future...
    (0013639)
    sopwith   
    2019-09-19 01:55   
    Is it possible that the ReverseEngineering workbench does this nowadays? :)
    (0016378)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5543.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4401 [FreeCAD] Feature feature N/A 2020-07-07 06:03 2021-02-06 06:49
    Reporter: Jee-Bee Platform:  
    Assigned To: berndhahnebach OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: NVT
    Summary: FEM: Viewing mixed meshes
    Description: Add funtionality to view mixed meshes in FreeCAD FEM module. See request: https://forum.freecadweb.org/viewtopic.php?p=411832#p411832
    Tags: FEM, Mesh
    Steps To Reproduce:
    Additional Information: https://forum.freecadweb.org/viewtopic.php?p=411832#p411832
    Attached Files:
    Notes
    (0016921)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6088.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4364 [FreeCAD] Feature minor always 2020-06-06 17:17 2021-02-06 06:49
    Reporter: unalcalde Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: feedback Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Ubuntu 20.04 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16146 (Git) AppImage
    Build type: Release
    Branch: (HEAD detached at 0.18.4)
    Hash: 980bf9060e28555fecd9e3462f68ca74007b70f8
    Python version: 3.6.7
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: Spanish/Spain (es_ES)
    Summary: Quick switch to a local part view
    Description: It would be interesting some option that hides all parts except the current and fit the screen with it.

    Something similar to the Local View (shortcut "/") of Blender.
    Tags: #post-to-forum
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0014511)
    openBrain   
    2020-06-07 17:29   
    @unalcalde : please address your issue following our reporting guidelines by opening first a topic in our forum. Thx
    We generally accept feature request only when it has been discussed and refined with the community.
    JFYI, your feature shouldn't be very difficult to script.
    (0016905)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6072.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4342 [FreeCAD] Bug minor always 2020-05-14 20:01 2021-02-06 06:49
    Reporter: fc_tofu Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 10 (10.0)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.21049 (Git)
    Build type: Release
    Branch: master
    Hash: 9c27f1078e5ec516fe882aac1a27f5c6c6174554
    Python version: 3.8.2
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: Chinese/China (zh_CN)
    Summary: grouped buttons conflict in customized toolbar
    Description: Use toolbar customize funtion. I dupliated PartWB toolbars into DraftWB.
    Before restarting FreeCAD, everything works ok.
    But after restarting FreeCAD, grouped buttons dont display name and dont work when pressed, on both DraftWB and PartWB sides.
    Tags:
    Steps To Reproduce: 1. Restart FreeCAD, and switch to DraftWB.
    2. menu >Tools >Customize >Toolbars.
    3. on right pane, add a toolbar named "Draft Custom" (for example).
    4. on left pane, find "Part >Compound Tools" (this is a tool group).
    5. add "Compound Tools" to "Draft Custom".
    6. Close "Customize" and restart FreeCAD.
    7. Obsever "Compound Tools" on DraftWB and PartWB toolbars.






    Additional Information: Forum:
    https://forum.freecadweb.org/viewtopic.php?f=34&t=42799&p=363857#p363857
    Attached Files:
    Notes
    (0016895)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6062.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4339 [FreeCAD] Bug minor always 2020-05-11 07:21 2021-02-06 06:49
    Reporter: fc_tofu Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 10 (10.0)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.20514 (Git)
    Build type: Release
    Branch: master
    Hash: a05ffd499366ab12fa1b43f37db73f4f1e9c332d
    Python version: 3.8.2
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: Chinese/China (zh_CN)
    Summary: auto working plane neglect Left/Right rotation
    Description: DraftWB, Menu >View >Standard view >Rotate left/right.
    Or, NaviCube >Rotatate clockwise/anti-clockwise.
    The roation angle is neglected when calculating automatic working plane.

    Tags:
    Steps To Reproduce: 1. Restart FreeCAD, and switch to DraftWB.
    2. Rendering mode >Flat lines.
    3. At current view (Front for example), draw a closed shape (Rectangle for example).
    4. Check Rectangle's Data >Base >Placement >Angle/Axis, and remember.
    5. Change view with Menu >View >Standard view >Rotatate left/right. (90 degree per click).
    6. Draw a closed shape (Rectangle001 for example).
    7. Check Rectangle001's Data >Base >Placement >Angle/Axis, and compare with Rectangle.
    8. Find 2 rectangle have same Angle/Axis data.
    Additional Information: ps.
    NaviCube >Rotatate clockwise/anti-clockwise, takes 45 degree rotation per click. It is more convinient to find this issue.

    Forum:
    https://forum.freecadweb.org/viewtopic.php?f=23&t=46157
    Attached Files:
    Notes
    (0016893)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6059.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4338 [FreeCAD] Bug minor always 2020-05-11 07:17 2021-02-06 06:49
    Reporter: fc_tofu Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 10 (10.0)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.20514 (Git)
    Build type: Release
    Branch: master
    Hash: a05ffd499366ab12fa1b43f37db73f4f1e9c332d
    Python version: 3.8.2
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: Chinese/China (zh_CN)
    Summary: Working Plane Proxy neglect Automatic Working Plane
    Description: In DraftWB, new added working plane proxy (WPP) neglect the orientation of automatic working plane.
    Tags:
    Steps To Reproduce: 1. Restart FreeCAD, and switch to DraftWB.
    2. Setup working plane mode as "Automatic".
    3. Change view from current (view 1) to any other (view 2, ortho or tilted).
    4. Menu > Utilities > Create working Plane Proxy.
    5. Observe orientation of the WPP, and find its orientation is still at view 1 (not affected by step 3).
    6. For further observation. Double click the WPP in TreeView, to take its orientation as working plane.
    7. Draw a closed shape in viewport.
    8. Find above shape's orientation is as WPP (view 1), not as auto workingplane (view 2).

    Additional Information: Workaround:
    Before step 4, draw a closed shape (rectangle for example) at current view, then go to step 4. New added WPP will take orientation of current view.

    Forum:
    https://forum.freecadweb.org/viewtopic.php?f=23&t=46152&p=396611#p396611
    Attached Files:
    Notes
    (0016892)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6058.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4333 [FreeCAD] Bug minor always 2020-05-02 19:52 2021-02-06 06:49
    Reporter: wrpetersen Platform: Intel i7 Laptop  
    Assigned To: OS: Windows 10  
    Priority: normal OS Version: Home  
    Status: feedback Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 10
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.4 (GitTag)
    Build type: Release
    Branch: releases/FreeCAD-0-18
    Hash: 980bf9060e28555fecd9e3462f68ca74007b70f8
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    Summary: Application defaults to display port dock instead of embedded graphics - causes empty editor screen without error notification
    Description: I have a laptop with a multi-monitor USB3 dock. When I open FreeCad with the dock connected I get a blank screen in the editor, cannot view cad files. There is no error message so it leaves you wondering what is wrong. If I unplug my dock and open FreeCad everything works fine, I can then reconnect my dock and use the application normally because at startup it pointed to my embedded graphics.

    This is especially frustrating because Windows loves to do automatic updates overnight and close out all of your applications. I would probably leave my laptop plugged into the dock for several weeks if it weren't for FreeCad needing to be opened off of it.
    Tags: #post-to-forum
    Steps To Reproduce: Attach a USB3 dock with external monitors, open application and attempt to make a new sketch/part etc. I am using a Wavlink UG39DK1 specifically on an i7 laptop without an additional GPU- laptop uses embedded CPU graphics.
    Additional Information: I have two possible suggestions; If there was a setting to permanently point to which graphics device FreeCad will use for processing OR when the default device is not compatible, the application will check for an additional graphics processor. I have similar issues with 3D printer slicers but they specifically throw an error with the OpenGL driver, I am not sure if FreeCad uses that driver.
    Attached Files:
    Notes
    (0014398)
    wrpetersen   
    2020-05-02 19:55   
    Just to clarify the description portion " If I unplug my dock and open FreeCad everything works fine, I can then reconnect my dock and use the application normally because at startup it pointed to my embedded graphics."

    If I open the application with the dock unplugged- you cannot correct the issue by unplugging dock while the application is already open. Once the application is open you can then re-dock the computer and use the external displays
    (0014399)
    openBrain   
    2020-05-03 10:13   
    @wrpetersen : please process according our reporting guidelines by always first open a topic in our forum. Thx
    Though some words about your issue :
    • Probably you can tell your GFX drivers which output to use with which application
    • You should give a try to FreeCAD 0.19. Latest Qt has fixed lot of issues with GFX
    Please add link to your forum topic here when it's created.
    (0016890)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6056.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4329 [FreeCAD] Feature feature N/A 2020-04-29 06:43 2021-02-06 06:49
    Reporter: Hakanseven12 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 10 (10.0)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.20802 (Git)
    Build type: Release
    Branch: master
    Hash: f4279f1bea8377a7ef63f7f4c69b67159d498965
    Python version: 3.8.2
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: Turkish/Turkey (tr_TR)
    Summary: [Feature Request] Table Object
    Description: Do FreeCAD have a table object like this? If don't it would be nice to create a table object. I know there is a spreadsheet workbench but I want to place a table to 3d view.

    Forum discussion: https://forum.freecadweb.org/viewtopic.php?f=8&t=45470
    Tags: #pending-forum
    Steps To Reproduce:
    Additional Information:
    Attached Files: table.png (28,382 bytes) 2020-04-29 06:43
    https://tracker.freecad.org/file_download.php?file_id=2464&type=bug
    Notes
    (0016887)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6053.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4314 [FreeCAD] Feature feature N/A 2020-04-14 17:29 2021-02-06 06:49
    Reporter: drmacro Platform: All  
    Assigned To: OS: All  
    Priority: normal OS Version: All  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Ubuntu 19.10 (XFCE/ubuntustudio)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.
    Build type: Release
    Python version: 3.7.5
    Qt version: 5.12.4
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/United States (en_US)
    Summary: Add visual orientation while creating datum plane
    Description: https://forum.freecadweb.org/viewtopic.php?f=3&t=45159

    During creation of a datum plane provide visual feedback depicting the orientation of the X,Y,Z. For example while selecting 3 point plane.

    Possibly toggle on for reference at later times, to clarify orientation when creating attached sketches.

    Tags: planes
    Steps To Reproduce: Create a datum plane based on existing geometry.
    Additional Information:
    Attached Files:
    Notes
    (0016880)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6046.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4268 [FreeCAD] Feature major always 2020-02-17 04:54 2021-02-06 06:49
    Reporter: bgoodr Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Ubuntu 19.10 (ubuntu:GNOME/ubuntu)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.
    Build type: Release
    Python version: 3.7.5
    Qt version: 5.12.4
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/United States (en_US)

    And also specifically this version of freecad-daily:

    $ dpkg --list freecad-daily\*
    Desired=Unknown/Install/Remove/Purge/Hold
    | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
    |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
    ||/ Name Version Architecture Description
    +++-=====================-====================================-============-======================================================
    ii freecad-daily 0.19~pre2~202002161351~ubuntu19.10.1 all Extensible Open Source CAx program
    ii freecad-daily-common 0.19~pre2~202002161351~ubuntu19.10.1 all Extensible Open Source CAx program - common files
    un freecad-daily-doc <none> <none> (no description available)
    un freecad-daily-python2 <none> <none> (no description available)
    ii freecad-daily-python3 0.19~pre2~202002161351~ubuntu19.10.1 amd64 Extensible Open Source CAx program - Python 3 binaries
    un freecad-daily-runtime <none> <none> (no description available)
    $
    Summary: Multi-Geometry Modal Selection and Deselection
    Description: Feature request: Multi-Geometry Modal Selection and Deselection
    Detailed description is in the forum post: https://forum.freecadweb.org/viewtopic.php?f=8&t=43438
    Tags:
    Steps To Reproduce: Not applicable. This is a feature request.
    Additional Information:
    Attached Files:
    Notes
    (0016867)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6033.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4249 [FreeCAD] Feature feature always 2020-01-16 19:00 2021-02-06 06:49
    Reporter: Pauvres_honteux Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: openSUSE Leap 15.1 (KDE//usr/share/xsessions/default)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.Unknown
    Build type: Release
    Python version: 3.6.5
    Qt version: 5.9.7
    Coin version: 4.0.0a
    OCC version: 7.4.1.dev
    Summary: Move versus edit objects
    Description: Move versus edit objects
    Tags:
    Steps To Reproduce:
    Additional Information: Extra demand for Move: the new position of an object SHALL NOT be stored in the object! It shall be stored in something related and coupled to the move command.
    Clarification of the non editable copy+moved object: it shall of course be possible to add thickness, scale, copy it and so on.
    This will form the very basics of making castings.
    Attached Files:
    Notes
    (0016858)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6024.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4240 [FreeCAD] Feature feature always 2020-01-04 09:47 2021-02-06 06:49
    Reporter: Pauvres_honteux Platform: Any  
    Assigned To: OS: Any  
    Priority: normal OS Version: Any  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: openSUSE Leap 15.1 (KDE//usr/share/xsessions/default)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19. (build time: 2020-01-02 08:56:40 by obs://build.opensuse.org/science:unstable)
    Build type: Release
    Python version: 3.6.5
    Qt version: 5.9.7
    Coin version: 4.0.0a
    OCC version: 7.4.1.dev
    Summary: 3D polyline with separate radii on each "corner"
    Description: See discussion at: 3D polyline with radii

    An extra wishing for a really handy feature: make it possible to have this 3D polyline to follow a surface of the users choice.
    Tags: lines, points, Poly-line, surfaces
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016854)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6020.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4204 [FreeCAD] Feature major always 2019-11-25 10:37 2021-02-06 06:49
    Reporter: Pauvres_honteux Platform: All  
    Assigned To: OS: All  
    Priority: high OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: openSUSE Leap 15.1 (KDE//usr/share/xsessions/default)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.Unknown
    Build type: Release
    Python version: 3.6.5
    Qt version: 5.9.7
    Coin version: 4.0.0a
    OCC version: 7.4.0
    Summary: BlendCurve - need it to accept ANY point / line as an argument
    Description: See forum discussion: 3D parametric curve.
    Adding to the list: selecting points / lines from the tree as well from 3D view.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0013842)
    Pauvres_honteux   
    2019-11-25 10:44   
    Clarification: this request is of course directed to Part / Part Design. Not directly at Chris_G.
    (0016845)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6011.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4203 [FreeCAD] Feature major always 2019-11-25 10:19 2021-02-06 06:49
    Reporter: Pauvres_honteux Platform: All  
    Assigned To: OS: All  
    Priority: high OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: openSUSE Leap 15.1 (KDE//usr/share/xsessions/default)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.Unknown
    Build type: Release
    Python version: 3.6.5
    Qt version: 5.9.7
    Coin version: 4.0.0a
    OCC version: 7.4.0
    Summary: Loft improvement - PartDesign
    Description: This request is basically about improving the loft functionality / multi section face.
    N.B. the difference between surface and face!

    In addition to what was typed in the forum discussion I add the demand of G1 and G2 to, users selection of, surrounding surfaces to the list.
    Tags:
    Steps To Reproduce: See forum discussion.
    Additional Information:
    Attached Files:
    Notes
    (0016844)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6010.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4202 [FreeCAD] Feature feature N/A 2019-11-25 09:58 2021-02-06 06:49
    Reporter: Pauvres_honteux Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: <!--ATTENTION:
    COMPLETELY ERASE THIS AFTER PASTING YOUR
    Help > About FreeCAD > Copy to clipboard
    NOTE: just the snippet alone will do without anything else included.
    The ticket will not be submitted without it.
    -->
    Summary: Working points, lines and planes
    Description: Requesting a solid single way of creating points, lines, and planes.
    See forum discussion: Working points, lines and planes
    Tags: datum line, datum point, lines, planes, points
    Steps To Reproduce: See forum discussion: Working points, lines and planes
    Additional Information:
    Attached Files:
    Notes
    (0016843)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6009.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4180 [FreeCAD] Bug minor have not tried 2019-10-29 10:10 2021-02-06 06:49
    Reporter: uwestoehr Platform:  
    Assigned To: OS:  
    Priority: high OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 10 (10.0)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.18637 (Git)
    Build type: Release
    Branch: master
    Hash: e243c6e943dc78e7e8093c5c38a879e46b37d0c1
    Python version: 3.6.8
    Qt version: 5.12.1
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: German/Germany (de_DE)
    Summary: [regression] DXF export option "project exported objects along current view direction" no longer working
    Description: Sketches that are not in the XY-plane are no longer correctly exported to DXF, despite the DXF export option "project exported objects along current view direction" is used.

    It only works if you use additionally the option "use legacy python exporter". However, it must also work without it.

    In FC 0.18 there is no legacy exporter and everything works fine there -> regression.
    Tags: DXF, export
    Steps To Reproduce:
    Additional Information: Forum thread: https://forum.freecadweb.org/viewtopic.php?f=3&t=40424
    Attached Files:
    Notes
    (0016835)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6001.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4178 [FreeCAD] Bug minor always 2019-10-27 01:53 2021-02-06 06:49
    Reporter: garya Platform: PC  
    Assigned To: OS: FreeBSD  
    Priority: normal OS Version: 11.2-RELEASE-p4  
    Status: confirmed Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: FreeBSD 11.2-RELEASE-p4
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.0.18.2
    Build type: Release
    Python version: 3.6.9
    Qt version: 5.12.2
    Coin version: 3.1.3
    OCC version: 7.3.0
    Locale: C/Default (C)
    Summary: Part Design auto-generated Body not placed under existing Part
    Description: A sketch which auto-creates a Body does not place it under the active Part. Instead, it is placed at the same level as the active part. It should be placed under the part.
    See forum topic
    Tags: Part Design
    Steps To Reproduce: Create a new document
    Part Design WB
    Create Part
    Create Sketch, select xy plane, click ok
    Close the sketcher task
    View the model tab
    The auto-generated Body is at the same level as the Part; it should be under it.
    Additional Information:
    Attached Files:
    Notes
    (0016834)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6000.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4176 [FreeCAD] Feature feature always 2019-10-26 17:15 2021-02-06 06:49
    Reporter: Izaius Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 10
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16131 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-18
    Hash: 3129ae4296e40ed20e7b3d460b86e6969acbe1c3
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    Summary: Add options to have entire property tree expanded by default instead of collapsed in Properties pane
    Description: When you click on an object in the Model view, the property tree is loaded into the Property view. All branches on the tree are collapsed by default.
    Request a preference be added to have these all expanded by default. It will save a tremendous number of clicks and time.
    Tags:
    Steps To Reproduce: See above
    Additional Information: See above
    Attached Files:
    Notes
    (0016833)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5999.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4172 [FreeCAD] Feature feature N/A 2019-10-24 07:06 2021-02-06 06:49
    Reporter: freedman Platform: all  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 7
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16085 (Git)
    Build type: Release
    Branch: master
    Hash: 6323069cbbda5ac71dff073f15cc632d8a1f3ea3
    Python version: 2.7.14
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.2.0
    Locale: English/UnitedStates (en_US)

    Summary: Add a new option to sketcher preferences, "Maintain camera position while editing"
    Description: Forum link: https://forum.freecadweb.org/viewtopic.php?f=8&t=40317
    I want this mostly for Part design but it should work in all workbenches. Currently when entering Sketcher the camera view changes to sketch-normal, this requested option if enabled would keep the current view. The sketch could then be edited in that view, probably a 3D view. The goal is to transistion to and from Sketcher without changing the users view.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016831)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5997.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4091 [FreeCAD] Bug minor always 2019-08-19 09:41 2021-02-06 06:49
    Reporter: tino Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: feedback Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: create links of a selected object along selected path
    Description: I made a cylinder and a spiral then I aligned the cylinder to the spiral and it should have created cylinders aligned to the spiral, it makes the cylinders aligned but it starts outside the spiral and part inside without any logic

    Tags: #post-to-forum
    Steps To Reproduce:
    Additional Information:
    Attached Files: bug.FCStd (14,379 bytes) 2019-08-19 09:41
    https://tracker.freecad.org/file_download.php?file_id=2284&type=bug
    Notes
    (0013431)
    Kunda1   
    2019-08-19 22:56   
    @tino Big yellow banner at the top of the page, please follow it.
    (0014082)
    Kunda1   
    2020-01-16 13:22   
    @tino ping
    (0014503)
    Kunda1   
    2020-06-07 14:31   
    where is the About info ?
    Please follow up!
    (0016810)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5976.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3789 [FreeCAD] Bug minor have not tried 2019-01-23 21:57 2021-02-06 06:49
    Reporter: yorik Platform: PC  
    Assigned To: yorik OS: Debian  
    Priority: normal OS Version: Testing 64bit  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Fix movement of children of Arch objects
    Description: When rotating an Arch object that has additions, the result is not correct (the additions get disaligned), and if removing the addition, moving it to the right place and re-add it, the result is not correct either. So:

    - The code that moves children (ArchComponent.onChanged) is buggy
    - The code that constructs the final object (ArchComponent.processSubShapes) is buggy too

    Below is an alternative snippet I tested but doesn't work either. Seems a better base to start with, though
    Tags:
    Steps To Reproduce:
    Additional Information: https://forum.freecadweb.org/viewtopic.php?f=23&t=33669&p=281903#p281903

    Snippet for ArchComponent.py, L330 - different method to calculate child movement

    # TODO - Implement/test this method instead - calculate additional movement caused by the rotation
    diff = child.Placement.Base.sub(self.oldPlacement.Base)
    if diff.Length:
        diff = self.oldPlacement.inverse().multVec(diff) # move back to origin
        diff = obj.Placement.multVec(diff) # move to the new location
        npos = obj.Placement.Base.add(diff) # new position of the child placement
        child.Placement.Base = npos
    System Description
    Attached Files: test structures.FCStd (11,837 bytes) 2019-01-23 21:57
    https://tracker.freecad.org/file_download.php?file_id=2109&type=bug
    Notes
    (0013795)
    mickele   
    2019-10-30 14:16   
    Any news about this bug?
    (0016703)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5868.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3758 [FreeCAD] Feature major N/A 2018-12-31 19:24 2021-02-06 06:49
    Reporter: Kunda1 Platform:  
    Assigned To: triplus OS:  
    Priority: immediate OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Sign AppImages
    Description:

    signing appimages looks straight-forward here - https://docs.appimage.org/packaging-guide/signatures.html . No special cert is needed so anyone can extend the travis.yml to perform the signing step. We would need to produce a key and embed it as a secure variable in the travis.yml. I’m trying to resurrect the macOS builds so don’t know when I will have a chance to look at this...

    blacey

    Per @probonopd in https://github.com/FreeCAD/FreeCAD-AppImage/issues/6 we can:
    Use the -s switch of appimagetool to embed a signature into the AppImage.

    Related Forum threads:
    https://forum.freecadweb.org/viewtopic.php?f=10&t=15525&start=300#p268325
    https://forum.freecadweb.org/viewtopic.php?f=10&t=34981&p=329620#p329620
    Tags: appimage, packaging
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0012383)
    Kunda1   
    2019-01-05 11:53   
    punting to sgrogan
    (0012916)
    Kunda1   
    2019-03-16 12:27   
    Hey @triplus is it OK that I assign this ticket to you? I was following the 0.18 Release thread on the forum and sgrogan defers to you on this task.
    (0013251)
    Kunda1   
    2019-06-18 09:19   
    Examples of users concerned with unsigned appimages:
    • https://www.reddit.com/r/FreeCAD/comments/c0pp2h/cannot_install_latest_freecad_package_from_ubuntu/erg3obe/
    • https://forum.freecadweb.org/viewtopic.php?f=4&t=33244&p=279262#p279233
    (0013420)
    Kunda1   
    2019-08-12 20:56   
    This still needs to happen
    (0013429)
    Kunda1   
    2019-08-19 00:49   
    Another inquiry regarding this issue:
    https://forum.freecadweb.org/viewtopic.php?f=3&t=38641
    (0013490)
    Kunda1   
    2019-08-30 13:07   
    Solution according to @probonopd is at
    https://github.com/FreeCAD/FreeCAD-AppImage/issues/6#issuecomment-525840839
    (0016691)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5856.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3420 [FreeCAD] Bug major always 2018-04-03 13:03 2021-02-06 06:49
    Reporter: herrdeh Platform: all  
    Assigned To: yorik OS: all  
    Priority: normal OS Version: all  
    Status: assigned Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: SVG imports from inkscape lead to wrong dimensions
    Description: With the change from 0.91 to 0.92 inkscape devs changed the conversion factor of userunit (uu) and mm. Pre-0.92 it was 1uu=1 inch/90 and starting from 0.92 it is 1 uu=1inch/96. This was necessary to meet the actual recommendations/rules of svg-standard and css. See this article in inkscapewiki for further reading.

    When a user creates a file in inkscape with absolute dimensions (mm) and saves it, then imports it into FC, bodies in Freecad come out with too large dimensions. For example - a 100mm square will be 106,66mm in FC now (100 x 96/90).

    In this discussion in the German forum folks who can read German can follow the process of isotating the bug.

    New forum thread opened in https://forum.freecadweb.org/viewtopic.php?f=8&t=37102
    Tags: import, Inkscape, SVG
    Steps To Reproduce: Import a SVG file from inkscape >=0.92 - check measures.
    Additional Information:
    Attached Files: Viereck-100x200-Rand0,1-inkscape092.svg (1,663 bytes) 2018-04-04 08:12
    https://tracker.freecad.org/file_download.php?file_id=1876&type=bug
    Viereck-100x200-Rand0,1-inkscape048.svg (1,846 bytes) 2018-04-04 08:12
    https://tracker.freecad.org/file_download.php?file_id=1877&type=bug
    1_08mm_plakene_DINA4.svg (1,455 bytes) 2019-11-23 13:40
    https://tracker.freecad.org/file_download.php?file_id=2389&type=bug
    Notes
    (0011114)
    yorik   
    2018-04-03 15:38   
    Would it be possible to provide two very simle test files that would allow to check the results?
    (0011120)
    herrdeh   
    2018-04-04 08:14   
    Here are inkscape test files. Unluckily, none of my FC versions are capable of SVG import at the moment, so I cannot provide FC test files. But importing both of these examples should lead to different squares, allthough both of them are 100x200mm in inkscape.
    (0011121)
    yorik   
    2018-04-04 14:07   
    Thanks! I'll have a look at this after the release is out.
    (0013238)
    Kunda1   
    2019-06-17 14:59   
    New forum discussion thread opened in https://forum.freecadweb.org/viewtopic.php?f=8&t=37102
    (0013837)
    teo8976   
    2019-11-23 13:40   
    This has nothing to do specifically with Inkscape, and it has nothing to do specifically with mm.

    Look at the attached SVG file. I wrote this SVG file by hand, it was not exported from Inkscape:

    <svg width="595.28pt" height="420.94pt"  viewBox="0 0 210 148" xmlns="http://www.w3.org/2000/svg">


    This defines a physical size in pt for the document (which is A4) and a corresponding viewbox such that 1 user unit should be 2.83465 pt which is 1 mm.

    Hence the physical size of 1 unit in the document should be that.
    That is defined by the document.

    I have imported this and exported to dxf and the resulting width of the 190mm rectangles is about 185mm.

    Then for some reason, if instead of exporting to dxf I print it to pdf (not export to pdf, print and select "print to pdf"), for some reason they're even much smaller.
    But I don't know, maybe the "print" feature has no notion of a real physical size and just print everything to fit whatever paper size you choose.
    (0013839)
    openBrain   
    2019-11-24 13:30   
    @teo8976 : actually it has to do with Inkscape because for long time, FreeCAD relies on Inkscape SVG format. Inkscape doesn't export a viewbox so user unit can't be arithmetically determined. Issue was that Inkscape was using a strange 90 dpi so FC converts with this setting. Inkscape has recently moved to SVG standard 96 dpi and it makes emerge some problems. Things has been greatly improved and I'm now able to correctly import your file with latest 0.19 (despite I found a small bug that I'll report). Time for you to leave your 0.15 release and upgrade. ;)
    (0013840)
    teo8976   
    2019-11-24 13:54   
    > Inkscape doesn't export a viewbox so user unit can't be arithmetically determined

    Yeah but my file (which was not created by Inkscape) does have a viewbox AND document width and height on the root node, so the size of a user unit should be calculated from those without any fixed dpi involved. I haven't tried changing the width, height and viewbox though, to see whether the results differ (they should).

    > Time for you to leave your 0.15 release and upgrade

    I know, that's the version I got with apt-get. Time for [whoever maintains that] to release a more recent one for Ubuntu.
    (0013841)
    openBrain   
    2019-11-24 14:20   
    @teo8976 : the file you posted in this ticket raised the evidence that 'pt' unit has been forever not well defined in FC. ;) I submitted this PR to fix it. However as I explained above, this only solves part of your problems as I explained above.
    Everything should be OK with 0.19 version once the PR is integrated. Thanks for your perseverance.
    (0016616)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5781.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2821 [FreeCAD] Patch minor always 2016-12-28 11:57 2021-02-06 06:49
    Reporter: stefan.althoefer Platform: FreeCAD  
    Assigned To: OS:  
    Priority: low OS Version:  
    Status: feedback Product Version: 0.16  
    Product Build: Resolution: reopened  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: IDF Import of Step Models
    Description: Hi,

    I'm using IDF module to import IDF Files written by Pulsonix.

    I found that working with external Step models (by footprint_models.csv)
    could be better.

    The attached patch addresses three issues:
    1. Difficulties in matching. I removed quotes from some strings
        before using them
    2. Read the step model now with Part.Shape.read() instead of using
        ImportGui.insert(). This has the advantage to work even if the Step
        Model has more than one solid/object.
    3. Ability to hide/remove EMP generated models when a Step file for
        a component was loaded. Without this you end up with the Step Model
        and the EMP model overlap.

    Although I tested with 0.16, the patch should apply to the current git.

    Sorry I'm not a git user, and neither a Python programmer ...
    Tags: #pending, import, STEP
    Steps To Reproduce:
    Additional Information: Forum thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=31627
    Attached Files: idf.py.patch (6,316 bytes) 2016-12-28 11:57
    https://tracker.freecad.org/file_download.php?file_id=1408&type=bug
    Notes
    (0007854)
    Kunda1   
    2017-01-17 20:43   
    Reminder sent to: shoogen
    Hey @shoogen do you have a moment to address this ticket(patch) ? Thanks
    (0008055)
    Kunda1   
    2017-01-28 13:25   
    Note: @vejmarie will check this ticket soon.
    (0008693)
    Kunda1   
    2017-03-23 23:57   
    changing to feedback to keep track of ticket.
    (0009246)
    Kunda1   
    2017-06-01 19:15   
    @stefan.althoefer do you mind reattaching the .py script?
    (0009415)
    Kunda1   
    2017-06-16 15:55   
    @stefan.althoefer ping
    (0009586)
    Kunda1   
    2017-06-28 22:12   
    @vejmarie I can't get OP to respond. Can you take a look/see and offer yours opinion?
    (0009719)
    Kunda1   
    2017-07-11 20:19   
    @stefan.althoefer ping
    (0009916)
    Kunda1   
    2017-08-13 16:57   
    @vejmarie please weigh in. Can I close this ticket?
    (0010173)
    Kunda1   
    2017-09-24 19:29   
    @vejmarie ping
    (0011498)
    stefan.althoefer   
    2018-07-06 22:07   
    Sorry for not having responded to all the pings. But here I'm back with
    this issue. Mainly because I switched to 0.17 with the same issues and
    had to recreate my patch.

    The issues/improvements are exactly the same as in the original description.

    My IDF looks like this:

    
    "SOT23" "BSS138 SOT23" T300
    -64.77 -10.795 0.0 TOP PLACED
    "SOT23" "BSS138 SOT23" T400
    -72.627 21.351 270.0 TOP PLACED
    "RES_SMD_0805_JUMPA" "0_JMP RES_SMD_0805_JUMP" R460
    -75.75 36 0.0 BOTTOM PLACED
    "RES_SMD_0805_JUMPA" "0_JMP RES_SMD_0805_JUMP" R461
    -75.75 34.25 0.0 BOTTOM PLACED
    

    With the original idf.py, the scanned input looked like this
    
    ['T300', '"BSS138 SOT23"', '"SOT23"', -64.77, -10.795, 0.0, 'TOP', 'PLACED']
    ['T400', '"BSS138 SOT23"', '"SOT23"', -72.627, 21.351, 270.0, 'TOP', 'PLACED']
    ['R460', '"0_JMP RES_SMD_0805_JUMP"', '"RES_SMD_0805_JUMPA"', -75.75, 36.0, 0.0, 'BOTTOM', 'PLACED']
    ['R461', '"0_JMP RES_SMD_0805_JUMP"', '"RES_SMD_0805_JUMPA"', -75.75, 34.25, 0.0, 'BOTTOM', 'PLACED']
    

    Obviously, the double quote should be eliminated, or matching with external
    step model files will not work.
    My fix just replaces double quotes with nothing. It is very unlikely that double quotes will be part of the Component names. Perhaps it would be better to fix split_records()?

    
    *** Idf-git.py	2018-07-06 23:26:28.250000000 +0200
    --- Idf-clean.py	2018-07-06 23:48:30.444397500 +0200
    ***************
    *** 49,54 ****
    --- 49,55 ----
      IDF_diag=0 # 0/1=disabled/enabled output (footprint.lst/missing_models.lst) 
      IDF_diag_path="/tmp" # path for output of footprint.lst and missing_models.lst
      
    + EMP_remove=2 # 0=leave, 1=hide, 2=remove EMP model when step has been found
      
      ########################################################################################
      #              End config section do not touch code below                              #
    ***************
    *** 114,122 ****
                drills.append([float(emnrecords[0])*emn_unit,float(emnrecords[1])*emn_unit,float(emnrecords[2])*emn_unit])
             if current_section==".PLACEMENT"  and section_counter>1 and fmod(section_counter,2)==0:
                place_item=[]
    !           place_item.append(emnrecords[2]) #Reference designator
    !           place_item.append(emnrecords[1]) #Component part number
    !           place_item.append(emnrecords[0]) #Package name
             if current_section==".PLACEMENT"  and section_counter>1 and fmod(section_counter,2)==1:
                place_item.append(float(emnrecords[0])*emn_unit) #X
                place_item.append(float(emnrecords[1])*emn_unit) #Y
    --- 115,123 ----
                drills.append([float(emnrecords[0])*emn_unit,float(emnrecords[1])*emn_unit,float(emnrecords[2])*emn_unit])
             if current_section==".PLACEMENT"  and section_counter>1 and fmod(section_counter,2)==0:
                place_item=[]
    !           place_item.append(str(emnrecords[2]).replace('"','')) #Reference designator
    !           place_item.append(str(emnrecords[1]).replace('"','')) #Component part number
    !           place_item.append(str(emnrecords[0]).replace('"','')) #Package name
             if current_section==".PLACEMENT"  and section_counter>1 and fmod(section_counter,2)==1:
                place_item.append(float(emnrecords[0])*emn_unit) #X
                place_item.append(float(emnrecords[1])*emn_unit) #Y
    ***************
    *** 265,272 ****
              emp_unit=1
           if (current_section==".ELECTRICAL" or current_section==".MECHANICAL") and section_counter==2:
              comp_outline=[] #no part outline
    !         comp_GeometryName=emprecords[0] # geometry name
    !         comp_PartNumber=emprecords[1] # Part Number
              comp_height=emp_unit*float(emprecords[3]) # Comp Height
           if (current_section==".ELECTRICAL" or current_section==".MECHANICAL") and section_counter>2:
              comp_outline.append([float(emprecords[1])*emp_unit,float(emprecords[2])*emp_unit,float(emprecords[3])]) #add point of outline
    --- 266,273 ----
              emp_unit=1
           if (current_section==".ELECTRICAL" or current_section==".MECHANICAL") and section_counter==2:
              comp_outline=[] #no part outline
    !         comp_GeometryName=str(emprecords[0]).replace('"','') # geometry name
    !         comp_PartNumber=str(emprecords[1]).replace('"','') # Part Number
              comp_height=emp_unit*float(emprecords[3]) # Comp Height
           if (current_section==".ELECTRICAL" or current_section==".MECHANICAL") and section_counter>2:
              comp_outline.append([float(emprecords[1])*emp_unit,float(emprecords[2])*emp_unit,float(emprecords[3])]) #add point of outline
    ***************
    *** 349,363 ****
          FreeCAD.Console.PrintMessage("Step models to be loaded for footprints: "+str(validkeys)+"\n")
          grp=doc.addObject("App::DocumentObjectGroup", "Step Lib")
          for validkey in validkeys:
    !          ImportGui.insert(step_path+model_dict[validkey],FreeCAD.ActiveDocument.Name)
    !          #partName=FreeCAD.ActiveDocument.ActiveObject.Name
    !          impPart=FreeCAD.ActiveDocument.ActiveObject
    !          #impPart.Shape=FreeCAD.ActiveDocument.ActiveObject.Shape
    !          #impPart.ViewObject.DiffuseColor=FreeCAD.ActiveDocument.ActiveObject.ViewObject.DiffuseColor
    !          impPart.ViewObject.Visibility=0
    !          impPart.Label=validkey
    !          grp.addObject(impPart)
    !          step_dict.append((validkey,impPart))
               FreeCAD.Console.PrintMessage("Reading step file "+str(model_dict[validkey])+" for footprint "+str(validkey)+"\n")
          step_dict=dict(step_dict)
          grp=doc.addObject("App::DocumentObjectGroup", "Step Models")
    --- 350,362 ----
          FreeCAD.Console.PrintMessage("Step models to be loaded for footprints: "+str(validkeys)+"\n")
          grp=doc.addObject("App::DocumentObjectGroup", "Step Lib")
          for validkey in validkeys:
    !          shape=Part.Shape()
    !          shape.read(step_path+model_dict[validkey])
    !          shapeobj = doc.addObject("Part::Feature",validkey)
    !          shapeobj.Shape = shape
    !          shapeobj.ViewObject.Visibility=0
    !          grp.addObject(shapeobj)
    !          step_dict.append((validkey,shapeobj))
               FreeCAD.Console.PrintMessage("Reading step file "+str(model_dict[validkey])+" for footprint "+str(validkey)+"\n")
          step_dict=dict(step_dict)
          grp=doc.addObject("App::DocumentObjectGroup", "Step Models")
    ***************
    *** 378,383 ****
    --- 377,389 ----
              placmnt=Base.Placement(Base.Vector(place_item[3],place_item[4],z_pos),toQuaternion(rotateY,place_item[5]*pi/180,0))
              step_model.Placement=placmnt
              grp.addObject(step_model)
    +         if EMP_remove==1:
    +            empobj = doc.getObject(place_item[0])
    +            # Fixme: should check if the object really exists?
    +            empobj.ViewObject.Visibility=0
    +         if EMP_remove==2:
    +            # Fixme: should check if the object really exists?
    +            FreeCAD.ActiveDocument.removeObject(place_item[0])
            else: 
              if IDF_diag==1:
                  model_file.writelines(str(place_item[0])+" "+str(place_item[2])+"\n")
    

    (0011499)
    stefan.althoefer   
    2018-07-06 22:14   
    I see that there is no demo IDF file set in the distribution. If you lack such thing for testing, I should be able to create one.
    (0011500)
    Kunda1   
    2018-07-08 15:15   
    @stefan.althoefer can you submit a PR to https://github.com/FreeCAD/FreeCAD ?
    (0011501)
    Kunda1   
    2018-07-08 15:16   
    @yorik care to weigh in on this ?
    (0011508)
    stefan.althoefer   
    2018-07-09 21:01   
    @Kunda1 regarding PR: Difficult, never did it before ...
    (0011511)
    Kunda1   
    2018-07-10 13:59   
    @chrisb would you please test and/or make a PR from 0002821:0011498 ?
    (0011514)
    chrisb   
    2018-07-12 09:00   
    I have no idea of IDF and very little of STEP. I see only @vejmarie who can handle this.
    (0011853)
    Kunda1   
    2018-09-26 13:55   
    @stefan.althoefer I'm having issues applying the patch
    
    patching file Idf.py
    patch: **** malformed patch at line 17: if current_section==".PLACEMENT"  and section_counter>1 and fmod(section_counter,2)==0:
    
    Can you rebase it? I'll apply it once you do.

    Also if you want to learn some quick and dirty 'git' check-out https://www.freecadweb.org/wiki/Source_code_management
    (0012047)
    Kunda1   
    2018-10-17 20:16   
    @stefan.althoefer ping
    (0012048)
    Kunda1   
    2018-10-17 20:19   
    Added forum thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=31627
    (0012067)
    Kunda1   
    2018-10-19 13:21   
    @stefan.althoefer ping^2
    (0012136)
    Kunda1   
    2018-11-05 18:29   
    @stefan.althoefer ping
    (0012828)
    Kunda1   
    2019-03-03 14:08   
    @vejmarie ping
    (0013992)
    Kunda1   
    2020-01-06 15:56   
    PING
    (0016511)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5676.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2738 [FreeCAD] Feature feature always 2016-10-17 07:23 2021-02-06 06:49
    Reporter: Fredus69 Platform:  
    Assigned To: sgrogan OS:  
    Priority: high OS Version:  
    Status: assigned Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Provide Hash source installation
    Description: Please, provide Hash information of the binaries in all versions and OS of FreeCAD on the download page product.
    In deed, this information is important to be sure that integrity installation source is ok and can be trust.

    Thanks
    Tags: packaging
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0007627)
    Kunda1   
    2017-01-11 13:06   
    Forum Thread: http://forum.freecadweb.org/viewtopic.php?f=4&t=19790
    (0007628)
    wmayer   
    2017-01-11 13:09   
    @sgrogan can you have a look at this, please?
    (0011170)
    rolandog   
    2018-04-20 19:02   
    Hi. I just created a script for the creation of a digest of SHA-256 checksums of the files in a directory. You can control the 'base directory', the 'output directory' and the 'block size' (read at most 'block size' bytes from each file).

    It is python 2.7 compatible code, as sys.version in FreeCAD 0.17 prints:
    '2.7.14 (default, Jan 16 2018, 16:11:42) [MSC v.1800 64 bit (AMD64)'

    Hopefully it will help with the automated creation of digests of hashes of future releases. I also published it as a gist, but I'm unsure that -- as a newly registered user -- that I can paste URLs here and not get automatically flagged as a spammer.

    So, here's the code of sha256digest.py:

    
    # -*- coding: utf-8 -*-
    """
    Script to create SHA-256 digest of all files in the current directory
    
    Based on an answer by Richard Neumann on Code Review
    https://codereview.stackexchange.com/a/147191
    
    Based on recommendation that file digests are created nowadays
    https://en.wikipedia.org/wiki/File_verification#File_formats
    
    Created on Fri Apr 20 12:07:41 2018
    
    @author: rolandog
    """
    
    
    from os import getcwd, listdir
    from os.path import join, isfile
    from time import strftime
    from hashlib import sha256
    
    
    def list_files(basedir=None):
        """List only files within the respective directory"""
    
        if basedir is None:
            basedir = getcwd()
    
        for item in listdir(basedir):
            path = join(basedir, item)
    
            # skip listing a hash of our hash digest
            if "sha256-digest" in item:
                continue
    
            if isfile(path):
                # changed so that we get the path and the filename
                yield (path, item)
    
    
    def sha256sum(file_name, block_size=None):
        """Returns the sha256 checksum of the respective file"""
    
        if block_size is None:
            block_size = 4096
    
        checksum = sha256()
    
        with open(file_name, "rb") as file_handle:
            block = file_handle.read(block_size)
    
            while block:
                checksum.update(block)
                block = file_handle.read(block_size)
    
        return checksum.hexdigest()
    
    
    def sha256sums(basedir=None, block_size=None):
        """Yields (<sha256sum>, <file_name>) tuples
        for files within the basedir.
        """
    
        for file_path, file_name in list_files(basedir=basedir):
            yield (sha256sum(file_path, block_size=block_size), file_name)
    
    
    def create_sha256_digest(basedir=None, block_size=None, outputdir=None):
        """Creates de sha256-digest file with a timestamp"""
    
        hash_file_name = strftime("sha256-digest_%Y%m%d-%H%M%S")
    
        if outputdir is None:
            outputdir = getcwd()
    
        hash_file_path = join(outputdir, hash_file_name)
    
        with open(hash_file_path, "w") as file_handle:
            for file_hash in sha256sums(basedir, block_size):
                file_handle.write(" *".join(file_hash) + "\n")
    
    
    if __name__ == "__main__":
        import argparse
        PARSER = argparse.ArgumentParser()
        PARSER.add_argument("-d",
                            "--directory",
                            default=None,
                            type=str,
                            required=False,
                            help="Path, str, to the directory of the files")
        PARSER.add_argument("-b",
                            "--blocksize",
                            default=None,
                            type=int,
                            required=False,
                            help="Block size, int, in bytes to read from files")
        PARSER.add_argument("-o",
                            "--outputdir",
                            default=None,
                            type=str,
                            required=False,
                            help="Output directory, str, for sha256 digest")
        ARGUMENTS = PARSER.parse_args()
        create_sha256_digest(basedir=ARGUMENTS.directory,
                             block_size=ARGUMENTS.blocksize,
                             outputdir=ARGUMENTS.outputdir)
    
    
    (0011183)
    rolandog   
    2018-04-23 16:43   
    I updated my script so that it has a permissive license and that it can also output individual sha256 files (if needed), though it defaults to a digest of checksums and filenames:

    
    # -*- coding: utf-8 -*-
    """
    Purpose
    =======
    Creates a SHA-256 digest of files in a directory
    
    
    Attributions
    ============
    Based on an answer by Richard Neumann on Code Review
    https://codereview.stackexchange.com/a/147191
    
    
    Based on statement that file digests are considered best-practice as of 2012
    https://en.wikipedia.org/wiki/File_verification#File_formats
    
    
    Creation and Modification Times
    ===============================
    Created on Fri Apr 20 12:07:41 2018
    Last Modified on Mon Apr 23 09:50:21 2018
    
    
    License
    =======
    License: Creative Commons CC0
    License URL: https://creativecommons.org/publicdomain/zero/1.0/legalcode
    
    
    Changelog
    =========
    * 0.0.2
        - Added option to request individual files instead of digest
        - Don't output hash of currently running script
        - Added changelog
        - Added last modified date
        - Added example usage by developer and end-user
        - Added Creative Commons CC0 License
    * 0.0.1
        - Initial release.
    
    
    @author: rolandog
    @version: 0.0.2
    """
    
    
    from os import getcwd, listdir
    from os.path import join, isfile, basename
    from time import strftime
    from hashlib import sha256
    from textwrap import dedent
    
    
    def list_files(basedir=None):
        """List only files within the respective directory"""
    
        if basedir is None:
            basedir = getcwd()
    
        # gets the name of the running script
        script_name = basename(__file__)
    
        for item in listdir(basedir):
            path = join(basedir, item)
    
            # don't make a hash of a hash file or current file
            if "sha256-digest" in item or ".sha256" in item or script_name in item:
                continue
    
            if isfile(path):
                # changed so that we get the path and the filename
                yield (path, item)
    
    
    def sha256sum(file_name, block_size=None):
        """Returns the sha256 checksum of the respective file"""
    
        if block_size is None:
            block_size = 4096
    
        checksum = sha256()
    
        with open(file_name, "rb") as file_handle:
            block = file_handle.read(block_size)
    
            while block:
                checksum.update(block)
                block = file_handle.read(block_size)
    
        return checksum.hexdigest()
    
    
    def sha256sums(basedir=None, block_size=None):
        """Yields (<sha256sum>, <file_name>) tuples
        for files within the basedir.
        """
    
        for file_path, file_name in list_files(basedir=basedir):
            yield (sha256sum(file_path, block_size=block_size), file_name)
    
    
    def create_sha256_digest(basedir=None,
                             block_size=None,
                             outputdir=None,
                             individual=False):
        """Creates de sha256-digest file with a timestamp"""
    
        if outputdir is None:
            outputdir = getcwd()
    
        if individual is False:
            hash_file_name = strftime("sha256-digest_%Y%m%d-%H%M%S")
            hash_file_path = join(outputdir, hash_file_name)
    
            with open(hash_file_path, "w") as file_handle:
                for file_hash in sha256sums(basedir, block_size):
                    file_handle.write(" *".join(file_hash) + "\n")
        else:
            for checksum, file_name in sha256sums(basedir, block_size):
                hash_file_name = file_name + ".sha256"
                hash_file_path = join(outputdir, hash_file_name)
                with open(hash_file_path, "w") as file_handle:
                    file_handle.write(" *".join((checksum, file_name)) + "\n")
    
    
    if __name__ == "__main__":
        from argparse import ArgumentParser, RawDescriptionHelpFormatter
        DESCRIPTION = "Creates a SHA-256 digest of files in a directory"
        EPILOG = """\
            example usage by developer
            --------------------------
            ls
                hello-world.txt  sha256digest.py
    
            cat hello-world.txt
                Hello, World!
    
            python sha256digest.py -i
    
            ls
                hello-world.txt  hello-world.txt.sha256  sha256digest.py
    
            cat hello-world.txt.sha256
                c98c24b677eff44860afea6f493bbaec5bb1c4cbb209c6fc2bbb47f66ff2ad31 *hello-world.txt
    
    
            example usage by end-user
            -------------------------
            ls
                hello-world.txt  hello-world.txt.sha256
    
            sha256sum -c hello-world.txt.sha256
                hello-world.txt: OK
            """
        PARSER = ArgumentParser(prog="sha256digest.py",
                                description=DESCRIPTION,
                                formatter_class=RawDescriptionHelpFormatter,
                                epilog=dedent(EPILOG))
        PARSER.add_argument("-i",
                            "--individual",
                            default=False,
                            action="store_true",
                            required=False,
                            help="outputs one hash file per file in folder")
        PARSER.add_argument("-d",
                            "--directory",
                            default=None,
                            type=str,
                            required=False,
                            help="path to the folder containing the files")
        PARSER.add_argument("-b",
                            "--blocksize",
                            default=None,
                            type=int,
                            required=False,
                            help="read files in chunks less than BLOCKSIZE bytes")
        PARSER.add_argument("-o",
                            "--outputdir",
                            default=None,
                            type=str,
                            required=False,
                            help="output directory for sha256 digest or files")
        ARGUMENTS = PARSER.parse_args()
        create_sha256_digest(basedir=ARGUMENTS.directory,
                             block_size=ARGUMENTS.blocksize,
                             outputdir=ARGUMENTS.outputdir,
                             individual=ARGUMENTS.individual)
    
    
    (0011243)
    rolandog   
    2018-05-10 17:01   
    Maybe a link in the Wiki pointing to the GitHub releases section, and having the hashes consistently published together with the binaries can help mark this issue as a fixed/resolved one?
    (0012263)
    Kunda1   
    2018-12-12 02:58   
    another discussion related to this ticket at https://forum.freecadweb.org/viewtopic.php?f=10&t=32738&p=273919#p273896
    (0016504)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5669.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2437 [FreeCAD] Feature major always 2016-02-05 14:20 2021-02-06 06:49
    Reporter: jimhigson Platform: OSX  
    Assigned To: OS: OSX  
    Priority: normal OS Version: El Capitan  
    Status: acknowledged Product Version: 0.15  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Trackpad navigation on mac does not use full capabilities of the trackpad
    Description: OSX conventions are:

    * Pinch to zoom in/out (currently this is done via scroll gesture)
    * 2-finger scroll gesture to pan (currently done via shift-move)
    * Recognise sideways scrolling (ie 2d, not 1d as with mouse wheel)

    These changes would make better use of the extended touch capabilities on mac laptops and the Apple magic touchpad.


    Tags: Bountysource Potential, gesture, macOS, Qt5, trackpad
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0008184)
    Kunda1   
    2017-02-03 00:18   
    From http://doc.qt.io/qt-5/qnativegestureevent.html

    Event Type: Qt::ZoomNativeGesture
    Description: Magnification delta in percent.
    Touch-equence: macOS: Two-finger pinch.
    URL: http://doc.qt.io/qt-5/qt.html#NativeGestureType-enum

    Event Type: Qt::SmartZoomNativeGesture
    Description: Boolean magnification state.
    Touch-equence: macOS: Two-finger douple tap (trackpad) / One-finger douple tap (magic mouse).
    URL: http://doc.qt.io/qt-5/qt.html#NativeGestureType-enum

    Event Type: Qt::RotateNativeGesture
    Description: Rotation delta in degrees.
    Touch-equence: macOS: Two-finger rotate.
    URL: http://doc.qt.io/qt-5/qt.html#NativeGestureType-enum
    (0009213)
    Kunda1   
    2017-05-31 05:06   
    (Last edited: 2017-12-04 15:03)
    Trackpad navigation on Linux: https://github.com/JoseExposito/touchegg

    (0013229)
    Kunda1   
    2019-06-17 06:27   
    Relevant 0003995 and https://forum.freecadweb.org/viewtopic.php?f=9&t=36387
    (0016475)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5640.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    897 [FreeCAD] Feature feature N/A 2012-12-04 13:21 2021-02-06 06:49
    Reporter: scopaev Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Map a 2D image onto the face of a 3D object
    Description: The ability to take a Jpg or png file and map it onto just one face of a 3D object.

    This would be useful for things like making labels, or placing images onto the top and bottom of an unpopulated circuit board to give it a life-like appearance.

    It would be helpful if the image could:
      1 be rotated at any angle
      2 be scaled to any value
      3 be positioned horz/vertically
      4 be autocentered with the click of a checkbox
      5 be mirrored (for placing images on the bottoms of things)

    Perhaps later on (way later ;-) ) the mapping could go beyond just working on flat planes.
    Ex. If I had a 3D scanned image of a persons head & I had a picture of the front of their face, ideally I would like to map the image onto the front of the 3D head (through just horizontal projection or something?).
    Tags:
    Steps To Reproduce:
    Additional Information: https://forum.freecadweb.org/viewtopic.php?f=3&t=3193
    Attached Files:
    Notes
    (0011662)
    Kunda1   
    2018-08-26 11:22   
    Replaced old sourceforge URL in the ticket summary
    (0014183)
    Kunda1   
    2020-02-26 01:54   
    See https://www.freecadweb.org/wiki/Part_ProjectionOnSurface
    (0016395)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5560.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4506 [FreeCAD] Feature feature always 2020-11-28 11:32 2021-02-06 06:49
    Reporter: tectone Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Ubuntu 19.04 (XFCE/xubuntu)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.22960 (Git) AppImage
    Build type: Release
    Branch: master
    Hash: c5a4b01d2e4218bcc0eb6650337650a6c65ef0e4
    Python version: 3.8.6
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: German/Germany (de_DE)
    Summary: Make it possible to copy items like bodys, primitives, solids, partgroups, sketches etc directly into partgroups, groups, comp.
    Description: Link of forum discussion: https://forum.freecadweb.org/viewtopic.php?f=3&t=52573

    Freecad as of today, lacks the vital capability to mimic the standard file management behavior that is used by basically every computer system in use in the tree view window that is used to access various items which are used to model objects in the software. This applies for operation systems like advertised from Microsoft and Apple but also for every Linux, Unix and Debian system and normally for every type of software like files managers (Explorer, Thunar, Dolphin etc.) but also for word processing software like Microsoft word, libreoffice, openoffice, abiword and most gui based editors. Here the behavior is, that during a copy action of files or data, first the selection is made and afterwards the data is transferd by the key combination Ctrl+C to the clipboard. Afterwards with Ctrl+V the data is transferred/copied from the clipboard to a new target location. For example one copies a sentence in word, copies the data to the clipboard and then marks another sentence. When the data is actually copied, the marked sentence gets overwritten by the content of the clipboard. Alternatively a position of the cursor can be selected and this becomes the new target of the data from the clipboard without overwriting data. The behavior of the named file managers works very similar. It is possible to copy, move or link files which is a visual representation of the bash commands cp, mv, ln (or the commands that that achieve the same result when they are named differently).
    Tags: #lowhangingfruit, 0.19, file, tree view
    Steps To Reproduce: Freecad violates this de facto standard of file handling which was described above, because it lacks the capability of making directed mv, cp and ln correspondences of those commands directly from the clipboard in the tree view. If an item is copied (a solid, a partgroup, a body etc.) with the intention to directly copy and move or copy and link it to another grouping element (partgroup, group, compound, etc.) it goes to the root directory or the project instead. Manually selecting the items and moving/linking them to the right directions/targets is time consuming, it slows down the work flow of the user and it can make the whole project very unstructured, because after a series of copy and paste operations, a large number or items accumulate in the root directory instead of their intended target location. This is a counter intuitive and time consuming lack of functionality that does not show much weight in smaller projects with just a small number of objects. In large projects the file management becomes extremely uncomfortable and confusing.
    Additional Information: I do not include a project file, because this is the standard behavior for every version of freecad, independently from the actual project. My proposal for this feature request is, that the new standard behavior is, that the user gets the option to copy directly to a selected area(active body, etc). This could be achieved with the standard Ctrl+C, Ctrl+V combination. If one intends to copy directly to the root directly without using the tree view before, one could use a different combination like Ctrl+Alt+C and Ctrl+Alt+V to achieve this different result in a fast and convenient way.
    Attached Files:
    Notes
    (0016967)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6134.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4502 [FreeCAD] Feature minor always 2020-11-25 11:12 2021-02-06 06:49
    Reporter: Pauvres_honteux Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: openSUSE Leap 15.1 (KDE//usr/share/xsessions/default)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.Unknown
    Build type: Release
    Python version: 3.6.5
    Qt version: 5.9.7
    Coin version: 4.0.0
    OCC version: 7.5.0
    Summary: Automate Link and ShapeBinder
    Description: See Automate Link and ShapeBinder
    Today one must first create a link-holder/container based on what you want to fill it with AND use it for, then fill it with the targeted object/feature. I say the user should not be bothered with the internals of linking. She/he should only need to decide whether to create a link or not.

    As seen in the forum thread I suggest it to be done as follows:

    Copy/ctrl+c then paste/ctrl+v(= Link or No link or Result or As is or ... etc [user sets a default for this]) or right click and choose other paste options.
    .
    If the user wants a link, then chose that type of pasting.
    .
    If the user wants a plain copy without link, then chose that type of pasting.
    .
    ... and so on and so forth.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016965)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6132.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4482 [FreeCAD] Feature feature always 2020-11-02 11:52 2021-02-06 06:49
    Reporter: Pauvres_honteux Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: openSUSE Leap 15.1 (KDE//usr/share/xsessions/default)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.Unknown
    Build type: Release
    Python version: 3.6.5
    Qt version: 5.9.7
    Coin version: 4.0.0
    OCC version: 7.5.0.beta
    Summary: Create point on plane while at the same time beeing connected to another point in/on the same plane.
    Description: Point on plane with respect to another point

    As of 2020-11-02

    it is not possible to create a point on a plane while at the same time being connected to another point on that plane.
    Tags:
    Steps To Reproduce: In Part:

    - Create 1:st point, to be used as master point.
    - Create 2:nd point and connect it to the first point by typing Vertex(vertex number here).Placement.Base.x Repeat for Y and Z. Set "Attachment offset" to [20,0,0].
    - Create 3:rd point and connect it to the first point by typing Vertex(vertex number here).Placement.Base.x Repeat for Y and Z. Set "Attachment offset" to [0,30,0].
    - Create 4:th point and connect it to the first point by typing Vertex(vertex number here).Placement.Base.x Repeat for Y and Z. Set "Attachment offset" to [0,0,40].
    - Create a plane_1 passing through point 1, 2 and 3.
    - Create a plane_2 passing through point 1, 3 and 4.
    - Create a plane_3 passing through point 1, 4 and 2.
    - Create a point on one of the planes and try to connect it to point 1 -> does not work.
    ______________________________________________________________________
    In PartDesign:

    - Create 1:st (Datum)point, to be used as master point.
    - Create 2:nd (Datum)point and connect it to the first point by choosing "Support" = (Datum)point 1 and Map Mode = Vertex. Set "Attachment" = [20,0,0]
    - Create 3:rd (Datum)point and connect it to the first point by choosing "Support" = (Datum)point 1 and Map Mode = Vertex. Set "Attachment" = [0,30,5]
    - Create 4:th (Datum)point and connect it to the first point by choosing "Support" = (Datum)point 1 and Map Mode = Vertex. Set "Attachment" = [-10,-15:40]
    - Create a plane_1 passing through point 1, 2 and 3 ("Map Mode" 'ThreePointsPlane').
    - Create a plane_2 passing through point 1, 3 and 4. ("Map Mode" 'ThreePointsPlane')
    - Create a plane_3 passing through point 1, 4 and 2. ("Map Mode" 'ThreePointsPlane')
    - Create a point on one of the planes and try to connect it to point 1 -> does not work.
    Additional Information:
    Attached Files:
    Notes
    (0016957)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6124.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4470 [FreeCAD] Bug minor always 2020-10-19 22:02 2021-02-06 06:49
    Reporter: BruceL Platform:  
    Assigned To: OS:  
    Priority: low OS Version:  
    Status: acknowledged Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Debian GNU/Linux bullseye/sid (GNOME/gnome)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.22665 (Git) AppImage
    Build type: Release
    Branch: master
    Hash: b0d7850406e046f3b7a8cd5da261e7d54df6bd99
    Python version: 3.8.6
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: English/Canada (en_CA)
    Summary: Crash on loft with twisted circles.
    Description: When executing a loft with a circles with 'twisted' starting points. FreeCAD will crash.
    Tags:
    Steps To Reproduce: 1. Open the attached file (part3.FCstd)
    2. Create a new subtractive loft starting with inner_0_sk
    3. Added sketches inner_1_sk, inner_2_sk, and inner_3_sk in that order.
    4. Click OK to accept the loft.
    5. FreeCAD crashes.

    forum post
    Additional Information:
    FreeCAD 0.19, Libs: 0.19R22665 (Git)
    © Juergen Riegel, Werner Mayer, Yorik van Havre and others 2001-2020
    FreeCAD is free and open-source software licensed under the terms of LGPL2+ license.
    FreeCAD wouldn't be possible without FreeCAD community.
      #####                 ####  ###   ####  
      #                    #      # #   #   # 
      #     ##  #### ####  #     #   #  #   # 
      ####  # # #  # #  #  #     #####  #   # 
      #     #   #### ####  #    #     # #   # 
      #     #   #    #     #    #     # #   #  ##  ##  ##
      #     #   #### ####   ### #     # ####   ##  ##  ##
    
    Loading Assembly4 WorkBench
    Program received signal SIGSEGV, Segmentation fault.
    #0  /lib/x86_64-linux-gnu/libc.so.6(+0x3be30) 
    #1  /tmp/.mount_FreeCAA40B2C/usr/lib/./libTKBool.so.7(+0x270559) 
    0000002  0x7fd54f9aef1b in BRepFill_CompatibleWires::SameNumberByPolarMethod(bool) from /tmp/.mount_FreeCAA40B2C/usr/lib/./libTKBool.so.7+0x130b
    0000003  0x7fd54f9b487a in BRepFill_CompatibleWires::Perform(bool) from /tmp/.mount_FreeCAA40B2C/usr/lib/./libTKBool.so.7+0xb6a
    0000004  0x7fd554b3b196 in BRepOffsetAPI_ThruSections::Build() from /tmp/.mount_FreeCAA40B2C/usr/lib/./libTKOffset.so.7+0x296
    0000005  0x7fd4ec437037 in PartDesign::Loft::execute() from /tmp/.mount_FreeCAA40B2C/usr/lib/_PartDesign.so+0x7f7
    0000006  0x7fd578c66ea2 in App::DocumentObject::recompute() from /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libFreeCADApp.so+0xf2
    0000007  0x7fd5552a713c in Part::Feature::recompute() from /tmp/.mount_FreeCAA40B2C/usr/lib/Part.so+0xc
    0000008  0x7fd578bf906c in App::Document::_recomputeFeature(App::DocumentObject*) from /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libFreeCADApp.so+0x31c
    0000009  0x7fd578c528bc in App::Document::recompute(std::vector<App::DocumentObject*, std::allocator<App::DocumentObject*> > const&, bool, bool*, int) from /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libFreeCADApp.so+0x60c
    0000010  0x7fd578cba5b2 in App::DocumentPy::recompute(_object*) from /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libFreeCADApp.so+0x382
    0000011  0x7fd578cbaa54 in App::DocumentPy::staticCallback_recompute(_object*, _object*) from /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libFreeCADApp.so+0x24
    0000012  /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libpython3.8.so.1.0(PyCFunction_Call+0xf7) 
    0000013  /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libpython3.8.so.1.0(_PyObject_MakeTpCall+0x250) 
    0000014  /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libpython3.8.so.1.0(_PyEval_EvalFrameDefault+0x4ea2) 
    0000015  /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libpython3.8.so.1.0(_PyEval_EvalCodeWithName+0x2e2) 
    0000016  /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libpython3.8.so.1.0(PyEval_EvalCodeEx+0x44) 
    0000017  /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libpython3.8.so.1.0(PyEval_EvalCode+0x1c) 
    0000018  /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libpython3.8.so.1.0(+0x219ecf) 
    0000019  /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libpython3.8.so.1.0(+0x252c44) 
    0000020  /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libpython3.8.so.1.0(PyRun_StringFlags+0x7d) 
    0000021  0x7fd57898a11a in Base::InterpreterSingleton::runString(char const*) from /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libFreeCADBase.so+0x6a
    0000022  0x7fd579723af8 in Gui::Command::_runCommand(char const*, int, Gui::Command::DoCmd_Type, char const*) from /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libFreeCADGui.so+0x98
    0000023  0x7fd4d1f97bd2 in void Gui::_cmdDocument<char const (&) >(Gui::Command::DoCmd_Type, App::Document const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, char const (&) ) from /tmp/.mount_FreeCAA40B2C/usr/lib/PartDesignGui.so+0x4b2
    0000024  0x7fd4d1f98465 in PartDesignGui::TaskDlgFeatureParameters::accept() from /tmp/.mount_FreeCAA40B2C/usr/lib/PartDesignGui.so+0x145
    0000025  0x7fd4d1f9be98 in PartDesignGui::TaskDlgSketchBasedParameters::accept() from /tmp/.mount_FreeCAA40B2C/usr/lib/PartDesignGui.so+0x4b8
    0000026  0x7fd4d2028259 in PartDesignGui::TaskDlgLoftParameters::accept() from /tmp/.mount_FreeCAA40B2C/usr/lib/PartDesignGui.so+0x579
    0000027  0x7fd5799c44e9 in Gui::TaskView::TaskView::accept() from /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libFreeCADGui.so+0x59
    0000028  0x7fd5773c60d2 in QMetaObject::activate(QObject*, int, int, void**) from /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libQt5Core.so.5+0x780
    0000029  /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libQt5Widgets.so.5(+0x274d73) 
    0000030  0x7fd5773c60d2 in QMetaObject::activate(QObject*, int, int, void**) from /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libQt5Core.so.5+0x780
    0000031  0x7fd577c73360 in QAbstractButton::clicked(bool) from /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libQt5Widgets.so.5+0x32
    0000032  /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libQt5Widgets.so.5(+0x20da19) 
    0000033  /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libQt5Widgets.so.5(+0x20e2ae) 
    0000034  0x7fd577c7434a in QAbstractButton::mouseReleaseEvent(QMouseEvent*) from /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libQt5Widgets.so.5+0x88
    0000035  0x7fd577c05c23 in QWidget::event(QEvent*) from /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libQt5Widgets.so.5+0x135
    0000036  0x7fd577bda83a in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libQt5Widgets.so.5+0xde
    0000037  0x7fd577bdf0a9 in QApplication::notify(QObject*, QEvent*) from /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libQt5Widgets.so.5+0x79d
    0000038  0x7fd5796f10c9 in Gui::GUIApplication::notify(QObject*, QEvent*) from /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libFreeCADGui.so+0x89
    #39  0x7fd5773afa9c in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libQt5Core.so.5+0x88
    #40  0x7fd577bde553 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool, bool) from /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libQt5Widgets.so.5+0x283
    0000041  /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libQt5Widgets.so.5(+0x1af580) 
    0000042  /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libQt5Widgets.so.5(+0x1b03d2) 
    0000043  0x7fd577bda83a in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libQt5Widgets.so.5+0xde
    0000044  0x7fd577be0405 in QApplication::notify(QObject*, QEvent*) from /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libQt5Widgets.so.5+0x1af9
    0000045  0x7fd5796f10c9 in Gui::GUIApplication::notify(QObject*, QEvent*) from /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libFreeCADGui.so+0x89
    0000046  0x7fd5773afa9c in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libQt5Core.so.5+0x88
    0000047  0x7fd577756724 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) from /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libQt5Gui.so.5+0x684
    0000048  0x7fd5777572f7 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) from /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libQt5Gui.so.5+0x175
    0000049  0x7fd577744020 in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libQt5Gui.so.5+0x64
    0000050  /tmp/.mount_FreeCAA40B2C/usr/plugins/platforms/../../lib/libQt5XcbQpa.so.5(+0x5b1ea) 
    0000051  /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/./libglib-2.0.so.0(g_main_context_dispatch+0x2cb) 
    0000052  /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/./libglib-2.0.so.0(+0x54ff1) 
    0000053  /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/./libglib-2.0.so.0(g_main_context_iteration+0x2e) 
    0000054  0x7fd5773ded23 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libQt5Core.so.5+0x63
    0000055  0x7fd5773ac4d7 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) from /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libQt5Core.so.5+0x187
    0000056  0x7fd5773b034f in QCoreApplication::exec() from /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libQt5Core.so.5+0x105
    0000057  0x7fd5796674f2 in Gui::Application::runApplication() from /tmp/.mount_FreeCAA40B2C/usr/bin/../lib/libFreeCADGui.so+0x15a2
    0000058  /tmp/.mount_FreeCAA40B2C/usr/bin/freecad(+0x37cd) 
    0000059  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea) 
    0000060  /tmp/.mount_FreeCAA40B2C/usr/bin/freecad(+0x4521) 
    
    Attached Files: part3.FCStd (37,855 bytes) 2020-10-19 22:02
    https://tracker.freecad.org/file_download.php?file_id=2548&type=bug
    Notes
    (0016952)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6119.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4446 [FreeCAD] Bug major always 2020-09-27 18:55 2021-02-06 06:49
    Reporter: qwerty_f Platform: Mac  
    Assigned To: OS: Catalina  
    Priority: normal OS Version: 10.15.6 (19G2021  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: macOS 10.15
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.22474 (Git)
    Build type: Release
    Branch: master
    Hash: a44f8ffd427fa9b23b1f00dbf62d66cd152cd774
    Python version: 3.8.5
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: C/Default (C)
    Summary: Fullscreen renders nothing
    Description: Since I randomly hit the touchbar turning on full screen FreeCAD switches to full screen mode. Noting except for the sides-cube and the axis icon is rendered. Nothing else. Closing the screen returns to an empty window. Only escape is to close FreeCAD and start over.
    Tags: #pending-forum, GUI, macOS
    Steps To Reproduce: (Intentionally) Hit the hot key for full screen (on my machines it's F11).
    Additional Information:
    Attached Files:
    Notes
    (0014809)
    openBrain   
    2020-10-09 21:24   
    @qwerty_f : please address your issue according our reporting guidelines by opening a new topic on our forum. Thx
    Consider searching for similar report in our forum, IIRC there already is a thread about this.
    (0014812)
    qwerty_f   
    2020-10-09 21:39   
    @openBrain will do so
    (0014813)
    Kunda1   
    2020-10-10 12:03   
    @vejmarie can you confirm?
    (0014859)
    Kunda1   
    2020-10-15 14:11   
    Discussion thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=51187
    (0014862)
    qwerty_f   
    2020-10-15 15:33   
    Uhm, I already entered into a similar thread about full screen to see what the outcome would be. Nothing so far, so another one seems superfluous. Sorry for the confusion.
    (0014863)
    Kunda1   
    2020-10-15 15:50   
    @qwerty_f this is bugtracker that tracks the progress of bugs/features. If you don't post the forum thread associated with the ticket as openBrain pointed out in 0004446:0014809 then it's only superfluous to you and not the rest of us reading this ticket.
    (0014864)
    Kunda1   
    2020-10-15 15:50   
    @chrisb can you confirm issue on macOS?
    (0016941)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6108.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4438 [FreeCAD] Feature feature N/A 2020-09-18 11:13 2021-02-06 06:49
    Reporter: Pauvres_honteux Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: All OS's, all versions.
    Summary: Flippin' direction of line / curve
    Description: While discussing https://forum.freecadweb.org/viewtopic.php?f=34&t=44278&start=10&sid=6e87795aa14b31f3b0ce47060b5f0f7e the denomination of the command "Reverting shape" it came to my attention that flippin' the direction of a line or curve was missing.
    Therefore I hereby request it to be added to "Reverting shape".

    I also request a name change of "Reverting shape" to "flip normal/direction".

    And finally I request a new icon in the tree somehow involving an arrow of some sort.
    And a clickable arrow in the 3D-viewport attached to the marked line/curve/plane/surface.
    Tags:
    Steps To Reproduce: Doesn't exist.
    Additional Information:
    Attached Files:
    Notes
    (0014761)
    Pauvres_honteux   
    2020-09-18 11:19   
    ... this homepage is not mobile friendly at all... =O(
    (0016938)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6105.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4423 [FreeCAD] Bug minor always 2020-08-25 08:23 2021-02-06 06:49
    Reporter: Roy_043 Platform:  
    Assigned To: OS: Windows  
    Priority: low OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 8.1 (6.3)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.22262 (Git)
    Build type: Release
    Branch: master
    Hash: f56825c79f11b75648a7a0dcc8a9f52bb4574e61
    Python version: 3.6.8
    Qt version: 5.12.1
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: Dutch/Netherlands (nl_NL)
    Summary: qwindowsvistastyle.dll does not style the line color
    Description: The lines (frames) in task panels and dialog boxes are not styled by qwindowsvistastyle.dll but the background is. In recent Windows version the default line color is light gray. This color is almost indistinguishable from the light blue background color.
    Tags: UI
    Steps To Reproduce:
    1. Start any command that shows a task panel or dialog box.
    2. The frame lines in the task panel/dialog box are almost invisible.
    3. Exit FreeCAD.
    4. Rename \bin\styles\qwindowsvistastyle.dll
    5. Restart FreeCAD.
    6. Start any command that shows a task panel or dialog box.
    7. The frame lines in the task panel/dialog box are visible now.
    8. But the this workaround has a negative side-effect: Selected option, f.e. in the Draft Snap toolbar are harder to distinguish.
    Additional Information: Related Forum topics:
    https://forum.freecadweb.org/viewtopic.php?f=3&t=49191
    https://forum.freecadweb.org/viewtopic.php?f=3&t=45022
    https://forum.freecadweb.org/viewtopic.php?f=21&t=49174 (where the issue has been confirmed)
    Attached Files:
    Notes
    (0014709)
    Roy_043   
    2020-08-25 08:47   
    Oops: the summary should be: qwindowsvistastyle.dll does NOT style the line color
    (0014710)
    Roy_043   
    2020-08-25 09:11   
    (Last edited: 2020-08-25 09:13)
    Oops 2: the DLL that should be renamed in step 4 is \bin\styles\qwindowsvistastyle.dll
    (0014725)
    Kunda1   
    2020-09-03 21:52   
    revised summary
    (0016935)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6102.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4415 [FreeCAD] Bug minor always 2020-08-03 12:40 2021-02-06 06:49
    Reporter: Roy_043 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 8.1 (6.3)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.22111 (Git)
    Build type: Release
    Branch: master
    Hash: cb2099aa6bb287a8d7843eb70684cce79bdef26b
    Python version: 3.6.8
    Qt version: 5.12.1
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: Dutch/Netherlands (nl_NL)
    Summary: Toolbar-only command must be visible for custom shortcut to work
    Description: For some reason a toolbar-only command (= a command that is not included in any menu) must be visible for the assigned custom shortcut to work. This seems like a strange limitation. One of the reasons for assigning shortcuts can be that you do not want to display the toolbar.
    Tags:
    Steps To Reproduce:
    1. Invoke the Std_DlgCustomize command.
    2. Assign a shortcut to the Std_Part command. The command can be found in the Structure category.
    3. Test the shortcut with the Structure toolbar visible.
    4. Result: OK.
    5. Disable the Structure toolbar.
    6. Re-test the shortcut.
    7. Result: the shortcut does not work anymore.
    Additional Information: Bug topic:
    https://forum.freecadweb.org/viewtopic.php?f=3&t=45896

    openBrain's analysis:
    https://forum.freecadweb.org/viewtopic.php?f=3&t=48949#p419162
    Attached Files:
    Notes
    (0016930)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6097.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4402 [FreeCAD] Feature major always 2020-07-08 10:58 2021-02-06 06:49
    Reporter: HoWil Platform:  
    Assigned To: wmayer OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: <!--ATTENTION:
    COMPLETELY ERASE THIS AFTER PASTING YOUR
    Help > About FreeCAD > Copy to clipboard
    NOTE: just the snippet alone will do without anything else included.
    The ticket will not be submitted without it.
    -->
    Summary: scientific notation for displaying numbers
    Description: I ask for using the scientific notation for displaying numbers where it is necessary.
    The reason is the following.
    I often use FEM and among others have to edit solver settings in the range of 1e-5 to 1e-9. All of these settings are simply shown as 0.0.

    I know that it is already possible to enter number in scientific notation. I ask for some additional switch in the preferences next to 'number of decimals called something like 'use scientific notation to display numbers where necessary?'

    The formula editor can help here. One can insert 1e-9 and the following is shown in the Value-column in the Data-Tab: 0,00 (1e-6). But I have to use the formula editor first which means I have to add all necessary (pre-filled) values into the formula editor to see/recognize it in the Value-column.
    Below you see an example where the entry for Linear Tolerance is 0,00000001 and is shown as "0,0" where 1e-8 would be nice. When I would like to change it without formula editor I would have to set the number of decimals to 8 making other dialogues hard to use because of many unnecessary zeros.
    Under Steady State Tolerance you can see the value "0,00 with (1e-9)" using the formula editor.
    Tags: display, formula, NumberFormat, Precision, Solver(FEM), spinbox
    Steps To Reproduce:
    Additional Information: Please see also :
    https://forum.freecadweb.org/viewtopic.php?f=8&t=48229
    Attached Files:
    Notes
    (0016922)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6089.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4354 [FreeCAD] Bug feature always 2020-05-31 09:17 2021-02-06 06:49
    Reporter: nikto_b Platform: Linux Wayland  
    Assigned To: OS: Arch Linux  
    Priority: low OS Version: Linux 5.6.12  
    Status: feedback Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Arch Linux (Unity)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.21329 (Git)
    Build type: Release
    Branch: master
    Hash: 2330eef823b32ac412d839031cc174353a76b013
    Python version: 3.8.3
    Qt version: 5.14.2
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: Russian/Russia (ru_RU)
    Summary: Native run on wayland?
    Description: Crashes at opening of any .FCStd file when QT_QPA_PLATFORM set to wayland-egl
    Fixes by setting that to xcb (running via xwayland)
    There is stacktrace
    
    Program received signal SIGSEGV, Segmentation fault.
    #0  /usr/lib/libc.so.6(+0x3c3e0) [0x7fc47a9213e0]
    #1  /usr/lib/libX11.so.6(XDefaultScreenOfDisplay+0) [0x7fc476ae9200]
    0000002  /usr/lib/libCoin.so.80(+0x448c4f) [0x7fc47a44fc4f]
    0000003  /usr/lib/libCoin.so.80(glxglue_init+0x3d) [0x7fc47a4506ad]
    0000004  /usr/lib/libCoin.so.80(cc_glglue_instance+0x243) [0x7fc47a448c63]
    0000005  0x7fc47a2c49f9 in SoGLRenderActionP::isDirectRendering(SoState const*) const from /usr/lib/libCoin.so.80+0x49
    0000006  0x7fc47a2c6e1d in SoGLRenderActionP::render(SoNode*) from /usr/lib/libCoin.so.80+0xcd
    0000007  0x7fc47a2c7072 in SoGLRenderAction::beginTraversal(SoNode*) from /usr/lib/libCoin.so.80+0xa2
    0000008  0x7fc47a2c02ea in SoAction::apply(SoNode*) from /usr/lib/libCoin.so.80+0x2ea
    0000009  0x7fc47d18857a in Gui::SoBoxSelectionRenderAction::apply(SoNode*) from /usr/lib/freecad/lib/libFreeCADGui.so+0x2a
    0000010  0x7fc47d23e316 in Gui::View3DInventorViewer::renderScene() from /usr/lib/freecad/lib/libFreeCADGui.so+0x156
    0000011  0x7fc47d1fe4ed in SIM::Coin3D::Quarter::QuarterWidget::paintEvent(QPaintEvent*) from /usr/lib/freecad/lib/libFreeCADGui.so+0x33d
    0000012  0x7fc47d208d15 in SIM::Coin3D::Quarter::SoQTQuarterAdaptor::paintEvent(QPaintEvent*) from /usr/lib/freecad/lib/libFreeCADGui.so+0x45
    0000013  0x7fc47ba360ce in QWidget::event(QEvent*) from /usr/lib/libQt5Widgets.so.5+0x1ce
    0000014  0x7fc47bae0adf in QFrame::event(QEvent*) from /usr/lib/libQt5Widgets.so.5+0x1f
    0000015  0x7fc47af4cfeb in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) from /usr/lib/libQt5Core.so.5+0x8b
    0000016  0x7fc47b9f4641 in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /usr/lib/libQt5Widgets.so.5+0x71
    0000017  0x7fc47cf1ecb9 in Gui::GUIApplication::notify(QObject*, QEvent*) from /usr/lib/freecad/lib/libFreeCADGui.so+0x89
    0000018  0x7fc47af4d2d2 in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /usr/lib/libQt5Core.so.5+0x182
    0000019  0x7fc47ba2e108 in QWidgetPrivate::sendPaintEvent(QRegion const&) from /usr/lib/libQt5Widgets.so.5+0x38
    0000020  0x7fc47ba2e97c in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags<QWidgetPrivate::DrawWidgetFlag>, QPainter*, QWidgetRepaintManager*) from /usr/lib/libQt5Widgets.so.5+0x81c
    0000021  0x7fc47ba2fd40 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, QFlags<QWidgetPrivate::DrawWidgetFlag>, QPainter*, QWidgetRepaintManager*) from /usr/lib/libQt5Widgets.so.5+0x510
    0000022  0x7fc47ba2e68d in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags<QWidgetPrivate::DrawWidgetFlag>, QPainter*, QWidgetRepaintManager*) from /usr/lib/libQt5Widgets.so.5+0x52d
    0000023  0x7fc47ba2fd40 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, QFlags<QWidgetPrivate::DrawWidgetFlag>, QPainter*, QWidgetRepaintManager*) from /usr/lib/libQt5Widgets.so.5+0x510
    0000024  0x7fc47ba2e68d in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags<QWidgetPrivate::DrawWidgetFlag>, QPainter*, QWidgetRepaintManager*) from /usr/lib/libQt5Widgets.so.5+0x52d
    0000025  0x7fc47ba2fd40 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, QFlags<QWidgetPrivate::DrawWidgetFlag>, QPainter*, QWidgetRepaintManager*) from /usr/lib/libQt5Widgets.so.5+0x510
    0000026  0x7fc47ba2e68d in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags<QWidgetPrivate::DrawWidgetFlag>, QPainter*, QWidgetRepaintManager*) from /usr/lib/libQt5Widgets.so.5+0x52d
    0000027  0x7fc47ba2fd40 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, QFlags<QWidgetPrivate::DrawWidgetFlag>, QPainter*, QWidgetRepaintManager*) from /usr/lib/libQt5Widgets.so.5+0x510
    0000028  0x7fc47ba2e68d in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags<QWidgetPrivate::DrawWidgetFlag>, QPainter*, QWidgetRepaintManager*) from /usr/lib/libQt5Widgets.so.5+0x52d
    0000029  /usr/lib/libQt5Widgets.so.5(+0x16c7d6) [0x7fc47ba057d6]
    0000030  0x7fc47ba3681b in QWidget::event(QEvent*) from /usr/lib/libQt5Widgets.so.5+0x91b
    0000031  0x7fc47b9f4652 in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /usr/lib/libQt5Widgets.so.5+0x82
    0000032  0x7fc47cf1ecb9 in Gui::GUIApplication::notify(QObject*, QEvent*) from /usr/lib/freecad/lib/libFreeCADGui.so+0x89
    0000033  0x7fc47af4d2d2 in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /usr/lib/libQt5Core.so.5+0x182
    0000034  0x7fc47af4fce3 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) from /usr/lib/libQt5Core.so.5+0x173
    0000035  /usr/lib/libQt5Widgets.so.5(+0x47bd17) [0x7fc47bd14d17]
    0000036  0x7fc47af79142 in QObject::event(QEvent*) from /usr/lib/libQt5Core.so.5+0x292
    0000037  0x7fc47b9f4652 in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /usr/lib/libQt5Widgets.so.5+0x82
    0000038  0x7fc47cf1ecb9 in Gui::GUIApplication::notify(QObject*, QEvent*) from /usr/lib/freecad/lib/libFreeCADGui.so+0x89
    #39  0x7fc47af4d2d2 in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /usr/lib/libQt5Core.so.5+0x182
    #40  0x7fc47af4fce3 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) from /usr/lib/libQt5Core.so.5+0x173
    0000041  /usr/lib/libQt5Core.so.5(+0x301ab4) [0x7fc47afa4ab4]
    0000042  /usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x25c) [0x7fc478c7b43c]
    0000043  /usr/lib/libglib-2.0.so.0(+0x9ffa9) [0x7fc478cc8fa9]
    0000044  /usr/lib/libglib-2.0.so.0(g_main_context_iteration+0x31) [0x7fc478c7a221]
    0000045  0x7fc47afa4101 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /usr/lib/libQt5Core.so.5+0x61
    0000046  0x7fc47af4bc0c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) from /usr/lib/libQt5Core.so.5+0x12c
    0000047  0x7fc47af540a6 in QCoreApplication::exec() from /usr/lib/libQt5Core.so.5+0x96
    0000048  0x7fc47ce86e53 in Gui::Application::runApplication() from /usr/lib/freecad/lib/libFreeCADGui.so+0x19a3
    0000049  freecad(+0x45e0) [0x5640082b35e0]
    0000050  /usr/lib/libc.so.6(__libc_start_main+0xf2) [0x7fc47a90c002]
    0000051  freecad(+0x48ee) [0x5640082b38ee]
    
    Tags: 0.19, linux, Qt5
    Steps To Reproduce:
    Additional Information: Running on Sway 1.4 with Intel UHD 620
    Attached Files:
    Notes
    (0014451)
    openBrain   
    2020-05-31 10:33   
    @nikto_b : please address your issue following our reporting guidelines by opening first a topic in our forum. Thx
    Also a basic search would have pointed this topic
    (0014497)
    Kunda1   
    2020-06-07 14:21   
    @nikto_b please open a forum thread
    (0014766)
    fourbytes   
    2020-09-24 08:22   
    (Last edited: 2020-09-24 08:23)
    With my recent pull request, FreeCAD now compiles with the git version of Coin3D. Running the latest version of Coin3D results in functional native Wayland support (Arch Linux, Sway 1.5). A caveat is that the freecad-git AUR package requires 'coin', not 'coin-git', so I had to modify the PKGBUILD for coin-git and rename it to coin.

    The only major issue I have come across is that at some point, my scroll wheel stopped working to zoom, and a week or so later the middle click panning also stopped working. When I get some time, I'll try and trace this issue.
    (0016901)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6068.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4351 [FreeCAD] Feature minor always 2020-05-28 19:27 2021-02-06 06:49
    Reporter: cbruner Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Linux Mint 19.3 (X-Cinnamon/cinnamon)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.21280 (Git) AppImage
    Build type: Release
    Branch: master
    Hash: 6f3160db3e88733536c7eaf97ad7d6ebd21baccd
    Python version: 3.8.2
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: English/Canada (en_CA)
    Summary: gui font sizes are very small on a large screen (High DPI) (how to fix)
    Description: My fix as shown in forum topic
    https://forum.freecadweb.org/viewtopic.php?f=3&t=41656&p=392509#p392509
    is to set environment variables before starting freecad.
    exec=/usr/bin/env QT_AUTO_SCREEN_SCALE_FACTOR=0 QT_SCALE_FACTOR=1.7 ~/bin/freecad_
    QT seems to be borked on highdpi monitors.
    According to QT documentation, these environment variables can be set inside program.

    My suggestion is to add to /edit/preferences/general/display
    a checkbox for QT_AUTO_SCREEN_+SCALL_FACTOR and if not checked then a text field for
    QT_SCALE_FACTOR.
    Tags: GUI, HiDPI
    Steps To Reproduce: use any high dpi monitor or large screen (in my case a 4k tv).
    I've attached two screen shots to illustrate the problem and solution.
    Current is without env variables set and hidpi is with env set.
    Additional Information:
    Attached Files: current.png (430,329 bytes) 2020-05-28 19:27
    https://tracker.freecad.org/file_download.php?file_id=2472&type=bug
    hidpi.png (605,417 bytes) 2020-05-28 19:27
    https://tracker.freecad.org/file_download.php?file_id=2473&type=bug
    image.png (745,403 bytes) 2020-07-21 21:24
    https://tracker.freecad.org/file_download.php?file_id=2508&type=bug
    report.txt (20,023 bytes) 2020-07-22 12:41
    https://tracker.freecad.org/file_download.php?file_id=2509&type=bug
    FreeCAD.log (59,248 bytes) 2020-07-22 13:56
    https://tracker.freecad.org/file_download.php?file_id=2510&type=bug
    Notes
    (0014659)
    vanuan   
    2020-07-19 11:09   
    I see you're using Cinnamon. Have you enabled HiDPI mode in display settings? If yes, what Zoom level did you choose? For example, GNOME supports 100%-400% scaling
    (0014660)
    vanuan   
    2020-07-19 11:12   
    (Last edited: 2020-07-19 11:12)
    Also, post your
    xrdb -query
    output
    (0014661)
    cbruner   
    2020-07-19 23:52   
    3840x2160 dpi, Double (Hi-DPI)

    xrdb -query
    customization: -color
    Xft.dpi: 211.19921875
    Xft.antialias: 1
    Xft.hinting: 1
    Xft.hintstyle: hintfull
    Xft.rgba: rgb
    (0014662)
    vanuan   
    2020-07-20 15:54   
    (Last edited: 2020-07-20 15:54)
    Ok, so it's not smaller than mine. It's just that the difference between window title font size and the Qt calculated font size is larger than mine. This means Cinnamon has larger theme fonts than GNOME's.

    But anyway, I see it now. Qt's menubar size should match the system's. So it doesn't inherit the theme of the operating system.

    Googling around I found this: https://github.com/AppImage/pkg2appimage/issues/88

    So I doubt it's related to HiDPI. It's rather an issue with AppImages not inheriting the System's theme
    (0014663)
    cbruner   
    2020-07-20 18:41   
    No, it's not an appImage problem. I compile from source (now) and the situation appears to be the same.

    Also if you look at the images, it's not just the title font, it's all the fonts.

    OS: Linux Mint 19.3 (X-Cinnamon/cinnamon)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.22038 (Git)
    Build type: Unknown
    Branch: master
    Hash: 71e1f7c331fcd97c74b4a159bb6a8c90df903e6e
    Python version: 3.6.9
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/Canada (en_CA)
    (0014664)
    vanuan   
    2020-07-21 20:20   
    You need to install qgtk3 platform plugin:

    https://bugreports.qt.io/browse/QTBUG-62510
    (0014665)
    vanuan   
    2020-07-21 20:25   
    Here's a package for Ubuntu:
    https://packages.ubuntu.com/bionic/qt5-gtk-platformtheme

    Not sure if there's equivalent for Mint
    (0014666)
    vanuan   
    2020-07-21 20:26   
    After installing, use env QT_QPA_PLATFORMTHEME=gtk3
    (0014667)
    vanuan   
    2020-07-21 20:28   
    Make sure that the plugin (libqgtk3.so) is in the correct folder, e.g. /usr/lib/x86_64-linux-gnu/qt5/plugins/platformthemes/
    (0014668)
    cbruner   
    2020-07-21 21:18   
    After installing it, and relogging in, I'm afraid I don't see a difference.
    Even compared to openoffice and gimp, freecad fonts are tiny.
    ls /usr/lib/x86_64-linux-gnu/qt5/plugins/platformthemes/
    KDEPlasmaPlatformTheme.so libqgtk3.so
    (0014669)
    cbruner   
    2020-07-21 21:24   
    (0014672)
    vanuan   
    2020-07-22 10:11   
    You don't need to relogin. Try this:

    
    QT_QPA_PLATFORMTHEME=gtk3 QT_DEBUG_PLUGINS=1 ./bin/FreeCAD
    

    Find the platformthemes output, something like this:

    QFactoryLoader::QFactoryLoader() looking at "/usr/local/Qt-5.13.2/plugins/platformthemes/libqgtk3.so"
    Found metadata in lib /usr/local/Qt-5.13.2/plugins/platformthemes/libqgtk3.so, metadata=
    {
        "IID": "org.qt-project.Qt.QPA.QPlatformThemeFactoryInterface.5.1",
        "MetaData": {
            "Keys": [
                "gtk3"
            ]
        },
        "className": "QGtk3ThemePlugin",
        "debug": false,
        "version": 329473
    }
    
    
    
    (0014673)
    cbruner   
    2020-07-22 12:41   
    (Last edited: 2020-07-22 12:45)
    I relogged in after installing the library because I didn't see any difference.

    Here is the total output from report view. I don't see any reference to libqgtk3.so
    The build was done with
    
    cmake .. -DBUILD_QT5=ON -DPYTHON_EXECUTABLE=/usr/bin/python3 -DFREECAD_USE_P
    CL=OFF
    
    (0014674)
    vanuan   
    2020-07-22 13:02   
    Indeed, I don't see any reference to plugins/platformthemes/ and plugins/platforms/

    Are you sure this is a full output? Here's mine fist lines:

    FreeCAD 0.19, Libs: 0.19R22036 +2 (Git)
    © Juergen Riegel, Werner Mayer, Yorik van Havre and others 2001-2020
    FreeCAD is free and open-source software licensed under the terms of LGPL2+ license.
    FreeCAD wouldn't be possible without FreeCAD community.
      #####                 ####  ###   ####  
      #                    #      # #   #   # 
      #     ##  #### ####  #     #   #  #   # 
      ####  # # #  # #  #  #     #####  #   # 
      #     #   #### ####  #    #     # #   # 
      #     #   #    #     #    #     # #   #  ##  ##  ##
      #     #   #### ####   ### #     # ####   ##  ##  ##
    
    Loading Assembly4 WorkBench
    QFactoryLoader::QFactoryLoader() checking directory path "/usr/local/Qt-5.13.2/plugins/platforms" ...
    QFactoryLoader::QFactoryLoader() looking at "/usr/local/Qt-5.13.2/plugins/platforms/libqlinuxfb.so"
    (0014675)
    cbruner   
    2020-07-22 13:39   
    (Last edited: 2020-07-22 13:47)
    My file was from the report view. You're showing the bash output.
    Mine bash output is
    
    FreeCAD 0.19, Libs: 0.19R22104 (Git)
    © Juergen Riegel, Werner Mayer, Yorik van Havre and others 2001-2020
    FreeCAD is free and open-source software licensed under the terms of LGPL2+ license.
    FreeCAD wouldn't be possible without FreeCAD community.
      #####                 ####  ###   ####  
      #                    #      # #   #   # 
      #     ##  #### ####  #     #   #  #   # 
      ####  # # #  # #  #  #     #####  #   # 
      #     #   #### ####  #    #     # #   # 
      #     #   #    #     #    #     # #   #  ##  ##  ##
      #     #   #### ####   ### #     # ####   ##  ##  ##
    
    Loading Assembly4 WorkBench
    Sheet Metal workbench loaded
    Interlocking laser cut workbench loaded
    A3 available
    connect failed: No such file or directory
    
    Interesting, I've never noticed the connect failed before.

    Apparently a known issue. https://forum.freecadweb.org/viewtopic.php?t=37021
    I tried renaming ~/.FreeCAD to ~/.FreeCAD1 but that made no difference (other then default pages were cleaned up).
    (0014676)
    cbruner   
    2020-07-22 13:56   
    I tried running it with --write-log and this is the result.
    (0014679)
    vanuan   
    2020-07-22 20:39   
    (Last edited: 2020-07-22 20:43)
    Now we're getting somewhere
    Log: QFactoryLoader::QFactoryLoader() checking directory path "/usr/lib/x86_64-linux-gnu/qt5/plugins/platformthemes" ...
    Log: QFactoryLoader::QFactoryLoader() looking at "/usr/lib/x86_64-linux-gnu/qt5/plugins/platformthemes/KDEPlasmaPlatformTheme.so"
    Log: Found metadata in lib /usr/lib/x86_64-linux-gnu/qt5/plugins/platformthemes/KDEPlasmaPlatformTheme.so, metadata=
    {
        "IID": "org.qt-project.Qt.QPA.QPlatformThemeFactoryInterface.5.1",
        "MetaData": {
            "Keys": [
                "kde"
            ]
        },
        "className": "KdePlatformThemePlugin",
        "debug": false,
        "version": 329989
    }
    
    
    Log: Got keys from plugin meta data ("kde")
    Log: QFactoryLoader::QFactoryLoader() looking at "/usr/lib/x86_64-linux-gnu/qt5/plugins/platformthemes/libqgtk3.so"
    Log: Found metadata in lib /usr/lib/x86_64-linux-gnu/qt5/plugins/platformthemes/libqgtk3.so, metadata=
    {
        "IID": "org.qt-project.Qt.QPA.QPlatformThemeFactoryInterface.5.1",
        "MetaData": {
            "Keys": [
                "gtk3"
            ]
        },
        "className": "QGtk3ThemePlugin",
        "debug": false,
        "version": 329989
    }
    
    
    Log: Got keys from plugin meta data ("gtk3")
    Log: QFactoryLoader::QFactoryLoader() checking directory path "/home/chris/github/freecad-source/build/bin/platformthemes" ...
    Log: loaded library "/usr/lib/x86_64-linux-gnu/qt5/plugins/platformthemes/libqgtk3.so"

    So you've got gtk3 and kde platform themes.

    Is switching between these two changes anything?

    $ QT_QPA_PLATFORMTHEME=gtk3
    
    vs
    
     $ QT_QPA_PLATFORMTHEME=kde


    Also try this option


    -style breeze
    (0014680)
    vanuan   
    2020-07-22 20:45   
    BTW, Cinnamon uses Gtk3 and D-Bus, right?
    (0014681)
    cbruner   
    2020-07-22 21:21   
    QT_QPA_PLATFORMTHEME=gtk3 QT_DEBUG_PLUGINS=1 ./bin/FreeCAD
    vs
    QT_QPA_PLATFORMTHEME=kde QT_DEBUG_PLUGINS=1 ./bin/FreeCAD
    kde was a little lighter in colour but otherwise no change in fonts.

    -style breeze made no difference to either.
    I believe you are correct regarding gtk3 and d-bus
    (0014707)
    cbruner   
    2020-08-24 15:33   
    A note about this topic. I recently upgraded to Linux Mint 20, and this issue has largely gone away. The only problem as this point is the fonts are slightly larger than the text box. For example, adding a constraint, change the diameter of a circle 18.0 will only show the top 2/3ds of the 18.
    (0014713)
    vanuan   
    2020-08-26 07:32   
    Any indication what's changed? Qt version?
    Has the debug output changed wrt plugins used ( QT_DEBUG_PLUGINS=1 ) ?
    Maybe it's just that system font better matches the Qt one?
    (0014720)
    cbruner   
    2020-08-26 13:59   
    It looks like the qt installed it 5.12.8
    No difference in the debug output.
    This was a fresh install (keeping my home directories), whereas my old one was updated over the last 5 years, so there was a lot of kruft on it.
    (0014796)
    Kunda1   
    2020-10-08 13:45   
    Any updates on this issue? What is left to do?
    (0014802)
    cbruner   
    2020-10-08 14:45   
    as far as I am concerned it can be closed. (It went away when I upgraded my system).
    (0016899)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6066.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4346 [FreeCAD] Feature tweak always 2020-05-17 22:55 2021-02-06 06:49
    Reporter: PedjaS Platform: Windows  
    Assigned To: OS: Windows  
    Priority: normal OS Version: 8.1  
    Status: feedback Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 8.1
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.4 (GitTag)
    Build type: Release
    Branch: releases/FreeCAD-0-18
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    Summary: Resolving FreeCAD stalls when creating mesh from complex objects
    Description: When I try to create mesh for complex objects FreeCAD becomes non responsive. It does not break, it just seems like it spends all resources to do mesh and does not update system messages.

    It just shows busy mouse icon and stops responding to anything user does.

    The only way to stop it after mesh creation started is to kill application.

    If I let it go for long time it eventually finishes the job.

    Here are my proposals:

    1. Resolve stalling by allowing FreeCAD to process system messages in appropriate place.

    2. Add some kind of progress indicator. Creating mesh can take lot of time and it is advisable to provide some kind of progress update for user instead of just busy mouse icon.

    I am aware that it is possible that mesh creator does not how much processing it needs to finish the job so it cannot provide accurate progress information. Accuracy is not required. More important is that user can see and follow that something is going on. Rough estimate of progress is good enough. Progress update does not even have to be in full real time. It is enough to update from time to time, as long as it keeps user informed that it works and does something.
    Tags: #pending-forum, Mesh
    Steps To Reproduce: I could not upload example file duo to it's size. Here is WeeTranfer link to file
    https://we.tl/t-Gc9uS981JQ

    Creating mesh for this object produces described issue.
    Additional Information:
    Attached Files:
    Notes
    (0014420)
    openBrain   
    2020-05-18 12:34   
    @PedjaS : please address your issue following our reporting guidelines by opening first a topic in our forum. Please get familiar with this important notice before. Once topic is created, please post here a link to it. Thx
    (0014740)
    Kunda1   
    2020-09-10 15:15   
    Forum thread
    (0016897)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6064.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4341 [FreeCAD] Bug minor always 2020-05-14 04:15 2021-02-06 06:49
    Reporter: fc_tofu Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 10 (10.0)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.20514 (Git)
    Build type: Release
    Branch: master
    Hash: a05ffd499366ab12fa1b43f37db73f4f1e9c332d
    Python version: 3.8.2
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: Chinese/China (zh_CN)
    Summary: shape flipped when Auto Working Plane and Bottom view
    Description: DraftWB, first added shape get flipped normal orientation when Automatic working plane and Bottom view.
    Tags: 0.19, Draft
    Steps To Reproduce: 1. Pref >Display >Part color >"Two-sided rendering" toggle off.
    2. Restart FreeCAD, and switch to DraftWB.
    3. Rendering mode >Flat lines.
    4. Working plane >Automatic.
    5. Change to Bottom view (Menu command "Bottom" or NaviCube "Bottom").
    6. Create a closed shape, rectangle for example.
    7. Find normal orientation of rectangle get flipped.
    Additional Information: Workaround:
    Befor step 5, change to other view (than Bottom) and draw a closed shape. Then goto step 5. Normal of created shape at Bottom view will get correct normal.

    ps.
    This issue doesnot happen on other views than Bottom.

    Forum:
    https://forum.freecadweb.org/viewtopic.php?f=23&t=46153
    Attached Files: draft2Dviewbug.png (18,273 bytes) 2020-07-28 17:53
    https://tracker.freecad.org/file_download.php?file_id=2512&type=bug
    Notes
    (0014692)
    roribez   
    2020-07-28 17:53   
    (Last edited: 2020-07-28 17:54)
    I cought a bug that I think may be related to this one:
    when using bottom view or front view as direction to create Shape2DView in Draft, the projection will be rotated like attached picture.

    Curiously, with the bottom view, the problem only happens when using NaviCube, is View menu is used to set bottom view, the Shape2dView works fine. With front view, the problem happens both when using NaviCube or View menu.
    (0016894)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6060.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4154 [FreeCAD] Bug minor always 2019-10-05 23:03 2021-02-06 06:49
    Reporter: axos88 Platform: Windows 10  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Parametric constraint can be changed only one way for fully constrained sketch
    Description: I've a sketchup drawing with named constraints. Increasing the constraint value works, decreasing it does not. (Increasing to a value and then trying to change back is broken too).

    I've encountered this bug in many forms, if the R is not a radius constraint but one of the length constraints (see file 2), it's not possible to change the value AT ALL.
    Tags: #pending-forum
    Steps To Reproduce: 1. Open attached file
    2. Open sketcher with the "Sketch"
    3. Change constraint R to 4mm
    4. Change constraint R back to 3mm

    Observe error: Negative datum values are not valid for the constraint with index 10 (That is the R constraint).

    Expected: Change back obviously.
    Additional Information: OS: Windows 10
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16131 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-18
    Hash: 3129ae4296e40ed20e7b3d460b86e6969acbe1c3
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedKingdom (en_GB)
    Attached Files: bug1.FCStd (12,451 bytes) 2019-10-05 23:03
    https://tracker.freecad.org/file_download.php?file_id=2366&type=bug
    bug2.FCStd (12,465 bytes) 2019-10-05 23:03
    https://tracker.freecad.org/file_download.php?file_id=2367&type=bug
    Notes
    (0013719)
    openBrain   
    2019-10-07 10:46   
    (Last edited: 2019-10-07 10:52)
    @axos88 thanks for reporting. According the guidelines (big yellow box on top of page), could you please first post to forum so your findings can be discussed ?
    Notice that despite what you found can lead to interesting corner case tests, your sketch is very very lamous. It's highly suboptimal, and I could have bet just by seeing it that it can seriously hurt the solver. :)

    EDIT : JFYI, you're cumulating 2 known corner cases.
    1 - Setting equal radius and horizontal/vertical distance on an arc
    2 - Having tangent arc/line obtained by construction but not by constraint

    (0013724)
    axos88   
    2019-10-07 17:02   
    @openBrian, thanks for getting back to me. Sorry for not asking in the forum first, I understood it's for verifying and prefiltering wether reports are actually bugs, and it was pretty straightforward that this is.

    I'll do that now, I'm curious why my sketch would be lamous and suboptimal and to learn how to do it better.

    I'm not sure I understand the second corner case you mentioned, but I'm sure I'll get an answer there.
    (0013725)
    openBrain   
    2019-10-07 17:09   
    @axos88 actually the problem with direct reporting is that there is high chance that your "bug" is known & already reported. ;) Also it can be a known limitation.
    Once you open a forum topic, may you please cross-reference it in this ticket ? Thx
    (0013726)
    axos88   
    2019-10-07 17:13   
    Once it gets approved, and I get a link to it, yes, of course.
    (0014790)
    Kunda1   
    2020-10-08 01:12   
    @axos88 link to forum thread?
    (0016828)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5994.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4090 [FreeCAD] Feature minor always 2019-08-12 12:56 2021-02-06 06:49
    Reporter: graffy Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Provide direct access to task panel dialog from Python
    Description: In Python, there's no way to provide direct access to the task panel. Typically, this can be managed easily enough by simply passing a reference to the form from the module that creates it to subsequent modules that may need it.

    However, the C++ API already provides this accessibility via Gui.Control().activeDialog(). Unfortunately, the Python wrapper implementation merely returns a boolean indicating whether or not the active dialog exists.

    Suggest rewriting the Python Control.activeDialog() to return a reference to the active dialog (or None). This should pose little issue for existing code using Control.activeDialog() as any boolean test will still function properly.
    Tags: GUI
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0013422)
    graffy   
    2019-08-13 13:01   
    Link to forum thread:

    https://forum.freecadweb.org/viewtopic.php?p=326529#p326529
    (0014968)
    rockn   
    2020-11-09 16:32   
    +1 for this feature request

    I agree this would be best to have this implemented in
    FreeCADGui.Control.activeDialog()
    but maybe we can add this method instead :
    FreeCADGui.Control.getActiveDialog()
    to provide name and other interesting informations about the current activeDialog.
    (0016809)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5975.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4048 [FreeCAD] Feature minor always 2019-07-02 18:17 2021-02-06 06:49
    Reporter: FreeCAD97990 Platform: Windows 10  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Linear and Polar Transform Tools apply the wrong failure criteria to Transforms and needlessly fail
    Description: Hi this is a bug that I have been aware of for the last 18 months or even longer. It happens with ALL the development releases that have been made over the last 18 months.

    I have over that time posted two forum threads describing the bug, but have got very little response.

    My second (and probably better) thread:

    https://forum.freecadweb.org/viewtopic.php?f=8&t=33742

    My first thread:

    https://forum.freecadweb.org/viewtopic.php?f=3&t=23222

    Tags:
    Steps To Reproduce: Run the four files below, the first two for Polar Transformation and the second two for Linear Transformation. In each case, one of the transformation fails and the other succeeds.

    In 'Polar Transformation Failed', go to the Tree View and select Edit Polar Pattern. You can see that the transformation has failed because one of the Pocket features (in red) has not intersected the Pad Plate.
    In 'Polar Transformation Succeeded', go to the Tree View and the transformation has succeeded. You can see that the Pocket Feature (the same one that was in red before) is now Sketched longer and it just intersects the Pad Plate. So no error!!!!!

    The two Linear Transformations files work in exactly the same way.

    The operation of the Linear Transformation and Polar Transformation Tools is described in the Users Documentation Help Files:

    PartDesign LinearPattern
    Limitations
    Any pattern shapes that do not overlap the original's support will be excluded. This ensures that a PartDesign feature always consists of a single, connected solid

    PartDesign PolarPattern
    Limitations
    See linear pattern feature limitations

    The reason for this bug is that these limitations are WRONG!

    If the pattern shapes are Pads, then YES!, any pattern shape that does not overlap the original's support should be excluded to ensure that a Part Design Feature always consists of a single, connected solid.

    BUT.... If the pattern shapes are Pockets, then any pattern shape that does not overlap the original's support should be INCLUDED because it CANNOT cut the original support into two pieces. It is therefore 'safe'!!!!

    The Linear (and Polar) Pattern Tools should both be changed to:

    Limitations
    Any Pad pattern shapes that do not overlap the original's support will be excluded. This ensures that a PartDesign feature always consists of a single, connected solid.

    You may think that there is no real bug here - that it does not cause much of a problem because you can use some sort of workaround. But I have been designing, over the last 2 years or so, graduated plates with cut-outs that are always causing Polar Pattern to fail. So I use two (or more) Polar Patterns to do the job. And then the cut-outs need to change.... It's very time consuming and non-parametric!!!!
    Additional Information: The problem occurs with all FreeCAD release and development versions!!!!!!!!!!!
    OS: Windows 10
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.17201 (Git)
    Build type: Release
    Branch: master
    Hash: 20b78fca97e21473716c7fc13cb4acc9afe4710a
    Python version: 2.7.14
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.2.0
    Locale: English/UnitedKingdom (en_GB)
    Attached Files: Polar Transformation Failed.FCStd (85,437 bytes) 2019-07-02 18:17
    https://tracker.freecad.org/file_download.php?file_id=2254&type=bug
    Polar Transformation Succeeded.FCStd (87,541 bytes) 2019-07-02 18:17
    https://tracker.freecad.org/file_download.php?file_id=2255&type=bug
    Linear Transformation Failed.FCStd (46,196 bytes) 2019-07-02 18:17
    https://tracker.freecad.org/file_download.php?file_id=2256&type=bug
    Linear Transformation Succeeded.FCStd (54,558 bytes) 2019-07-02 18:17
    https://tracker.freecad.org/file_download.php?file_id=2257&type=bug
    Notes
    (0013330)
    FreeCAD97990   
    2019-07-03 18:23   
    Please note that where I have written 'Pad pattern shapes' in the above bug report this really would refer to any Additive Feature that is selected to be Linear Patterned or Polar Patterned. I think these are Pad, Revolve, Additive Loft, Additive Sweep, or any Additive Primitive.

    In the User Documentation Help Files, it would probably be clearer to refer to 'Additive Pattern Feature' rather than 'Additive Pattern Shapes'.

    And where I have written 'Pocket pattern shapes' this really would refer to any Subtractive Feature that is selected to be Linear Patterned or Polar Patterned. I think these are Pocket, Hole, Groove, Subtractive Loft, Subtractive Sweep, or any Subtractive Primitive.

    Of course, the Linear and Polar Pattern Tools can both be used to pattern not just a single feature, but a list of several features, some of which might be Additive, and the others Subtractive. Some thought needs to be given regarding the order in which the Patterning and the intersection test is applied where several features are involved. Possibly do all the Additive Features first, followed by the Subtractive Features? Or perhaps just in the order selected by the FreeCAD user, to give the user more control and allow him to re-order them to his best advantage?

    Finally,maybe the Mirror and Multitransform Tools have these same problems too.
    (0014957)
    jmaustpc   
    2020-10-30 05:21   
    This is not a bug, it is deliberately intended designed behavior. It is certainly not worthy of a "blocking" priority.

    It is just that a Body must be a single contiguous solid. How pattern features should behave when some or all of its elements don't intersect with the solid is a matter for discussion that may or may not result in any change to the current behavior. Hence this is really a feature request.

    Please continue with any discussion about this on the forum. I will leave this ticket open for future reference until any decision is made on the matter.

    I will leave this here as a feature request
    (0016798)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5964.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4020 [FreeCAD] Bug minor always 2019-06-14 07:23 2021-02-06 06:49
    Reporter: freman Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: untrapped file error on start up.
    Description: Due to manual changes to file ownerships, some file has become a problem when starting FreeCAD. However, the error does not seem to be trapped at the point where the file is accessed and just bubbles up to be caught as an untrapped error which is so general as to not be any help in identifying and resolving the problem

    https://forum.freecadweb.org/viewtopic.php?f=3&t=37021&p=314367#p314367

    connect failed: No such file or directory
    Unhandled std::exception caught in GUIApplication::notify.
    The error message is: Permission denied

    freeCAD

    An error report which stated the full file path and name would allow this to be fixed immediately.

    It seems that whatever function is attempting this file access is not trapping any file access errors and assumes it always works.


    While the cause in this case is outside FreeCAD, it seems it should trap any errors in file access.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files: FreeCAD.log (59,248 bytes) 2020-07-22 14:05
    https://tracker.freecad.org/file_download.php?file_id=2511&type=bug
    Notes
    (0013211)
    freman   
    2019-06-14 07:26   
    OS: Linux
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.15303 (Git)
    Build type: Release
    Branch: master
    Hash: 6199c95fd71eacb9cc168426e55254aa79a42034
    Python version: 2.7.15
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedKingdom (en_GB)
    (0013212)
    openBrain   
    2019-06-14 16:03   
    @freman as required in the bug submission guidelines, could you please confirm bug is still present in the latest release version (yours is outdated) ?
    If possible, could also provide a way to reproduce the issue ?
    (0013214)
    freman   
    2019-06-14 17:16   
    yes, still present on new build of 0.19 master today.

    However, as discussed in thread, there are two things happening here. The file permissions problem disappeared after a reboot, so the cause will be undetermined unless it happens again.

    the other connection message seems to be be LVM related coming from Qt. It is probably banal.

    This still reflects the need for better error trapping at a lower level, though it will not be possible to work out exactly where in this case until and unless it reoccurs. It seems some file access was being attempted without the success being tested. Knowing what file it was would have enabled it being resolved in minutes instead of not detected properly after hours.

    If I see it again , I will report back.
    (0014677)
    cbruner   
    2020-07-22 14:05   
    (Last edited: 2020-07-22 14:06)
    While going through https://tracker.freecadweb.org/view.php?id=4351#bugnotes found this error as well. Using wmayer's comments in https://forum.freecadweb.org/viewtopic.php?t=37021 I modified the FreeCAD/src/Gui/GuiApplication.cpp to have Base::Console().Error("Event type: %d, receiver: %s\n", (int)event->type(), receiver->metaObject()->className()); at the exception handling areas.
    (made no difference).
    starting it with QT_QPA_PLATFORMTHEME=gtk3 QT_DEBUG_PLUGINS=1 ./bin/FreeCAD --write-log produced the attached file.
    OS: Linux Mint 19.3 (X-Cinnamon/cinnamon)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.22108 (Git)
    Build type: Unknown
    Branch: master
    Hash: 886d9656f0c4ccfd016e373f74cc2dde965d88e1
    Python version: 3.6.9
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/Canada (en_CA)
    (0016781)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5947.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3995 [FreeCAD] Bug major always 2019-05-31 03:07 2021-02-06 06:49
    Reporter: robotarmy Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Trackpad on Macbook unusable in any mouse model so far
    Description: Hi all,

    My trackpad and FreeCAD don't get along :(

    None of the two-finger things (pan, pinch to zoom) behave as I would expect, and it makes it almost impossible to use FreeCAD on my normal platform.

    Forum posts related:
    https://forum.freecadweb.org/viewtopic.php?f=3&t=34351
    ('Gesture mode' as is suggested doesn't work at all well for me)

    https://forum.freecadweb.org/viewtopic.php?f=3&t=33282&start=10
    (If lack of mac is the root cause, I'd be happy to loan one! Good luck DeepSOIC/all)

    I think this may also be related to 0002437 but that's listed as a 'minor feature request' on 0.15. This is a showstopper for me using FreeCAD.

    I've captured two videos with the default settings, and I'm not seeing what I would consider 'expected behaviour' with my trackpad, and none of the mouse models make it much more useful.

    You can see what I see here with only very minor finger movements in each case.
    https://www.youtube.com/watch?v=iA9-QKA6iQ8
    https://www.youtube.com/watch?v=6hmtKJJUAKM

    It 'should' behave (I suppose?) as described here: https://developer.apple.com/design/human-interface-guidelines/macos/user-interaction/mouse-and-trackpad/

    Maybe setting some zoom multiplier would help it not be so wild, but the gestures are being interpreted incorrectly, as well as being too fast.

    The 'Gesture' model looks the most correct on the mouseover, but it seems that the two finger gestures are being picked up as scrolling (or something?) rather than the gestures they are.

    Thanks for all your hard work crew, it's come a long way!!
    Tags: Bountysource Potential, gesture, macOS, trackpad
    Steps To Reproduce: Run 0.18 on a Macbook with the mouse model set to 'Gesture' mode and try to do two-finger gestures.
    Additional Information: OS: macOS Sierra (10.12)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16117 (Git)
    Build type: Release
    Branch: (HEAD detached at 0.18.2)
    Hash: dbb4cc6415bac848a294f03b80f65e888d531742
    Python version: 3.6.7
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedKingdom (en_GB)
    Attached Files:
    Notes
    (0013228)
    Kunda1   
    2019-06-17 06:23   
    @robotarmy please participate in https://forum.freecadweb.org/viewtopic.php?f=9&t=36387
    DeepSOIC has updated the gesture navigation code in 0.19_pre but mostly for windows. We need MacOS X testers that can give him feedback (because he doesn't own a mac).
    (0013787)
    krite   
    2019-10-25 15:07   
    (Last edited: 2019-10-25 15:42)
    This issue is exactly as bad in Ubuntu on a Lenovo T480s, totally unusable.
    The behaviour is also identical in the newest 19_pre from Sep 7.

    Further analysis actually show that the scroll upp/down on the trackpad behaves as pressing pgup/pgdown-keys. Thus not zooming like a mouse at all, which is totally unusable of course.

    The two-finger up/down-scroll is thus not usable (large hops), and the pinch-zoom is actually intercepted incorrectly and interfer with the two-finger action, and does not work at all.

    (0014757)
    Kunda1   
    2020-09-16 13:07   
    @DeepSOIC were you working on this ?
    (0014758)
    DeepSOIC   
    2020-09-16 17:15   
    i am not. Fixing gigantic zoom sensitivity ( https://forum.freecadweb.org/viewtopic.php?f=9&t=49680 ) should have made things a lot better, but i don't have a macbook to try (and thus i can't work on it). @chrisb ?
    (0014759)
    DeepSOIC   
    2020-09-16 17:17   
    As for the linux part, I can try. I don't have linux, but i can install one in theory.
    (0016772)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5938.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3398 [FreeCAD] Feature feature always 2018-03-26 23:02 2021-02-06 06:49
    Reporter: pager48 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Hiding / Showing features hides entire body
    Description: Cannot hide and show features repeatedly, what happens is entire body is hidden.
    Tags:
    Steps To Reproduce: Make some 3D solid
    Make a fillet on some edge
    Select fillet from model panel
    Hit space to hide it

    Results: Entire body is hidden
    What should have happened is the filled feature becoming hidden.
    Additional Information:
    Attached Files: example.fcstd (48,857 bytes) 2018-03-27 00:54
    https://tracker.freecad.org/file_download.php?file_id=1863&type=bug
    Notes
    (0011058)
    pager48   
    2018-03-26 23:03   
    This works with many other feature types as well, including chamfer.
    (0011067)
    pager48   
    2018-03-27 03:34   
    Freecad revision:

    OS: Linux
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.13452 (Git) AppImage
    Build type: None
    Branch: master
    Hash: 34633c144de9133c1f9aeb7da783f369cae9bfaf
    Python version: 2.7.6
    Qt version: 4.8.6
    Coin version: 4.0.0a
    OCC version: 7.1.0
    Locale: English/UnitedStates (en_US)
    (0011077)
    Kunda1   
    2018-03-29 10:55   
    @chrisb care to respond to this ticket? Thanks
    (0011084)
    pager48   
    2018-03-30 08:27   
    It should work regardless of how many times visibility is toggled.
    (0011125)
    DeepSOIC   
    2018-04-04 22:18   
    This is by design. When a feature is shown, the whole state of the solid after applying the feature is shown. Hide/Show is not going to switch features on and off in the middle of modeling history.

    What can be done, is when you hide Fillet, a previous feature is made visible automatically. I would regard this as a valid feature request, but not a bug.
    (0011126)
    DeepSOIC   
    2018-04-04 22:20   
    @pager48, please don't pollute the tracker, and ask on forum first!
    (0011147)
    Kunda1   
    2018-04-15 17:10   
    Changing to feature request per DeepSOIC's recommendations
    (0014857)
    Kunda1   
    2020-10-15 13:59   
    This feature may be already implemented in realthunder's LinkStage3 branch:
    Right click on a feature in the tree -> suppress
    (0016610)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5775.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3081 [FreeCAD] Feature minor sometimes 2017-06-13 10:28 2021-02-06 06:49
    Reporter: berka Platform: Intel  
    Assigned To: OS: MacOS  
    Priority: normal OS Version: 10.12.5  
    Status: confirmed Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: MacOS application crashes should generate Diagnostic Reports
    Description: I'm testing 0.17 nightlies (primarily to use Path Workbench).
    I found 0.17 crashes often enough to be annoying. However, unlike other MacOS apps I'm accustomed to, this application doesn't pop up with a backtrace and other diagnostic report information. I've spent a long time fishing through log files with no result.
    This is de ja vu for me (bug 0002521). I will now start systematically running under lldb.

    However, I think it would be helpful if an unexpected crash generated some diagnostic information. Please identify and implement what you need to do to enable such diagnostic gathering.

    I looked, but couldn't find how to enable the MacOS facility that generates these reports. Some things that show up in web search:
    ReportCrash utility (e.g. "man ReportCrash")
    CrashReporter https://developer.apple.com/library/content/technotes/tn2004/tn2123.html <- This describes what I'm accustomed to seeing as an app user.

    I find the crash reports I expect from other applications at: ~/Libary/Logs/DiagnosticReports
    Tags: #post-to-forum, crash, distribution specific, macOS, packaging
    Steps To Reproduce:
    Additional Information: OS: Mac OS X
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.11232 (Git)
    Build type: Release
    Branch: (detached from 5f54fc0)
    Hash: 5f54fc0298cea749c53fa3c1a6be71f1f1e1476f
    Python version: 2.7.13
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.1.0
    Attached Files:
    Notes
    (0009353)
    berka   
    2017-06-13 10:42   
    This may be related to why crash reports aren't displayed/logged for FreeCAD. I had found this in my syslog:
    com.apple.xpc.launchd[1] (com.apple.xpc.launchd.oneshot.0x10000016.FreeCAD[4320]): Service exited with abnormal code: 1
    Thinking back, it hints that FreeCaD may be running as a background app. Crash reports (by default) are not generated for background apps.
    (0009357)
    Kunda1   
    2017-06-13 21:44   
    @blacey care to comment?
    (0009358)
    Kunda1   
    2017-06-13 21:47   
    In the same vein as 0002731
    (0009607)
    Kunda1   
    2017-06-29 13:12   
    @peterl94 mind taking a look?
    (0009644)
    peterl94   
    2017-07-01 22:21   
    It seems to depend on how the app crashed. The following two examples both crash freecad ( builds from github), but only the first shows the mentioned diagnostic report.

    part1 = App.ActiveDocument.addObject("App::Part", "Part1")
    part1.Group = [part1]
    

    import Part
    circle = Part.makeCircle(10)
    result = Part.makeFilledFace([circle])
    
    (0016546)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5711.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2688 [FreeCAD] Feature feature have not tried 2016-09-04 08:21 2021-02-06 06:49
    Reporter: Willeman Platform:  
    Assigned To: OS: All OS's  
    Priority: normal OS Version:  
    Status: feedback Product Version: 0.16  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Model Presentation Workbench
    Description: I have a request for a new feature (new workbench maybe?). I would call it 'presentation model workbench' or something.

    This feature would enable a user to prepare a digital document of his/her design for presentation purposes to a client, such that when the client downloads the file and opens it, he/she will be able to navigate around- and into the object using the same navigation tools the user uses on FreeCAD while constructing it - as shown on page 31 of "A FreeCAD manual" compiled by Yorik van Havre - but without being able to tamper with the document or alter it in any way and without having to download the whole FreeCAD program to be able to view the presentation.

     It would also be nice if the client, like the user, can have access to the "The combo view" so as to enable him/her to switch the visibility of components on- and off to enable the client to strip the design layer by layer to be able to see what goes on on the inside.

    This function could later on perhaps be expanded to include full rendered objects using raytracing etc. but for a start just being able to have a client navigate a basic solid- and/or mesh model would be very useful.

    A comparable proprietary equivalent that comes to mind would be VoloView for AutoCAD.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0007302)
    yorik   
    2016-09-04 18:53   
    It would be best to discuss that kind of idea on the forum instead of posting here... The chances to interest someone to this here on the tracker are very low
    (0008845)
    Kunda1   
    2017-05-01 23:44   
    @Willeman please open a thread in the forum a don bidirectionally link ticket <=> thread. Thx
    (0009378)
    Kunda1   
    2017-06-15 12:10   
    Opened forum thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=22957
    (0015013)
    Kunda1   
    2020-11-21 14:08   
    (Last edited: 2020-11-21 14:08)
    Possible solutions exist for this already:

    Off-topic but relevant is @microelly2's code that @HakanSeven12 is working on in the Trails WB
    https://forum.freecadweb.org/viewtopic.php?f=8&t=34371&start=300#p448337
    (0016498)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5663.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1417 [FreeCAD] Feature feature have not tried 2014-02-16 16:13 2021-02-06 06:49
    Reporter: Pauvres_honteux Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Half width tangential lines
    Description: Hi, I would like to see tangential lines width half the size of boarder lines and in a bleaker color. This makes it easier on the eyes and you can emediatly see if two surfaces are tangential or not - speeds up work.

    Regards Pauvres_honteux
    Tags: #pending, colors, GUI, lines
    Steps To Reproduce:
    Additional Information: Had this in the "Open discussion" before but it was apparently the wrong place.
    Attached Files: G0-2.png (16,157 bytes) 2017-06-20 05:20
    https://tracker.freecad.org/file_download.php?file_id=1661&type=bug
    G1-2.png (16,574 bytes) 2017-06-20 05:23
    https://tracker.freecad.org/file_download.php?file_id=1662&type=bug
    G2-2.png (16,725 bytes) 2017-06-20 05:23
    https://tracker.freecad.org/file_download.php?file_id=1663&type=bug
    51.png (108,734 bytes) 2020-10-22 11:26
    https://tracker.freecad.org/file_download.php?file_id=2552&type=bug
    52.png (142,803 bytes) 2020-10-22 11:26
    https://tracker.freecad.org/file_download.php?file_id=2553&type=bug
    Notes
    (0004230)
    Pauvres_honteux   
    2014-02-16 19:58   
    Sorry for not being clear enough. With tangential lines I mean the lines that are visible on a surface where, for example, a flat surface pass over to a curved surface like in a radius between two perpendicular surfaces. When one see that passage you would immediately get a visual confirmation on its state: sharp (boarder line width), tangential (half boarder line width), or curve smooth passage (no line at all).

    Example:
    The three different basic passages - http://s3files.core77.com/blog/images/3surface.jpg

    The black line equals C0 (not tangent and sharp), the "half width bleak colored" light grey line equals C1 (tangent), the gap will eventually be filled by a curvature correct surface and its boarders limit will no be visible, i.e. C2 - http://architosh.com/wp-content/uploads/2013/09/03_evolve_chair_surface_blend.jpg

    Tangential lines with no difference to boarder lines - http://www.inceptra.com/images/newsletters/newletter6/catia_14.jpg
    (0004692)
    mdinger   
    2014-05-18 17:49   
    I find this explanation confusing. Does Rhino do tangency this way? Here is my interpretation of your request referring to each C elements from the first picture? It won't agree with the pictures. I have no idea what they are trying to explain.

    C1-3 picture:
    1. Circle should be black because it is *not* tangent.
    2. Line or Curve should be faint because it *is* tangent
    (0004701)
    Pauvres_honteux   
    2014-05-19 20:50   
    (Last edited: 2014-05-19 20:54)
    Hi guys, pictures were done in Catia. Don't ask me why I went over the top with all the tangent lines and tangent circle and what not. Maybe I had the first picture I made a link to in mind...
    Anyway, you seem to understand what I originally proposed and that's what counts.
    In V5 you can also turn off all internal tangent lines. While this makes any non tangent line really stand out it's hard to see how the surfaces really looks like.
    To summarize it a bit I'd say an really easy option for switching between different viewing behaviour is high on my whish list.

    (0004725)
    mdinger   
    2014-05-24 00:08   
    Solidworks supports this. See `solidworks_construction_tangent.png`.

    Note: It can be difficult to tell that they are construction linetype sometimes because of aliasing. Line thickness does not appear to have changed.
    (0007782)
    Pauvres_honteux   
    2017-01-15 07:06   
    Hi, Kunda1 !
    Sure, here it is:

    http://forum.freecadweb.org/viewtopic.php?f=8&t=5712
    (0009442)
    Pauvres_honteux   
    2017-06-18 09:02   
    Shame on thy giving up...
    Hopefully these pictures are clear enough?
    To clarify this once and for all: this issue is about the line seen between two surfaces in contact with each other. In CATIA there's an exception: curvature transition between surfaces does not show any line, but it would be beneficial to have another line type for that.

    @Kunda1, what do you think about cleaning up this thread and remove all misunderstood/irrelevant stuff? I think the links I originally posted can be removed as well.
    (0009466)
    Pauvres_honteux   
    2017-06-20 05:33   
    @Kunda1 , could you please remove the pictures from post 009442, which includes the picture above it?

    @kkremitzki , would it be possible to let us users remove/change/edit the pictures we've uploaded as well?
    (0009467)
    kkremitzki   
    2017-06-20 05:50   
    @Pauvres_honteux actually I need to revert the change because it allows any 'reporter' user to edit others' issues. Standby
    (0009468)
    kkremitzki   
    2017-06-20 06:04   
    @Pauvres_honteux @Kunda1 from http://mantisbt.org/manual/#admin.lifecycle.workflow.thresholds it doesn't seem like there's any granularity to

    Update an issue - The access levels that are allowed to update the header information of an issue.

    and therefore no option for reporters to edit their own issue headers. I also don't see any option for deleting one's attachments
    (0009486)
    Kunda1   
    2017-06-22 02:10   
    @Pauvres_honteux tell me what to remove and I'll make it happen
    (0009488)
    Pauvres_honteux   
    2017-06-22 04:33   
    @Kunda1 , thank you for your kind offering, please see post 0009466.
    And if you feel adventurous; all the other posts just adding to the confusion:
    0004227
    0004696
    0004697
    0004698
    0004699
    0004700
    0004703
    0004704
    0004705
    0007741
    (0009490)
    Kunda1   
    2017-06-22 10:57   
    @Pauvres_honteux Done! ;)
    (0014924)
    Pauvres_honteux   
    2020-10-22 11:26   
    My pictures seems to have vanished!?!?
    Oooh well, I'll add a couple of new ones.

    Picture 51.png shows the tangential lines in full width and black.
    Picture 52.png shows the tangential lines in half width and grey.

    And please do not delete my added files from now on.
    (0014928)
    Kunda1   
    2020-10-22 15:48   
    They weren't deleted purposely. It may have been a broken by an update or something. There are other tickets with missing attachments we all.
    (0016418)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5583.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    477 [FreeCAD] Feature minor have not tried 2011-11-10 15:28 2021-02-06 06:49
    Reporter: wmayer Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: acknowledged Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Proper interface for edit modes of view provider
    Description: http://forum.freecadweb.org/viewtopic.php?f=10&t=1875&p=12429#p12429
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0001337)
    Jriegel   
    2011-11-21 09:13   
    Really needed!
    (0005958)
    wmayer   
    2015-03-31 08:38   
    There is a new class ActionFunction which allows you to connect a QAction with a standard C++ member function of a class that is not inherited from QObject.

    So, this makes it quite easy to use with the view providers. There is an example for MeshGui::ViewProvider.

    In the setupContextMenu method you get a pointer to a QMenu instance where you can add further items with addAction. The returned QAction instance then can be connected with a member function of the view provider using the ActionFunction class.

    Since you can use arbitrary member functions (but the argument and return type must be void) this solution can be considered as an alternative to the setEdit function.
    (0008659)
    wmayer   
    2017-03-20 13:52   
    See also: https://forum.freecadweb.org/viewtopic.php?f=22&t=21330
    (0009622)
    Kunda1   
    2017-06-30 12:14   
    Also see wmayer's comment 0001954:0007874
    (0011421)
    Kunda1   
    2018-06-13 13:25   
    Unassigning Jriegel
    (0016381)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5546.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    402 [FreeCAD] Feature major have not tried 2011-07-18 06:45 2021-02-06 06:49
    Reporter: wmayer Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: acknowledged Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Switch on and off parametric behaviour of document objects
    Description: According to the thread [1] we need a way to switch on and off the parametric of document objects. Since this should be serialized we have to use a PropertyBool member. If this flags is off we simply have to skip the execute() method inside the recompute() of DocumentObject.

    [1] http://forum.freecadweb.org/viewtopic.php?f=8&t=1070&p=8654#p8652
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0006165)
    bejant   
    2015-05-28 14:01   
    Here's a new link to the topic, after the FreeCAD forum moved from SourceForge:
    http://forum.freecadweb.org/viewtopic.php??f=8&t=1070&p=8654#p8652
    (0011424)
    Kunda1   
    2018-06-13 13:27   
    Unassigning Jriegel
    (0011661)
    Kunda1   
    2018-08-26 11:20   
    Updated URL in ticket summary from old sourceforge URL
    (0012355)
    Kunda1   
    2019-01-01 13:13   
    New discussion at https://forum.freecadweb.org/viewtopic.php?f=8&t=33101
    (0016380)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5545.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4537 [FreeCAD] Bug minor always 2021-01-17 18:03 2021-02-06 06:49
    Reporter: bertrand.lancelot@objectspirit.net Platform:  
    Assigned To: OS:  
    Priority: high OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: to be completed
    Summary: Export GCode - 'PrimitivePy' object has no attribute 'Proxy' error message
    Description: OS: MAC Catalina 10.15.7
    Freecad version 018.16146 (same problem with install from a download or with brew install)

    Impossible to export the 3D model to print it with my 3D printer. Anyway the processor used.
    Then this issue is blocking issue for me.

    Thanks in advance, but in waiting, I will try another tool to be able to test and use my new 3D printer.
    Tags:
    Steps To Reproduce: create a symple Cylinder 3D object or anything else in 3D.
    Go to menu file / export
        title: test.gc for exemple
        validate
        select the first processor in the list "centroid_post" (none is working after many tests)
        Validate

    Then the error message appear:
    Cylinder
    postprocessing...
    Traceback (most recent call last):
      File "<string>", line 4, in <module>
    <class 'RuntimeError'>: 'PrimitivePy' object has no attribute 'Proxy'
    Additional Information:
    Attached Files:
    Notes
    (0015219)
    bertrand.lancelot@objectspirit.net   
    2021-01-24 08:02   
    Hi,

    I did find a turnaround in using ultimaker cuba tool. Then, I have to export to obl file and open it in cuba to transform obj file to g-code.
    A bit longer but acceptable in waiting a fix.

    So, possible to change priority to low if you want.
    Regards,
    (0016982)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6150.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4511 [FreeCAD] Bug minor always 2020-12-16 11:41 2021-02-06 06:49
    Reporter: Vorpal Platform: Linux  
    Assigned To: OS: Ubuntu  
    Priority: normal OS Version: 18.04  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Ubuntu 18.04.5 LTS (X-Cinnamon/cinnamon)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.23323 (Git) AppImage
    Build type: Release
    Branch: master
    Hash: 512d5c6141aec52b6eecc67370336a28fde862a6
    Python version: 3.8.6
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: English/United Kingdom (en_GB)
    Summary: AppImage update fails with python error in report view
    Description: Using the built in AppImage updater has since a few weeks always failed at a late stage. The resulting new AppImage file is produced, but the update does not inform the user and offer to restart with the new version. The behaviour can be seen in the attached screenshot.

    Forum thread with at least two users experiencing the issue: https://forum.freecadweb.org/viewtopic.php?f=4&t=53022
    Tags:
    Steps To Reproduce: 1. Start FreeCAD 0.19dev
    2. Perform AppImage update from the settings where there is an update to download
    3. Select to update.
    4. Towards the end of the update the python error mentioned above is reported and the update stalls, never informing the user that it completed.
    Additional Information:
    Attached Files: Appimage update Error.png (244,848 bytes) 2020-12-16 11:41
    https://tracker.freecad.org/file_download.php?file_id=2576&type=bug
    Notes
    (0016971)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6138.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4475 [FreeCAD] Bug minor always 2020-10-26 22:52 2021-02-06 06:49
    Reporter: fcaduser Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Debian GNU/Linux 10 (buster) (GNOME/gnome)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.22798 (Git)
    Build type: Release
    Branch: master
    Hash: a29d834bd31fcf5dedfceb159c4d36c18194197f
    Python version: 3.7.3
    Qt version: 5.11.3
    Coin version: 4.0.0a
    OCC version: 7.5.0.beta
    Locale: French/France (fr_FR)
    Summary: Thumbnail creation sometime fails.
    Description: About 20% of them are "blank" (ie using the default FC logo) within the start page.
    This behavior is quite old but I still can't determine if there is a specific property of a file preventing the creation mechanism, it seems totally random.
    Tags: #pending-PR
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0014954)
    Kunda1   
    2020-10-27 01:03   
    Please link to the forum thread.
    (0014955)
    fcaduser   
    2020-10-28 10:47   
    Link to the forum about this :
    https://forum.freecadweb.org/viewtopic.php?f=8&t=51493
    (0015018)
    Kunda1   
    2020-11-24 12:38   
    (Last edited: 2020-11-24 12:47)
    Looks like someone is submitting a fix. See FreeCAD Pull Request 4078
    Thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=48509&p=451098#p451063
    (0015099)
    Kunda1   
    2020-12-06 19:57   
    (Last edited: 2020-12-06 19:58)
    @fcaduser please retest
    (0015100)
    Kunda1   
    2020-12-06 19:59   
    (Last edited: 2020-12-06 20:41)
    @drmacro care to weigh in?
    (0015129)
    fcaduser   
    2020-12-12 15:35   
    Same problem with the last release.

    --------------------------------
    OS: Debian GNU/Linux 10 (buster) (GNOME/gnome)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.23073 (Git) <--------------------------------------------------
    Build type: Release
    Branch: master
    Hash: acf9b1f0de0b931ba767d1d3a3115627b35b441e
    Python version: 3.7.3
    Qt version: 5.11.3
    Coin version: 4.0.0a
    OCC version: 7.6.0.dev
    Locale: French/France (fr_FR)
    (0016954)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6121.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4403 [FreeCAD] Feature feature N/A 2020-07-08 13:54 2021-02-06 06:49
    Reporter: ferdymercury Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Linux Mint 19.3 (MATE/mate)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.21775 (Git) AppImage
    Build type: Release
    Branch: master
    Hash: 1f741aa511e898849e46ed14515fce416fe32acb
    Python version: 3.8.2
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: English/United States (en_US)
    Summary: import PRC file or 3D PDF into FreeCAD
    Description: This is a follow up the suggestion I made in the forum.

    PRC files are commonly used by several vendors to embed 3D models in a PDF file. Unfortunately, these files can only be opened with Adobe PDF reader. For example, Linux does not have a native Adobe viewer, which means it is impossible to view correctly this type of documents. One needs some workarounds (Wine, Virtualbox, or old Adobe versions for Linux).

    I thought that in general, not only for Linux users, it would be nice if FreeCAD would be able to import PRC files in the same way it imports STEP files. (Also including nested parts in the tree model).

    It is easy to extract the embedded PRC file from the 3D PDF, by just searching for 'stream.PRC' and 'endstream' bytes in a hex editor, so in principle this could be done automatically also by FreeCAD. Everything inbetween is the PRC binary file that can be extracted, and for example included in your own PDF with pdflatex media9 package.

    Thinking about a 'far future', if FreeCAD is able to open and import it, this would allow in the future that Linux PDF viewers display inline also 3D models, by embedding a small FreeCAD plugin directly, instead of having to open it in external FreeCAD window. In the same way than Adobe PDF reader has a Flash Player plugin to do that.

    To implement this feature, one might reuse some parts of this code: https://github.com/XenonofArcticus/libPRC

    The PRC file format is defined [url=https://web.archive.org/web/20091123055411/http://pdf.editme.com/files/PDFE/SC2N570-PRC-WD.pdf]here[/url].

    Other posts related to generating PRC files from a FreeCAD model:
    https://forum.freecadweb.org/viewtopic.php?t=20224&start=10
    https://forum.freecadweb.org/viewtopic.php?f=8&t=18497#p144546
    (This is the opposite direction than the feature requested here)
    Tags: conversion, file format, import, STEP
    Steps To Reproduce:
    • Download https://tetra4d.com/wp-content/uploads/2015/04/3D-PDF-Sample-Outlet.pdf
    • Open it with Bless hex editor or equivalent
    • Search for PRC keyword (search option Text, not Hex).
    • Select and delete in the hex editor from beginning of document until & including line above, containing keyword 'stream', so that first three bytes of the resulting file are 'PRC'.
    • Search for 'endstream' keyword. Delete from (including) this line until the end of the document.
    • Save result as .prc
    • In a Latex document, you can include it with
    • 
      \usepackage{media9}
      ...
      \includemedia[
        %label=dice, % name for referencing 3D object
        width=\linewidth,
        height=0.495\linewidth,
        3Dtoolbar,
        3Dmenu
        %activate=pagevisible,
        %3Dcoo=13.514159202575684 -210.37330627441406 265.50933837890625,
        %3Dc2c=-0.6669085025787354 0.39916229248046875 0.6292078495025635,
        %3Droo=9603.325257430366,
        %3Droll=-110.37121928895962,
        %3Dortho=0.001394091872498393,
        %3Dlights=Cube
        ]{}{result.prc}
      
    • Compile with pdflatex, and open it with Adobe PDF Reader

    (Side note: if a 3D PDF file has several 3D models embedded, this has to be done in a for loop. Or the user has to select in the import dialog one among those)
     
    %
    %
    Additional Information:
    Attached Files:
    Notes
    (0014636)
    ferdymercury   
    2020-07-08 14:13   
    The following link is more updated than the one from libPRC I posted before.
    https://github.com/vectorgraphics/asymptote/tree/50fb809fdaf2383385f09884174262964a046156/prc

    One could expand the code in asymptote repository and write the functions in the opposite direction (Deserialize, Read) instead of (Serialize, Write). So that Asymptote library could be used as an 'intermediary'. Then, one would 'only' need to convert Asymptote structure to FreeCAD structure.

    See also:
    https://forum.freecadweb.org/viewtopic.php?t=156
    (0015124)
    wmayer   
    2020-12-10 16:49   
    https://forum.freecadweb.org/viewtopic.php?f=8&t=53116
    (0015125)
    ferdymercury   
    2020-12-10 16:54   
    See also: https://github.com/vectorgraphics/asymptote/issues/167
    (0016923)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6090.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4375 [FreeCAD] Feature minor always 2020-06-16 07:06 2021-02-06 06:49
    Reporter: TedM Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 10 (10.0)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.21125 (Git)
    Build type: Release
    Branch: master
    Hash: 40600a55c2fe71ff589be677f6e427ccc937d003
    Python version: 3.8.2
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: English/United States (en_US)
    Summary: Do not add files to the recent list on import or export
    Description: See forum thread here.

    Currently, all user files read or written are added to the recent files list on the start page. However, files that are imported or exported are unlikely to be simply opened and so make little sense to be in this list. These files get little or no value from being able to be clicked on to be opened and push off files that the user are likely to want to simply open.

    Specifically, the feature request is that only files that used in "open", "save" and "save as" should be added to the recent file list. File read or written in any other way (including but not necessarily limited to "import" and "export") should not be added to the list.

    It may be desirable to make this a preferences option to maintain the old way for those who may like it.
    Tags:
    Steps To Reproduce: 1. Create a new file.
    2. Go to Part WB and create a cube.
    2. Select the cube and use file->export to create test.stl
    3. Go to the start page; observe that test.stl is in the recent file list even though there is little value on being able to click on it to open it.
    Additional Information:
    Attached Files:
    Notes
    (0014560)
    TedM   
    2020-06-16 11:24   
    “Save copy” should also go into the resent file list. I overlooked that in the initial report.
    (0015229)
    chennes   
    2021-01-30 16:14   
    Hidden preferences "RecentIncludesImported" and "RecentIncludesExported" were added to control the Recent files list behavior:
    PR: https://github.com/FreeCAD/FreeCAD/pull/4165
    Commit: https://github.com/FreeCAD/FreeCAD/commit/ca346b90992e9241e0edea953a1528dfbe41a693
    Wiki documentation: https://wiki.freecadweb.org/Fine-tuning
    (0016909)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6076.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4265 [FreeCAD] Bug major always 2020-02-15 10:38 2021-02-06 06:49
    Reporter: wmayer Platform:  
    Assigned To: realthunder OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: reopened  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Ubuntu 18.04.4 LTS (XFCE/xubuntu)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.19593 (Git)
    Build type: Unknown
    Branch: master
    Hash: a10a0d9e0f7f3783ee6728e4df60050aba4306ee
    Python version: 3.6.9
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: German/Germany (de_DE)
    Summary: Undo doesn't restore the state as it was before opening a transaction
    Description: When opening a transaction and adding an arbitrary amount of objects to a document before committing it then the undo should always remove these objects again.

    In v0.19 this doesn't work any more.
    Tags: #pending-PR, undo
    Steps To Reproduce:
    1. Go to Part Design
    2. Create a document
    3. Create a sketch, select one of the predefined planes and confirm with OK
    4. Undo now or close the sketch and then undo

    => The body and origin will be removed from the document but the sketch stays

    It's possible to edit the sketch (some error messages appear) and as soon as closing the sketch after doing some changes FreeCAD crashes.
    Additional Information:
    Attached Files:
    Notes
    (0014177)
    wmayer   
    2020-02-23 11:12   
    (Last edited: 2020-02-23 11:13)
    Another regression:
    1. Create a PD box
    2. Select some edges and create a fillet
    3. Now add or remove an edge. This causes to open a second transaction
    4. Click cancel. The expected behaviour is that the fillet object will disappear but because of the 2nd transaction it won't
    (0014227)
    wmayer   
    2020-03-14 10:01   
    Another test case:
    
    doc=App.newDocument()
    doc.openTransaction("Test")
    doc.commitTransaction()
    App.getActiveTransaction() # does not return None but ('None', <int>)
    
    (0014228)
    wmayer   
    2020-03-14 10:31   
    With v0.18
    
    doc1=App.newDocument()
    doc2=App.newDocument()
    doc1.UndoNames # => [] ok
    doc2.UndoNames # => [] ok
    doc1.openTransaction("Test1")
    doc1.UndoNames # => ['Test1'] ok
    doc2.openTransaction("Test2")
    doc2.UndoNames # => ['Test2'] ok
    doc1.addObject("App::FeaturePython")
    doc1.UndoNames # => ['Test1'] ok
    doc1.commitTransaction()
    doc2.commitTransaction()
    

    With v0.19
    
    doc1=App.newDocument()
    doc2=App.newDocument()
    doc1.UndoNames # => [] ok
    doc2.UndoNames # => [] ok
    doc1.openTransaction("Test1")
    doc1.UndoNames # => [] now an empty list. Can be considered as ok when no actual change was made
    doc2.openTransaction("Test2")
    doc2.UndoNames # same as above
    doc1.addObject("App::FeaturePython")
    doc1.UndoNames # => ['Test2'] but expected is ['Test1']. So this is clearly a bug
    doc2.UndoNames # => ['-> Test2'] but expected is ['Test2']. So this is clearly a bug
    doc1.commitTransaction()
    doc2.commitTransaction()
    

    Storing the transaction name and id independent of a document messes up the transaction system.
    (0014229)
    wmayer   
    2020-03-14 14:19   
    This https://github.com/FreeCAD/FreeCAD/commit/69ea7a3d51d653906d35a86203ce197cf22f73a5 fixes the issue with the remaining sketch on undo.
    And this https://github.com/FreeCAD/FreeCAD/commit/8c0dc924269ece2490378889da12636767cd6f9f fixes the disappearance of the fillet on undo

    So, what still needs to be fixed is the mess with the active transaction name which is only a medium severe issue.
    (0014265)
    realthunder   
    2020-03-22 22:21   
    Fix committed to master branch.
    (0014270)
    wmayer   
    2020-03-23 14:36   
    (Last edited: 2020-03-23 14:37)
    The reported mess with the transaction name is not fixed!!!

    Another regression is that GUI changes are not recorded any more:
    In v0.18:
    
    doc=App.newDocument()
    doc.openTransaction("Create box")
    box=doc.addObject("Part::Box","Box")
    doc.commitTransaction()
    doc.recompute()
    
    doc.openTransaction("Change GUI")
    box.ViewObject.ShapeColor=(1.,1.,0.)
    doc.commitTransaction()
    doc.undo() # restores the previous color
    

    In v0.19:
    
    doc=App.newDocument()
    doc.openTransaction("Create box")
    box=doc.addObject("Part::Box","Box")
    doc.commitTransaction()
    doc.recompute()
    
    doc.openTransaction("Change GUI")
    box.ViewObject.ShapeColor=(1.,1.,0.)
    doc.commitTransaction()
    doc.undo() # instead of restoring the color it removes the box
    
    (0014271)
    wmayer   
    2020-03-23 16:08   
    Another odd regression compared to v.018:

    • Create a part container, a box and move the box into the container
    • Make the origin visible
    • Select the box and in the property editor open the map mode
    • Select the XZ plane as reference => box will move
    • Confirm with OK
    • Press undo & redo 5 times => box will move
    • Press undo again => box stops moving

    In v0.18 you can press undo & redo as often as you like and the box is always updated correctly.
    (0014273)
    realthunder   
    2020-03-24 03:18   
    PR submitted to enable transaction on view object. Can't remember exactly, but I think previously view object changes are not recorded?

    The Box movement undo problem is an entirely different issue. It happens because the property changes recorded in transaction is unordered, and AttachEngine will recalculate positioning regardless if it is performing transaction.

    The non movement happens in undo if Placement is restored first, and then some attachment related property is restored next, which triggers AttachEngine positionBySupport(). Because MapMode and Support have not been restored yet, the placement is revert back, which nullifies the undo.

    The reason this problem does not shown up before is because std::map was used to store property changes of each object, with the pointer to the property as the key. When the application starts up, the memory pointer value is likely increasing. So the order in std::map is temporary stable, but not for long. I have changed map to unordered_map, thus exposing the problem.

    I propose to fix this by blocking PropertyContainer::onChange() call temporary while undo/redo, i.e. inside TransactionObject::applyChn(). Once all changes are applied for the current transaction, call Property::touch() for each changed property. Any thoughts?
    (0014274)
    realthunder   
    2020-03-24 09:34   
    See this PR for the proposed fix. Class TransactionGuard is used to temporary disable onChanged() notification, and call touch() when goes out of scope.

    This fix exposes another potential problem in PartFeature::onChange(Placement), as it modifies the Shape without recording it in the transaction.
    (0014287)
    realthunder   
    2020-03-25 00:50   
    There is some mistake in the TransactionGuard PR. Fixed by force push. Also split the Part Placement/Shape onChanged() problem into a separate commit.
    (0015205)
    uwestoehr   
    2021-01-12 00:53   
    What's the status of this bugfix? People treat it as release blocker: https://forum.freecadweb.org/viewtopic.php?f=8&t=51016 but we have a PR as fix that was also approved by yorikvanhavre on Github. Why can/is this not merged?
    (0016865)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6031.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4186 [FreeCAD] Bug minor always 2019-11-04 18:02 2021-02-06 06:49
    Reporter: dadam Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 10
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16131 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-18
    Hash: 3129ae4296e40ed20e7b3d460b86e6969acbe1c3
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    Summary: hang on union of objects
    Description: When tried to unio a number of objects for 10 minutes and there were no errors
    ie the array and the cut
    Tags: #pending-forum
    Steps To Reproduce:
    Additional Information:
    Attached Files: tempknob.FCStd (351,752 bytes) 2019-11-04 18:02
    https://tracker.freecad.org/file_download.php?file_id=2385&type=bug
    Notes
    (0013797)
    openBrain   
    2019-11-04 19:35   
    @dadam : please address this kind of issues according the reporting guidelines (big yellow banner on top of page, or "read this before reporting" on the left), i.e. first create a topic in our forum so the community can help confirm it is a bug, and eventually identify causes.
    I'll let this ticket open at the moment so you can add a link to the forum thread you'll create. ;)
    (0013809)
    Kunda1   
    2019-11-08 19:30   
    @dadam ping
    (0013868)
    Kunda1   
    2019-12-05 14:18   
    @dadam please follow up
    (0014032)
    Kunda1   
    2020-01-09 19:04   
    @dadam this ticket will be closed unless you respond.
    (0014086)
    Kunda1   
    2020-01-16 13:29   
    Thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=42485
    (0015121)
    Kunda1   
    2020-12-08 22:09   
    (Last edited: 2020-12-08 22:10)
    I can reproduce this on
    OS: Manjaro Linux (KDE//usr/share/xsessions/plasma)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.23237 (Git)
    Build type: Release
    Branch: master
    Hash: 71726a11d0844f263dad636fb98bb996a479e007
    Python version: 3.8.6
    Qt version: 5.15.2
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: English/United States (en_US)

    Details in forum thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=42485&p=455866#p455866
    (0016839)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6005.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3786 [FreeCAD] Feature feature always 2019-01-21 11:34 2021-02-06 06:49
    Reporter: Moult Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Ability to cycle between selectable objects (using a keyboard shortcut)
    Description: Sometimes, I am unable to select an object or edge. This is because that edge or object may be coincident with another edge or object. I can usually get around this by hiding objects in the tree, or by changing into wireframe mode, or both. This works, but is slow and not user friendly.

    In Revit, you can press "tab" to cycle between objects to select under your mouse until you have the right object. In Blender, you can keep on clicking to select until you select the right one and then perform the operation.

    I propose that a similar feature such as hitting tab be implemented. I suspect the Blender approach of clicking again will not work, because FreeCAD implementations select the operation beforehand, and then select the object. Therefore some keypress should occur. "Tab" seems sensible (after all, alt-tab is switch windows in window management)

    Forum discussion is here:
    https://forum.freecadweb.org/viewtopic.php?p=281380
    Tags: shortcuts
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0012589)
    Moult   
    2019-02-07 20:44   
    PR for new feature to cycle between selectable objects: https://github.com/yorikvanhavre/BIM_Workbench/pull/19
    PR for new feature to cycle between snappable objects that overlap: https://github.com/FreeCAD/FreeCAD/pull/1943

    This bugreport can be closed :)
    (0016702)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5867.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3494 [FreeCAD] Bug feature always 2018-05-25 22:11 2021-02-06 06:49
    Reporter: easyw-fc Platform:  
    Assigned To: OS:  
    Priority: high OS Version:  
    Status: confirmed Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: DXF export (Autodesk DXF 2D type) doesn't add any UNITS field inside the dxf file.
    Description: FreeCAD DXF export does not add $LUNITS and $INSUNITS both of which are needed for correct importing into any CAD.
    $LUNITS and $INSUNITS should be included in the exported file, to specify which units the design is based on.
    Autodesk section group codes:
    https://www.autodesk.com/techpubs/autocad/acad2000/dxf/header_section_group_codes_dxf_02.htm

    Related forum topics:
    https://forum.freecadweb.org/viewtopic.php?f=8&t=28925
    https://forum.kicad.info/t/units-once-more-dxf-import-trouble/10844
    Tags: DXF, export, units
    Steps To Reproduce:
    Additional Information:
    Attached Files: internal.dxf (1,332 bytes) 2018-05-25 22:11
    https://tracker.freecad.org/file_download.php?file_id=1924&type=bug
    legacy.dxf (1,332 bytes) 2018-05-25 22:11
    https://tracker.freecad.org/file_download.php?file_id=1925&type=bug
    Notes
    (0011278)
    easyw-fc   
    2018-05-25 22:58   
    following the KiCAd forum here some valuable notes:
    The fun you find while digging into obscure specifications

    $INSUNITS was introduced in the “Autocad 2000” specification for DXF.

    This means any export methods set to AC1006 = R10, AC1009 = R11 and R12, AC1012 = R13 or AC1014 = R14. Will not have that tag present if the tool is respecting the export option,

    Freecads export is for AC1009 / R12, so it will never include that tag so long as they are following the specification, and to include it would involve them remaking the exporter to support whatever the Autocad 2000 version is.

    Before this, It was simply that DXF files where unitless, Most tools like solidworks and Autocad assumed this to be in inches if not specified on import,
    (0011311)
    Kunda1   
    2018-05-30 23:22   


    I had this issue once too. Back than it turned out the DXF version freecad exports does not use units, it is not in this versions standart. You can check the version by the DXF file header, there is a identifier which you can than relate to the spec version.

    The conclusion back than was, that the error is on the importing software site: it needs to check the specification version of the DXF and use units only when supportet by it.

    Don't know if this is still valid though it if freecad has upgraded the DXF version.

    ickby
    ref: https://forum.freecadweb.org/viewtopic.php?f=8&t=28925#p235782
    (0011744)
    Kunda1   
    2018-09-14 19:56   
    Related: 0003594
    (0011745)
    rawrpenguinzombies   
    2018-09-14 20:05   
    I am willing to pitch in on something for whoever fixes this and the related 0003594 ID tickets.
    (0011747)
    Kunda1   
    2018-09-15 12:48   
    @rawrpenguinzombies please mention that on the forum thread so it's more visible.
    (0016628)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5793.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3393 [FreeCAD] Feature feature N/A 2018-03-26 13:06 2021-02-06 06:49
    Reporter: Kunda1 Platform:  
    Assigned To: OS:  
    Priority: low OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Configuration wizard when launching FreeCAD for the first time
    Description: Inspired by this thread: https://forum.freecadweb.org/viewtopic.php?f=3&t=27623&start=10#p223411
    Discussion thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=27691



    But wouldn't the best be to open a configuration wizard when launching FreeCAD for the first time? Something like what LibreCAD has, but extended. It could give you the possibility to set your units, define your mouse model (explanation window required, similar to Navigation Indicator), even TechDraw template size.

    Going further, we could introduce "custom profiles" in the wizard that would automatically filter the workbench list to different selections.

        * Architecture profile would filter the wb selector to only display Arch, Draft, Sketcher, Spreadsheet, TechDraw and possibly a few others (Mesh Design? Part? Raytracing?)
        * Mechanical Design profile would filter the wb selector to only display Sketcher, PartDesign, Spreadsheet, TechDraw, Mesh Design, FEM and possibly Raytracing and Draft
        * General modeling profile would display Draft, Sketcher, Part...
        * Complete profile would display all installed workbenches.

    NormandC
    Tags: #lowhangingfruit
    Steps To Reproduce:
    Additional Information: Here is the librecad code:
    ui: https://github.com/LibreCAD/LibreCAD/blob/master/librecad/src/ui/forms/qg_dlginitial.ui
    cpp: https://github.com/LibreCAD/LibreCAD/blob/master/librecad/src/ui/forms/qg_dlginitial.cpp
    h: https://github.com/LibreCAD/LibreCAD/blob/master/librecad/src/ui/forms/qg_dlginitial.h
    Attached Files:
    Notes
    (0011064)
    normandc   
    2018-03-27 00:47   
    fix typo
    (0011560)
    Kunda1   
    2018-07-29 11:54   
    Wikilab team has started to tackle this issue in:
    https://forum.freecadweb.org/viewtopic.php?f=10&t=29610
    (0012478)
    silas   
    2019-01-21 18:21   
    Hi. Just communicating we Wikilab (https://lab.wiki.br) are still working on that. We couldn't finish it before 0.18 and we are in school holiday period, we are in very slow pace, but but we are still on this issue.

    If want to see [slow] progress, check the branch: https://github.com/wikilab-abc/FreeCAD/tree/config-wizard
    (0014854)
    Kunda1   
    2020-10-14 20:41   
    @silas looks like development stalled. What is the status of the wizard ?
    (0015130)
    silas   
    2020-12-12 19:37   
    Hi! Sorry for taking so long to send a reply. It happened that the group had vanished, so we halted the development. Consider it will not be done by our group in the short term. Sorry for that and thank you for the opportunity.
    (0016607)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5772.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3353 [FreeCAD] Feature minor N/A 2018-02-22 17:58 2021-02-06 06:49
    Reporter: yorik Platform: PC  
    Assigned To: yorik OS: Debian  
    Priority: normal OS Version: Testing 64bit  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Direct modeling tools
    Description: FreeCADs is a feature-based parametric modeling system, hence different modeling steps depend on one or multiple previous steps. Each step is at the same time a tool/operation, and a geometrical object, resulting from that operation. This mix of operation and object is called a feature. Direct modeling, often presented as the opposite of parametric modeling, allows to graphically move vertices, push or pull faces and edges to modify the geometry of an object.

    This issue is a GSOC idea https://www.freecadweb.org/wiki/Direct_modeling_tools

    and also as a test for bountysource...
    Tags:
    Steps To Reproduce:
    Additional Information:
    System Description
    Attached Files:
    Notes
    (0015233)
    Kunda1   
    2021-01-31 11:21   
    (Last edited: 2021-01-31 11:21)
    Several attempts have already begun to tackle this issue:
    (0016599)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5764.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4531 [FreeCAD] Bug minor always 2021-01-09 20:48 2021-02-06 06:49
    Reporter: qwerty_f Platform:  
    Assigned To: vejmarie OS: OSX  
    Priority: normal OS Version: Big Sur  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: macOS 11.1
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.23648 (Git)
    Build type: Release
    Branch: master
    Hash: 5b058a9f13c89bb374ddf77b93008d560822398c
    Python version: 3.9.0
    Qt version: 5.15.2
    Coin version: 4.0.0
    OCC version: 7.5.0
    Locale: German/Germany (de_DE)
    Summary: homebrew does not have a beer
    Description: When running homebrew to create FC on Big Sur it ends without success message. See forum post. At least there should be a message where to find the binary to start it manually. Of course a bundled app would be preferable.
    Tags:
    Steps To Reproduce: brew install freecad --head
    Additional Information:
    Attached Files:
    Notes
    (0015240)
    Kunda1   
    2021-01-31 12:01   
    Sorry @vejmarie for the flood.
    which ticket do you want to keep? :P
    (0016980)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6148.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4509 [FreeCAD] Bug major always 2020-12-11 22:16 2021-02-06 06:49
    Reporter: 533online Platform: pc  
    Assigned To: Kunda1 OS: win  
    Priority: normal OS Version: 10  
    Status: feedback Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 10 (10.0)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.23074 (Git)
    Build type: Release
    Branch: master
    Hash: 74b866ed3022fd1452c534dae31a721bcc668f2f
    Python version: 3.6.8
    Qt version: 5.12.1
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/United States (en_US)
    Summary: round pocket exports as a hexagonal pocket in obj format. Is filled in solid in stl and 3mf formats. There is no gco export.
    Description: round pocket exports as a hexagonal pocket in obj format. Is filled in solid in
    stl and 3mf formats. There is no gcode export in FC 0.19.

    I tried turning off curves as line segments in export preferences, but no go.
    Every format I tried that is compatible with cura either fills in the pocket
    as a solid, or converts the round pocket into a hexagonal pocket. Only when I
    loaded my fcstd model into Freecad 0.18.4 did the round pocket actually export
    as a round pocket in obj format. I am currently printing the model to confirm
    a successful print.
    Tags: #post-to-forum
    Steps To Reproduce: Create round pocket in model. I ain't tried it with a through hole.
    Finish model. Export model in any format recognized by cura. Round
    pocket translates to hexagon in cura. To my knowledge, the latest
    cura has no issues that I am aware of. I'm pretty much a newbie to
    Freecad and cura and 3d printing, so this probably should be more
    thoroughly tested by some one with more experienced.
    Additional Information:
    Attached Files: boxtrielbowplt121120.FCStd (90,527 bytes) 2020-12-11 22:16
    https://tracker.freecad.org/file_download.php?file_id=2572&type=bug
    testexport.stl (81,084 bytes) 2020-12-22 08:30
    https://tracker.freecad.org/file_download.php?file_id=2582&type=bug
    testexport.obj (131,987 bytes) 2020-12-22 08:30
    https://tracker.freecad.org/file_download.php?file_id=2583&type=bug
    Notes
    (0015128)
    Kunda1   
    2020-12-12 13:36   
    (Last edited: 2020-12-12 13:39)
    Forum thread where the discussion happened before opening the ticket?
    Please also choose a more friendly tracker username. Let me know and I will update it.

    Edit: most up to date version of 0.19 at the time of this ticket is:
    FreeCAD_0.19.23258-Win-Conda_vc14.x-x86_64.7z
    FreeCAD_0.19.23266_Win-LPv12.1.6_vc14.x-x86-64.7z
    Please make sure to test on the most up to date 0.19 before submitting bug reports to the forum. Thx.
    (0015171)
    kisolre   
    2020-12-22 08:30   
    Body exports properly to STL and OBJ. Could you provide your exports for comparison?
    OS: Windows 8.1 Version 6.3 (Build 9600)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.23489 (Git)
    Build type: Release
    Branch: master
    Hash: a43736b04ec26745865ee78afa88c112c62d2dde
    Python version: 3.8.6+
    Qt version: 5.15.1
    Coin version: 4.0.1
    OCC version: 7.5.0
    Locale: Bulgarian/Bulgaria (bg_BG)
    (0015268)
    Kunda1   
    2021-02-04 10:32   
    @533online ping
    (0016970)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6137.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4544 [Sketcher] Feature feature N/A 2021-01-25 16:23 2021-02-06 06:48
    Reporter: Jee-Bee Platform:  
    Assigned To: OS:  
    Priority: low OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: nvt
    Summary: Add new method for trim sketch
    Description: Add a new method for trimming multiple sketch lines at once.
    Description of work flow
    - Model a shape that needs a trim
    - start trim tool
    - click at some point and while clicking move the mouse
    - All lines that are crossed remove them till nearest intersection(s)
    See images for simple example
    Tags: sketcher, trim
    Steps To Reproduce:
    Additional Information: see: https://forum.freecadweb.org/viewtopic.php?f=10&t=54441#p468692
    Attached Files: 2021-01-25 17_15_14-FreeCAD 0.19.png (18,675 bytes) 2021-01-25 16:23
    https://tracker.freecad.org/file_download.php?file_id=2604&type=bug
    2021-01-25 17_17_52-FreeCAD 0.19.png (8,131 bytes) 2021-01-25 16:23
    https://tracker.freecad.org/file_download.php?file_id=2605&type=bug
    Notes
    (0016984)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6152.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4503 [Sketcher] Feature feature N/A 2020-11-25 19:54 2021-02-06 06:48
    Reporter: Mistermaker Platform:  
    Assigned To: OS:  
    Priority: none OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 10 (10.0)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.22960 (Git)
    Build type: Release
    Branch: master
    Hash: c5a4b01d2e4218bcc0eb6650337650a6c65ef0e4
    Python version: 3.8.6
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: Dutch/Netherlands (nl_NL)
    Summary: Dimension between 2 concentric circles
    Description: Request is a method on how to add a dimensional constrain between 2 concentric circles. This is closely related to the requested offset feature. See added gif for how it is currently done in Fusion360 and how it is done in Freecan 0.19

    See forum topic:
    https://forum.freecadweb.org/viewtopic.php?p=450998#p450998
    Tags: constraints, sketcher
    Steps To Reproduce:
    Additional Information:
    Attached Files: offset dimemension.gif (395,044 bytes) 2020-11-25 19:54
    https://tracker.freecad.org/file_download.php?file_id=2566&type=bug
    offset dimemension freecad.gif (560,126 bytes) 2020-11-25 19:54
    https://tracker.freecad.org/file_download.php?file_id=2567&type=bug
    Notes
    (0016966)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6133.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4472 [Sketcher] Feature feature N/A 2020-10-23 14:53 2021-02-06 06:48
    Reporter: Sandkuchen Platform:  
    Assigned To: OS:  
    Priority: low OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 7 SP 1 (6.1)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.22665 (Git)
    Build type: Release
    Branch: master
    Hash: b0d7850406e046f3b7a8cd5da261e7d54df6bd99
    Python version: 3.8.6
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: German/Germany (de_DE)
    Summary: Place and orientate dimension constraints in one go
    Description: Concerned environment/workbench: Sketcher

    Requested Feature: Ability to orientate the labels/arrows of dimensional constraints (aka drag them to a convenient place within the the sketch) while still being within the constraint command

    The feature is described and to some degree discussed in https://forum.freecadweb.org/viewtopic.php?f=8&t=51125

    The requested feature is not related to the consolidated dimension constraint tool (aka "Smart Dimension" etc.) described in https://forum.freecadweb.org/viewtopic.php?f=8&t=50521 apart from both requests dealing with dimensional constraints in general. Neither feature depends on the other; neither includes the other; neither makes the other obsolete; they don't come as a set.

    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016953)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6120.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4467 [Sketcher] Bug minor always 2020-10-18 20:46 2021-02-06 06:48
    Reporter: TedM Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: acknowledged Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 10 (10.0)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.22665 (Git)
    Build type: Release
    Branch: master
    Hash: b0d7850406e046f3b7a8cd5da261e7d54df6bd99
    Python version: 3.8.6
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: English/United States (en_US)
    Summary: Cloning and placing to automatically constrain to old objects creates malformed constraints
    Description: Referencing this thread.

    Creating a circle and connected line and then cloning these and placing the clone to automatically constrain to original objects generates a malformed constraint.

    I have reproduced this as far beck as 0.19.21125 which is the earliest 0.19 I have.

    I cannot reproduce this on 0.18.4, possibly because the automatic constrain on clone placement doesn't work.
    Tags:
    Steps To Reproduce: 1. Start FreeCAD.
    2. Open the report view panel at the bottom of the screen.
    3. Create a new document.
    4. Go to the Part Design WB.
    5. Create a body.
    6. Create a sketch on the XY plane.
    7. Place a circle, not constrained in location and constrain the radius to 2.5mm.
    8. Place a line with one end constrained to the center of the circle and the other end to the right. Add a horizontal constraint and a length constraint of 14mm.
    9. Select both objects and then slowly double-click the center of the circle so that everything is still selected and the circle center is last selected.
    10. Clone the objects and use the mouse to move the clone reference point onto the right end of the line so that the constrained constraint symbol (a circle on a diagonal cross) shows to make the cloned circle constrained to the old line and click the mouse button.
    11. These errors will immediately appear in the report window:
    12:03:06 Sketcher constraint number 8 is malformed!
    12:03:06 Sketch Sketch has malformed constraints!
    12:03:06 Sketcher constraint number 8 is malformed!
    12:03:06 Sketcher constraint number 8 is malformed!
    12:03:06 Sketch Sketch has malformed constraints!

    In 0.18.4, step 10 above still shows the constrained constraint symbol (just a dot in that release) but the cloned line and original circle does not constrain.
    Additional Information: The attached file is the result of the above procedure.
    Attached Files: malformed constraints created.FCStd (5,313 bytes) 2020-10-18 20:46
    https://tracker.freecad.org/file_download.php?file_id=2546&type=bug
    Notes
    (0014910)
    TedM   
    2020-10-18 20:49   
    So, small error in procedure. Step 10 should read:

    10. Clone the objects and use the mouse to move the clone reference point onto the right end of the line so that the constrained constraint symbol (a circle on a diagonal cross) shows to make the cloned circle constrained to the old line and release click the mouse button.
    (0014919)
    openBrain   
    2020-10-21 15:50   
    @TedM : I fixed the typo in the original text according your note ;)
    (0016949)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6116.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4331 [Sketcher] Feature trivial N/A 2020-04-30 13:44 2021-02-06 06:48
    Reporter: aster Platform:  
    Assigned To: OS:  
    Priority: low OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 10
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16131 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-18
    Hash: 3129ae4296e40ed20e7b3d460b86e6969acbe1c3
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: Italian/Italy (it_IT)
    Summary: Enable visual grouping of constraints
    Description: Hello,

    A few days ago we started a discussion on the forum about a visual improvement in how freeCAD shows constraints in the combo box. This feature may be enabled by checking a combo box in the above "Filter" menu.


    https://forum.freecadweb.org/viewtopic.php?f=8&t=45753&p=392705#p392705

    Here, for example, I should see only 4 constraints, ideally:
    Constraint 1, 2, 3
    Constraint 4, 5
    Constraint 6, 7
    Constraint 8



    I created the FR with low priority and severity trivial, feel free to change
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016888)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6054.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4253 [Sketcher] Feature feature N/A 2020-01-21 10:33 2021-02-06 06:48
    Reporter: Bernhard Schiffner Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: KDE neon User Edition 5.17 (KDE//usr/share/xsessions/plasma)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.
    Build type: Release
    Python version: 3.6.9
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: German/Germany (de_DE)
    Summary: No "snap to intersection" implemented in Sketcher
    Description: I'am used to work a lot in construction mode (blue lines), and anchor object lines (white lines) to points defined there later in the process.
    I noticed that there is no "snap to intersection" feature implemented in FreeCAD / Sketcher.
    If compared to other CAD tools this is (for me) something essential missing.

    The example attached, gives a nice opportunity to test the problem.

    On the way you can notice, that the order of snapping is improveable too.
    (Snap to the next construction point first and not the next line possible.)

    To understand the example: it symbolizes the end of a shaft entering a gear. The sides of the triangle are milled a little bit "malicious" and don't fit the regular hexagon.
    An (example) shape is given, but I'd like to do the equivalent using blue construction lines and their intersections for defining points.
    Tags: #post-to-forum
    Steps To Reproduce: Try to catch two intersecting construction lines to define a point.

    Additional Information: You can use workarounds like defining a point by "snap to line" to two different lines.
    But if you close the contour this way, sketcher starts to claim nonsense about redundant dependencies. :-)

    (Using self compiled pyside2 packages to make FreeCAD run with KDE NEON.)
    Attached Files: Entry_to_Gear.FCStd (12,048 bytes) 2020-01-21 10:33
    https://tracker.freecad.org/file_download.php?file_id=2426&type=bug
    Constraint_PointOnIntersection.svg (20,900 bytes) 2020-01-21 20:41
    https://tracker.freecad.org/file_download.php?file_id=2427&type=bug
    Notes
    (0014101)
    openBrain   
    2020-01-21 16:23   
    Thx for suggesting. However, could you open a topic in our forum so the proposal is discussed by the community (you can also get there help about the 'redundant constraint' issue) ? Thx
    (0014102)
    Bernhard Schiffner   
    2020-01-21 20:41   
    I'll start this discussion.
    I am new at this, so please excuse possible errors from my side.
    For the moment I add some (possible) icon for the idea.

    Where to snap first ...
    1.) Snap to point (removes 2 DOF by using 1 user created constituent)
    2.) Snap to intersection (removes 2 DOF by using 2 user created constituents)
    3.) Snap to line (removes 1 DOF by using 1 user created constituent)
    ....
    x.) vertical constraint (removes 1 DOF by using 1 general constituent)
    (0014104)
    Kunda1   
    2020-01-24 11:28   
    OP, please post to the forum per the guidelines (big yellow banner at the top of this page). Please do not forget to crosspost the URL of the thread back here.
    (0014504)
    Kunda1   
    2020-06-07 14:33   
    @Bernhard_Schiffner forum thread pls
    (0014514)
    Bernhard Schiffner   
    2020-06-07 20:13   
    If this forum post of 2017 (as an example) is more or less about the same thing, is it necessary to open a new thread there?

    https://forum.freecadweb.org/viewtopic.php?f=8&t=24815&p=194830&hilit=snap+intersection#p194830
    (0016860)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6026.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4185 [Sketcher] Feature feature N/A 2019-11-04 08:39 2021-02-06 06:48
    Reporter: freedman Platform: See below  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 7
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16085 (Git)
    Build type: Release
    Branch: master
    Hash: 6323069cbbda5ac71dff073f15cc632d8a1f3ea3
    Python version: 2.7.14
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.2.0
    Locale: English/UnitedStates (en_US)
    Summary: Sketcher opens a sketch at the current location, we need an icon to take us to the sketch.
    Description: Sketcher needs a way to center selected sketch elements in sketch window. My example in the thread; If you have a 10 story building and your looking at the first floor, you click to edit a sketch of something on the 10th floor, sketcher will open a window at the current view location, we need an icon to center the sketch elements in the sketch window, in this case it would chage the view to the 10th floor. Sketcher does not do this currently. Here is a link to a discussion, about page 3.
    https://forum.freecadweb.org/viewtopic.php?f=8&t=40317&start=10
    Tags:
    Steps To Reproduce:
    Additional Information: The new icon could be a sketch with a bulls-eye on it to depict a focus of the sketch elements.
    Thank you
    Attached Files:
    Notes
    (0013802)
    freedman   
    2019-11-07 01:33   
    (Last edited: 2019-11-19 20:03)
    I have started a new thread asking for more advice.
    https://forum.freecadweb.org/viewtopic.php?f=8&t=40643

    This thread addresses the issue directly. From what I see Mario52 has solved the problem with his code. Included in the thread is code to test. This seems like a huge improvement to sketcher. If this code is run when entering sketcher the target sketch is focused in the screen.
    https://forum.freecadweb.org/viewtopic.php?f=22&t=40938#p348173

    (0016838)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6004.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4184 [Sketcher] Feature feature N/A 2019-11-04 08:21 2021-02-06 06:48
    Reporter: freedman Platform: See below  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 7
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16085 (Git)
    Build type: Release
    Branch: master
    Hash: 6323069cbbda5ac71dff073f15cc632d8a1f3ea3
    Python version: 2.7.14
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.2.0
    Locale: English/UnitedStates (en_US)
    Summary: Add an addition usage to a current icon in sketcher
    Description: Many designers use Sketcher in Normal and 3D camera view. We have a current icon that when clicked will change the camera view to "normal to sketch". I would like an addition to the use of this icon, when clicked on it could toggle between sketch normal and the saved prior view before entering sketcher. Here is a link to a discussion, page 2 of the posts.
    https://forum.freecadweb.org/viewtopic.php?f=8&t=40317&start=10
    Tags:
    Steps To Reproduce:
    Additional Information: Below is an image of the icon for "change view perpendicular to sketch", it's in the Sketch toolbar list at the bottom. It is a sketch with a magnifying glass on it.
    The version number and platform are unimportant for this discussion.
    Attached Files: sketch_normal.JPG (11,184 bytes) 2019-11-04 08:21
    https://tracker.freecad.org/file_download.php?file_id=2384&type=bug
    Notes
    (0016837)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6003.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4160 [Sketcher] Feature minor N/A 2019-10-11 01:57 2021-02-06 06:48
    Reporter: bejant Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Constraint Symbols and Numbers In The 3D View - Allow Users To Specify a Size
    Description: Allow users the ability to change the size for Constraint numbers and symbols shown in the 3D view. This would probably be similar to how users can specify a font size for Constraint numbers and units in the 3D view. Users with high resolution displays and / or poor vision may increase the size and other users may want to keep the size small to reduce clutter.

    An image that probably illustrates this more clearly than my description here, and the forum discussion:
    https://forum.freecadweb.org/viewtopic.php?f=3&t=4362&start=10#p339894
    Tags:
    Steps To Reproduce: Does not apply.
    Additional Information: OS: Ubuntu 18.04.3 LTS (ubuntu:GNOME/ubuntu)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19. (dated 2019-08-21)
    Build type: Release
    Python version: 3.6.8
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    Attached Files: Screen Shot 2019-10-13 at 9.05.38 AM.png (1,125,255 bytes) 2019-10-13 16:07
    https://tracker.freecad.org/file_download.php?file_id=2372&type=bug
    Notes
    (0013753)
    KenA   
    2019-10-13 16:07   
    Confirmed on brand New Mac using every display I have - Thank You
      Model Name: MacBook Pro
      Model Identifier: MacBookPro15,3
      Processor Name: Intel Core i9
      Chipset Model: Radeon Pro Vega 16
    OS: macOS 10.14
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16131 (Git)
    Build type: Release
    Branch: (HEAD detached at 0.18.3)
    Hash: 3129ae4296e40ed20e7b3d460b86e6969acbe1c3
    Python version: 3.6.7
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    (0016830)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5996.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3928 [Sketcher] Feature feature always 2019-04-05 22:49 2021-02-06 06:48
    Reporter: uwestoehr Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: missing preferences option to specify increment of spin buttons in dialogs
    Description: When adding dimension constraints you can use in the dialogs the spin buttons to in/decrease the dimension.
    Currently the increment of these spin buttons is 1mm. This value should be changeable because for example in microtechnology, one would rather have an increment of 0.1 mm while in architectural constructions one might like to have an increment of 10 mm.

    Thus the feature request is to have a preferences settings to change the increment of the sketcher length constraints dialogs.

    Tags: constraints, sketcher
    Steps To Reproduce:
    Additional Information: Forum thread: https://forum.freecadweb.org/viewtopic.php?f=3&t=35422

    OS: Windows 7
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16093 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-18
    Hash: 690774c0effe4fd7b8d2b5e2fb2b8c8d145e21ce
    Python version: 2.7.14
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.2.0
    Locale: German/Germany (de_DE)
    Attached Files:
    Notes
    (0016745)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5911.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3910 [Sketcher] Bug minor always 2019-03-17 13:25 2021-02-06 06:48
    Reporter: Jee-Bee Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: sketch lost tangent constraint using trim
    Description: Trim function in sketcher removes (wrong) constraint with tangent lines.
    Tags: Sketch, Tangent
    Steps To Reproduce:
    1. New part
    2. create new sketch
    3. add a line and a arc
    4. make arc and line tangent
    5. force that line and arc have overlap (both have to much length
    6. trim overlap
    7. end with coincident/ point on entity and tangent is lost
    see https://forum.freecadweb.org/viewtopic.php?f=8&t=34774&start=20#p293117
    and https://forum.freecadweb.org/viewtopic.php?f=8&t=34774&start=20#p293495
    Additional Information: OS: OS X El Capitan (10.11)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.14976 (Git)
    Build type: Release
    Branch: (HEAD detached at e79a19828)
    Hash: e79a19828e2e92269ff96110dfeadaa245ad17c2
    Python version: 2.7.15
    Qt version: 5.11.2
    Coin version: 4.0.0a
    OCC version: 7.2.0
    Locale: English/Netherlands (en_NL)

    Also at windows but don't know with version
    Attached Files: 2019-03-19 14_11_13-FreeCAD 0.18.png (28,350 bytes) 2019-03-19 13:12
    https://tracker.freecad.org/file_download.php?file_id=2159&type=bug
    Notes
    (0012928)
    harrygeier   
    2019-03-19 13:12   
    I can verify that . It´s even more strange as the constraints still are existing, but do not act on the elements
    (0012930)
    Kunda1   
    2019-03-20 18:48   
    Marking issue 'Confirmed'
    BTW @Jee-Bee did you mean to tag as 'Tangent' (instead of 'tangend') ?
    (0012939)
    Jee-Bee   
    2019-03-21 06:18   
    @Kunda1 you right i have updated the Tag.
    (0016737)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5902.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3780 [Sketcher] Feature feature have not tried 2019-01-18 08:23 2021-02-06 06:48
    Reporter: freecad-heini-1 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Feature request sketcher - overload of the horizontal/vertical distance constraints between curves
    Description: https://forum.freecadweb.org/viewtopic.php?p=280421#p280421
    https://forum.freecadweb.org/viewtopic.php?p=280680#p280680
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016699)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5864.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3576 [Sketcher] Feature minor always 2018-08-31 23:36 2021-02-06 06:48
    Reporter: ceremcem Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Orthogonally restrict dragging of geometry in Sketcher (invoked by pressing ctrl or shift or ctrl+shift)
    Description: It would be very helpful to have a mode to restrict dragging of lines, vertices or possibly other geometry to only one axis (vertical or horizontal) while creating a sketch.

    My first reflex was pressing Ctrl or Shift or Ctrl+Shift keys while dragging a rectangle edge, just like is done in Gimp.

    Here is the forum link we discussed the issue: https://forum.freecadweb.org/viewtopic.php?f=3&t=30501
    Tags: shortcuts
    Steps To Reproduce: (Can be seen in the forum thread)
    Additional Information:
    Attached Files:
    Notes
    (0011677)
    normandc   
    2018-09-01 15:36   
    Reworded summary description to better convey meaning.
    (0016639)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5804.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3489 [Sketcher] Feature feature N/A 2018-05-21 12:52 2021-02-06 06:48
    Reporter: Rafa Mahiques Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: acknowledged Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Toggle visibility of all construction geometry
    Description: First of all, congratulations for all the new features that have been added to the latest version. It has great capabilities now and makes the projects smoother.
    I can think of many scenarios where this feature would be useful, but there is a specific one where I really miss it.
    When 2 lines of different nature (normal, construction, external) overlap and you want to select the overlapped one to apply any constraint or function (fillet, scale, etc.) you have to find the instance in the "elements" list and select it there.
    However, it would be useful that the overlapped geometry can be selected without having to identify it in that list. Let's say with a combination of a keystroke and the mouse wheel.
    Tags:
    Steps To Reproduce:
    Additional Information: OS: Windows 7
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.16.6712 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-16
    Hash: da2d364457257a7a8c6fb2137cea12c45becd71a
    Python version: 2.7.8
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 6.8.0.oce-0.17
    Attached Files:
    Notes
    (0011279)
    Kunda1   
    2018-05-26 21:56   
    @Rafa Mahiques please open a forum thread to discuss with community before opening tickets as per the enormous yellow banner at the top of this page.
    (0011293)
    Kunda1   
    2018-05-29 18:48   
    Rafa Mahiques, Please respond.
    (0011410)
    normandc   
    2018-06-11 20:12   
    Moved to Sketcher as description seems to indicates this is specifically about it.
    (0016627)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5792.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3374 [Sketcher] Feature feature have not tried 2018-03-14 19:00 2021-02-06 06:48
    Reporter: paullee Platform: All  
    Assigned To: OS: All  
    Priority: normal OS Version: All  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Sketch + Gui.SelectionEx() - - - Identify Geometry Index Outside Edit Mode
    Description: Discussion Thread in Forum ... (seem more than Sketcher, 'Selection' function?)
    "Sketch - Identify Geometry Index (inside and outside Edit Mode)"

    Problem is:-
    Gui.SelectionEx()[0].SubElementNames would provide different Edges 'name' Inside and Outside Sketch Edit mode ...See screencaptures
    1. Say a rectangle inside sketch, Edges index report are, Anti-Clockwise, 1-2-3-4 [EDIT] ('1' being the edge at the 'bottom')
    2.     
    3. Edge 2 is construction
    4.     
    5. Exiting Edit mode, same code seem report the Wire edge number created, INSTEAD of the Geometry inside edit mode
    6.     
    7. So, only 3 edges form a wire Outside edit mode
    8.     
    9. Edges nos. BECOME (report here as it is in same direction) 1-(none)-3-2 [EDIT] 3-none-1-2 (same edge by edge)
    10.     
    11. Or ClockWire as 1-2-3 [EDIT] Top Edge is '1' now
    12.     
    13. Using the latter 'index' in sketch.geometry[index] would report wrong edge (following Geometry Index) information
    So, Solution I haven't found:-
    • Outside Edit Mode, how can I without enter edit mode, a script to identify the selected edge's (the wire shape I guess) internal Edge geometry Index?

    Feature Request
    e.g.
     Gui.Selection.getSelectionEx()[0].SubElement_INTERNAL_Names  
    to return the same name or index as in sketch.geometry[i]

    Thanks!










    Tags:
    Steps To Reproduce:
    Additional Information: OS: Linux
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.13375 (Git) AppImage
    Build type: None
    Branch: master
    Hash: 2bfea410fce1434fec0f853b032549aa2cd3c47e
    Python version: 2.7.6
    Qt version: 4.8.6
    Coin version: 4.0.0a
    OCC version: 7.1.0
    Locale: English/HongKong (en_HK)
    Attached Files: Test_ Sketch_ Identify Geometry Index.fcstd (3,408 bytes) 2018-03-14 19:00
    https://tracker.freecad.org/file_download.php?file_id=1857&type=bug
    Notes
    (0011363)
    Kunda1   
    2018-06-07 18:58   
    @realthunder has implemented this in his fork: https://forum.freecadweb.org/viewtopic.php?f=22&t=27215&start=10#p222807
    (0016602)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5767.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3203 [Sketcher] Feature feature have not tried 2017-10-01 00:48 2021-02-06 06:48
    Reporter: SparkyCola Platform:  
    Assigned To: OS:  
    Priority: low OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: More convenient arc-drawing in polyline mode
    Description: 1. Usage of mouse-gestures (similar to those in Solid Works, Solid Edge, AutoCAD and more) and
    2. Multiple key bindings (a for arc and l for line which seems to be a CAD convention).

    The mouse-gestures would also allow to determine the perpendicularity/tangency of the arc to the last, and the next line/arc-segment.

    The feature has been discussed in the forum.
    Tags: arc, input, keyboard, mouse-gestures, Poly-line
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016565)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5730.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3107 [Sketcher] Feature feature have not tried 2017-06-26 11:18 2021-02-06 06:48
    Reporter: graffy Platform: Linux  
    Assigned To: OS: Mint  
    Priority: normal OS Version: 18.1  
    Status: new Product Version: 0.16  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Customize Sketcher units
    Description: While it is straightforward to select between different units systems in Sketcher, there is no way to control which units are employed.

    For example, if "US Customary" units are selected, as the magnitudes of the dimensions increase / decrease, inches become feet, which become yards, etc. In some workflows, however, there may only be one or a few of the conversions that are desirable - for example it may be that we only want to convert between feet and miles, or want to display in feet only.

    Recommended change:

    When a system of units is selected under File->Preferences-Units, populate a series of checkboxes, each representing one of the units within that system.

    The user can then seleect / deseselect which units are used in the sketch.

    Sketcher, then, retains those choices and converts only between the user-selected units.
    Tags: #post-to-forum, units
    Steps To Reproduce:
    Additional Information: OS: Linux Mint 18.1 Serena
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.16.6707 (Git)
    Build type: None
    Branch: releases/FreeCAD-0-16
    Hash: 5465bc47c95db45e0be85dc0e2872419efadce0f
    Python version: 2.7.6
    Qt version: 4.8.6
    Coin version: 4.0.0a
    OCC version: 6.8.0.oce-0.17
    Attached Files:
    Notes
    (0009534)
    Kunda1   
    2017-06-26 12:31   
    @graffy thanks for the reports. I can't test them ATM but please be aware of how we ask folks to report bugs for the FC project: https://forum.freecadweb.org/viewtopic.php?f=3&t=5236
    Can you post these tickets to the forum (make sure to include your full version info (per the guidelines). Thanks
    (0016550)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5715.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3086 [Sketcher] Feature feature N/A 2017-06-16 12:15 2021-02-06 06:48
    Reporter: trampas Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: CTRL key during line operation increase the snap active area such that it is easy to match points
    Description: It would be nice to have the CTRL key during line operation increase the snap active area such that it is easy to match points.
    Tags: shortcuts, snap
    Steps To Reproduce:
    Additional Information: Forum thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=23220
    Split from 0002653
    Attached Files:
    Notes
    (0016547)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5712.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2774 [Sketcher] Feature minor always 2016-11-16 11:16 2021-02-06 06:48
    Reporter: Joachimthome Platform: Lenovo x220  
    Assigned To: OS: Linux  
    Priority: normal OS Version: Ubuntu 14.04.5  
    Status: new Product Version: 0.16  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Can not select points in sketcher properly when changing viewangle
    Description: When i try to edit a sketch and change to "bottom" view (default shortcut "5") i can not select the dots in the sketch properly anymore.
    The same thing happens in the other two planes also.
    switching back to "top" view makes it possible again.
    Even selecting via drag selection leads to buggy behaviour where i can not select the (0,0,0)point properly.
    Its not a major issue but inconvenient.
    Tags:
    Steps To Reproduce: start freecad 0.16
    open a new freecad project
    got to part design workbench
    click create new sketch
    choose xy plane
    use the line tool to make a line
    press 5 to change to bottom view
    try to select endpoints of line
    > the line gets selected instead
    Additional Information: OS: Ubuntu 14.04.5 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.16.6703 (Git)
    Build type: None
    Branch: releases/FreeCAD-0-16
    Hash: 2ce5c8d2e3020d05005ed71f710e09e9aa561f40
    Python version: 2.7.6
    Qt version: 4.8.6
    Coin version: 4.0.0a
    OCC version: 6.8.0.oce-0.17
    Attached Files:
    Notes
    (0007641)
    Kunda1   
    2017-01-11 19:14   
    Can't reproduce on 0.16 (d/led via AUR)
    OS: "Manjaro Linux"
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.16.Unknown
    Build type: Release
    Python version: 2.7.12
    Qt version: 4.8.7
    Coin version: 3.1.3
    OCC version: 6.9.1
    (0007642)
    Kunda1   
    2017-01-11 19:17   
    Forum thread: http://forum.freecadweb.org/viewtopic.php?f=8&t=19798
    (0007647)
    Kunda1   
    2017-01-11 19:58   
    @sgrogan writes in http://forum.freecadweb.org/viewtopic.php?f=8&t=19798&p=152873#p152873
    > I can reproduce it, but I think its the intended behavior. In the Top View the points are "over" the line so they can be selected. In the Bottom view the points are "under" the line so the line is selected. I don't have any problems with box selection it works as expected.
    > Switch to the front view and zoom way in on an endpoint to see.
    (0007755)
    nemesis   
    2017-01-14 08:43   
    confirmed but is it , a bug, or made on purpose regarding the orientation of the sketch...and with 0.17 and the "map reversed" option, I don't think it's still valid
    (0009156)
    Kunda1   
    2017-05-26 20:25   
    Changing ticket to Feature Request per @DeepSOIC in https://forum.freecadweb.org/viewtopic.php?f=8&t=19798&start=10#p154435
    (0011947)
    abdullah   
    2018-10-06 15:10   
    With the inclusion of the "reverse mapping" and the clip planes (section view), it is more and more difficult to find actual scenarios when one shall rotate the sketcher view in order to operate.

    This was certainly difficult before.

    In the next development cycle we should look into whether there is a need or not.
    (0016508)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5673.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2492 [Sketcher] Feature feature have not tried 2016-04-03 05:05 2021-02-06 06:48
    Reporter: mimosa Platform: PC  
    Assigned To: OS: Windows  
    Priority: normal OS Version: 10  
    Status: new Product Version: 0.15  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Multiple entities overlayed
    Description: When more than one entity are overlayed (two lines, a line and the reference horizontal, 2 points, a point and the end point of a line, etc) the user should be able to chose which entity to interact with:

    1) User would hover the mouse over (near) the area of interest,
    2) If in that zone surrounding the mouse there exist more than one entity, after 2 second, a little button would appear (say, with 3 dots as a text)
    3) when the button is clicked, a list would popup listing all the selectable entities in the vicinity
    4) the user can select an entity (or close the popup without selecting any) and the program would continue (either the user was in the middle of an operation, ir want to start an operation with the selected entity).
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0006946)
    normandc   
    2016-04-05 00:34   
    (Last edited: 2016-04-05 00:35)
    There's already a mechanism to select overlapping sketch entities in v0.16 due to come out shortly.

    (0010724)
    normandc   
    2018-01-06 19:16   
    @abdullah @wmayer

    Should this be closed as fixed? In v0.17's Sketcher, we can now define the display order of normal/construction/reference geometry.

    But this would not solve the issue where two lines of the same type are overlapping.
    (0010737)
    abdullah   
    2018-01-11 10:13   
    @normandc

    I think it is an open point in the sketcher.

    All you say is absolutely right, v.17 (probably also 0.16) has the elements widget which allows any selection. In this sense it is not a bug (but this ticket was opened as a feature).

    The new rendering order in v.17 will help as you comment... except in that case of two overlapping lines of the same type and one is fully overlapped by the other.

    So let's say that the current implementation can be improved.

    Eventually, the whole inner parts of sketcher visualization (interface with coin3d) will need to be rewritten. It may be that in that effort this feature is "rescued".
    (0016483)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5648.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1343 [Sketcher] Feature minor always 2014-01-03 09:16 2021-02-06 06:48
    Reporter: ildawson Platform:  
    Assigned To: OS: Windows  
    Priority: low OS Version: Eight  
    Status: new Product Version: 0.13  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Request for additional (dynamic) detail in error messages
    Description: When attempting to place a constraint, if the incorrect parts of the sketch are selected an error message will be displayed (for example when selecting the InternalAngle constraint the message "Wrong Selection: Select exactly one or two lines from the sketch." is displayed). It would be helpful is the message could detail what was selected (for example "One line and two points have been selected.") This would make it easier to correct/understand your mistake.

    In general when an error message indicates that a user has not performed an action correctly, and details what the user is required to do, the message should also detail what inputs the user entered to better train/educate the user.


    Tags: exception, Solver
    Steps To Reproduce: 1. Enter sketch mode
    2. draw a line.
    3. Select the line
    5. Select InternalAngle constraint on toolbar. (works on other constrains as well)
    3. Observe error message.
    Additional Information: This feature will be more useful to beginner users as they learn how to apply constraints.

    Version Details:
    OS: Windows
    Platform: 32-bit
    Version: 0.13.1828
    Python version: 2.6.2
    Qt version: 4.5.2
    Coin version: 3.1.0
    SoQt version: 1.4.1
    OCC version: 6.3.0
    Attached Files:
    Notes
    (0010021)
    Kunda1   
    2017-08-28 14:33   
    @Abdullah did any of your Error throwing logs address this ticket ?
    (0011207)
    abdullah   
    2018-04-27 10:23   
    Not really. I think the reporter is asking for improving the strings of the error messages that already exist. I am not sure if this is reasonable for all cases, as there may be many combinations.

    I am moving this to Sketcher, as it is not really GCS related...
    (0016411)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5576.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1271 [Sketcher] Feature feature always 2013-10-12 15:28 2021-02-06 06:48
    Reporter: bejant Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version: 0.13  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Allow User to Toggle Automatic Grid Sizeing in Sketcher On and Off
    Description: Shamelessly copied from the forum topic referenced below:

    "I wish there was a feature where you set it so that the grid covers the entireity of the sketcher view, instead of just a bit near the most recent sketch. Basically, when I try and draw something right now the grid goes away except near the object, so if I draw a 1mm square box on a 1mm grid, and then want to draw another box next to it, the grid goes away entirely. What I am having to do now is draw a huge box around everything, just to keep my grid, then draw my sketch, then erase the huge box."

    https://sourceforge.net/apps/phpbb/free-cad/viewtopic.php?f=19&t=4659&start=0&sid=ccf9198913c5b711c7f8c59ce330d136
    or

    https://forum.freecadweb.org/viewtopic.php?f=19&t=4659&start=0&sid=ccf9198913c5b711c7f8c59ce330d136
    Tags: grid
    Steps To Reproduce:
    Additional Information: Some users may prefer the automatic sizing feature, and if automatic sizing was done to reduce CPU processing time, maybe a toggle box in the Edit Controls area (directly below the Sketcher Solver area)? A screen grab of this area is attached.
    Attached Files: 20131012a.png (32,386 bytes) 2013-11-04 13:30
    https://tracker.freecad.org/file_download.php?file_id=588&type=bug
    Notes
    (0003888)
    raulshc   
    2013-11-16 18:19   
    (Last edited: 2013-11-16 18:19)
    This issue is related with 0001049 : Sketcher preferences in preferences editor.

    (0005928)
    wmayer   
    2015-03-23 09:42   
    See also http://forum.freecadweb.org/viewtopic.php?f=3&t=10203&start=10#p82464
    (0007501)
    wmayer   
    2016-12-01 19:41   
    See also http://forum.freecadweb.org/viewtopic.php?f=13&t=18771
    Possible solution: depending on zoom level and screen size compute the number of grids. If zoomed out too much use an upper limit based on resolution.
    (0008619)
    Kunda1   
    2017-03-13 13:51   
    Mentioned again in https://forum.freecadweb.org/viewtopic.php?f=3&t=21286&p=165096#p165096
    (0008679)
    Kunda1   
    2017-03-21 12:50   
    Resolved dupe of this ticket (0002734)
    (0011945)
    abdullah   
    2018-10-06 14:52   
    Solving a different ticket, I have implemented a dynamic grid size enlarging.

    It is not exactly what the reporter requests, but maybe it (partly)fulfils the needs.

    Basically, the grid is expanded to surpase the biggest object drawn so far (to the next 10 power, so 5 mm => 10 mm, 50mm => 100mm).

    Additionally the grid is now always symetric on the two planes. Before it gave odd representations.

    This implementation is now in master and in the PPA.
    (0013078)
    kevlevrone   
    2019-05-03 12:47   
    Open the file.
    Create a new sketch, XY plane.
    Toggle construction mode On.
    Make sure Auto Remove Redundant is Off
    Carbon Copy Sketch005 - constraints 21,24 are showed as redundant.
    Undo https://goo.gl/KyvnZF
    Toggle construction mode Off.
    Carbon Copy Sketch005 - no redundant constraints.
    (0016408)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5573.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    847 [Sketcher] Feature feature always 2012-09-27 06:13 2021-02-06 06:48
    Reporter: pperisin Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: acknowledged Product Version: 0.12  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: [Sketcher] Dragging + snap to grid
    Description: Hi,

    Snap to grid works nicely in Sketcher, but there is problem when dragging a line. IN this case snap to grid only works if a mouse location is next to grid. It would be nice if line "Snaps" if one of it's endpoints is also near grid.

    Regards,
    Petar
    Tags: #lowhangingfruit, #post-to-forum, snap
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0004162)
    mrlukeparry   
    2014-02-08 00:23   
    The algorithm is pretty simple and you're right just uses the mouse cursor in relation to the grid. This is similar problem to dragging nodes to other edges and automatically adding constrains. This probably would need discussing with logari

    A lot of improvements are needed to the grid in general such as being full screen.
    (0008865)
    Kunda1   
    2017-05-02 21:49   
    Unassigned
    (0009380)
    Kunda1   
    2017-06-15 12:14   
    @abdullah is this not implemented in sketcher 0.17 ?
    (0009385)
    abdullah   
    2017-06-15 12:41   
    @kunda1

    I have to check, as I never use this function...

    No, it is not. I just checked. Works nicely on creation, but on dragging it only enforces the grid if you are very close to one point. Just as the reporter describes. You may "low hanging fruit" this.
    (0012126)
    abdullah   
    2018-11-01 18:40   
    https://github.com/FreeCAD/FreeCAD/pull/1767
    (0012138)
    abdullah   
    2018-11-05 18:40   
    wwmayer commented 7 hours ago

    I don't think it's a matter of preference, it's a matter of usability.

    Setting such a huge tolerance doesn't make any sense because effectively it's not easily possible any more to move a point somewhere inside a grid cell. If you want to achieve it you must always go back to the task dialog and tmp. disable the option.

    And if you start to draw a new line you click somewhere but don't get any feedback that the first point is already accepted and when pressing twice an error is raised that adding the line failed because both points are equal. In order to see the preview line you must move at least half a size of the grid cell along X or Y axis.

    I think this odd behaviour will be confusing to many users.

    wwmayer commented 7 hours ago

    Btw, I looked at the feature request 847 and changing the snapping tolerance doesn't do what the OP wanted. If you have a line where none of its endpoint is snapped it still won't snap when starting to drag it.


    abdullah:

    Ok, it is a misunderstanding of what gridsnap should do. As I understood it, one point of having the gridsnap on may be precisely not to be able to move points inside the grid. Under such assumption, using 0.5 precisely prevents points outside the grid. When creating a new line, with an appropriate grid size, as soon as the line passes 50% of the grid size, you get a line segment of exactly one grid size measure. Of course using inappropriate values of the grid size leads to unusable behaviour. Because endpoints of lines cannot be outside the grid, when dragging points snap to the grid. Of course, if one creates a line without snap on, outside the grid, then sets snap on and drags, it won't align.

    Of course, if weak snap, as currently implemented in FC is how it should work, this PR makes no sense.

    Regarding the ticket:
    Dragging an endpoint of the line works perfectly with weak snap.

    I am not sure I will implement dragging the edge and trying to snap the endpoints.
    (0016392)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5557.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4358 [Part] Feature feature always 2020-06-04 09:22 2021-02-06 06:46
    Reporter: sangue Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: feedback Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 10
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.4 (GitTag)
    Build type: Release
    Branch: releases/FreeCAD-0-18
    Hash: 980bf9060e28555fecd9e3462f68ca74007b70f8
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: German/Switzerland (de_CH)
    Summary: Combo view > Data should consistently retain state of property foldouts
    Description: When changing values in ComboView > Data > Placement > Position directly and switching between parts in the tree, the foldouts (Placement, Axis and Position) collapse most of the time.
    Changing a specific value in multiple parts yields in repeatedly reopening placement>position to edit let's say, x.
    Tags: #pending-forum
    Steps To Reproduce: 1. Part module
    2. Make 2 Cubes
    3. in Tree, click on Cube1
    4. in Data, open Placement foldout, open Position foldout to see x,y,z
    5. in Tree, click on Cube2
    6. in Data, (re-)open Placement, (re-)open Position (because they just have been closed)
    7. now Edit the y-value of a cube under Placement>Position>y and hit enter
    8. in Tree, click on Cube1
    9. the foldouts remain open now.
    > between steps 5 and 6, the foldouts close
    > between steps 7 and 8 the foldouts don't close
    Additional Information: Additionally, after the bug has occurred:
    - if the same color is re-selected on the part, the part will still not show the right color.
    - if another color is selected for the part, the part will show the right color.
    Attached Files:
    Notes
    (0014461)
    openBrain   
    2020-06-04 18:11   
    @sangue : please address your issue following our reporting guidelines by opening first a topic in our forum. Thx
    We generally accept tickets when issue has been vet by the community, and especially confirmed to still exist in current development version (which you can test by yourself).
    (0014464)
    Kunda1   
    2020-06-05 10:35   
    Forum thread opened by OP: https://forum.freecadweb.org/viewtopic.php?f=34&t=47268
    (0016903)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6070.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4262 [Part] Bug crash always 2020-02-07 13:14 2021-02-06 06:46
    Reporter: openBrain Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: macOS High Sierra (10.13)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.19405 (Git)
    Build type: Release
    Branch: master
    Hash: d2b943e8b7d8fe2673a4e20671b6cb0f8180fdbd
    Python version: 3.8.1
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: C/Default (C)
    Summary: Thickness function crashes FC when applied on a pipe that has equal section radius & bending radius
    Description: If creating a pipe with equal section radius & bending radius, then applying an inward thickness function to it crashes FC.
    This doesn't happen if both radii are different (even if bending radius is lesser than section radius, which create a degenerated shape).
    This doesn't happen if the thickness is done outward.
    This is reproducible both in Part & PartDesign with their respective commands.
    Forum thread : https://forum.freecadweb.org/viewtopic.php?f=3&t=42986
    Tags:
    Steps To Reproduce: Please look at forum thread
    Additional Information:
    Attached Files:
    Notes
    (0016862)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6028.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4159 [Part] Feature feature always 2019-10-09 21:31 2021-02-06 06:46
    Reporter: vocx Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Show spiral length in the property editor
    Description: Part Helix and Part Spiral (which are derived from Helix) objects don't show a length property in the property editor.

    The length is included in the Shape, so it just has to be displayed as a read-only value.
    
    obj.Shape.Length
    

    See this thread Length of a spiral
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016829)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5995.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4075 [Part] Feature minor N/A 2019-07-30 19:03 2021-02-06 06:46
    Reporter: openBrain Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: CompoundFilter items selection helper
    Description: Part CompoundFilter is a nice tool, but especially when used in "specific items" mode, it is really odd to setup. Particularly because you don't know how many fragments are in the compound, and which index corresponds to which fragment.
    ---
    See proposal mockup on the forum thread
    Tags:
    Steps To Reproduce: N/A
    Additional Information: Same helper could be used to implement a selective Compound Explode
    Attached Files:
    Notes
    (0016806)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5972.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4034 [Part] Feature minor N/A 2019-06-24 22:25 2021-02-06 06:46
    Reporter: bejant Platform: 32 bit  
    Assigned To: OS: Ubuntu  
    Priority: low OS Version: 18.04.2 LTS  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Easier Way to Toggle BOPCheck On / Off
    Description: Provide an easier method to enable / disable BOPCheck instead of always having to go through Tools > Edit Parameters. The initial thought was to provide a button or tickbox in the Check Geometry widget but (other than a progress indicator) the Check Geometry widget doesn't appear until after Check Geometry has arrived at the results. Even though a new user would have to first run Check Geometry before seeing an option for BOPCheck enable / disable, the user would at least be alerted that the option exists, and simultaneously be presented with a simpler way to change the setting.

    TheMarkster posted in the forum that he had written a tiny macro to quickly and easily enable/disable RunBOPCheck, which gave rise to this feature request.

    Forum discussion initially started here, and this post includes the macro:
    https://forum.freecadweb.org/viewtopic.php?f=3&t=37156&start=10#p316228

    I later started a discussion for this feature request to avoid further hijacking the original thread:
    https://forum.freecadweb.org/viewtopic.php?f=8&t=37240
    Tags: UI
    Steps To Reproduce:
    Additional Information: OS: Ubuntu 18.04.2 LTS
    Word size of OS: 32-bit
    Word size of FreeCAD: 32-bit
    Version: 0.18.1.
    Build type: Release
    Python version: 3.6.7
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    Attached Files:
    Notes
    (0013306)
    TheMarkster   
    2019-06-25 01:59   
    https://github.com/FreeCAD/FreeCAD/pull/2291
    (0013695)
    Kunda1   
    2019-09-30 00:07   
    @TheMarkster FYI, please use the mantisBT syntax to remotely close a MantisBT ticket from a Github PR. And do you mind stating here how the PR addresses this ticket? Thanks. (I'll associate the commit with this ticket manually)
    (0013696)
    Kunda1   
    2019-09-30 00:10   
    @TheMarkster, Sorry, let me correct myself, you did try to use the syntax but didn't execute it correctly. You can omit the superflous 0's and just use the number after the pound sign in the future... so either
    Fixed #(issue number) <-closes
    or
    issue #(issue number) <-references
    (0016787)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5953.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3858 [Part] Feature feature always 2019-02-24 13:57 2021-02-06 06:46
    Reporter: uwestoehr Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Additive primitives of the Part WB should use existing task dialogs of PartDesign WB
    Description: When you insert an additive primitive like a box in the PartDesing WB you get a nice task dialog where you can specify the dimensions etc.

    When adding a primitive in the part WB, there is no task dialog at all. Since there exists task dialogs for primitives in PartDesign the part WB could use them somehow.

    This would increase the usability because a visual feedback during the creation of a primitive is very helpful and currently you have to set the dimensions etc. in the Data tab of the Combo view without any visual preview.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0012752)
    wmayer   
    2019-02-24 17:31   

    When adding a primitive in the part WB, there is no task dialog at all.

    Uwe Stoehr
    This is not correct. In the one toolbar of the Part wb the first five buttons are supposed to quickly create some standard primitives. The sixth button opens a task panel where some further primitives are listed and there you can define the parameters.

    Since there exists task dialogs for primitives in PartDesign the part WB could use them somehow.
    Technically this is impossible because the PartDesign library links the Part library. So, it's not possible to use PartDesign stuff in Part as this would cause a cyclic dependency and thus to unresolvable linker errors.
    (0012756)
    uwestoehr   
    2019-02-24 18:11   
    > The sixth button opens a task panel where some further primitives are listed and there you can define the parameters.

    Hmm, but this dialog offers for example no rotation and also no visual preview. The PartDesing dialog offers both. Also issue 0003857 applies for all primitives added this way.

    > Technically this is impossible

    OK. So let's keep this as feature request for an improved task dialog for the Part WB.
    (0015120)
    Kunda1   
    2020-12-08 20:38   
    @uwestoehr was this issue addressed recently ?
    (0015122)
    uwestoehr   
    2020-12-09 12:22   
    Only partly: existing primitives use now the PartDesign dialogs, but when creating a new primitive like a box, you don't get any dialog.
    I failed to get this working. So the bug must be kept open.
    (0016721)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5886.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3407 [Part] Feature feature N/A 2018-03-28 01:49 2021-02-06 06:46
    Reporter: chrisb Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Provide Attachment mode perpendicular to an existing plane
    Description: Attachment should support attachin a plane perpendicular to another plane.
    See forum discussion
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016614)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5779.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3196 [Part] Feature minor have not tried 2017-09-21 22:33 2021-02-06 06:46
    Reporter: wmayer Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Extend attachment engine
    Description: When a cylinder or cone is selected allow to use the axis of curvature for a datum line.
    When two planes are selected allow to use the intersection for a datum line.
    When three planes are selected allow to use the intersection point for a datum point
    Tags:
    Steps To Reproduce: https://forum.freecadweb.org/viewtopic.php?f=13&t=23174
    Additional Information:
    Attached Files:
    Notes
    (0016563)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5728.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2905 [Part] Feature feature always 2017-02-17 14:17 2021-02-06 06:46
    Reporter: easyw-fc Platform:  
    Assigned To: OS:  
    Priority: high OS Version:  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: cannot make a compound or a union or even a simple copy of the App::Part structure
    Description: for App::Part models in its structure I miss the option to:
    1) make a compound
    2) make a union
    3) make a simple copy

    Tags: 3D printing, App::Part, Part Design, simple copy, STEP, STL
    Steps To Reproduce: 1) in FC 0.17 create a new doc
    2) go to Part Design Next
    3) Make a Part
    4) goto Part
    5) create a Cube and a Cone
    6) move Cube and Cone into Part container
    7) select Part
    8) try to make compound, make union or even make a single copy
    everything is disabled
    Additional Information: forum thread
    https://forum.freecadweb.org/viewtopic.php?f=22&t=20698&p=160405#p160384
    Attached Files:
    Notes
    (0008336)
    ickby   
    2017-02-17 14:31   
    An App::Part container is a universal object which can hold any kind of DocumentObject like meshs or Paths or even pictures. I can't work with Part tools (Booleans, Compound etc.) which work with Part::Features only and hence result in a undefined behavior. The App::Part object should not work with those tools. Current behavior is correct.
    (0008337)
    ickby   
    2017-02-17 14:34   
    To point 3: make a simple copy. I agree that the simple copy tool should handle App::Part objects, but this must involve creating a simple copy of all child DocumentObjects, as a DocumentObject is allowed to be only in a single local coordinate system (GeoFeatureGrouip, Which App::Part is).
    (0008707)
    easyw-fc   
    2017-03-25 16:02   
    as for this forum post
    https://forum.freecadweb.org/viewtopic.php?f=22&t=21510
    the option to make a simple copy of App::Part objects is becoming requested ...
    (0009506)
    Kunda1   
    2017-06-24 11:18   
    Is this 'General' or should I move it to 'Part' category?
    (0009507)
    Kunda1   
    2017-06-24 11:18   
    Changed from bug to feature
    (0010001)
    Kunda1   
    2017-08-23 12:19   
    @DeepSOIC do you mind weighing in?
    (0010115)
    Kunda1   
    2017-09-13 12:29   
    @easyw-fc do you mind updating this ticket illustrating it's status? Thanks!
    (0010126)
    easyw-fc   
    2017-09-14 20:52   
    (Last edited: 2017-09-14 20:57)
    @Kunda1
    an other user case where a single copy of App::Part and Body would be useful
    https://forum.freecadweb.org/viewtopic.php?f=3&t=24405&p=191408#p191408

    (0010334)
    easyw-fc   
    2017-10-20 21:44   
    @Kunda1
    an other user case where this feature is required
    https://forum.freecadweb.org/viewtopic.php?f=28&t=21541#p195863
    I suspect that the more people will use FC0.17 to elaborate STEP files, the more this issue will raise its relevance.
    Maurice
    (0010335)
    Kunda1   
    2017-10-20 23:10   
    bumping to higher priority
    (0010960)
    easyw-fc   
    2018-02-15 08:05   
    @Kunda1
    an other user case where this feature is required
    https://forum.freecadweb.org/viewtopic.php?f=3&t=26914
    (0010961)
    Kunda1   
    2018-02-15 12:10   
    @wmayer may I make this an 0.18 target ?
    (0010962)
    normandc   
    2018-02-17 19:10   
    (Last edited: 2018-02-17 19:13)
    Just FYI, Draft Clone works on Part containers, it may be suitable as a workaround. EDIT: while it works on a simple Part container, it will not work on a Part container that contains other containers.

    In Steps to reproduce, step 2 is no longer required. The Part container is now global and available in all workbenches within the Structure toolbar.

    (0011181)
    easyw-fc   
    2018-04-23 13:16   
    and another user case
    https://forum.freecadweb.org/viewtopic.php?f=18&t=27537&p=229559#p229535

    This is a function also useful for STL export and also for FEM meshing.
    (0016516)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5681.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2748 [Part] Feature feature N/A 2016-10-25 16:05 2021-02-06 06:46
    Reporter: nokian Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: feedback Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: PART_WB: Add "Measure Radial" to Std Measure Menu
    Description: Discussed here:
    http://forum.freecadweb.org/viewtopic.php?f=8&t=18102
    Tags: Part, UI
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0009831)
    nokian   
    2017-07-26 21:18   
    @Devs: What do you think about increasing the priority of this issue?
    (0009834)
    Kunda1   
    2017-07-27 01:05   
    @nokian better to ask in the forum thread than here.
    (0010290)
    Kunda1   
    2017-10-11 03:50   
    A workaround could be to use @triplus new Command Panel Workbench: https://forum.freecadweb.org/viewtopic.php?f=34&t=23207
    (0012142)
    Kunda1   
    2018-11-07 00:48   
    @wmayer verdict on this ticket ?
    (0016505)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5670.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2700 [Part] Bug major always 2016-09-16 19:06 2021-02-06 06:46
    Reporter: DeepSOIC Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Part Offset2D fill offset problems
    Description: Filling offset does not work, when a 2D offset is applied to another 2D offset.
    Tags:
    Steps To Reproduce: 1. Sketch. Circle.
    2. Part 2D Offset the circle. Leave values at defaults.
    3. 2D Offset the offset. Tick Fill checkbox. The offset is filled incorrectly (face covers the hole, instead of the offset space).
    Additional Information: OS: Windows 10
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.8361 (Git)
    Build type: Release
    Branch: DeepSOIC10
    Hash: 4ac7673e543274bcae856872033a114c7b60481b
    Python version: 2.7.8
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.0.0

    Seems to be related to extrusion direction weirdness. Offsetting a Draft Clone of offset works as expected.

    forum thread:
    "Bug in Part Offset 2D filling"
    http://forum.freecadweb.org/viewtopic.php?f=3&t=17445
    Attached Files:
    Notes
    (0010662)
    wmayer   
    2018-01-02 13:42   
    Postpone to 0.18 is it's not realistic to get this fixed soon.
    (0016499)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5664.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2677 [Part] Feature feature always 2016-08-19 06:24 2021-02-06 06:46
    Reporter: ickby Platform: All  
    Assigned To: OS: All  
    Priority: normal OS Version: All  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Extend TopoShape API with topology traversing functionality
    Description: Currently TopoShape API allows access to all subshapes, e.g. Faces, Edges etc. It does however not allow to access those subshapes in any topological order or relation. Example of those could be:

    - Get all faces adjecent to certain edge/vertex/face
    - Get face connected to a face by this edge
    - Get all Edges connected to a certain Vertices
    - Iterate Edges in Wire in correct order and orientation
    - many more

     A clever API must be designed to allow a flexible querying of topological relation without providing an overhelming amount of functions.

    This functionality would make scripting in FreeCAD much easier, as currently much repetitive work needs to be done to find topological related subshapes in python.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0010912)
    normandc   
    2018-02-02 05:23   
    Is it realistic to set target for 0.17 on this issue?
    (0012085)
    ezzieyguywuf   
    2018-10-22 20:42   
    I agree that this sort of topological relationship information is needed. I question whether or not it belongs in FreeCAD though -> should this type of functionality come directly from OpenCascade? I would think that the CAD kernel itself, being that it manages the Topology, would have this information more readily available.

    Any solution we come up with will likely be mostly a hack, as OpenCascade does not make very apparent (or easily available) the mechanism by which it stores and modifies underlying topologies.

    As an example, you can see here in my opencascade wrapper library that I've added a method for checking whether a particular TopoDS_Face contains a particular TopoDS_Edge. What is being suggested is essentially to continue adding these sorts of "helper methods" to FreeCAD's TopoShape class.

    Personally, I believe these types of "helper methods" that help with using OpenCascade should be contained in a separate library altogether - that is the intent of the OccWrapper library I'm writing.

    I hope posting this on this bug is appropriate: I've been holding off on posting much in the forums regarding this OccWrapper library because it is largely incomplete, and mostly a labor of love that's made (attempting to) resolve the topological naming problem less painful. I thought this comment would be well placed here, though, given the topic of the bug report.
    (0016496)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5661.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2595 [Part] Feature minor have not tried 2016-06-18 18:20 2021-02-06 06:46
    Reporter: quick61 Platform: All  
    Assigned To: OS: All  
    Priority: normal OS Version: All  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Part ShapeBuilder Enhancements
    Description: Add the ability for box select, greedy select - remove the need for holding the [Ctrl] key while selecting vertices, edges, and faces, (Part > Fillet already does this), and allow selection from the hierarchy tree.
    Tags:
    Steps To Reproduce:
    Additional Information: Discussion on the subject came up in this thread on the forum - http://forum.freecadweb.org/viewtopic.php?f=3&t=16212&start=10#p128433
    Attached Files:
    Notes
    (0009158)
    Kunda1   
    2017-05-26 20:36   
    Discussion thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=22664
    (0016494)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5659.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2509 [Part] Bug minor always 2016-04-15 16:54 2021-02-06 06:46
    Reporter: gdolle Platform: Linux  
    Assigned To: OS: Archlinux  
    Priority: normal OS Version: x86-64  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Sweep using bezier curve bug
    Description: Create a pipe using bezier curve. Depending on geometric point placement, the sweep bugs.

    -------------------------------------
    OS: "Arch Linux"
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.16.Unknown
    Build type: Release
    Python version: 2.7.11
    Qt version: 4.8.7
    Coin version: 3.1.3
    OCC version: 6.9.1
    Tags: #pending, bezier curve, sweep
    Steps To Reproduce: Simple case:

    1) Create a bezier curve using 4 points aligned (2 vertex, 2 geometric).
    2) Create 2 disks placed to the curve extremities.
    3) Create a sweep with the two disks along the bezier curve.
    Additional Information: See the joint example in the FreeCAD file and a screenshot
    Attached Files: bug1.fcstd (184,262 bytes) 2017-01-18 01:10
    https://tracker.freecad.org/file_download.php?file_id=1441&type=bug
    screen.jpeg (152,020 bytes) 2017-01-18 01:11
    https://tracker.freecad.org/file_download.php?file_id=1442&type=bug
    Notes
    (0007858)
    Kunda1   
    2017-01-18 01:15   
    Forum thread: http://forum.freecadweb.org/viewtopic.php?f=10&t=19999
    I also edited the ticket by removing the tar and re-uploading the screenshot and .fcstd separately.
    (0008329)
    normandc   
    2017-02-17 03:56   
    See my tests in the forum topic: https://forum.freecadweb.org/viewtopic.php?f=10&t=19999&p=160351#p160351

    The gist of it is that forcing the BezCurve to be straight is probably what's causing the issue. I really can't see how producing such a "straight curve" would be desirable. If you want a straight path, why not create a line? When creating a Draft BezCurve with only two end points, the object that is automatically created is a Draft Line rather than a BezCurve.

    The same issue with the sweep applies to a B-spline with 4 poles constrained to be straight. But a B-spline with two poles produces a valid sweep.

    What needs to be decided: is the use of a straight BezCurve with more than 2 points an appropriate use here; only then can this be considered a bug. But that is for the developers with deep knowledge of such geometry to decide...
    (0008331)
    gdolle   
    2017-02-17 11:00   
    @normandc

    Yes, there's a point. The idea was to curve this line after the sweep (The idea is that the curvature is not determined and can change in my current usage).
    It was some times ago, but if I remember, it was not possible to convert a straight line to a BezCurve (at least if you already create the sweep on the straight line).

    Also if I remember what I was doing, there was some bugs with BezCurve boolean depending on the curvature, so I wanted to create a straight BezCurve, then curve it.
    (0008786)
    Kunda1   
    2017-04-28 01:57   
    @kkremitzki please create a Part project and move this ticket in to it. Thanks!
    (0009033)
    kkremitzki   
    2017-05-16 14:45   
    @Kunda1 moved
    (0012854)
    Kunda1   
    2019-03-06 11:29   
    @Chris_G care to take a look at this issue? It supposedly is related to 0002187
    (0013510)
    Kunda1   
    2019-09-01 19:17   

    the sweep path has some straight segments, that have a normal plane, but no unique normal vector ( which is needed for Frenet ).
    IMHO, this is an OCC bug. A nurbs or Bezier curve with poles aligned is perfectly valid.

    Chris_G
    per @Chris_G's response in the forum thread
    (0013511)
    Kunda1   
    2019-09-01 19:18   
    @abdullah can I put this on your radar to take a look at ?
    (0016486)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5651.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2508 [Part] Bug minor always 2016-04-15 12:37 2021-02-06 06:46
    Reporter: PaulC Platform: PC Intel Xeon E3 1220 V3 @3.1GHz  
    Assigned To: OS: Windows10 Pro 64bit  
    Priority: normal OS Version: 10.0.10586  
    Status: confirmed Product Version: 0.15  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Lofting edges get swapped over
    Description: I was trying to create a handle using the lofting command. I created the frames for the loft and every time I try and use the loft command either 1 or 2 edges get swapped over. See attached file. I get the same behaviour in the newly released Version 0.16.

    This has been discussed on the Forum. See:-

    http://forum.freecadweb.org/viewtopic.php?f=3&t=13981&p=111632&hilit=Problems+with+Loft+PaulC#p111632
    Tags:
    Steps To Reproduce: Just try lofting between the frames in the attached drawing. Fails every time, which is good in a way !
    Additional Information:
    Attached Files: Loft_6.FCStd (20,143 bytes) 2016-04-15 12:37
    https://tracker.freecad.org/file_download.php?file_id=1239&type=bug
    IMG_0041.JPG (24,420 bytes) 2017-06-03 15:51
    https://tracker.freecad.org/file_download.php?file_id=1628&type=bug
    loft_flipped_edges.FCStd (311,909 bytes) 2019-03-27 02:56
    https://tracker.freecad.org/file_download.php?file_id=2166&type=bug
    SketchEdgeOrder.jpg (77,859 bytes) 2019-03-27 12:54
    https://tracker.freecad.org/file_download.php?file_id=2170&type=bug
    Notes
    (0008027)
    Kunda1   
    2017-01-27 14:35   
    bumped thread
    (0008061)
    normandc   
    2017-01-28 18:23   
    Still an issue in master.

    OS: Ubuntu 14.04.5 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.9822 (Git)
    Build type: None
    Branch: master
    Hash: 0df4af4ba5e6edce825af6ecf6d024c704292633
    Python version: 2.7.6
    Qt version: 4.8.6
    Coin version: 4.0.0a
    OCC version: 6.8.0.oce-0.17
    (0009278)
    Kunda1   
    2017-06-03 15:51   
    Adding screenshot from forum thread
    (0009280)
    abdullah   
    2017-06-04 05:47   
    @kunda1 @abdullah

    Checking if I can trigger myself, so that I have an unread email in my account. I can not "unread" forum posts and now I am at two other issues simultaneously.

    https://forum.freecadweb.org/viewtopic.php?p=176804#p176804

    Ref ticket:issue 0002508

        Abdullah wrote:
        ping

    Is this a PDN blocker?
    (0009306)
    chrisb   
    2017-06-07 16:05   
    This isn't a bug, not even an issue. The documentation states
    This means that if one is doing a loft between two squares, the maximum twist possible is <45°.
    F2 is twisted 45° so the twist of the loft is expected.
    (0009424)
    normandc   
    2017-06-17 21:30   

    Is this a PDN blocker?

    abdullah
    It cannot be a PDN blocker since this bug was wrongly reported to PartDesign instead of Part. This is about the Part Loft tool, but admittedly it may affect the PDN additive/subtractive loft feature as well.

    This isn't a bug, not even an issue. The documentation states

    chrisb
    @all the link to the page that mentions it: https://www.freecadweb.org/wiki/Part_Loft_Technical_Details (@DeepSOIC wrote that page)

    Should this be indicated as an upstream OCC issue then?
    (0009460)
    abdullah   
    2017-06-19 21:53   
    @normandc

    It is misquoted that I asked whether it is a PDN blocker. I just pasted the text from an email where I was asked whether it is a PDN blocker.

    That clarified. It is as a PDN blocker as it is a Part blocker, i.e. the same issue happens in PDN.

    DeepSOIC did a great job explaining what is under the hood when creating a Loft.

    It is not uncommon to get lack of correspondence of the profiles (which honestly it is not the best explanation ever in a pop up). It is not uncommon to have a flipped profile path like above.

    I am not sure that profile is overtwisted (as per documentation). I would tend to think that if the one half of the arc was possible, the other half should be possible as well.

    What I understand from the documentation is that if the twist would me more than 45º, the selection of correspondance would change so as to minimize the twist.

    We best ask the master (ping @DeepSOIC), but I would tend to think that it is a bug and I am not so sure it is on the OCC side (I am somewhere 50-50 it is our bug). However, I did not try to fix it. Though I might try if I keep having this kind of awful flipping in my designs (it gets even worse with a subtractive loft feature, the poor thing does not know what to remove and what to leave)...
    (0010314)
    Kunda1   
    2017-10-18 11:08   
    @DeepSOIC ping
    (0010315)
    DeepSOIC   
    2017-10-18 11:39   
    sorry guys, I don't have an answer, and I don't want to dive into this problem at the moment.
    (0012964)
    graffy   
    2019-03-27 02:56   
    (Last edited: 2019-03-27 17:40)
    I looked through the FreeCAD code and nothing jumped out at me - I stopped looking when I started seeing calls to BRepOffsetAPI_ThruSections (which I assume is OCC code).

    Anyway, I'm siding with abdullah - I think it's a bug, and it might be an OCC bug. The reason is because I've encountered this edge flipping effect between profiles which had a twist substantially less than 45 degrees. At first, I thought I was doing something wrong, but I could see no immediate difference between the lofts with the flipped edges and those which generated correctly.

    In my case, I created a profile in a sketch and simply reproduced it several hundred times along a wire, orienting each duplicate normal to the wire at whatever interval it was placed. When I saw an edge flip between profiles, I decreased the profile interval and, not surprisingly, the issue went away. It doesn't happen a lot, but it does happen, and without any apparent consistency.

    The attached file shows a very long wire with a loft consisting of hundreds of profiles. If you move along it, you will see multiple examples of what I'm referring to - in one case, the rotation between the profiles is about 3 degrees on the z-axis.

    I'm siding with abdullah - I think it's a bug, but I don't see anything in the FreeCAD code that makes me think it's our bug. I stopped looking when I saw BRepOffsetAPI_ThruSections, which I presume is an OCC library call...

    (0012967)
    kisolre   
    2019-03-27 12:54   
    I think that at least in the first file (Loft_6) it works as expected - it gets Edge1, Edge2, Edge3, Edge4 from F5 and connects them to coresponding Edge1, Edge2, Edge3, Edge4 from F6. Classic TopoNaming problem with Sketch edge names.
    (0016485)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5650.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1739 [Part] General major always 2014-09-10 13:16 2021-02-06 06:46
    Reporter: ickby Platform:  
    Assigned To: ickby OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.15  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Sweep tolerances are too high
    Description: Cuts with sweeps often fail, see the example given in thread http://forum.freecadweb.org/viewtopic.php?f=3&t=7612

    By investigation it can be shown that this is a tolerance issue which can be fixed from freecad side. Let me explain:

    If you use part measure tool to measure the distance between the sweep vertex and the box face gives 7.26nm, which is 7.6290e-06mm (freecad shape tolerances are given in mm). The Vertex itself has a Tolerance value of 1.53e-05 assigned. this means the face is in tolerance of the vertex. However, the edge has a tolerance of 1e-7 assigned (Prcision::Confusion, the standart) and is therefore NOT in region of the face at the vertex location, but it only has a intersection with the face at a different lcoation then the vertex. It is quite clear that this situation must fail.

    To resolved this I used the OpenScad increase tolerance tool to increase the sweep tolerances to 1e-7, as it should have been from begining. With this sweep all cuts work nicely.

    The sweep should therefore be fixed to use Precision::Confusion per default. Either search for a correct constructor of the c++ class or change the tolerances after creation.

    One drawback however stays, but this is somethign for another issue: The distance between the vertex and the cut box is still too high for normal tolerances. OCC creates only one new vertex, not a vertex and a intersection with the edge, which is very sensible. This works by an increased tolerance of the new vertex, which gives the expected result for the user but which is bad for follow-up operations. We have to find out why the distance is bigger then the tolerance and fix this.
    Tags: sweep, tolerances
    Steps To Reproduce: load the file feder and recompute the document. To see the working fix load feder_fixed and see the result.
    Additional Information:
    Attached Files: feder_fixed.fcstd (130,865 bytes) 2014-09-10 13:16
    https://tracker.freecad.org/file_download.php?file_id=822&type=bug
    feder.fcstd (129,355 bytes) 2014-09-10 13:32
    https://tracker.freecad.org/file_download.php?file_id=823&type=bug
    forceC1.brep (1,068,064 bytes) 2014-09-11 15:00
    https://tracker.freecad.org/file_download.php?file_id=824&type=bug
    Notes
    (0005085)
    tanderson69   
    2014-09-11 01:00   
    ickby, glad you are looking into this.

    your statement: "To resolved this I used the OpenScad increase tolerance tool to increase the sweep tolerances to 1e-7, as it should have been from begining. With this sweep all cuts work nicely." confuses me. The OpenScad tolerance feature increases the vertex tolerances to 0.1. From DRAWEXE:

    Draw[3]> restore first.brep
    first
    Draw[4]> restore second.brep
    second
    Draw[5]> tolerance first
    Tolerance MAX=1.53540271460213e-05 AVG=8.8165869405836007e-06 MIN=9.9999999999999995e-08
    FACE : MAX=9.9999999999999995e-08 AVG=9.9999999999999995e-08 MIN=9.9999999999999995e-08
    EDGE : MAX=9.9999999999999995e-08 AVG=9.9999999999999995e-08 MIN=9.9999999999999995e-08
    VERTEX : MAX=1.53540271460213e-05 AVG=1.53540271460213e-05 MIN=1.53540271460213e-05

    Draw[6]> tolerance second
    Tolerance MAX=0.10000000000000001 AVG=0.057142900000000003 MIN=9.9999999999999995e-08
    FACE : MAX=9.9999999999999995e-08 AVG=9.9999999999999995e-08 MIN=9.9999999999999995e-08
    EDGE : MAX=9.9999999999999995e-08 AVG=9.9999999999999995e-08 MIN=9.9999999999999995e-08
    VERTEX : MAX=0.10000000000000001 AVG=0.10000000000000001 MIN=0.10000000000000001

    Where "first" is the sweep before the OpenScad tolerance feature and "second" is after. Did I miss something?

    You are aware that the bopalgo geometry check is complaining about continuity of swept geometry?
    (0005088)
    ickby   
    2014-09-11 05:50   
    (Last edited: 2014-09-11 05:53)
    did you export the final cut or the sweep to brep? I checked the tolerances on the sweep object and the tolerance_sweep object. The openscad tool allows to set the wanted tolerance and I have set it to 1e-7. When checking it with toelrance_sweep.Shape.Vertexes[0].Toelrance etc. it shows that the tolerance was increased to this value.

    The 0.1 tolerance can be observed after the cut and is an issue we have to look further into. that is what I entitled a "further drawback" in my original post. But this is IMHO something seperate and need an own issue.

    I was not aware of the continuity issue with this particular sweep, thanks for pointing it out, but have seen this before. I think we should look into this too to understand why this occurs (and why this is a problem), maybe this function helps with fixing this: http://dev.opencascade.org/doc/refman/html/class_b_rep_offset_a_p_i___make_pipe_shell.html#a19bd34665e3f612621cee16271f2d4e9 . But it is also possible that we fix the c0 issue with tighter tolerancey, as it could be possible that the c0 geometry is only c0 because of a lack of precison... but this is wild guessing.

    To fix the tolerance issue I think we can use http://dev.opencascade.org/doc/refman/html/class_b_rep_offset_a_p_i___make_pipe_shell.html#a56df032bc1be96f5d41f823cf0114495

    (0005089)
    tanderson69   
    2014-09-11 13:38   
    Whoops. Sweep feature was "first" and Tolerance_Sweep(openscad) was "second". The file you posted had the openscad feature set to 0.1. That was messing me up. So I adjusted the openscad tolerance feature to 1e-07 and the final cut was messed up again. I then exported the 3 breps out to draw again and here is what I got:

    Draw[6]> tolerance first
    Tolerance MAX=1.53540271460213e-05 AVG=8.8165869405836007e-06 MIN=9.9999999999999995e-08
    FACE : MAX=9.9999999999999995e-08 AVG=9.9999999999999995e-08 MIN=9.9999999999999995e-08
    EDGE : MAX=9.9999999999999995e-08 AVG=9.9999999999999995e-08 MIN=9.9999999999999995e-08
    VERTEX : MAX=1.53540271460213e-05 AVG=1.53540271460213e-05 MIN=1.53540271460213e-05

    Draw[7]> tolerance second
    Tolerance MAX=1.53540271460213e-05 AVG=8.8165869405836007e-06 MIN=9.9999999999999995e-08
    FACE : MAX=9.9999999999999995e-08 AVG=9.9999999999999995e-08 MIN=9.9999999999999995e-08
    EDGE : MAX=9.9999999999999995e-08 AVG=9.9999999999999995e-08 MIN=9.9999999999999995e-08
    VERTEX : MAX=1.53540271460213e-05 AVG=1.53540271460213e-05 MIN=1.53540271460213e-05

    Draw[8]> tolerance finalCut
    Tolerance MAX=1.53540271460213e-05 AVG=6.1633279253641203e-06 MIN=9.9999999999999995e-08
    FACE : MAX=9.9999999999999995e-08 AVG=9.9999999999999995e-08 MIN=9.9999999999999995e-08
    EDGE : MAX=5.0000000000000004e-06 AVG=1.3249999999999998e-06 MIN=9.9999999999999995e-08
    VERTEX : MAX=1.53540271460213e-05 AVG=9.5298868763843228e-06 MIN=5.0000000000000004e-06

    "first" = the original sweep.
    "second" = openscad tolerance feature. set 1e-07
    "finalCut" = the last boolean cut feature.

    I did this twice to make sure I didn't mess something up. It appears the tolerance feature didn't tighten any tolerances. At least here.




    "BRepOffsetAPI_MakePipeShell::SetForceApproxC1" would be simple to try. I don't know if the continuity is the cause of any problems, but it can't help.

    we could try "BRepOffsetAPI_MakePipeShell::SetTolerance" to see what happens.
    (0005090)
    tanderson69   
    2014-09-11 15:01   
    BRepOffsetAPI_MakePipeShell::SetForceApproxC1 doesn't appear to be the answer. See uploaded file.
    (0005091)
    tanderson69   
    2014-09-11 15:18   
    tried "makeSweep.SetTolerance(Precision::Confusion(), Precision::Confusion(), Precision::Angular());"

    tolerances from drawexe:
    Draw[5]> tolerance tol
    Tolerance MAX=1.62647393406168e-06 AVG=9.7227081946381715e-07 MIN=9.9999999999999995e-08
    FACE : MAX=9.9999999999999995e-08 AVG=9.9999999999999995e-08 MIN=9.9999999999999995e-08
    EDGE : MAX=9.9999999999999995e-08 AVG=9.9999999999999995e-08 MIN=9.9999999999999995e-08
    VERTEX : MAX=1.62647393406168e-06 AVG=1.62647393406168e-06 MIN=1.62647393406168e-06

    slight change. tried subtraction of 2 cubes and got a different output, but still invalid.
    (0005092)
    tanderson69   
    2014-09-11 15:35   
    Tried both the tolerance and the forceC1 and made some progress. Got a good looking solid that passed the bopalgo check. still failed on the boolean cuts. I am thinking that this is a boolean problem and not a tolerance problem.

    construction snippet:

    BRepOffsetAPI_MakePipeShell makeSweep(helix);
    makeSweep.SetMode(true); //frenet
    makeSweep.SetTransitionMode(BRepBuilderAPI_RightCorner);
    makeSweep.SetForceApproxC1(true);
    makeSweep.SetTolerance(Precision::Confusion(), Precision::Confusion(), Precision::Angular());
    makeSweep.Add(circle);
    makeSweep.Build();
    makeSweep.MakeSolid();
    TopoDS_Shape output = makeSweep.Shape();
    (0006461)
    triplus   
    2015-09-26 12:38   
    I can confirm the issue:

    http://forum.freecadweb.org/viewtopic.php?f=3&t=12584&p=101155#p101155
    (0010092)
    industromatic   
    2017-09-08 15:22   
    Here is another example of this bug of leaving out a sliver of tolerance so a PartDesign additive or subtractive pipe will be incomplete.

    https://forum.freecadweb.org/viewtopic.php?f=3&t=24266

    The work around is to use 2 overlapping sweeps to do a cut operation.
    (0010093)
    industromatic   
    2017-09-08 15:31   
    Since in two days will be the three year anniversary of this bug, is it time to institute a workaround in the GUI? It seems that one profile to sweep in one location is enough to do a cut successfully using PartDesign subtractive pipe. The method is to sweep clockwise a segments, and also sweep CCW b segments, where n is the total number of segments to make a closed loop, and a + b = n + 1.

    A workaround could be to do one sweep with a new GUI button that skips selecting individual segments, and the button is called sweep all segments. It would sweep CW n segments, then add a sweep CCW of 1 segment.
    (0010529)
    abdullah   
    2017-12-07 05:08   
    @kunda1

    Hi! This ticket is not "sketcher" related. Is it possible to move it, maybe to project "Part"?
    (0010530)
    Kunda1   
    2017-12-07 05:10   
    (Last edited: 2017-12-07 05:10)
    @abdullah done ;)

    (0016429)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5594.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1288 [Part] Feature feature have not tried 2013-10-27 05:10 2021-02-06 06:46
    Reporter: shoogen Platform:  
    Assigned To: wmayer OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Edit Mode for Part::Spline
    Description: 1. Move Poles
    2. change local continuity (multicities and degree)
    3. insert and remove knots
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0006832)
    wmayer   
    2016-02-14 16:19   
    http://forum.freecadweb.org/viewtopic.php?f=24&t=14100
    (0016409)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5574.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    122 [Part] Feature minor have not tried 2010-06-30 11:09 2021-02-06 06:46
    Reporter: Jriegel Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Part reference element
    Description: Object which reference a shape at a different position. So the objects
    always looks the same and use the same inventor nodes to render.

    Needed for IDF import which place lots of the same shape at a wire board...
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0011419)
    Kunda1   
    2018-06-13 13:24   
    Unassigning Jriegel
    (0016377)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5542.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4382 [Draft] Bug major always 2020-06-22 04:40 2021-02-06 06:45
    Reporter: fc_tofu Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 10 (10.0)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.21329 (Git)
    Build type: Release
    Branch: master
    Hash: 2330eef823b32ac412d839031cc174353a76b013
    Python version: 3.8.2
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: Chinese/China (zh_CN)
    Summary: DraftWB, error in Array position when "Link Array" checked off
    Description: DraftWB, Array operator, when "Link Array" option checked off, error appear on viewport.
    Tags: 0.19, array
    Steps To Reproduce: 1. Startup FreeCAD, switch to DraftWB
    2. Draw a circle
    3. invoke "Array" operator
    4. Task panel of "Array", check off "Link Array", OK
    5. Observe on viewport, strange points appear and placement of array instance is wrong.







    Strange points seems center of circles, the only vertex of circle. So, the issue means vertices and edges are separated after non-link Array.

    In case of "Link array" checked on, the result looks right in viewport. Then after Downgrade, same result (as Reproduce step 5) happens.

    Recompute, restart FC, restart PC, reset "user.cfg" donn't help in both cases.
    This bug doesnot happen to FC0.18.4/Win10x64.

    From discussion, this bug seems related to OCCT 7.4.0, not to 7.3.0.
    Additional Information: Forum:
    https://forum.freecadweb.org/viewtopic.php?f=3&t=47471
    Attached Files:
    Notes
    (0016911)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6078.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4242 [Draft] Bug crash always 2020-01-09 05:25 2021-02-06 06:45
    Reporter: vocx Platform: Linux  
    Assigned To: OS: Ubuntu  
    Priority: normal OS Version: 18.04  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Ubuntu 18.04.3 LTS (ubuntu:GNOME/ubuntu)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.19212 (Git)
    Build type: Debug
    Branch: master
    Hash: 004fda205ed8470702864083f417710db222b760
    Python version: 3.6.9
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    Summary: Crash: when testing Draft Dimension
    Description: All workbenches include unit tests to tests many of its tools.

    When running the test for the Draft Dimension tool, and only this tool, from the command line, the software crashes.

    It doesn't crash if all tests are run, only when this single test is run in isolation.

    Many people can't reproduce this crash. Therefore, the problem could be my particular system, including Coin version, and graphics card.

    Forum thread Crash: when testing Draft Dimension
    Tags:
    Steps To Reproduce: Run from the command line

    
    freecad -t drafttests.test_creation.DraftCreation.test_dimension_linear
    

    It does not crash if all tests are run
    
    freecad -t TestDraft
    
    Additional Information: My system has
    
    pivy.__version__
    '0.6.5a0'
    

    And Intel HD 620 (rev 02) graphics.

    Backtrace in the attached file.
    Attached Files: bug_4242.txt (52,156 bytes) 2020-02-11 16:47
    https://tracker.freecad.org/file_download.php?file_id=2430&type=bug
    Notes
    (0014155)
    vocx   
    2020-02-11 16:47   
    Attachment of log
    (0014417)
    vocx   
    2020-05-17 20:23   
    Another forum thread to reproduce the error with a single file containing a single Draft Dimension, Crash with a single Draft Dimension.

    Probably an explanation for the problem is that the Dimension rebuilds its viewprovider using Pivy (Coin), which is not available at start.

    To make it work, first create a new document, which creates a 3D view, and then switch to the Draft Workbench to initialize Pivy. Then loading the single document with a single dimension works correctly.
    (0016855)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6021.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4094 [Draft] General minor always 2019-08-21 11:56 2021-02-06 06:45
    Reporter: doubters Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Incorrect behavior of the Label tool in the Draft workspace
    Description: 1. The label parameter "Display Mode" is not saved and, after opening the file, returns to "3D text"
    2. Extra characters for Custom text on the working field (fixed in version 0.19)
    3. When changing the "Display Mode" from "3D text" to "2D text", "Text Alignment" has to be changed several times to correctly position the inscription.
    Tags: #post-to-forum
    Steps To Reproduce:
    Additional Information:
    Attached Files: label.mp4 (2,400,436 bytes) 2019-08-21 11:56
    https://tracker.freecad.org/file_download.php?file_id=2285&type=bug
    Notes
    (0013444)
    Kunda1   
    2019-08-21 20:03   
    You didn't add you full FC version (per the guidelines in large yellow banner top of page). Also, please open forum thread to signal to community about this issue.
    (0013447)
    doubters   
    2019-08-22 06:05   
    In which section of the forum to post?

    Information about versions of FreeCADs that were checked:

    OS: Ubuntu 19.04
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.3.
    Build type: Release
    Python version: 3.7.3
    Qt version: 5.12.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: C/Default (C)

    OS: Ubuntu 19.04 (ubuntu:GNOME/ubuntu)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.
    Build type: Release
    Python version: 3.7.3
    Qt version: 5.12.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: C/Default (C)
    (0013448)
    Kunda1   
    2019-08-22 15:28   
    @doubters https://forum.freecadweb.org/viewforum.php?f=3
    (0014033)
    Kunda1   
    2020-01-09 19:08   
    @carlopav care to test this to see if in fact it's an issue ?
    (0014034)
    carlopav   
    2020-01-09 19:20   
    @kunda1, i can confirm the behaviour with:
    OS: Windows 7 SP 1 (6.1)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.19093 (Git)
    Build type: Release
    Branch: master
    Hash: 9e4710d679d44613a1ae4264b86ef9f6d12f4e5a
    Python version: 3.6.8
    Qt version: 5.12.1
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: Italian/Italy (it_IT)

    I never had a serious look at this part of Draft code, so I don't know what's happening, but anyway this is not an intuitive behaviour. When I'll have some time i could give it a deeper look, but not so soon...
    (0014036)
    Kunda1   
    2020-01-10 20:45   
    Thanks carlopav! I'm marking this ticket 'confirmed' and setting the target for 0.19
    If you do have time that is great but no worries.
    (0016811)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5977.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3908 [Draft] Feature tweak always 2019-03-17 08:33 2021-02-06 06:45
    Reporter: brjhaverkamp Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Entering text in Arch annotation is confusing and non-intuitive
    Description: When adding a text annotation in the Arch workbench, I was not able to create the text object. After entering the text in the single line edit in the task panel, nothing happened. After pressing close, there was no text object.

    I consulted the forum and Regis explained that he initially (long time ago) had the same confusion. The trick is to press enter twice. It is possible to enter multiple lines of text and only when entering an empty line at the end, the text object is created.

    This is very workable for experienced freecad users, but totally confusing when first using the function.
    Proposal: make the line edit in the task pane a multi-line edit to clearly show it is possible to enter multiple lines and add an OK button to confirm the action.
    This would be more clear and userfriendly.
    Tags: Arch, Bountysource Potential, Draft, Task View, UI
    Steps To Reproduce:
    Additional Information: OS: Ubuntu 18.10
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16093 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-18
    Hash: 690774c0effe4fd7b8d2b5e2fb2b8c8d145e21ce
    Python version: 2.7.15+
    Qt version: 5.11.1
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    Attached Files:
    Notes
    (0012927)
    vocx   
    2019-03-18 21:47   
    First of all, the annotation tool is part of Draft, not Arch. So strictly speaking this should be classified in Draft.

    Second, the behavior of double Enter is documented in the wiki and in the offline documentation included with FreeCAD.

    https://www.freecadweb.org/wiki/Draft_Text

    However, I agree that the behavior is not intuitive, and should probably be changed as you describe.
    (0012932)
    Kunda1   
    2019-03-20 18:53   
    @brjhaverkamp please discuss this on the forums. We ask users do this (per the large annoying yellow banner at the top of every page of this bug tracker) per our guidelines. Thanks
    (0012935)
    brjhaverkamp   
    2019-03-20 20:42   
    Hi Kunda1,

    Of course I read the yellow banner. And indeed it is common practice. Only missed linking the bugreport the thread and vice versa. Here is the link.
    https://forum.freecadweb.org/viewtopic.php?f=23&t=34934

    I realise this is probably not high on the list of improvements. But I wanted to make sure that if someone wants to attack the low-hanging fruit, it is in the system.

    Regards,
    Bert
    (0016735)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5900.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3853 [Draft] Bug minor always 2019-02-22 00:13 2021-02-06 06:45
    Reporter: uwestoehr Platform:  
    Assigned To: yorik OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: ShapeString is not editable
    Description: - created with the Draft WB a ShapeString.

    This opens a task dialog where you can specify settings

    - after the creation, double-click on the ShapeString in the model tree

    result: the ShapeString gets a yellow background but the task dialog doesn't show up. So FC is in editing mode but there is nothing to edit.
    In the report panel I see
    "This object type is not editable"

    Since there exists a nice task dialog for ShapeStrings, it should be shown.
    Tags: Task View
    Steps To Reproduce:
    Additional Information: OS: Windows 7
    Word size of OS: 64-bit
    forum thread: https://forum.freecadweb.org/viewtopic.php?f=3&t=34370

    Word size of FreeCAD: 64-bit
    Version: 0.18.15959 (Git)
    Build type: Release
    Branch: master
    Hash: 397418078a6f61e8c39cedfe1160adc2abd73510
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: German/Germany (de_DE)
    Attached Files:
    Notes
    (0012726)
    yorik   
    2019-02-22 13:27   
    Indeed that object has its edit mode not fully implemented. I'll do that after the 0.18 release
    (0014945)
    uwestoehr   
    2020-10-24 22:02   
    > I'll do that after the 0.18 release

    Did you find time to have a look meanwhile?
    (0015071)
    Kunda1   
    2020-12-03 23:50   
    @yorik should we bump this to 0.20 ?
    (0015152)
    yorik   
    2020-12-16 11:19   
    No, let me try to fix it before 0.19 ;)
    (0016720)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5885.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3817 [Draft] Bug minor always 2019-02-05 00:40 2021-02-06 06:45
    Reporter: chrisb Platform:  
    Assigned To: yorik OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Draft Preferences "Always show the grid" have no effect
    Description: From the forum discussion:
    Draft grid behaviour seems to be in independent of Preferences->Draft->Grid&snapping->"Always show the grid"

    - Switch to Draft -> grid appears all by itself
    - Switch to other WB -> grid stays
    - Switch to and fro another time to switch it off.

    I can switch the grid off completely in Preferences, but then in the rare occasions where I need it, I cannot switch it on at all.

    This is what I would like to see:
    - The behaviour is ok as it is if "Always show the grid" is checked.
    - if it is not checked: switching to Draft will not show the grid. If the grid is switched on it can stay so even when switching WBs.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0012587)
    yorik   
    2019-02-06 14:46   
    To resume what should be done:

    If Draft -> Use grid is on and always use grid is on:
    - Show the grid on entering Draft, keep the grid on leaving Draft

    If Draft -> Use grid is on and always use grid is off:
    - Do not show the grid on entering Draft, hide the grid on leaving Draft

    If Draft -> Use grid is off:
    - Do not show the grid ever

    Okay?
    (0012823)
    garya   
    2019-03-02 23:20   
    The desired behavior sounds right, but I have a question about the location of the preference. Logically, things that appear in a WB preference should only apply to that WB. So if the grid can apply to FC as a whole, then it seems like it should be in a preference for FC as a whole, not Draft. If it's in a preference for FC as a whole, and it's possible to have it off/on for particular WBs, then the preference should probably be something like "On/off in all" with a further refinement of "except" where one can check the appropriate WBs.
    (0016713)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5878.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3764 [Draft] Feature feature always 2019-01-09 18:31 2021-02-06 06:45
    Reporter: Renato Rebelo Platform:  
    Assigned To: yorik OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: dxf export units
    Description: When trying to export a file to dxf the file is always exported in millimeters, would it be possible to create an option to choose the export units?
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016693)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5858.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3235 [Draft] Feature minor always 2017-11-04 12:31 2021-02-06 06:45
    Reporter: Kunda1 Platform:  
    Assigned To: yorik OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Allow to change Draft Label's target object
    Description: Per http://yorik.uncreated.net/guestblog.php?2017=414
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0014536)
    vocx   
    2020-06-13 21:16   
    This bug doesn't provide a lot of information about what is wrong.

    With this https://github.com/FreeCAD/FreeCAD/pull/3593, I clean up the Label object. It works well, and you can change the target object by changing the "Target" property. So I'm not sure what this bug describes.
    (0016572)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5737.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2795 [Draft] Feature minor have not tried 2016-11-26 18:57 2021-02-06 06:45
    Reporter: TomV Platform: Linux  
    Assigned To: yorik OS: Ubuntu  
    Priority: normal OS Version: 16.0  
    Status: assigned Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Allow cherrypicking individual lines from a sketch when creating a wall
    Description: My current (noob) workflow is as follows:
    1. create a single monster sketch with the floorplan of my house
    2. then draw draft rectangle over the sketch lines to specify walls
    3. then convert those draft rectangles into a wall

    It's not possible to select lines from the sketch directly, which makes step number 2 necessary. If you select a single line from the sketch and then press 'wall', all lines of the sketch are converted into a wall.

    My RFE is to make it possible to specify select lines from a sketch.
    Tags:
    Steps To Reproduce: N/A
    Additional Information:
    Attached Files:
    Notes
    (0007498)
    yorik   
    2016-11-29 14:14   
    That could be a good thing indeed. Will try to think a bit about how to do it (users must be able to pick the whole object as well)
    (0016510)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5675.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2562 [Draft] Feature feature N/A 2016-05-26 12:26 2021-02-06 06:45
    Reporter: wandererfan Platform: all  
    Assigned To: OS: all  
    Priority: low OS Version: all  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Add Skew/Shear Angle to ShapeString
    Description: Would be occasionally convenient to specify skew angle for text in a ShapeString.

    Merge @DeepSOIC's macro into core ShapeString.
    Tags: shapestring
    Steps To Reproduce:
    Additional Information: http://www.forum.freecadweb.org/viewtopic.php?f=3&t=15573
    Attached Files:
    Notes
    (0008278)
    normandc   
    2017-02-12 20:57   
    Shouldn't this report be under the Draft sub-project, where the ShapeString tool is located?
    (0010462)
    Kunda1   
    2017-11-24 11:36   
    @DeepSOIC should I bump to 0.18 or do you want to have a go at implementing this in to core ?
    (0010473)
    DeepSOIC   
    2017-11-26 16:27   
    @Kunda1, bump it.
    (0016491)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5656.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2349 [Draft] Feature minor have not tried 2015-12-01 12:42 2021-02-06 06:45
    Reporter: yorik Platform: PC  
    Assigned To: yorik OS: Debian  
    Priority: normal OS Version: Testing 64bit  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Use Units widgets in preferences pages
    Description: Currently they all work in mm. The units widget should be used instead for Arch and Draft
    Tags: units
    Steps To Reproduce:
    Additional Information:
    System Description
    Attached Files:
    Notes
    (0016472)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5637.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2190 [Draft] Feature minor always 2015-07-10 19:03 2021-02-06 06:45
    Reporter: triplus Platform: Linux  
    Assigned To: carlopav OS: Ubuntu  
    Priority: normal OS Version: 14.04  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Use relative coordinates for changing dimension text position.
    Description: When user tries to change dimension text position global coordinates are used instead of relative coordinates.

    1.) Use relative coordinates by default.
    2.) Use global coordinates but therefore default values for X,Y,Z text position property should not be set at 0 but at global coordinate values.

    Tags:
    Steps To Reproduce:
    Additional Information: http://forum.freecadweb.org/viewtopic.php?f=3&t=11733&p=94386#p94386
    Attached Files:
    Notes
    (0006393)
    yorik   
    2015-09-10 19:39   
    relative coordinates don't exist anymore once the object has been created.
    (0006437)
    triplus   
    2015-09-19 21:02   
    If Text Position X Y Z property is set to 0 dimension text will always be centered and slightly above dimension line. Regardless of the changes made to X Y Z Dimline Property.

    Therefore if user changes for example Text Position Y property from 0 to 0,5 i am guessing the user expects the result where dimension text is moved by 0,5 in Y direction from that original position (centered and slightly above dimension line). Instead dimension text is moved away from dimension line to global 0,5 in Y direction.
    (0006442)
    yorik   
    2015-09-20 16:38   
    Hmm I don't like that, because if the dimension changes, the text position will change too, which is not what I want.
    (0006443)
    triplus   
    2015-09-20 21:37   
    That already happen if X Y Z property is set to 0. Dimension text is tied to dimension and should move with it and therefore respect relative changes in X Y Z direction set by the user.

    Positioning the dimension text individually in the global coordinate system makes less sense compared to positioning the dimension text relative to the dimension itself. I am not against having an option for both as probably there could be use case for everything. As for positioning text in global coordinate system Draft Text tool makes more sense.
    (0006444)
    triplus   
    2015-09-22 16:14   
    Alternative solution could be to have "auto" and "manual" mode.

    -Default mode would be "auto" and it would do the same as current 0,0,0 setting.
    -If changed to "manual" mode global coordinates could be set (as now) with one difference and that is X,Y,Z value would be pre-filled with current dimension text global coordinates.
    (0009649)
    steelman   
    2017-07-02 14:51   
    There need to be "relative" positioning too, to move the text around the "auto" (centre of the line) position, for example to the other side of the line. When changes are small, chances are that such "relatively" positioned text is still in acceptable position. Those chances are smaller when position is global.
    (0014544)
    carlopav   
    2020-06-14 20:28   
    @yorik, are you still of the same idea about relative coordinates of the text position vector?
    (0014549)
    yorik   
    2020-06-15 08:14   
    No not really... indeed it would make sense.
    (0014552)
    carlopav   
    2020-06-15 11:13   
    I can have a look at it, it doesn't seem something complicated to address... Do you think we should provide some kind of backward compatibility or just change it?
    (0014559)
    yorik   
    2020-06-16 10:42   
    Maybe we can change the property name? So there is a clear "before" and "after"... But also I don't think this feature is used much, so it might be overkill and we could just do it and see (and maybe provide a method that users can do manually to fix things)
    (0014564)
    yorik   
    2020-06-16 12:59   
    Looking at https://forum.freecadweb.org/viewtopic.php?f=8&t=47677&p=408935#p408935
    That property could even become a full placement.
    (0014941)
    Kunda1   
    2020-10-23 02:53   
    @carlopav any progress on this ?
    (0014942)
    carlopav   
    2020-10-23 11:53   
    @Kunda1 , sorry not much time to dedicate to Freecad at the moment, i'll be back soon I hope. :)
    (0016466)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5631.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1866 [Draft] Feature minor N/A 2014-12-19 15:32 2021-02-06 06:45
    Reporter: rockn Platform: Linux Ubuntu  
    Assigned To: OS: 14.04  
    Priority: normal OS Version: 64 bits  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Extend Draft Trimex tool to change length property of basic Arch Structure object
    Description: As a basic Arch Structure is a simple parametric box, could it be possible to extend the Draft Trimex tool to adjust the length of the Arch object depending of the selected face instead of create an extrusion ?
    Tags:
    Steps To Reproduce:
    Additional Information:
    System Description
    Attached Files:
    Notes
    (0016443)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5608.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1786 [Draft] Feature minor always 2014-10-13 14:59 2021-02-06 06:45
    Reporter: more11 Platform: Dell XPS  
    Assigned To: OS: Windows 7  
    Priority: normal OS Version: 64 bit  
    Status: new Product Version: 0.14  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Change default draft precision to allow planar surfaces from dwire
    Description: See forum discussion: http://forum.freecadweb.org/viewtopic.php?f=3&t=7989

    Increase default precision to 8 digits in order to avoid extrusion problems. Alternatively don't truncate position values when using snap.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0005212)
    more11   
    2014-10-13 16:34   
    OS: Windows 7
    Word size: 64-bit
    Version: 0.14.3700 (Git)
    Branch: releases/FreeCAD-0-14
    Hash: 32f5aae0a64333ec8d5d160dbc46e690510c8fe1
    Python version: 2.7.6
    Qt version: 4.8.5
    Coin version: 4.0.0a
    SoQt version: 1.6.0a
    OCC version: 6.6.0
    (0005213)
    shoogen   
    2014-10-13 16:58   
    increasing the draft precision will break code elsewhere (liuke dxf and svg import). IMHO changing snapping should be the preferable solution.
    (0005223)
    more11   
    2014-10-16 16:23   
    There is also a problem with tessellation. I have another thread about that at the forum: http://forum.freecadweb.org/viewtopic.php?f=3&t=8042

    Maybe change the default tessellation value to 0.05% as well?
    (0016433)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5598.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1367 [Draft] Feature minor N/A 2014-01-27 14:03 2021-02-06 06:45
    Reporter: yorik Platform:  
    Assigned To: yorik OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Extend Draft Edit mode to work with 3D shapes
    Description: Allow to edit simple, non-parametric prismatic shapes

    in Draft Edit:
    - check if the object has no curves (all edges are derived from Part Line)
    - get the position of an original vertex and its new position

    in a new Draft function:
    - find the vertex that has the original position
    - find all faces that have that vertex
    - redo these faces with the new vertex
    - rebuild a shell from all faces
    - rebuild a solid from the shell, if the original one was a solid

    possible extension:
    - instead of eding the original shape, create a new parametric feature, that links to the original object and its vertex, and has a "delta" property. This would allow to elso edit parametric objects, and keep the edit.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0004124)
    yorik   
    2014-01-27 14:08   
    (Last edited: 2014-01-27 14:08)
    Forum thread: http://forum.freecadweb.org/viewtopic.php?f=10&t=5369&p=44354

    (0014543)
    carlopav   
    2020-06-14 20:21   
    This issue is quite old it seems. @yorik, do you still think this could be something to implement in Draft_Edit or we'd better address Moult partial work on subelement modifiers?
    (0014550)
    yorik   
    2020-06-15 08:16   
    Well Draft Edit has come a long way since then... You are more able to assess this question than me now, probably. I would say maybe we could make it into a kind of full feature now, which could make changes parametric.
    (0014553)
    carlopav   
    2020-06-15 17:12   
    Well, it's a difficult question: DraftEdit it's already a quite complex tool, it deals with a ton of different object from Draft, Part, Arch, Sketcher WBs. All those objects are treated parametrically (it means we do not modify the shape directly, but modify parameters such as vector lists, length, radius, angles, etc...)
    So to introduce the shape modification seems quite odd to me... and what mostly seems strange is to do it just by points: what if we want to move a face? what if we want to move an edge? If we move just one point of a cube face, and then the others, in the meantime we obtain a bspline surface, or whatever other strange surface...
    So to me it's better if we limit Draft Edit to parameter editing and we complete Moult work on subelements modifiers. At the moment those tools are really in bad shape: they just work on Draft Wire. It would be better to me to adapt them to modify raw part shapes directly instead of changing a vector list...
    What do you think?
    (0014555)
    yorik   
    2020-06-15 18:48   
    I had in mind something like: 1) user moves a face. 2) identify all edges of that face 3) move the edges 4) identify all verts that have moved 5) recalculate all needed edges 6) recalculate all needed faces. This operation would be stored in a new feature on top of the original object. So yeah it's a pretty different operation than draft edit. Actually this is more a generic idea that is not really related to draft anymore..
    (0014556)
    carlopav   
    2020-06-15 20:51   
    Yes, I agree...
    I think anyway that this kind of task that you imagine can be added to draft subelements move... it's just not so straightforward to implement, but neither impossible...
    Should we change the issue title to readdress it or just close it?
    (0016414)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5579.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3905 [PartDesign] Bug major always 2019-03-14 01:45 2021-02-06 06:43
    Reporter: mihai.dumitresq Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Editing unlinked parts of a sketch breaks other sketches that have edges linked to it
    Description: Editing unlinked parts of a sketch breaks other sketches that have edges linked it.

    When using the part design workbench, if I have multiple sketches that depend on one another (have edges linked from one another) and I try to edit one of the earlier sketches that's very likely to break later sketches, even if what I'm editing is not linked by other sketches.

    Set the severity as "major" since often times there's no easy workaround. If I wanted to edit, say, the first sketch I would have to:
    - remove almost all links to the initial sketch
    - edit it
    - then add all of the links back

    "breaking" here means either:
    - Weird changes in the geometry of the dependent sketches due to edge linked changing (it's like if I originally linked something else)
    - Dependent sketches become invalid ("The sketch is invalid and cannot be edited")
    Tags:
    Steps To Reproduce: Here's an easy way to reproduce this.

    I) Either do this or load the attached file (invalid_sketch_test.fcstd) and skip to part II):
    Go to Part Design workbench.
    Create a new body.

    Create a new sketch in the XY plane.
    Create a rectangle in the sketch (with the tool, R).
    Close the sketch.

    Create a new sketch in the XZ plane (we want it to be dependent and fully constrained).
    Set to isometric view (0) so you can see the first sketch.
    Click "Create an edge linked to external geometry (X)" and select the two sides parallel to the Y axis.
    Set to front view (2).
    You'll have 2 linked points (not edges).
    Create a rectangle in the sketch (with the tool, R).
    Make both linked points be midpoints of two edges of the created rectangle.
    Make the rectangle a square by setting two adjacent sides be equal.
    It's now fully constrained.
    Close the sketch.

    II)
    Open the first sketch.
    Delete Constraint1 which is the first coincident constraint and should have been the constraint for the top right corner.
    Move the top right corner so it's not a rectangle anymore.
    Close the first sketch.
    Try to open the second sketch.

    Expected:
    Opens and is unchanged.

    Actual:
    "The sketch is invalid and cannot be edited."
    Additional Information: OS: Ubuntu 16.04.6 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16079 (Git) AppImage
    Build type: Release
    Branch: master
    Hash: 6363c90a20b296ab69d7b52230009928199d90df
    Python version: 3.6.7
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedKingdom (en_GB)

    I also tested with:
    OS: Ubuntu 16.04.6 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.13541 (Git) AppImage
    Build type: None
    Branch: releases/FreeCAD-0-17
    Hash: 9948ee4f1570df9216862a79705afb367b2c6ffb
    Python version: 2.7.6
    Qt version: 4.8.6
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedKingdom (en_GB)
    Attached Files: invalid_sketch_test.fcstd (6,799 bytes) 2019-03-14 01:45
    https://tracker.freecad.org/file_download.php?file_id=2154&type=bug
    Screenshot from 2019-03-16 14-44-06.png (334,756 bytes) 2019-03-16 14:49
    https://tracker.freecad.org/file_download.php?file_id=2155&type=bug
    Screenshot from 2019-03-16 14-42-48.png (328,216 bytes) 2019-03-16 14:49
    https://tracker.freecad.org/file_download.php?file_id=2156&type=bug
    Screenshot from 2019-03-16 16-27-52.png (314,096 bytes) 2019-03-16 16:40
    https://tracker.freecad.org/file_download.php?file_id=2157&type=bug
    Notes
    (0012910)
    Kunda1   
    2019-03-15 22:18   
    Please open a thread on the forum and link back to this ticket. (Don't forget to notate said thread URL in this ticket as well)
    (0012917)
    mihai.dumitresq   
    2019-03-16 12:40   
    I've started a thread but it's pending moderation. I'll post a link when it shows up.

    Were you able to reproduce the issue? Do you need more information?
    (0012918)
    mihai.dumitresq   
    2019-03-16 13:16   
    (Last edited: 2019-03-16 13:18)
    Also note that I had previously looked at other reported issues and found some similar ones:
    https://www.freecadweb.org/tracker/view.php?id=922
    However, they're not exactly the same issue.

    The issues in https://www.freecadweb.org/tracker/view.php?id=922 are about sketches that have links to external geometry.
    My report is specifically about sketches that have links to other sketches.

    To explain more clearly, this issue is about:
    create sketch -> create another sketch that depends on it -> modify original sketch (problem!)

    https://www.freecadweb.org/tracker/view.php?id=922 looks to be about:
    create sketch -> create geometry from sketch (pad, loft, etc.) and maybe chamfer/fillet, etc. -> create another sketch that depends on the geometry -> modify original sketch (problem!)

    (0012920)
    normandc   
    2019-03-16 14:15   
    Once again this is the topological naming issue at work, and yes, this is what 0000922 is about. This report is therefore unnecessary because redundant.
    (0012921)
    normandc   
    2019-03-16 14:16   
    https://www.freecadweb.org/wiki/Glossary#Topological_Naming
    (0012922)
    mihai.dumitresq   
    2019-03-16 14:49   
    That's the interesting thing: I don't think it's the same issue or at least this bug has a much much simpler solution than topological naming.
    The ids of the edges in the sketch don't change! (in my repro case)
    invalid_sketch_test.Sketch.Edge1 through Edge4 are the same in the Sketcher view, before and after removing Constraint1 as per my repro steps. See attached screenshots.
    (0012923)
    mihai.dumitresq   
    2019-03-16 16:40   
    (Last edited: 2019-03-16 16:41)
    Looks like there's a mismatch between the edge names when in the full PartDesign view compared to when in the Sketcher view (i.e. when "Sketch" is opened).
    The same edge is called:
    invalid_sketch_test.Sketch.Edge1 when the sketch is open
    invalid_sketch_test.Sketch.Edge4 when the sketch is closed

    Can anyone point me to the code that assigns edge names? (i.e. the code that resulting in invalid_sketch_test.Sketch.Edge4 being assigned here?)

    And yes, I realize that this is getting closer and closer to topological naming and @normandc is right but I still think that this issue has a much easier fix than topological naming.

    (0012925)
    mihai.dumitresq   
    2019-03-16 17:37   
    (Last edited: 2019-03-16 17:38)
    I couldn't reproduce this issue with the latest version of https://github.com/realthunder/FreeCAD_assembly3/releases
    And the more complex model that I was editing that prompted this issue works perfectly.

    @realthunder Awesome!

    (0016732)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5897.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3893 [PartDesign] Feature feature have not tried 2019-03-08 22:32 2021-02-06 06:43
    Reporter: chrisb Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Counterbore and countersink with top clearance
    Description: According to this forum discussion it is sensible to extend thePartDesign hole feature:
    - Countersink should have an additional (counterbore) depth at the top
    - Countersink and Counterdepth should both provide the possibility for top clearance (reversed through all).

    This image is linked from the forum discussion:
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files: Rastergrafik.png (116,150 bytes) 2019-04-13 12:26
    https://tracker.freecad.org/file_download.php?file_id=2183&type=bug
    Notes
    (0013023)
    eivindkvedalen   
    2019-04-11 18:18   
    Branch for test: https://github.com/eivindkv/FreeCAD/tree/Fix_issue_3893
    (0013025)
    reox   
    2019-04-13 12:26   
    Additional features:

    * Set the depth of the (useable) thread (Usually this can be made in combination with the hole depth, see below)
    * Option: Set the depth of the bore without the angled point, i.e. set the useable bore depth instead of the total depth.

    I know there are some rules for tapped blind holes how deep the core hole should be and how long the threaded part ist. But I can not find them right now...
    I think it was like useable thread + 4 times the screw pitch or something like that.
    The reason is that a normal tap has some non cutting threads in the beginning.
    Other CAD packages:
    http://ww3.cad.de/foren/ubb/upl/B/BenediktKuepper/BohrungsundGewindetiefe.JPG
    http://www.ask-hochreiter.de/Info/PM12/D/Gewinde00.gif

    The Counterbore + Countersink parts could be also available for tapped holes - in German this is called "Stufenbohrung"
    Like this:
    https://ww3.cad.de/foren/ubb/uploads/Eduard+Beser/esfunzt.jpg
    (Although the question is if this is really needed...)

    Another useful feature would be to have two default counterbore settings: A shallow one (which is the current counterbore setting) and a deeper one, where the head of a ISO4672 screw is completly hidden.
    (0016729)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5894.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3889 [PartDesign] Feature minor have not tried 2019-03-06 21:33 2021-02-06 06:43
    Reporter: wmayer Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Dragging a PartDesign object to a body should not create a BaseFeature in all cases
    Description: https://forum.freecadweb.org/viewtopic.php?f=3&t=34684&p=291637#p291608
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016728)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5893.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3770 [PartDesign] Feature feature always 2019-01-12 12:36 2021-02-06 06:43
    Reporter: vectronic Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Scripted references to body origin planes
    Description: As discussed here:

    https://forum.freecadweb.org/viewtopic.php?f=22&t=31540

    it would be great if the Python API was expanded to provide convenient methods to access the plane and axis of a body origin.

    At the moment it is necessary to iterate through the origin features array and match against a label.

    I have also written a small summary of the scenario here:

    https://vectronic.io/posts/freecad-part-design-indices/

    A suggestion would be to support something like:

    origin = App.getDocument('Unnamed').getObject('myBody').Origin
    xAxis = origin.xAxis
    Tags:
    Steps To Reproduce:
    Additional Information: OS: macOS 10.14
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.15310 (Git)
    Build type: Release
    Branch: (HEAD detached at c88a64e8e)
    Hash: c88a64e8e7a3bb66a23b965b655b5a5040dfa4d2
    Python version: 2.7.15
    Qt version: 5.11.2
    Coin version: 4.0.0a
    OCC version: 7.2.0
    Locale: English/UnitedKingdom (en_GB)
    Attached Files:
    Notes
    (0012419)
    Kunda1   
    2019-01-12 13:09   
    Note @vectronic
    Please always try to use the most up to date dev version.
    Current one is at r15611 you are 301 commits behind it.
    (0012420)
    Kunda1   
    2019-01-12 13:12   
    Since we're in a feature freeze I'm setting the target for the 0.19 cycle.
    (0016694)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5859.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3751 [PartDesign] Bug minor always 2018-12-28 11:10 2021-02-06 06:43
    Reporter: sleeply4cat Platform: Linux  
    Assigned To: OS: Ubuntu  
    Priority: normal OS Version: 18.04.1  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FreeCAD crashes on Loft creation when master-sketch added as a section
    Description: May be related to 0002461
    Reproduces if the master-sketch added as a not last section of Loft.
    Tags: Loft
    Steps To Reproduce: 1. Create two sketches on different planes
    2. Activate a Loft tool
    3. Select sketch A as base
    4. Add sketch A as a section
    5. Add sketch B as a section
    6. FreeCAD crashes after clicking on the sketch B

    https://youtu.be/fKxVAzo2-0A
    Additional Information: [quote=$ freecad-daily FreeCAD 0.18, Libs: 0.18R15495 (Git) © Juergen Riegel, Werner Mayer, Yorik van Havre 2001-2018 ##### #### ### #### # # # # # # # ## #### #### # # # # # #### # # # # # # # ##### # # # # #### #### # # # # # # # # # # # # # # ## ## ## # # #### #### ### # # #### ## ## ## (freecad-daily:5562): IBUS-WARNING **: 13:29:16.710: Unable to connect to ibus: Could not connect: Connection refused 'ascii' codec can't decode byte 0xd0 in position 33: ordinal not in range(128) ** (freecad-daily:5562): WARNING **: 13:29:21.446: invalid source position for vertical gradient ** (freecad-daily:5562): WARNING **: 13:29:21.446: invalid source position for vertical gradient Program received signal SIGSEGV, Segmentation fault. #0 /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20) [0x7f2e23e5af20] #1 /usr/lib/x86_64-linux-gnu/libTKTopAlgo.so.7(+0x17bcb5) [0x7f2de1d9bcb5] 0000002 0x7f2de1d9c77e in BRepLib::EncodeRegularity(TopoDS_Shape const&, double) from /usr/lib/x86_64-linux-gnu/libTKTopAlgo.so.7+0x14e 0000003 0x7f2de0a7ada8 in BRepOffsetAPI_ThruSections::Build() from /usr/lib/x86_64-linux-gnu/libTKOffset.so.7+0xd28 0000004 0x7f2d91d9514b in PartDesign::Loft::execute() from /usr/lib/freecad-daily/lib/_PartDesign.so+0x7db 0000005 0x7f2e2641e035 in App::DocumentObject::recompute() from /usr/lib/freecad-daily/lib/libFreeCADApp.so+0x155 0000006 0x7f2de55af55b in Part::Feature::recompute() from /usr/lib/freecad-daily/lib/Part.so+0xb 0000007 0x7f2e263d2324 in App::Document::_recomputeFeature(App::DocumentObject*) from /usr/lib/freecad-daily/lib/libFreeCADApp.so+0xb4 0000008 0x7f2e263d9df3 in App::Document::recomputeFeature(App::DocumentObject*) from /usr/lib/freecad-daily/lib/libFreeCADApp.so+0x83 0000009 0x7f2d915fe490 in PartDesignGui::TaskLoftParameters::onSelectionChanged(Gui::SelectionChanges const&) from /usr/lib/freecad-daily/lib/PartDesignGui.so+0xf0 0000010 0x7f2e26edc896 in Gui::SelectionObserver::_onSelectionChanged(Gui::SelectionChanges const&) from /usr/lib/freecad-daily/lib/libFreeCADGui.so+0x56 0000011 0x7f2e26eeac3f in boost::signals2::detail::signal_impl<void (Gui::SelectionChanges const&), boost::signals2::optional_last_value<void>, int, std::less<int>, boost::function<void (Gui::SelectionChanges const&)>, boost::function<void (boost::signals2::connection const&, Gui::SelectionChanges const&)>, boost::signals2::mutex>::operator()(Gui::SelectionChanges const&) from /usr/lib/freecad-daily/lib/libFreeCADGui.so+0x20f 0000012 0x7f2e26ee4f21 in Gui::SelectionSingleton::addSelection(char const*, char const*, char const*, float, float, float) from /usr/lib/freecad-daily/lib/libFreeCADGui.so+0x281 0000013 0x7f2e26d49aca in Gui::SoFCUnifiedSelection::handleEvent(SoHandleEventAction*) from /usr/lib/freecad-daily/lib/libFreeCADGui.so+0xcba 0000014 0x7f2e237b6ea0 in SoNode::handleEventS(SoAction*, SoNode*) from /usr/lib/x86_64-linux-gnu/libCoin.so.80+0x80 0000015 0x7f2e2355ba54 in SoAction::traverse(SoNode*) from /usr/lib/x86_64-linux-gnu/libCoin.so.80+0x64 0000016 0x7f2e236c1425 in SoChildList::traverse(SoAction*, int, int) from /usr/lib/x86_64-linux-gnu/libCoin.so.80+0x165 0000017 0x7f2e237ab436 in SoGroup::doAction(SoAction*) from /usr/lib/x86_64-linux-gnu/libCoin.so.80+0x56 0000018 0x7f2e237ca7c7 in SoSeparator::doAction(SoAction*) from /usr/lib/x86_64-linux-gnu/libCoin.so.80+0x27 0000019 0x7f2e237b6ea0 in SoNode::handleEventS(SoAction*, SoNode*) from /usr/lib/x86_64-linux-gnu/libCoin.so.80+0x80 0000020 0x7f2e2355ba54 in SoAction::traverse(SoNode*) from /usr/lib/x86_64-linux-gnu/libCoin.so.80+0x64 0000021 0x7f2e23566a4a in SoHandleEventAction::beginTraversal(SoNode*) from /usr/lib/x86_64-linux-gnu/libCoin.so.80+0x7a 0000022 0x7f2e2355d262 in SoAction::apply(SoNode*) from /usr/lib/x86_64-linux-gnu/libCoin.so.80+0x442 0000023 0x7f2e236e0c19 in SoEventManager::actuallyProcessEvent(SoEvent const*) from /usr/lib/x86_64-linux-gnu/libCoin.so.80+0x69 0000024 0x7f2e26dc2dce in SIM::Coin3D::Quarter::QuarterWidget::processSoEvent(SoEvent const*) from /usr/lib/freecad-daily/lib/libFreeCADGui.so+0x1e 0000025 0x7f2e26dcae26 in SIM::Coin3D::Quarter::SoQTQuarterAdaptor::processSoEvent(SoEvent const*) from /usr/lib/freecad-daily/lib/libFreeCADGui.so+0x56 0000026 0x7f2e26df41a9 in Gui::View3DInventorViewer::processSoEventBase(SoEvent const*) from /usr/lib/freecad-daily/lib/libFreeCADGui.so+0x9 0000027 0x7f2e26dd93c9 in Gui::BlenderNavigationStyle::processSoEvent(SoEvent const*) from /usr/lib/freecad-daily/lib/libFreeCADGui.so+0x219 0000028 0x7f2e26dd4848 in Gui::NavigationStyle::processEvent(SoEvent const*) from /usr/lib/freecad-daily/lib/libFreeCADGui.so+0xf8 0000029 0x7f2e26df4123 in Gui::View3DInventorViewer::processSoEvent(SoEvent const*) from /usr/lib/freecad-daily/lib/libFreeCADGui.so+0x63 0000030 0x7f2e26dbd21c in SIM::Coin3D::Quarter::EventFilter::eventFilter(QObject*, QEvent*) from /usr/lib/freecad-daily/lib/libFreeCADGui.so+0x1ac 0000031 0x7f2e24938a16 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) from /usr/lib/x86_64-linux-gnu/libQtCore.so.4+0x86 0000032 0x7f2e24e6501c in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /usr/lib/x86_64-linux-gnu/libQtGui.so.4+0x6c 0000033 0x7f2e24e6c136 in QApplication::notify(QObject*, QEvent*) from /usr/lib/x86_64-linux-gnu/libQtGui.so.4+0x476 0000034 0x7f2e26b967c8 in Gui::GUIApplication::notify(QObject*, QEvent*) from /usr/lib/freecad-daily/lib/libFreeCADGui.so+0x88 0000035 0x7f2e249388ad in QCoreApplication::notifyInternal(QObject*, QEvent*) from /usr/lib/x86_64-linux-gnu/libQtCore.so.4+0x8d 0000036 0x7f2e24e6b73d in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) from /usr/lib/x86_64-linux-gnu/libQtGui.so.4+0x14d 0000037 /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x249452) [0x7f2e24ee9452] 0000038 0x7f2e24ee8ce3 in QApplication::x11ProcessEvent(_XEvent*) from /usr/lib/x86_64-linux-gnu/libQtGui.so.4+0x16b3 #39 /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x272592) [0x7f2e24f12592] #40 /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x2e7) [0x7f2e1d63f387] 0000041 /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c5c0) [0x7f2e1d63f5c0] 0000042 /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f2e1d63f64c] 0000043 0x7f2e2496920e in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /usr/lib/x86_64-linux-gnu/libQtCore.so.4+0x7e 0000044 /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x272666) [0x7f2e24f12666] 0000045 0x7f2e2493712f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /usr/lib/x86_64-linux-gnu/libQtCore.so.4+0x3f 0000046 0x7f2e24937495 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) from /usr/lib/x86_64-linux-gnu/libQtCore.so.4+0x1b5 0000047 0x7f2e2493d459 in QCoreApplication::exec() from /usr/lib/x86_64-linux-gnu/libQtCore.so.4+0x99 0000048 0x7f2e26b22c7a in Gui::Application::runApplication() from /usr/lib/freecad-daily/lib/libFreeCADGui.so+0x16ba 0000049 freecad-daily(main+0x6db) [0x55f64076043b] 0000050 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f2e23e3db97] 0000051 freecad-daily(_start+0x2a) [0x55f6407615ea]][/quote]
    Attached Files: log.txt (7,201 bytes) 2018-12-28 11:12
    https://tracker.freecad.org/file_download.php?file_id=2081&type=bug
    Notes
    (0012344)
    sleeply4cat   
    2018-12-28 11:12   
    (Last edited: 2018-12-28 11:16)
    omg, sorry. Attached a log by the right way.

    Also, build info:
    OS: Ubuntu 18.04.1 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.15495 (Git)
    Build type: Release
    Branch: master
    Hash: 9c7128ea77fc1046e11ebf2fbeb41216446eac4f
    Python version: 2.7.15rc1
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)

    (0016690)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5855.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3527 [PartDesign] Feature minor always 2018-07-03 12:23 2021-02-06 06:43
    Reporter: fix daddy Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Unable to edit linear Patterns
    Description: The file has the complete list of features to be final. However, when I'm trying to edit the parameters of the two linear pattern in the last multitransform, the software would run forever without converging.

    Prior to the attempt to have two multitransform, I had only one ending with a polar pattern. I couldn't get this to work either.

    Is there a way to simplify the part design to achieve what I want - a cross-hatch network of triangular grooves, separated by 5 mm?
    Tags: Part Design
    Steps To Reproduce: Open the file Friction_Plate1.FCstd
    Right-click on the "Side Set of grooves" and choose Edit MultiTransform.
    [The program crashes sometimes at this point]
    Uncheck the “update view” box, to give the software a chance.
    Right-Click on the LinearPattern002 and select Edit
    Edit the Length to 260 mm
    Edit the Occurrences to 52
    [At this point, the software may start spinning. Not always, though]
    Click OK
    [The parameters of the linear transform might revert back to the default, but not all the time]
    Additional Information: OS: Windows 7
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.13522 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-17
    Hash: 3bb5ff4e70c0c526f2d9dd69b1004155b2f527f2

    EDIT: DO NOT CLOSE THIS TICKET AS IT SERVES AS A USECASE FOR 0003600
    Attached Files: Friction_Plate1.FCStd (1,968,165 bytes) 2018-07-03 12:23
    https://tracker.freecad.org/file_download.php?file_id=1952&type=bug
    Notes
    (0011491)
    fix daddy   
    2018-07-03 22:44   
    After days of trying and waiting, the software finally finished. The attached part is likely what I need, based on the view.
    (0011494)
    Kunda1   
    2018-07-05 00:31   
    You can also try with the latest 0.18dev version to see if the speed improves. If not then you open a forum thread to discuss with the community (just as the giant yellow banner at the top of this page asks users). thank you
    (0011555)
    normandc   
    2018-07-27 16:21   
    There were no changes to PartDesign Transformation features between v0.17 and v0.18.

    A bug report is not the proper place to inquire about alternative methods. That's what the forum is for.
    (0011557)
    Kunda1   
    2018-07-27 17:49   
    @normandc should I close this ticket or is "the software would run forever without converging" a valid issue that needs to be explored a but more?
    (0011561)
    normandc   
    2018-07-29 15:54   
    The problem is that the required cross-hatch network of grooves is extremely heavy to compute, and that is true for any CAD program, but painfully more so for transformation features in the PartDesign workbench. There are three transformation features in the MultiTransform, they multiply each other and create thousands of objects to apply a Boolean operation with.

    The Draft Array tool is much more efficient with dealing with massive numbers of occurrences which may indicate there is room for improvement with the performance of PD Transformation tools, even though they have a higher overhead.

    Therefore it would be useful to create a general report named "Improve PartDesign Transformation features performance" and link this report to it as use case.
    (0012372)
    Kunda1   
    2019-01-04 19:03   
    DO NOT CLOSE THIS TICKET AS IT SERVES AS A USECASE FOR 0003600
    (0016630)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5795.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3500 [PartDesign] Feature feature N/A 2018-06-04 20:05 2021-02-06 06:43
    Reporter: dbecad Platform: All  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Adding Interpolating Spline feature to Sketcher/PartDesign
    Description: Good day,
    Some time you want to interpolate a curve through some measured key points (that should be controlled/constrained as normal sketcher points) an in this case the control over the order of curvature / knot weight is less important.

    These splines are similar to the b-spline tool in draft WB, even if it might be more accurate to call them centripetal / Catmull-Rom splines

    They do have a lot of really interesting properties for modeling:
    - they are nicely behaved, stay local and never diverge/loop even when control points are close together,
    - you can also set the tangent at the beginning/end to connect with the rest of sketches elements
    - possible to generate close loop with them.

    But the most important feature is you control the curve with way points, not knots like B-Splines/NURBS that have no relation with the end result curve.

    Thanks for your hard work!

    Reference Forum Thread
    Tags: b-splines
    Steps To Reproduce: NA
    Additional Information: NA
    Attached Files:
    Notes
    (0016629)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5794.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3301 [PartDesign] Feature feature always 2018-01-04 10:59 2021-02-06 06:43
    Reporter: Pauvres_honteux Platform: x64  
    Assigned To: OS: OpenSUSE  
    Priority: normal OS Version: 42.2  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Container for intersections
    Description: Forum discussion: Intersection container
    Tags: containers
    Steps To Reproduce:
    Additional Information: Moreover; the output of/from the container shall not change id, that is, anything linked to the container shall only see/feel/get a static and never changing id from it. If the output involves a direction vector, AND the content has changed, it shall be verified that it is within a range of less than 90 degrees. If outside that range a popup, containing a viewport, shall ask the user and show the user the current direction vector and the new direction vector. And then user can choose to change the new direction vector, in a simple way, maybe via the viewport?
    Attached Files:
    Notes
    (0016591)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5756.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3297 [PartDesign] Feature feature always 2018-01-03 17:43 2021-02-06 06:43
    Reporter: chrisb Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Part Design usability improvement for selection of Sweep Path
    Description: When creating a sweep in PDN the selection and deselection of path elements is time consuming and tedious.
    Selection: It is only possible to select one path segment at a time. It would be far more compfortable to use the common multi selection using the ctrl key.
    The Path Workbench has an appropriate selection mechanism plus the comfortable possibility to select all segments of a path in a certain plane.

    Deselection: Same as above, plus the fact, that if the path segments have to be repaired due to topo naming issues they have to be searched in the model.
    It would be far easier if the elements in the list could be selected and deleted. Additional comfort would be provided if on selection of a list element the corresponding edge or sweep element could be highlighted.
    Tags:
    Steps To Reproduce: See corresponding forum discussion
    Additional Information: OS: Mac OS X
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.12915 (Git)
    Build type: Release
    Branch: (HEAD detached at 90a71f3)
    Hash: 90a71f34bc448d1396d2e27f4177885897199152
    Python version: 2.7.14
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.1.0
    Locale: German/Germany (de_DE)
    Attached Files:
    Notes
    (0010686)
    normandc   
    2018-01-03 17:57   
    Another point: it is possible to select edges of the existing solid as path elements. It would be nice to have an option to propagate the selection to edges tangent, like what is done with FIllet and Chamfer features.
    (0016590)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5755.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3269 [PartDesign] Feature feature always 2017-11-22 20:15 2021-02-06 06:43
    Reporter: GlouGlou Platform:  
    Assigned To: OS:  
    Priority: normal OS Version: W8.1  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Draft from Loft doesn't work.
    Description: Despite I have same shapes, I've got some troubles with Draft in V0.17:
    Draft from a Loft doesn't work.
    Draft seem to be inverted either its born from a cube or a refine shape.
    Tags: Loft
    Steps To Reproduce:
    Additional Information:
    Attached Files: Image1.jpg (29,325 bytes) 2017-11-22 20:15
    https://tracker.freecad.org/file_download.php?file_id=1761&type=bug
    draft1.FCStd (50,229 bytes) 2017-11-22 20:15
    https://tracker.freecad.org/file_download.php?file_id=1762&type=bug
    Notes
    (0010460)
    Kunda1   
    2017-11-24 09:54   
    @GlouGlou please post full version info and also link to forum thread discussing this issue. Thanks.
    (0010468)
    GlouGlou   
    2017-11-25 09:29   
    Sorry first tracking ;-)

    OS: Windows 8.1
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.12619 (Git)
    Build type: Release
    Branch: master
    Hash: b3631e134be8bfade0534f2dc0ee668ae71a223f
    Python version: 2.7.8
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.1.0
    Locale: French/France (fr_FR)

    https://forum.freecadweb.org/viewtopic.php?f=3&t=25297
    (0010489)
    Kunda1   
    2017-11-28 04:41   
    Per @bejant
    For some reason Loft does not create planer faces between the Sketches - and although planar faces is not the Draft problem with curved surfaces, the problem may be in the faces Loft does create.
    (0016584)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5749.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3195 [PartDesign] Feature minor have not tried 2017-09-21 17:09 2021-02-06 06:43
    Reporter: ickby Platform:  
    Assigned To: ickby OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Make Transformation tool available for GeoFeatureGroups
    Description: The default 3D view GeoFeature Transformation tool will be very handy for GeoFeatureGroups and should be available by default from the mouse menu.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0010980)
    normandc   
    2018-02-25 07:50   
    ickby wrote on the forum that he won't be available for FreeCAD development for the foreseeable feature. https://forum.freecadweb.org/viewtopic.php?f=8&t=26958&p=215930#p215930

    Unless someone else is willing to tackle this very soon, maybe we should bump it to 0.18.
    (0012742)
    normandc   
    2019-02-24 15:40   
    @wmayer
    I'm not certain what a GeoFeatureGroup is, if it's a Part or Body container, hasn't this been implemented already? Both provide a Transform item in the contextual menu, even in v0.17.
    (0012750)
    wmayer   
    2019-02-24 17:17   
    Recently I had a look at this ticket too and the forum thread but for me it's not clear either what exactly is meant with GeoFeatureGroup. A class of this name doesn't exist and furthermore the transformation tool should be implemented for a view provider, not its feature class.

    The closest thing I found is the class ViewProviderGeoFeatureGroupExtension and this ticket could be about to implement the transformation tool there so that it's available for all classes that use or inherit from this extension class. But this is just guessing.
    (0016562)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5727.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3186 [PartDesign] Bug major always 2017-09-15 17:25 2021-02-06 06:43
    Reporter: ickby Platform:  
    Assigned To: ickby OS:  
    Priority: high OS Version:  
    Status: assigned Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Reference select dialog needs to be reworked
    Description: The reference select dialog is not yet ported to the new linked scope restrictions and does hence not really work right now.
    When working on it the code structure of that functionality can be revised and made more elegant. It's a mess.

    https://forum.freecadweb.org/viewtopic.php?f=10&t=20749&start=30#p187270
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016561)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5726.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3177 [PartDesign] Feature feature have not tried 2017-09-06 11:45 2021-02-06 06:43
    Reporter: chrisb Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Part Design Pad should allow besides "Up to face" something like "Up to plane" as well
    Description: The well known pad option "Up to face" should be extended to
    - Up to Plane for Datum planes
    - Up to edges and Datum lines
    - Up to vertices and Datum points
    Tags:
    Steps To Reproduce:
    Additional Information: Forum discussions:
    In the german forum (origin of this feature request)
    and in the english forum
    Attached Files: FC_issue3177_Pad_up_to_face_datum_plane_nc1.fcstd (21,500 bytes) 2018-09-02 20:14
    https://tracker.freecad.org/file_download.php?file_id=1992&type=bug
    Notes
    (0011663)
    wmayer   
    2018-08-26 11:23   
    Up to Face for Datum planes is fixed with: https://github.com/FreeCAD/FreeCAD/commit/fe2660b4684b51100ccc19c7479d08f7ae507398
    (0011687)
    normandc   
    2018-09-02 20:14   
    (Last edited: 2018-09-02 20:14)
    Unfortunately, there is a limitation that the datum plane has to be parallel to the sketch plane. If the datum plane is not parallel, this error message pops up:
    Pad: Extruding up to a face is only possible if the sketch plane is parallel to it
    This appears like a bug, because if there is a solid created first, then a new pad "up to face" works with a slanted datum plane.

    In the attached file FC_issue3177_Pad_up_to_face_datum_plane_nc1.fcstd, padding the Body's Sketch up to the slanted datum plane produces the aforementioned error.

    But Body001 shows that a sketch attached to an existing pad can be padded to the same datum plane with no such error message.

    OS: Ubuntu 18.04.1 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.14498 (Git)
    Build type: Release
    Branch: master
    Hash: e381e6b739a6b83b5f476546b64569cfa03a4e3a
    Python version: 2.7.15rc1
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: French/Canada (fr_CA)

    (0012261)
    normandc   
    2018-12-11 02:15   
    Setting target version to 0.18 to remove the restriction on plane parallel to sketch plane.
    (0012351)
    normandc   
    2018-12-31 18:00   
    (Last edited: 2018-12-31 18:01)
    Restriction on parallel datum plane was removed by commit ffd980b27e.

    As for the rest of the request, I'm not sure. The request asks for "up to edge/vertex". How would that work exactly? How would the pad operation know how to define the ending face, if only a vertex or an edge is selected?

    In a commercial CAD I'm familiar with, you can define the extrusion distance with a vertex selected in the 3D view. But it is a different option from the "up to face/plane" option. In this case, the pad ending face is parallel with the sketch plane. Otherwise, the tool does not allow to use an edge.

    EDIT: OK I just realized that the request is for multiple vertices and edges.

    (0016559)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5724.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3151 [PartDesign] Bug minor always 2017-08-08 20:31 2021-02-06 06:43
    Reporter: chrisb Platform: Macbook  
    Assigned To: eivindkvedalen OS: MacOS  
    Priority: low OS Version: 11  
    Status: assigned Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Renaming elements in the DataTab can make Expressions invalid
    Description: There is a forum topic containing a model and screenshot.

    In that Model I use Expressions
    - I have given the name "R" to the radius of Sketch
    - I use it in the second sketch, dividing it by 2 and give that small radius the name "r"
    - I pad the second sketch and use an expression Sketch001.r for the length.

    Next I want to rename the Sketch001 to something more sensible, let's say "SketchInner"

    I go to the Data Tab and delete "001". The problem is, that on every keystroke the name is set - to be seen in the python console. So there is a point where both sketches have the same name. I add "Inner" and leave the input field. I had expected that the second pad would break, but the second sketch breaks as well, because instead of "Sketch.R" it uses now "SketchI.R". The renaming mechanism inserts the first "I" of "Inner".
    Tags: spreadsheet
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016556)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5721.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3115 [PartDesign] Feature minor always 2017-07-05 19:44 2021-02-06 06:43
    Reporter: HoWil Platform:  
    Assigned To: OS:  
    Priority: low OS Version:  
    Status: confirmed Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Reassign pad or pocket on complete face (AKA Extend editor to allow to re-assign a different value for Profile property)
    Description: In part-desing-next it is possible to pad or pocket complete faces. This is a nice feature but can cause trouble when faces are renamed due to 'topological renaming' because until now it is not possible to reassign the pad/pocket to a new face.

    In the according Task-View is a appropriate 'Face'-selection-field but it is grayed out. Is it possible to activate it?

    See also: https://forum.freecadweb.org/viewtopic.php?f=19&t=19474&hilit=pad


    OS: Ubuntu 16.04.2 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.11495 (Git)
    Build type: None
    Branch: master
    Hash: 9e7eb3bc2c7b6d374f165b7b938da475a422763b
    Python version: 2.7.12
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.1.0
    Tags: Part Design NEXT
    Steps To Reproduce: Select 'Pad' in the included file

    OR

    File->New
    Change to PD-Next
    Create an additive box -> OK
    Select one of the faces and use "Pad a selected sketch"

    -> In the pad parameters is a 'Face' button shown to reassign the face but its grayed out.
    Additional Information: Maybe a point for the GSoC project.
    Attached Files: PDN-reassign_pad_or_pocket.fcstd (10,485 bytes) 2017-07-05 19:44
    https://tracker.freecad.org/file_download.php?file_id=1673&type=bug
    Screenshot from 2017-07-05 21-31-47.png (90,756 bytes) 2017-07-05 19:44
    https://tracker.freecad.org/file_download.php?file_id=1674&type=bug
    Notes
    (0009672)
    Kunda1   
    2017-07-05 20:27   
    @HoWil how does this relate to addon-manager?
    (0009733)
    Kunda1   
    2017-07-12 12:23   
    @HoWil ping
    (0010181)
    wmayer   
    2017-09-25 08:27   
    The pad has a property called Profile which links to an object and a face. The editor needs to be extended to allow to re-assign a different value.
    (0016552)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5717.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3067 [PartDesign] Feature minor N/A 2017-06-02 17:36 2021-02-06 06:43
    Reporter: abdullah Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Add Mirror body tool to PartDesign
    Description: Create a new separate body that is symmetric to the original body and depending on it, so that the second can have some extra features but still change with the original one. In this case an automatic fuse is not desired, as they are intended as separate parts of an assembly.

    Tags:
    Steps To Reproduce:
    Additional Information: Not to be confused with ticket 2863 which requests mirroring a body but to fuse the result inside the existing Body container.
    Attached Files:
    Notes
    (0009429)
    normandc   
    2017-06-17 23:31   
    Why did you keep the same title as the 2863 ticket? It is not a feature anymore, it's a separate body.

    And would such a tool be really needed? This is exactly what the current Part Mirror tool does.
    (0009453)
    Kunda1   
    2017-06-18 19:39   
    @abdullah asked me to clone this ticket and it's on his agenda to rename it
    (0009455)
    abdullah   
    2017-06-19 13:44   
    (Last edited: 2017-06-19 13:46)
    @normandc

    Creating this ticket is my fault.

    I can tell you why I thought I needed it. I was doing an enclosure consisting of two parts (first result-part and second result-part) almost symmetric about a plane, attaching with bolts/nuts.

    I was solving this by creating a body with the common symmetry, then I would part refine that common part and I would start a second part on that part feature to add the differences of the first result-part and I would part-mirror the refined common part and do a third part to add the differences of the second result-part.

    By doing a refine I was losing any connection between the common part body and the two results, so that I could not modify them afterwards. So I felt the need of it.

    Now I realise that if I use autorefine, I can just start a first body with the common part. At a given feature, I can part-mirror that feature and start a second body from that result (without refining). I can then continue the first body with the non-common parts of the first half. Now if I modify anything before that feature where the common part stops, everything gets updated just fine.

    Maybe the end result tree is not the cleanest, however the functionality is there. I just wanted the functionality.

    Now, if after reading this you have any input for me, then we may see if we need a new feature or not. If we do not need it, we may well close this ticket.

    (0009569)
    normandc   
    2017-06-28 05:11   
    I just realized that I asked for a similar thing on the forum.
    https://forum.freecadweb.org/viewtopic.php?f=8&t=23144
    (0009628)
    normandc   
    2017-07-01 05:59   
    Changed summary to replace "feature" with "tool" and better differentiate this ticket from 0002863. This one would not create a feature under an existing Body, but create a new mirrored Body linked to the original.
    (0009629)
    normandc   
    2017-07-01 06:04   
    An alternative to creating a new tool was discussed with @ickby in the topic linked in comment c9569: expand the existing ShapeBinder command to create a solid when the original selection is a solid, and to have the option to mirror the ShapeBinder copy along a standard datum plane.
    (0012748)
    normandc   
    2019-02-24 16:17   
    I've had a recent thought about this. It is currently possible to use a Body as Base Feature of another Body. This cannot be done directly, but through the Body's Base Feature property. This is a useful method to build variations of parts, see https://forum.freecadweb.org/viewtopic.php?f=20&t=33841#p288657

    What if the Base Feature was expanded to have a mirror option? I'm not sure how that would work out. Maybe create a new menu entry for creating a base feature based on another Body, and open a dialog in the Tasks tab that allows different options: mirrored from a plane inside the new Body, or even scaled? I know that scaling is already possible through a Draft Clone, but this is clunky and messes the tree, as you need to create a new Body with the clone as base feature.
    (0016540)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5705.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3065 [PartDesign] Bug major always 2017-06-01 23:08 2021-02-06 06:43
    Reporter: abdullah Platform:  
    Assigned To: OS:  
    Priority: high OS Version:  
    Status: assigned Product Version: 0.17  
    Product Build: Resolution: reopened  
    Projection: none      
    ETA: none Fixed in Version: 0.17  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Part::checkIntersection returns false negatives preventing functioning of PDN Mirror transformation when faces just touch
    Description: Problem 1

    Part::checkIntersection first uses first_bb.IsOut(second_bb) for a quick test. However, this function is known to fail in cases of touching (there is even a previous comment in the code). Mirror transformation explicitly asks that touching to be considered intersection. Therefore it is wrong to rely on this test.

    Problem 2

    The Extrema method implemented in Part::checkIntersection fails:

    Case 1: When mirroring a feature that just touches, it sometimes fails because BRepExtrema_DistShapeShape returns BRepExtrema_IsVertex instead of BRepExtrema_IsInFace, so the manyfold detection mechanism fails to identify a non-manyfold case. In one example, instead of InFace it returns 4 Vertex: [0, 5.5, -2.5], [0,5.5,2.5], [1E-15, 13, -2.5], [1E-15, 13, 2.5] for Support1 and [0, 5.5, -2.5], [0,5.5,2.5], [-1E-15, 13, -2.5], [-1E-15, 13, 2.5] for Support2. I am unsure if this can be somehow reused.

    Case 2: When doing a multitransformation to create a part out of a quarter like here:
    https://forum.freecadweb.org/viewtopic.php?f=19&t=22747#p176513

    The extrema method provides a separation (notable, in the order of milimeters) in operations with intersection parts. This may be a consequence of which parameters we are passing the to function.

    OTHER ISSUES

    Some related problems not directly related to the extrema method, but that seem to be related:
    https://forum.freecadweb.org/viewtopic.php?f=19&t=22747#p176509
    Tags: Mirror transformation
    Steps To Reproduce: EXAMPLE 1

    1. Load the attached file.

    2. Activate the first body

    3. Select the pad and add a Mirror transformation (you can try directly the mirror, or a multi-transformation, vertical+horizontal to see the different cases)

    EXAMPLE 2

    1. Load the attached file

    2. Activate the second body

    3. Select the pad and mirror or multi-transform mirror the pad
    Additional Information: https://forum.freecadweb.org/viewtopic.php?f=19&t=22747
    Attached Files: Helix_Mirror2.fcstd (17,168 bytes) 2017-06-01 23:08
    https://tracker.freecad.org/file_download.php?file_id=1626&type=bug
    Notes
    (0009441)
    kkremitzki   
    2017-06-18 03:49   
    @abdullah should this be resolved now that FreeCAD Pull Request 816 has been merged?
    (0009454)
    abdullah   
    2017-06-19 12:49   
    Yes, this ticket is to be closed as fixed by that PR
    (0009459)
    Kunda1   
    2017-06-19 17:12   
    Thanks! Closed.
    (0009522)
    abdullah   
    2017-06-25 09:36   
    (Last edited: 2017-06-25 09:36)
    The boolean check method fails in some circumnstances where the extrema method success. For example:

    https://forum.freecadweb.org/viewtopic.php?t=23029#p178800

    The result is that "the shape does not intersect support" is generated, when the real problem is OCE/OCCT can not make a proper fusion of those valid and perfectly intersecting objects.

    IMO it is not ok to inform that something that clearly intersect does not. So this is a bug.

    The final outcome in these cases should be: no error because it does intersect, and a resulting bad solid because it is what OCC gives back. This can be solved by a three phase checking (instead of a two phase one):

    1.Quick check
    2. Extrema
    3. If Extrema says it does not intersect (sometimes because of the non-manifold detection failure), boolean check.

    In case of OCC>6.9.0, this checkIntersection, as well as all the fusing in PDN should probably be upgraded to use generalFuse (same as Part boolean fragments fuse).

    (0010435)
    DeepSOIC   
    2017-11-20 10:08   
    (Last edited: 2017-11-20 10:10)
    How about avoiding the check altogether? I.e., mirror, then fuse, then check the result of fusion (it should remain a single solid; if it doesn't -> show the "does not intersect support" message to user).

    Another option is to drop the single-solid limitation altogether. Then, the check can also be removed.

    (0010674)
    abdullah   
    2018-01-02 17:56   
    @DeepSOIC

    Good to hear from you :)

    What we have currently in master seems to work well. I am not sure if I "fixed" this, or what exactly went on (I can not remember).

    I have just updated the target version to 0.18 to get it out of the 0.17 roadmap, as this is no urgent matter.

    I do not close the ticket. I will eventually come back to this and assess it again.
    (0013009)
    Kunda1   
    2019-04-06 19:15   
    Changing ticket status from 'feedback' to 'assigned'
    (0016539)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5704.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3028 [PartDesign] Feature feature always 2017-05-13 12:49 2021-02-06 06:43
    Reporter: Kunda1 Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: [PartDesign] Per face colors and keeping colors when adding a feature
    Description: Hi,

    This is a cloned version of an old ticket to keep part of the original feature request.

    - Per face colors in PDN.
    - Keep preexisting per face colors of a solid when adding a feature (such as Pad, Pocket, Groove, Revolution, and Patterns).

    Original request by Petar
    Tags: colors
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0008986)
    mrlukeparry   
    2017-05-13 12:49   
    Wouldn't this be part of the new PartDesign? I haven't used it for a while. Shouldn't only the Body Feature be the only feature that can have the material properties set...
    (0008987)
    Kunda1   
    2017-05-13 12:49   
    Abdullah wrote:
    I am not sure of the current applicability of this issue:
    1. Keeping transparency, I just fixed this a couple of days ago.
    2. Per face colors, I do not think it is currently possible with PD NEXT (I do not know how at least).

    Maybe this feature request should be updated/rewritten in line with the current user requirements for v0.17 PD NEXT.


    @Abdullah what commit did you add for number 1?
    Since this ticket is old I'm not sure @pperisin will respond to point number 2. How to proceed if not?
    (0008988)
    abdullah   
    2017-05-13 12:49   
    https://github.com/FreeCAD/FreeCAD/pull/685

    Face per color is a feature PD should have. So I think that a feature request asking for this is appropriate.

    We should have a procedure for those cases where part of a bug is fixed but not the whole and the same for feature request. Something like splitting a ticket into two, so that one can be marked as fixed while the other remains open. Or a new ticket deriving from an old one...
    (0008989)
    Kunda1   
    2017-05-13 12:49   
    @abdullah I'd be happy to clone this ticket and you can edit the clone so that it's rewritten correctly to PDN specs?
    (0008990)
    abdullah   
    2017-05-13 12:49   
    @kunda1

    Sure!! Give me the new ticket number and I will edit it.
    (0009170)
    Kunda1   
    2017-05-27 19:18   
    @Abdullah here is the cloned ticket of 0000848
    (0009172)
    abdullah   
    2017-05-27 20:29   
    @kunda1

    I acknowledge I have been notified. I will take action in due time.
    (0011317)
    Kunda1   
    2018-05-30 23:47   
    linked 0001626 to this ticket as well
    (0016531)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5696.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2863 [PartDesign] Feature minor N/A 2017-01-15 21:08 2021-02-06 06:43
    Reporter: normandc Platform:  
    Assigned To: ickby OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Add Mirror body feature to PartDesign
    Description: The current ParDesign Mirrored feature only mirrors selected feature(s).

    A new mirror feature that mirrors the whole body would be really useful in the design of symmetrical parts. At this time the Part Mirror tool can be used but it forces the user to leave the PartDesign workflow, requires an additional step of creating a Part Fuse, then having to import the resulting Fusion as a base feature inside a new Body.

    The new "Mirror body" feature should automatically fuse the mirror copy to the main body to follow the single body rule.
    Tags:
    Steps To Reproduce:
    Additional Information: I think this tool should not require a selection before launching it. It would simply take the active body, mirror it and fuse the copy, then add a "Mirror body" feature to the Body tree.

    Maybe the existing "Mirrored" feature will need to be renamed to avoid confusion...
    Attached Files:
    Notes
    (0007819)
    ickby   
    2017-01-16 09:58   
    I thought of extending the current transformation tools like mirror a bit. By default they would use the whole body instead to the selected features as currently. Than the feature list in the task dialog would be called "Restrict to following features:".

    Would you think this is intuitive, or is this too much functionality in the tools and would become confusing? I personally like having one tool for a operation and this tool to support specific subtasks, and "mirror" I would use for both, mirroring the whole part as well as individual features.
    (0007820)
    thor   
    2017-01-16 16:48   
    Separate "mirror feature(s)" and "mirror body" would be OK, though increasing the number of menu and toolbar items is a drawback.

    If it becomes integrated, I think it should be radio buttons for "Body" and "Feature(s)", the later followed by a list of the features. This way, it is spelled out what either does and it stays in line with how a user would likely describe the intention: either "I want to mirror the body", or "I want to mirror a feature (or features)", rather NOT "I want to restrict mirroring to the following feature(s)".
    (0008860)
    Kunda1   
    2017-05-02 21:31   
    I asked Abdullah if
    can some of the mirroring code that you've implemented recently be leveraged against this feature (0002863) and also 0002235 ?

    Abdullah's response:
    Not really. The mirror code I wrote is for sketcher geometry. This is the mirror of a part design feature. Has to be tackled in the Part Design WB.
    (0009255)
    abdullah   
    2017-06-02 13:55   
    Maybe also another related "feature option" (in addition to the ticket): Do a separate body that is symmetric to the original body and depending on it, so that the second can have some extra features but still change with the original one. In this case an automatic fuse is not desired, as they are intended as separate parts of an assembly.
    (0009256)
    Kunda1   
    2017-06-02 14:03   
    (Last edited: 2017-06-02 14:03)
    @Abdullah shall I open a new Feature Request then ?

    (0009259)
    abdullah   
    2017-06-02 17:28   
    @kunda1

    I was weighting it, it that it is different, but unsure because it may be implemented together. Some hours later and after some sunshine I would say that: yes, please, open a new feature request and link it to this one as related. Thanks for keeping an eye ;)
    (0009267)
    Kunda1   
    2017-06-02 17:41   
    Created and linked 0003067
    (0009430)
    normandc   
    2017-06-17 23:33   
    Setting target version to 0.17 to make it appear in the roadmap, if it proves impractical we can always bump the target version.
    (0012208)
    normandc   
    2018-11-17 20:25   
    @ickby if you do not expect to return to PartDesign workbench development for the foreseeable future, wouldn't it be relevant to unassign this report and other PartDesign reports that were assigned to you?
    (0016513)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5678.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2510 [PartDesign] Feature feature N/A 2016-04-16 10:13 2021-02-06 06:43
    Reporter: cox Platform:  
    Assigned To: OS:  
    Priority: low OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Request for attachment mode for a plane on a cylinder etc.
    Description: I would like to see a feature where one can attach a point,line plane on a sphere, cylinder, cone and preferably any other surface(sounds difficult)

    As discussed in http://forum.freecadweb.org/viewtopic.php?f=10&t=15207&p=121813#p121813
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016487)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5652.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2220 [PartDesign] Feature minor have not tried 2015-08-18 17:16 2021-02-06 06:43
    Reporter: bluemirage335 Platform: X220_ThinkPad  
    Assigned To: OS: Arch Linux  
    Priority: normal OS Version: current  
    Status: new Product Version: 0.15  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Extrude contours (sketch regions).
    Description: Modern CAD programs allow specific regions of sketches to be extruded, rather than placing rigorous requirements on the sketch.
    Tags:
    Steps To Reproduce:
    Additional Information:
    System Description
    Attached Files: example.png (117,788 bytes) 2015-08-18 17:16
    https://tracker.freecad.org/file_download.php?file_id=1065&type=bug
    Notes
    (0016468)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5633.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2037 [PartDesign] Feature feature N/A 2015-04-07 15:04 2021-02-06 06:43
    Reporter: larsen Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.14  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Fillet to maximum possible value
    Description: As a simple example, take a box where one corner is already filleted. Now, when I want to fillet a neighboring corner, that fillet is limited by the first one. I can enter values and FreeCAD will show the new fillet, but when the entered value is too big, nothing will happen (no preview, no warning message). I could enter "999 mm" and FC simply wouldn´t create the fillet. I then have to reduce the value to find out what maximum I can use.

    It would be convenient if FC replaced "999" by the maximum possible value (or used this as the maximum wanted valued in case the maximum possible value would change afterwards).
    Tags: fillet
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016455)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5620.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2003 [PartDesign] Feature minor have not tried 2015-03-12 20:34 2021-02-06 06:43
    Reporter: triplus Platform: Linux  
    Assigned To: OS: Ubuntu  
    Priority: normal OS Version: 14.04  
    Status: feedback Product Version:  
    Product Build: Resolution: reopened  
    Projection: none      
    ETA: none Fixed in Version: 0.17  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Embossing/imprinting an FC logo directly to a solid model
    Description: An idea came to life while taking on the Logo challenge:

    http://forum.freecadweb.org/viewtopic.php?f=8&t=9468&start=40#p79679

    There should be a tool in Part/PartDesign WB allowing the user to easily tag the part with FreeCAD logo.
    Tags: #post-to-forum
    Steps To Reproduce:
    Additional Information:
    Attached Files: TAG.png (17,490 bytes) 2015-03-12 20:34
    https://tracker.freecad.org/file_download.php?file_id=946&type=bug
    Notes
    (0008213)
    normandc   
    2017-02-04 18:16   
    This feature request is not related to just closed issue 0002887.

    This is about embossing/imprinting a FreeCAD logo directly to a solid model which may be interesting when 3D printing it.

    Although this could be easily addressed with a macro, IMO this report should be reopened.
    (0008214)
    Kunda1   
    2017-02-04 21:03   
    Re-opened per @NormandC's request.
    (0008215)
    Kunda1   
    2017-02-04 21:06   
    Renamed ticket for better comprehension
    (0008216)
    wmayer   
    2017-02-04 22:34   
    What's the point of having a specialized command for it, then?
    (0008217)
    normandc   
    2017-02-04 22:56   
    (Last edited: 2017-02-04 22:59)
    I'm not sure how triplus envisioned this feature.

    Yes, a macro could do the job, but a menu entry would be more user-friendly. Arch has a Utilities menu that contains tools that do not immediately appear to be relevant to Arch.

    Whether the menu calls a native C++ function or a python macro, or if its place is in the Part workbench or somewhere else is a matter to be discussed.

    This tool could behave like a Draft Shapestring and create a single parametric object containing 2 faces (the F and the gear) that you can extrude, pad or pocket (which means it should be possible to attach it to a solid, just like Draft Shapestring). This FC logo object would have a scale property.

    It's also not unlike the Involute gear utility in the Part Design menu.

    In such form, maybe the best place for it would be the Draft workbench?

    Another more involved alternative would be to give it a fully automated creation method including padding/pocketing process, but that is a high-level function that would not be suited to the Part workbench and may be a bit too specialized for the Part Design workbench.

    Since this feature would in fact promote FreeCAD it would be useful to offer it natively.

    (0010176)
    Kunda1   
    2017-09-24 19:51   
    @triplus please weigh in at your convenience...thanks!
    (0016452)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5617.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1987 [PartDesign] Feature feature N/A 2015-03-01 18:26 2021-02-06 06:43
    Reporter: pfirszt Platform:  
    Assigned To: OS:  
    Priority: none OS Version:  
    Status: new Product Version: 0.14  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Map a sketch to a face behaviour improvement
    Description: Current workflow to map a sketch on a face (correct me please if I'm wrong):
    1. Select face
    2. Click "Map a sketch to a face" icon
    3. Select sketch frem a drop down list.

    I trink that selecting one face and one sketch should allow to map it without showing the drop down list, so
    1. Select one face and one sketch
    2. Click "Map a sketch to a face" icon

    I found myself canceling the mapping quite often when I'm not sure if i.e I want Sketch001 or Sketch005 to be mapped.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0010979)
    normandc   
    2018-02-25 07:43   
    IMHO this can be bumped to 0.18.
    (0016451)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5616.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1942 [PartDesign] Feature feature N/A 2015-01-31 14:12 2021-02-06 06:43
    Reporter: arust Platform:  
    Assigned To: eivindkvedalen OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Allow optical+physical material properties in addition to RGB color specification
    Description: Advanced spectral renderers (like LuxRender and to some extend Povray) do not use RGB internally, but physical spectral reflection, refraction, emission properties, given for example as color temperature, spectrum texture or look-up table[1], lamp-vendor-provided IES file[2], and physical refraction and reflection indices.[3]

    In addition to specify plain RGB color, shininess and translucency which were fine in the time of "classical" fixed-function OpenGL not using actual shaders and programmable shaders implementing the traditional Phong lighting model, it is desirable to specify physical optical properties, which are supported by LuxRender, Povray and other advanced rendering engines.

    [1] http://www.luxrender.net/wiki/LuxRender_Textures_Spectrum
    [2] http://www.luxrender.net/wiki/LuxRender_Lighting#IES_data
    [3] http://www.luxrender.net/wiki/Scene_file_format_dev#Material
    Tags: colors, IFC
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0007605)
    clel   
    2017-01-10 15:31   
    I support the request, makes sense and is used in common CAD systems.
    (0007617)
    eivindkvedalen   
    2017-01-10 18:48   
    Work in progress: http://forum.freecadweb.org/viewtopic.php?f=10&t=16714
    (0007619)
    Kunda1   
    2017-01-11 01:33   
    Should this ticket be assigned to you then, @eivindkvedalen ?
    (0008332)
    Kunda1   
    2017-02-17 11:22   
    Test branch is at https://github.com/eivindkv/FreeCAD2/tree/Material
    (0017151)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6320.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1802 [PartDesign] Feature feature have not tried 2014-10-26 08:35 2021-02-06 06:43
    Reporter: Pauvres_honteux Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Add Devil (rounded, angled and tapered contact surface with a round hole in it)
    Description: I'd like to propose a feature that takes away the effort from the user to make a so called "Devil". It's the rounded, angled and tapered contact surface with a round hole in it:
    http://1.bp.blogspot.com/-xV7VHydI7F0/U52tHzHMg3I/AAAAAAAAdAY/GprPZqbatiY/s1600/1.jpg

    With a bit of good will you may see it here too:
    http://www.plmmarketplace.com/blog/content/binary/actas-mpa.png
    Tags: fillet, variable fillet
    Steps To Reproduce:
    Additional Information: I may make one at work for a really good close up picture to attach.
    Attached Files: Devil_1.tar.xz (2,280,832 bytes) 2014-11-02 19:11
    https://tracker.freecad.org/file_download.php?file_id=853&type=bug
    Devil_2.tar.gz (3,137,274 bytes) 2014-11-02 19:11
    https://tracker.freecad.org/file_download.php?file_id=854&type=bug
    Devil_FC.fcstd (24,331 bytes) 2014-11-02 19:12
    https://tracker.freecad.org/file_download.php?file_id=855&type=bug
    Notes
    (0005255)
    yorik   
    2014-10-26 15:31   
    It's interesting, but I think you should describe much better all the particularities, properties and behaviours such feature should have, to interest a developer in coding it.
    (0005256)
    Pauvres_honteux   
    2014-10-26 16:18   
    Hi Yorik, I'll do my best. Just hang in there! =O)
    (0005270)
    Pauvres_honteux   
    2014-11-02 20:22   
    (Last edited: 2014-11-02 20:25)
    Now, I tried it in FC and failed. So I did it at work in the cognac soaked programme.
    I tried to make one picture per step as I went along, but I'm pretty sure I missed some steps here and there (my eyelids were almost touching my knees...).

    The tricky part comes when the two cones radii are touching each other. I had to make radii without the cutting operation (as one normally does) in one step. When all fillets / radii where made I had to cut all surfaces and then join them. If one makes different radii on all surfaces it's no problem, but all radii equal spells trouble.

    (0005271)
    Pauvres_honteux   
    2014-11-02 20:24   
    First of all: note that everything is done oversized, one shall always make sure all constituent parts, with guarantee, cross each other, no matter how much you change your parts later on.

    The first 7 pictures just shows how I build up the double curved surface, including a bunch of intersections for easier visual orientation.

    Picture 8 -> 13 shows how to make a common point, projection line, intersection point, planes for placing sketches on and a contact surface width common point.

    Picture 14 -> 17 show how I build up the first cone including the projection of "the common point for surface width" and constrain it to the profile to revolve. Then cone 1 is split by the common plane.

    Picture 18 -> 20 shows the second cone, which is made in the same way as the first one.

    Picture 21 -> 23 shows the making of the "real" contact surface.

    Picture 24 -> 26 shows the making of the hole cutting feature.

    Picture 27 -> 30 shows the making of a "loose" fillet (Trim support 1 [and 2] are deactivated) so one later can make boundaries and later still extract one of them for the purpose of cutting a hole in the double curved surface.

    Picture 31 -> 38 shows the making of the second cone and its constituent contact surface with related radius and boundaries.

    Picture 39 shows the making of the "real connected" radius between first cone and double curved surface by joining them.

    Picture 40 -> 46 shows the making of the second cones radius with the same technique as before.

    Picture 47 -> 52 shows gradual visual transition to ready surface with everything tangent.

    Picture 53 -> 56 shows the tangency problem areas.

    Picture 57 -> 60 shows the power of this modelling technique.
    (0005272)
    Pauvres_honteux   
    2014-11-02 20:36   
    I have in mind a function that takes one point on a surface as parameters, i.e. point and surface.
    And then asks for the contact surface radius/diameter and plane.
    And yet again for draft angles and radii.

    Hope this straightened some question marks?
    (0007639)
    Kunda1   
    2017-01-11 18:27   
    Updated title of ticket for better comprehension
    (0008972)
    Kunda1   
    2017-05-12 12:29   
    @yorik can you weigh in on this ticket?
    (0009045)
    yorik   
    2017-05-18 02:11   
    Well you can probably already do something like that in FreeCAD with surfaces, but there could be a tool or macro to automate it, if someone wants to code it.
    (0009046)
    Kunda1   
    2017-05-18 02:42   
    @mario52 interested? Or perhaps propose this as a macro writing challenge?
    (0009504)
    Kunda1   
    2017-06-24 11:09   
    @Pauvres_honteux we lost the attachments to this ticket as well :(
    Care to recreate?
    (0009517)
    Pauvres_honteux   
    2017-06-24 13:04   
    @Kunda1 ,
    I'll check mi dungeon, I might have some luck...
    (0009535)
    Kunda1   
    2017-06-26 12:41   
    @Pauvres_honteux Another way to get this done is to build this as a macro yourself and then add to the FreeCAD-macro repo for others to download. What do you think?
    (0009554)
    Pauvres_honteux   
    2017-06-27 05:06   
    @Kunda1, as of now, to me it seems as the compressed tape archives I originally posted are back and working!
    If they go away again, gimme a ping! =O)
    (0009555)
    Pauvres_honteux   
    2017-06-27 05:10   
    Hmm, macro ye say? Mi n' macros... Let me put it this way, we know where we have each other...
    (0016436)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5601.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1801 [PartDesign] Feature feature have not tried 2014-10-26 07:41 2021-02-06 06:43
    Reporter: Pauvres_honteux Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Ball corner
    Description: I'd like to propose a feature called "ball corner".
    As I saw dubstar-04 starting on variable fillets I thought this would be one step closer to become reality, although it might be a feature on its own.

    A principally example: http://www.dkszone.net/wp-content/uploads/2010/05/CATIA_Part_with_blended_corner_Edge_Fillet_7_.jpg
    Tags: #post-to-forum, ball corner, variable fillet
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0009505)
    Kunda1   
    2017-06-24 11:12   
    @Pauvres_honteux please post to forum and bi-directionally link ticket<=>thread so people associate one to another. Thx!
    (0009516)
    Pauvres_honteux   
    2017-06-24 12:59   
    Variable radius fillet
    (0009536)
    Kunda1   
    2017-06-26 13:03   
    @Pauvres_honteux I bumped the forum thread. Too bad that user (dubstar) didn't share his work. Let's see what happens.
    (0016435)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5600.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1567 [PartDesign] Feature minor N/A 2014-05-30 15:41 2021-02-06 06:43
    Reporter: bejant Platform:  
    Assigned To: wmayer OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: trunk  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Request for Ability to Trim Surfaces in Part and Part Design WB's
    Description: The ability to trim a surface based on it's intersection with another surface would be a time-saver when modelling. For example in the attached screen grab it would be handy to be able to trim off the upper part of the vertical surface above the horizontal surface in a point and click manner.

    From the following forum thread:
    http://forum.freecadweb.org/viewtopic.php?f=3&t=6706

    Tags: trim
    Steps To Reproduce:
    Additional Information:
    Attached Files: 20140530a_Surface Trim.png (8,116 bytes) 2014-05-30 15:41
    https://tracker.freecad.org/file_download.php?file_id=762&type=bug
    Notes
    (0016422)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5587.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1262 [PartDesign] Feature feature always 2013-10-01 19:24 2021-02-06 06:43
    Reporter: mntc Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Smart tools for part design (Grow, Lattice, Snap&Lock, Split to mill, Convert to Frame, Puzzle)
    Description: This can be a new group of automatic design tools.

    1) "Grow": Sometimes up to 99% of engineers work is dedicated to bulding bulk bridge connection between active components (motors, actuators, etc). Sometimes it is boring and evident work. What if we could specify contact faces and spatial limitations, and "grow" between them part like a plant (may be with help of cellular automata mathematics). There can be preferences like "optimize weight/stiffness/volume/etc" or "style: frame/tree/box/etc"

    2) "Lattice": used like "Pocket", but not cuts, but converts corresponding volume to 3D lattice of arbitrary pattern. It can easily produce springy and spongy areas in 3D-printable parts.

    3) "Snap&lock": convert bulk part (with only flat faces) to set of flat walls (with used defined thickness) assembled by snap'n'lock principle. It can make easy design of lasercut boxes.

    4) "Split to mill": splits freeform part to set of parts which can be milled on common 3D CNC milling machine fron one side. E.g. sphere will be split to 2 halves.

    5) "Convert to Frame: reduces weight and material volume by substracting lots of material with specific algorithm

    6) "Puzzle": splits big flat parts to small fragments with puzzle-like connections. Used to make big things on small CNC and lasercut machines.
    Tags: snap, split ticket
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0008903)
    Kunda1   
    2017-05-07 14:48   
    @kkremitzki should I split this ticket?
    (0008906)
    kkremitzki   
    2017-05-07 23:03   
    @Kunda1 No, I think it's fine as is. If one of the individual tools starts getting worked on, then it would be appropriate to create a new issue to track that effort.
    (0009159)
    Kunda1   
    2017-05-26 21:31   
    Per @DeepSOIC
    [quote="DeepSOIC"]
    I think the suggested "Lattice" feature is impractical, because it will generate a very heavy and complex b-rep, that will not help at all in the end because it will simply confuse slicers.

    I think such a feature can make sense only in tight integration of some slicer, in a form of creating a compsolid-like geometry.[/quote]
    (0016407)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5572.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1192 [PartDesign] Feature feature always 2013-07-31 15:49 2021-02-06 06:43
    Reporter: din743 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: acknowledged Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Full round fillet
    Description: Option to create a fillet that is tangent to three adjacent faces.
    Tags:
    Steps To Reproduce:
    Additional Information: Example from another CAD package: http://help.solidworks.com/2013/English/SolidWorks/sldworks/r_Full_Round_Fillets.htm
    Attached Files:
    Notes
    (0003438)
    normandc   
    2013-08-02 19:13   
    (Last edited: 2013-08-02 19:13)
    This might require to fix bug 0000938 first.

    (0016404)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5569.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1190 [PartDesign] Feature minor always 2013-07-27 14:07 2021-02-06 06:43
    Reporter: vnks Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: acknowledged Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Option for PolarPattern to obey individual UpToFirst/UpToLast/UpToFace pad features for each instance.
    Description: Hi,

    Applying a polar pattern to a pad feature in Part Design, it appears that the length is taken from the original feature instead of padding each individual rotated feature to first/last/specific face. In the attached design, if you look inside the hollowed out part, you can see that the two poles, meant to hold screws, are the same height, instead of extending up to the 'ceiling' per 'UpToFirst' pad feature.
    Tags: PolarPattern
    Steps To Reproduce:
    Additional Information:
    Attached Files: polar_bug.fcstd (64,128 bytes) 2013-07-27 14:07
    https://tracker.freecad.org/file_download.php?file_id=528&type=bug
    Notes
    (0009232)
    Kunda1   
    2017-05-31 22:19   
    @Abdullah when you get a moment please check this ticket. Thanks!
    (0009340)
    abdullah   
    2017-06-10 23:29   
    @kunda1

    I think I understand what the reporter wanted to do. I am not sure how this should actually work.

    The first pad goes up to first. Now, I am not sure whether the transformation should "recompute" where it should end or not. I mean, I understand it would be useful for the case of the reporter. I simply do not know how general such a case is.

    I think it is worth to involve one of the CAD experts to gather more information about user requirements.
    (0009427)
    normandc   
    2017-06-17 21:46   
    I'll test in the commercial CAD software I use at work and report back.
    (0009428)
    normandc   
    2017-06-17 21:49   
    FYI, there is a simple workaround here since there are only two occurrences, delete the polar pattern and add a second circle in Sketch016031002. Two posts will be created up to the face of the inner loft.
    (0009479)
    Kunda1   
    2017-06-21 10:51   
    @vnks please respond
    (0009863)
    normandc   
    2017-08-02 11:02   
    (Last edited: 2017-08-02 11:02)
    Forgot to report back. In the commercial parametric CAD program I use at work, the behaviour is as the reporter is asking. The transformation is recomputed according to the ending condition of the original pad.

    Maybe this could be considered an enhancement request rather than a bug.

    (0009868)
    Kunda1   
    2017-08-02 14:00   
    Changed to 'Feature'
    (0011321)
    Kunda1   
    2018-05-31 00:31   
    Opened forum thread for further discussion: https://forum.freecadweb.org/viewtopic.php?f=8&t=29035
    (0011971)
    Kunda1   
    2018-10-08 14:17   
    @NormandC how would you rename this ticket to reflect that it's a feature instead of something missing in FC ?
    (0012831)
    Kunda1   
    2019-03-03 14:19   
    Renamed ticket title per the chrisb's recommendation in the forum
    (0016403)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5568.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    622 [PartDesign] Feature feature have not tried 2012-03-05 21:17 2021-02-06 06:43
    Reporter: electronlibre Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version: 0.12  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Add taper angle feature in pad and pocket
    Description: It would be nice to have a taper angle option in pad and pocket tools (Part design workbench), similar to that on Extrude (Part WB).
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files: TaperAngle_Pad.patch (27,938 bytes) 2012-04-29 05:53
    https://tracker.freecad.org/file_download.php?file_id=219&type=bug
    Notes
    (0002058)
    Jriegel   
    2012-05-18 10:38   
    Patch applied to Assembly branch!

    Works well!

    To be done -> Use code in Pocket
    (0002156)
    helo10   
    2012-06-08 11:26   
    in progress
    (0002845)
    jrheinlaender   
    2013-01-13 14:32   
    V0.13 now has a PartDesign::Draft feature which allows to select faces and apply a draft angle to them.

    This is not the same functionality as that requested, but will lead to the same result.

    I am not sure whether we should put even more options into the Pad/Pocket features. When I modelled for customers from the German automative industry, they insisted on always having draft in a separate feature.
    (0002846)
    Jriegel   
    2013-01-13 14:39   
    Draft can be done Pocket/Pad for easy and simple cases. If you want to have more control Pad/Pocket get for sure overloaded.
    I think both make sense. A one angle solution in the basic features and a own feature for the more sophisticated (future) solutions..

    I have generally no problem if there are overlapping features functionality.
    May the better win!
    (0016388)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5553.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4498 [PartDesign] Bug feature always 2020-11-21 06:41 2021-02-06 06:43
    Reporter: robotarmy Platform: x86  
    Assigned To: OS: Mac OS  
    Priority: normal OS Version: 10.15.7 (19H2)  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: macOS 10.15
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.22756 (Git)
    Build type: Release
    Branch: master
    Hash: ce87f586ee36ffe8ebcdcd3947ced4ab389ae795
    Python version: 3.8.6
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: C/Default (C)
    Summary: Loft between sketches with inner and outer elements created in different order results in bad 3D geometry
    Description: When creating a loft, the order the sketch elements are created should not matter, but it does.

    Take the case of lofting between two sketches, with two circles each, for example, to make a kind of cylinder. In one sketch the inside was created first, and in the other sketch the outside was created first, the loft tries to cross over itself resulting in zero thickness geometry and a 'black part'.

    See forum post https://forum.freecadweb.org/viewtopic.php?p=449244#p449244
    See updated limitations on wiki page for PartDesign Loft: https://wiki.freecadweb.org/index.php?title=PartDesign_AdditiveLoft&type=revision&diff=794134&oldid=763800

    Thanks!
    Tags: #pending-forum, Loft
    Steps To Reproduce: See attached file
    Additional Information:
    Attached Files: vacuumadapter.FCStd (129,174 bytes) 2020-11-21 06:41
    https://tracker.freecad.org/file_download.php?file_id=2564&type=bug
    Notes
    (0016963)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6130.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4484 [PartDesign] Bug minor always 2020-11-03 17:31 2021-02-06 06:43
    Reporter: openBrain Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Ubuntu 18.04.5 LTS (KDE/plasma)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.22894
    Build type: Release
    Branch: master
    Hash: 9eb080488d970d313c538473e7272117ea0a7cd1
    Python version: 3.6.9
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: French/France (fr_FR)
    Summary: ShapeBinder can or not be padded depending on pad type
    Description: When trying to pad a ShapeBinder :
    • If pad type is "Dimension", I can well pad a ShapeBinder.
    • If pad type is "To first", FreeCAD rejects it with the error message "Linked object is not a Sketch or Part2DObject".
    Forum discussion
    Tags:
    Steps To Reproduce: Cf. forum
    Additional Information:
    Attached Files:
    Notes
    (0016958)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6125.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4417 [PartDesign] Bug minor always 2020-08-05 07:02 2021-02-06 06:43
    Reporter: TedM Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 10 (10.0)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.22130 (Git)
    Build type: Release
    Branch: master
    Hash: dc65b055e5143a7d7349520da466d4d722df57e8
    Python version: 3.8.5
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: English/United States (en_US)
    Summary: Additive/Subtractive Pipe while in wireframe view leaves multiple features visible
    Description: Creating an AdditivePipe or SubtractivePipe while in wireframe draw style results in both the Pipe feature and the previous tip feature being visible (in model view, both are shown visible and they overlap in the 3D view). (I've also seen this happen when working in No-shading draw style, but it doesn't always happen.)

    In addition, at this point, toggling visibility of these features is incorrect. Toggling the new tip (the Pipe) has no effect on the visibility of the previous tip. Toggling the previous tip the first time removes it from the 3D view but it remains visible in the model view. From then on, toggling the previous tip works correctly.

    This has been reproduced in other 0.19 versions but cannot be reproduced in 0.18.4.
    Tags:
    Steps To Reproduce:
    1. Create new document.
    2. Go to Part Design WB.
    3. Create new body.
    4. Create new sketch on XY plane.
    5. Place a 20mm x 20mm square centered on origin and close sketch.
    6. Pad it 20mm.
    7. Create a second sketch on XY plane.
    8. Place a 10mm x 10mm square centered on the origin and close sketch.
    9. Change attachment to Z=21mm.
    10. Create a third sketch, this time on the XZ plane.
    11. Create a vertical line, bottom end on Y axis and 10mm above the origin and length 21mm and close sketch.
    12. At this point, you have a 20x20x20mm cube with a 10x10mm square sketch floating 1mm above and a line sketch coming up through the top of the cube and ending in the center of the square. This is what is in the attached file.
    13. In the model view, make sure the pad and both sketches are visible.
    14. (Optional, but probably required) Switch draw type to wireframe.
    15. Select the square (second) sketch and activate SubtractivePipe.
    16. In Pipe Parameters, click object, select the vertical line in the 3D view and click OK.
    17. At this point, you should observe that BOTH the Pad and SubtractivePipe are visible in the model view.
    18. Change the draw style to flat lines to confirm that the pipe is hidden in the pad, except for the square on the surface.
    19. In the model view, select the Pad and toggle visibility, either from the menu or space bar. The 3D view now shows the cavity (SubtractivePipe) in the face of the cube (Pad) but the model view still shows both visible.
    20. Again, toggle visibility and now the SubtractivePipe goes not visible in both views.
    The same procedure may be done with AdditivePipe instead, except, of course, it's harder to detect the fault in the 3D view.
    Additional Information:
    Attached Files: pipe problem.FCStd (9,798 bytes) 2020-08-05 07:02
    https://tracker.freecad.org/file_download.php?file_id=2516&type=bug
    Notes
    (0014700)
    TedM   
    2020-08-05 07:06   
    Forum discussion here: https://forum.freecadweb.org/viewtopic.php?f=3&t=49021
    (0016931)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6098.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4412 [PartDesign] Bug major always 2020-08-01 15:49 2021-02-06 06:43
    Reporter: MRx Platform:  
    Assigned To: OS:  
    Priority: urgent OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: <!--ATTENTION:
    COMPLETELY ERASE THIS AFTER PASTING YOUR
    Help > About FreeCAD > Copy to clipboard
    NOTE: just the snippet alone will do without anything else included.
    The ticket will not be submitted without it.
    -->
    Summary: Pockets into a circular hole and refining object damages the object structure
    Description: I've created a sample project, and it seems creating a vertical circular pocket into a horizontal circular pocket damages the object structure.

    1. create some shape with horizontal pockets
    2. create some vertical pockets touching the horizontal pockets
    3. run refine object
    4. run check geometry

    it gives a lot invalid curve on surface.
    A sample project is attached.

    It happened to me on 2 other objects, all I could do is to redraw the object when this happened.


    OS: macOS Mojave (10.14)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.21938 (Git)
    Build type: Release
    Branch: master
    Hash: 5666598a6be219830a992610243fe23144a61453
    Python version: 3.8.2
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: C/Default (C)


    Forum Post:
    https://forum.freecadweb.org/viewtopic.php?f=3&t=49154&p=421135#p421094
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files: fc_shapebug.FCStd (457,701 bytes) 2020-08-01 15:49
    https://tracker.freecad.org/file_download.php?file_id=2514&type=bug
    Notes
    (0014696)
    MRx   
    2020-08-02 00:30   
    With FreeCad 0.19 I have to refine an object and create a simple copy.
    With FreeCad 0.18 it's enough to refine the object and the history can be deleted.

    Is this intended?
    (0016928)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6095.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4334 [PartDesign] Feature minor have not tried 2020-05-03 09:18 2021-02-06 06:43
    Reporter: wmayer Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: empty
    Summary: Thicken sketch
    Description: https://forum.freecadweb.org/viewtopic.php?f=8&t=31624
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016891)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6057.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4308 [PartDesign] Bug tweak always 2020-04-10 06:55 2021-02-06 06:43
    Reporter: Roy_043 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: acknowledged Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 8.1 (6.3)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.20311 (Git)
    Build type: Release
    Branch: master
    Hash: 915e551bbb7e3614bc804f1ae1f65027b5432b9f
    Python version: 3.6.8
    Qt version: 5.12.1
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: Dutch/Netherlands (nl_NL)
    Summary: 5 standard options are missing in the PartDesign Tree view context menu.
    Description: 5 standard options are missing in the PartDesign Tree view context menu:
    "Toggle visibility" - "Select all instances"
    Tags:
    Steps To Reproduce: Select an object in the tree and right-click.
    Additional Information:
    Attached Files:
    Notes
    (0014333)
    Roy_043   
    2020-04-10 08:46   
    Forum topic:
    https://forum.freecadweb.org/viewtopic.php?f=3&t=44948
    (0016877)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6043.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4300 [PartDesign] Feature feature always 2020-03-31 15:54 2021-02-06 06:43
    Reporter: drmacro Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Ubuntu 19.10 (XFCE/ubuntustudio)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.
    Build type: Release
    Python version: 3.7.5
    Qt version: 5.12.4
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/United States (en_US)
    Summary: Part object, if not at origin, moves to global origin when moved to Part Design Body
    Description: Discusson thread: https://forum.freecadweb.org/viewtopic.php?f=3&t=44739#p382393%5DPart%20object%20moves%20to%200,0%20when%20dragged%20into%20Part%20Design%20Body

    When a Part WB object that is not positioned at origin is used as a base feature the offset is not maintained.

    Could the following features be added?
    - add AttachmentOffset to BaseFeatures
    - add TraceSupport as it is used for ShapeBinders.

    The current work around is to add a Compound wrapper around the object before moving to the Part Design Body.
    Tags:
    Steps To Reproduce: Create object in Part WB, move it's position away from 0,0,0
    Drag/drop it into Part Design Body
    Moves back to origin
    Additional Information:
    Attached Files:
    Notes
    (0016876)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6042.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4267 [PartDesign] Bug major always 2020-02-15 17:58 2021-02-06 06:43
    Reporter: uwestoehr Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 10 (10.0)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.19603 (Git)
    Build type: Release
    Branch: master
    Hash: 62251e3b398ce7d46aba6c84d68da990bfb8b0f9
    Python version: 3.6.8
    Qt version: 5.12.1
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: German/Germany (de_DE)
    Summary: adding primitives changes body coordinate system
    Description: - Add 2 primitives, the first one attached to the xy-plane, the second one attached to a face of the first one. Attached is an example file.
    - now try to mirror the first one along the xy-plane

    result: you get the error

    <App> Document.cpp(3464): Failed to recompute Cube#Mirrored: Transformation failed
    Recompute failed! Please check report view.

    The problem is hereby that the addition of the primitive changes the body coordinate system. Therefore the mirroring is correctly done, but the xy-plane was moved.
    Tags:
    Steps To Reproduce:
    Additional Information: forum thread: https://forum.freecadweb.org/viewtopic.php?f=3&t=43395
    Attached Files: Cube.FCStd (23,157 bytes) 2020-02-15 17:58
    https://tracker.freecad.org/file_download.php?file_id=2433&type=bug
    Notes
    (0014330)
    openBrain   
    2020-04-07 16:37   
    @uwestoehr : I changed "global coordinate system" to "body coordinate system" as the GCS roughly can't be altered. However, do you have some evidence that the behavior is linked with coordinate system tampering ? Or is it just rough inference ? I see nothing about it in the forum discussion. ;) Thx.
    (0016866)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6032.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4211 [PartDesign] Bug minor always 2019-12-05 06:04 2021-02-06 06:43
    Reporter: Dan-K Platform:  
    Assigned To: OS: Windows 10, macOS Catalina  
    Priority: normal OS Version: 1607, 10.15.1  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 10 (10.0)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.18811 (Git)
    Build type: Release
    Branch: master
    Hash: b809867021deb37be1039dab37b9fe1cafab254e
    Python version: 3.6.7
    Qt version: 5.12.1
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/Canada (en_CA)
    Summary: PartDesign Pad 'Up to face' has issues when selecting a ShapeBinder's or Binder's face
    Description: If a PartDesign body has a ShapeBinder or Binder to a reference object and a sketch within that same body attempts to pad to once of the binder's surfaces with 'Up to face', the following error occurs:

    311.375 <App> Document.cpp(3462): Failed to recompute uptoface_bug#Pad002: Pad: Resulting shape is empty

    Discussed on the forum: https://forum.freecadweb.org/viewtopic.php?f=3&t=41280
    Tags: 0.18, 0.19, shapebinder
    Steps To Reproduce: 1. Download and open the attached 'uptoface-bug.FCStd' file.
    2. Notice the 'Target Body' PartDesign Body has a ShapeBinder and a Binder of the 'Static Body' body and that the positions of these binders are correct.
    3. Hide the 'Static Body' and one of the binder objects such that the other binder object is visible.
    4. Switch to the 'PartDesign' workbench.
    5. Select 'Sketch002' from the tree.
    6. Press the 'PartDesign' 'Pad' button.
    7. Change the 'Type' to 'Up to face'.
    8. Select one of the two faces of the visible binder object whose normal is parallel to the sketch's face.
    9. Press 'OK'.
    10. Notice the error popup and error message in the 'Report view'.
    11. This can be repeated with the other binder object, the issue will happen with both ShapeBinder and Binder.
    Additional Information:
    Attached Files: uptoface-bug.FCStd (21,377 bytes) 2019-12-05 06:04
    https://tracker.freecad.org/file_download.php?file_id=2395&type=bug
    Notes
    (0016848)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6014.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4135 [PartDesign] Feature feature have not tried 2019-09-17 23:47 2021-02-06 06:43
    Reporter: townkat Platform:  
    Assigned To: OS:  
    Priority: high OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Add PartDesign Common operations
    Description: Please add Common (intersection) operations in PartDesign in addition to Additive and Subtractive features.

    More info in the following topics:
    https://forum.freecadweb.org/viewtopic.php?f=8&t=35755
    https://forum.freecadweb.org/viewtopic.php?f=8&t=39297

    Thank you.
    Tags: Part Design
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016825)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5991.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4061 [PartDesign] Bug minor always 2019-07-18 12:22 2021-02-06 06:43
    Reporter: wmayer Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Weird behavior in Placement dialog when using "center of mass" with Datum Plane
    Description: https://forum.freecadweb.org/viewtopic.php?f=3&t=37803&p=321702
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016801)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5967.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4040 [PartDesign] Bug minor always 2019-06-27 10:26 2021-02-06 06:43
    Reporter: freman Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: lack of error message on failing to pad sketch
    Description: There is clearly some test or operation which is failing here but nothing is output at a stage where it can be useful.

    Having effectively broken the outline in the sketch, no error is produce on closing when the pad attempts to recompute.

    Errors should be adequately trapped and useful output provided as to what failed, at a level where that information is available.

    Similarly, on attempting to change the length of the pad in this condition, a window with the text "Error! is really not that informative.

    This could be handled in a way which is more informative to the user.
    Tags:
    Steps To Reproduce: Create a sketch with closed form.
    pad from sketch.
    edit sketch to no longer be a closed form.
    close sketch.
    Note exclamation on pad: try to find some error output, explaining the error.


    The attached file shows the state of a model after inadvertently leaving a sketch without a closed form ( the construction lines masked that there was a missing line to close the loop ).

    On exiting sketch editor, the pad element named base-block showed an exclamation mark but there was no output in report window nor on the console showing that an error had occurred.

    Subsequent attempts to edit the pad produce a tiny window with the text "Error!". As before, nothing more is produced.

    Additional Information: OS: Linux (LXDE/LXDE)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.17119 (Git)
    Build type: Release
    Branch: master
    Hash: e72b48e0cfcf4773e4b6527c74f2bac11ccff1ab
    Python version: 2.7.15
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedKingdom (en_GB)
    Attached Files: housing-error.FCStd (49,989 bytes) 2019-06-27 10:26
    https://tracker.freecad.org/file_download.php?file_id=2250&type=bug
    Notes
    (0013314)
    freman   
    2019-06-28 06:06   
    TheMarkster has noticed that the presence of the path elements seems to be eating the error context, leading to the terse and unhelpful "Error!".

    https://forum.freecadweb.org/viewtopic.php?f=3&t=37313#p317383

    I have confirmed that the presence of the jobs do not affect this but at least one path in either job will trigger this bug. With no paths present there is a proper error msg which reports "failed-to-validate-broken-face".

    Presumably the change to pad triggers a recompute of the paths and the error context is lost. It seems that this should be trapped and reported before attempting a recompute ( which will be futile anyway if the base pad object is broken).
    (0016792)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5958.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4039 [PartDesign] Bug minor always 2019-06-27 02:15 2021-02-06 06:43
    Reporter: jmaustpc Platform: 64 bit  
    Assigned To: OS: Kubuntu  
    Priority: normal OS Version: 18.04 LTS  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: MapSketch tool in PartDesign creates cyclic dependencies by offering Sketches their own axis planes
    Description: forum topic link
    https://forum.freecadweb.org/viewtopic.php?f=3&t=36142&p=317197#p317197

    MapSketch tool in PartDesign creates cyclic dependencies by offering Sketches their own axis planes
    Tags:
    Steps To Reproduce: Create a new sketch by duplicating an existing sketch, drag it into the active body, click on PartDesign "MapSketch" icon, select the duplicate sketch from the drop down list, look at the attachments offered, the xy etc. axis planes say objects xy etc.

    I thought Object was referring to Body but it is referring to the sketch's own axis planes, hence selecting one maps the sketch to its self.
    Additional Information: in FreeCAD from both PPAs (0.18.1 and 0.19)

    OS: Ubuntu 18.04.2 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.1.
    Build type: Release
    Python version: 3.6.7
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/Australia (en_AU)



    OS: Ubuntu 18.04.2 LTS (KDE/plasma)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.
    Build type: Release
    Python version: 3.6.8
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/Australia (en_AU)
    Attached Files: sketchswitchingplanes019.FCStd (17,691 bytes) 2019-06-27 02:15
    https://tracker.freecad.org/file_download.php?file_id=2249&type=bug
    testpartdesign_mapsketch.FCStd (36,314 bytes) 2019-06-29 05:06
    https://tracker.freecad.org/file_download.php?file_id=2252&type=bug
    Notes
    (0013319)
    jmaustpc   
    2019-06-29 05:06   
    Just another example file.
    (0016791)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5957.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4029 [PartDesign] Bug minor always 2019-06-19 08:38 2021-02-06 06:43
    Reporter: fabrico Platform: AMD64  
    Assigned To: OS: Ubuntu  
    Priority: normal OS Version: 18.04.2 LTS  
    Status: confirmed Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Pocket operation yields invalid result with "Refine = True"
    Description: Certain pocket geometries yield invalid results with missing surfaces or distorted shapes when their "Refine" property is set to "True". See examples in the forum thread for details.

    forum thread
    Tags:
    Steps To Reproduce: Use Part Design Workbench in the provided file.

    Behavior1:
    1) Open the attached file.
    2) Create a new sketch on the front face of the part.
    3) Draw a circle somewhere on the face of the part.
    4) Close the sketch.
    5) Attempt to create a pocket with the sketch.
    6) The part disappears.
    7) Cancel the pocket task.
    8) Hover over "Body" in the tree.
    9) An error message appears: "Tip shape is empty (but must be executed)"

    Behavior2:
    1) Open the attached file.
    2) Right click on "SubtractivePipe" in the tree.
    3) Select "Set tip".
    4) Create a new sketch on the front face of the part.
    5) Draw a circle somewhere on the face of the part.
    6) Close the sketch.
    7) Attempt to create a pocket with the sketch.
    8) The pocket is created.
    9) Click OK for the pocket task.
    10) No error is evident.

    openBrain's posted reply revealed that the part had a missing surface before the attempted pocket. This missing surface is the evidence of the bug.

    openBrain : it seems user level root cause is that setting "Refine=True" on the CableSlitPocket in the example file fails (a face vanishes leading to an invalid solid). Setting "Refine=False" solves the problem.
    Moreover, despite step 3 of Behavior2 may prevent the bug to happen, there is still a missing face.
    Additional Information: OS: Ubuntu 18.04.2 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.1.
    Build type: Release
    Python version: 3.6.7
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    Attached Files: test.FCStd (150,534 bytes) 2019-06-19 08:38
    https://tracker.freecad.org/file_download.php?file_id=2243&type=bug
    Notes
    (0013260)
    openBrain   
    2019-06-19 10:57   
    @fabrico : I added some details in your ticket so devs hopefully don't have to go to the forum to get a basic understanding of the possible cause. Hope you're OK with that. ;)
    (0016783)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5949.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3975 [PartDesign] Bug major always 2019-05-15 19:41 2021-02-06 06:43
    Reporter: openBrain Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Specific pocket fails with solid obtained by revolution
    Description: Specific pocket shape fails when applied on a solid that has been obtained by revolution.
    Same sketch correctly pockets the same solid obtained by different function.
    Tags:
    Steps To Reproduce: Attached file demonstrates the problem by exposing one failing case and one succeeding one.

    Notice that replacing the inner arc of the sketch by a line makes the pocket to succeed.
    Screenshot: https://forum.freecadweb.org/download/file.php?id=83727 (attached below)
    Additional Information: Forum thread (FR)
    ---
    OS: Ubuntu 18.04.2 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.1.
    Build type: Release
    Python version: 2.7.15rc1
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: French/France (fr_FR)
    ---
    (OS: Windows 8.1 - Version: 0.19.16523 - Python version: 2.7.14 - Qt version: 4.8.7)
    ---
    Attached Files: revolution_pocket_bug.FCStd (68,438 bytes) 2019-05-15 19:42
    https://tracker.freecad.org/file_download.php?file_id=2219&type=bug
    revolution_bug.png (6,621 bytes) 2019-06-17 06:51
    https://tracker.freecad.org/file_download.php?file_id=2240&type=bug
    Notes
    (0013114)
    openBrain   
    2019-05-15 19:42   
    Forget the file :)
    (0016764)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5930.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3949 [PartDesign] Bug minor always 2019-04-29 09:58 2021-02-06 06:43
    Reporter: locutusofborg Platform: Linux  
    Assigned To: kkremitzki OS: Ubuntu 18.04 and later  
    Priority: normal OS Version: 32 bit  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: PartDesign Loft test failures on i386
    Description: As you can see in the following test log, the newly created

    testSimpleAdditiveLoftCase (PartDesignTests.TestLoft.TestLoft) ... FAIL
    testSimpleSubtractiveLoftCase (PartDesignTests.TestLoft.TestLoft) ... FAIL

    fails on i386...

    Can you please have a look? thanks!

    https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/i386/f/freecad/20190429_060906_d8c75@/log.gz

    This happens since its implementation, in commit e1b78ab91f86f259dc268cb742b4dc42dae7fcea

    We started having that failure in 0.17, so it probably never worked on i386 platform
    Tags:
    Steps To Reproduce: Run tests on a 32bit
    Additional Information:
    Attached Files:
    Notes
    (0013068)
    Kunda1   
    2019-04-29 12:09   
    @locutusofborg thank you for the ticket. Please follow the guidelines next time (yellow banner top of page). Please open a forum thread to discuss with the devs and testers. Thank you.
    (0013070)
    locutusofborg   
    2019-04-29 12:54   
    @Kunda1 thanks! I also sent an email to the original developer of the test (found via git log) and pointed him to this bug!
    (0013765)
    Kunda1   
    2019-10-17 22:51   
    @locutusofborg who is the original author ? The title of this ticket is too generic
    (0014067)
    locutusofborg   
    2020-01-13 12:07   
    hello @Kunda1, according to git log

    From e1b78ab91f86f259dc268cb742b4dc42dae7fcea Mon Sep 17 00:00:00 2001
    From: Kurt Kremitzki <kkremitzki@gmail.com>
    Date: Wed, 28 Jun 2017 11:31:34 -0500
    Subject: [PATCH] Add basic PartDesign::Loft test cases

    https://github.com/FreeCAD/FreeCAD/commit/e1b78ab91f86f259dc268cb742b4dc42dae7fcea.patch
    (0016756)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5922.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3943 [PartDesign] Bug minor always 2019-04-24 17:13 2021-02-06 06:43
    Reporter: jmaustpc Platform: AMD64  
    Assigned To: OS: Kubuntu  
    Priority: normal OS Version: 18.04  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Disable auto hide solid option when entering Sketch edit mode sets and leaves solid hidden
    Description: In PartDesign, if you enter edit mode of a feature's sketch, by default the solid will be set to hidden so that the solid will not obscure the sketch. There is a property of the sketch to disable this feature as well as a setting in preferences to change the default value of that property.

    When the property is set to disable this auto hide function, FreeCAD still hides the solid and also leaves the solid hidden when you close sketch edit mode.

    The first feature seems to work correctly but subsequent features show this bug.

    https://forum.freecadweb.org/viewtopic.php?p=303218#p303218
    Tags:
    Steps To Reproduce: In the file attached, try toggling the "Hide Dependent" property of the three sketches then double click so that the sketch goes into edit mode.

    The first sketch will hide or not hide the solid and then if it was hidden it returns it to visible after closing sketch edit mode.

    however the subsequent sketches when "Hide Dependent" is set to false, 1) the feature related to that sketch is firstly hidden anyway, and then when edit mode is closed, the solid remains hidden
    Additional Information: OS: Ubuntu 18.04.2 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.1.
    Build type: Release
    Python version: 3.6.7
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/Australia (en_AU)
    Attached Files: hiding_1_mod.FCStd (22,532 bytes) 2019-04-24 17:13
    https://tracker.freecad.org/file_download.php?file_id=2193&type=bug
    Notes
    (0016753)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5919.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3942 [PartDesign] Feature minor always 2019-04-22 15:09 2021-02-06 06:43
    Reporter: freedman Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Using "Tab" to cycle thru properties, go up to the first once we get to the last.
    Description: The "Tab" key works to cycle thru properties but when it gets to the last property it stops there. It would be best if it goes back to the first property, hince the feature request.

    It appears to work differently in Part, that's why i'm targeting Part Design.
    Tags: keyboard, shortcuts, UI
    Steps To Reproduce: Use the "Tab" to cycle thru properties.
    Additional Information: OS: Windows 7
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16093 +17 (Git)
    Build type: Release
    Branch: (HEAD detached at 0.18.1)
    Hash: f7dccfaa909e5b9da26bf50c4a22ccca9bb10c40
    Python version: 2.7.14
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.2.0
    Locale: English/UnitedStates (en_US)
    Attached Files:
    Notes
    (0013092)
    Kunda1   
    2019-05-09 13:32   
    @freedman moving forward, please use a py3/qt5 0.18/0.19_pre builds
    Thanks
    (0016752)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5918.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3888 [PartDesign] Bug minor always 2019-03-06 21:21 2021-02-06 06:43
    Reporter: wmayer Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Moving object in body causes cyclic dependencies
    Description: When choosing the option to move an object at the beginning of the body a cyclic dependency will be created.
    Tags:
    Steps To Reproduce: 1. Create a body
    2. Create a sketch and pad
    3. Select a face, create new sketch and pad it
    4. Select the second pad, call the function to move the object
    5. Press OK to accept the default value
    Additional Information: https://forum.freecadweb.org/viewtopic.php?f=3&t=34684
    Attached Files:
    Notes
    (0016727)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5892.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3818 [PartDesign] Feature minor always 2019-02-05 11:03 2021-02-06 06:43
    Reporter: LAROBERTE Platform:  
    Assigned To: uwestoehr OS:  
    Priority: normal OS Version:  
    Status: resolved Product Version: 0.18  
    Product Build: Resolution: fixed  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: PartDesign Hole Depth Dimension should provide the option not to take the angled drill point type into account
    Description: In the PartDesign Hole feature, the Depth Dimension option controls the overall depth of a blind hole. When the Drill point option is set to Angled, the dimension includes the conical end point generated by the Angled drill point option.

    There should be an option to set the depth dimension so that it does not include the conical end point, to comply with some standards.

    http://euro.branly.free.fr/ISI/Construction/Dessin/filet/filets.htm
    http://joho.p.free.fr/EC/COURS%20DOC/FILETAGE/REPRESENTATION/Cotation%20des%20filetages.pdf
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files: Capture_Hole.PNG (52,156 bytes) 2019-02-05 11:03
    https://tracker.freecad.org/file_download.php?file_id=2122&type=bug
    Capture vis.jpg (189,539 bytes) 2019-02-12 17:21
    https://tracker.freecad.org/file_download.php?file_id=2124&type=bug
    2_56de1357158a5.pdf (2,497,939 bytes) 2019-02-12 17:21
    https://tracker.freecad.org/file_download.php?file_id=2125&type=bug
    Hole depht.FCStd (27,467 bytes) 2019-02-12 17:21
    https://tracker.freecad.org/file_download.php?file_id=2126&type=bug
    Notes
    (0012585)
    Kunda1   
    2019-02-06 03:00   
    @LAROBERTE Did you mean Path Workbench ?
    Have you opened a forum thread to discuss this ? (per our guidelines at the top of the page)

    CC @sliptonic
    (0012586)
    LAROBERTE   
    2019-02-06 08:18   
    Hello
    I do not speak English, it is very difficult for me to open and follow a discussion, I am obliged to translate everything, it is long and tedious.
    I looked in the forum if someone was talking about it, but I did not find anything.
    The problem is not a bug, but rather an error in the standards of rating, surely very easy to solve, that's why I intervened.
    (0012592)
    Kunda1   
    2019-02-08 21:48   
    @mlampert care to weigh in ?
    (0012593)
    mlampert   
    2019-02-08 22:14   
    I have never seen this dialog before - where does it come from?
    (0012601)
    Kunda1   
    2019-02-10 00:46   
    @LAROBERTE please provide instructions on how to reproduce the bug
    (0012602)
    LAROBERTE   
    2019-02-10 05:16   
    Ok
    I take care of it, but I do not work until Tuesday
    thank you for considering my post.
    (0012615)
    normandc   
    2019-02-10 19:02   
    Bug was wrongly reported in "FreeCAD (all projects)" instead of PartDesign.

    Changed bug severity from major to minor.

    I cannot reproduce the issue. For me, if I set the hole depth to 10mm with angled drill point, the 10mm value includes the drill point. Please provide your FreeCAD info as explained in the enormous yellow banner that you could not possibly miss.

    I'm switching this report's status to feedback required.

    OS: Ubuntu 18.04.2 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.15816 (Git)
    Build type: Release
    Branch: master
    Hash: 7ee0e4d43909ec688299b8498b240cccf8362c47
    Python version: 2.7.15rc1
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: French/Canada (fr_CA)
    (0012616)
    normandc   
    2019-02-10 19:05   
    Okay, I think I understand the issue now. You actually want the hole depth NOT TO take the conical end into account.

    This would be a feature request then, because in commercial software I use, both possibilities are offered (depth with or without the conical drill point).
    (0012617)
    LAROBERTE   
    2019-02-10 22:41   
    hello, the downhole cone should never be included in the hole depth, it is only the consequence of the shape of the drill bit. The depth of a hole should take into account only the part with the correct diameter. see the two links of my first post.
    if you want to add a feature, you should be able to choose the thread depth and drilling depth. Drilling and always deeper than the threading so as not to break the tools. the angle of the drilling cone is 120 degrees, the angle of the thread is 90 degrees. I do not have freecad until Tuesday, I promise you to make a correct post as soon as possible.
    it's not very important for 3D printing, but it's very important for mechanical machining
    (0012618)
    normandc   
    2019-02-10 23:51   

    the downhole cone should never be included in the hole depth

    LAROBERTE
    I disagree. At work, plenty of time I really, really needed to define the total depth of a blind hole including the drill tip, so it would not punch through the material or would leave minimal thickness. Doing it your way would require guesswork or calculation.

    As I said, Solid Edge (a commercial mid-range CAD package) offers both options. FreeCAD should do the same.

    Your other arguments about thread depth and drilling depth are of course to the point. But the Hole feature cannot currently display a modelled thread, and the TechDraw workbench cannot extract hole information nor display it; so implementing this at this time would not really be useful. With 0.18 nearing release I doubt that we will see this implemented before release, which is why I set the target version to 0.19. Unfortunately, there is no longer a developer dedicated to the PartDesign workbench.
    (0012619)
    LAROBERTE   
    2019-02-11 01:13   
    I agree with you, which is why my first post did not mention a request to add a function. I know that Freecad is evolving, but in the current state of things, the most important is the useful depth of the hole, which is the current standard in technical drawing. if you feel that the cone depth is half a diameter, you will have no problem and it is very easy with a 3D software to see if the cone of the bottom of the hole passes through.
    Of course, if the drill cone is a problem, nothing prevents you from making a hole with a flat bottom with a suitable tool.
    very cordially
    (0012630)
    LAROBERTE   
    2019-02-12 17:21   
    Hello
    For years, technicians have been working to develop international standards for technical drawing.
    If you want freecad to become one of the software that can also be used by professionals, you have to respect them.
    The Hole function of freecad is for the moment only the draft, I am sure, of a practical and complete intuitive function. You can add as many functions as you want, but basic functions and their default values ​​must comply with existing standards.
    I am willing to participate on a forum to help develop Freecad, this particular function, but I opened this post only to correct this glaring error which will only cause the development of other functions or options for the materialization of the threads of freecad.
    I'm not sure if the translation is understandable, I'm really sorry I do not write English directly.
    I leave attached sketches that will be more meaningful than me.
    Very sincerely
    OS: W10 lasted version or UBUNTU 18.10 with virtual box 5.2.26 r128414 (Qt5.6.2)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.15806 (Git) or 0.17
    Build type: Release
    Locale: French/Fr
    (0012635)
    LAROBERTE   
    2019-02-14 14:05   
    thank you
    (0015043)
    uwestoehr   
    2020-12-01 13:29   
    Thanks for the report. We are currently fixing all known hole dialog issues, see this forum thread: https://forum.freecadweb.org/viewtopic.php?p=453371#p453371

    Should your requested option be the default or not?
    (0015057)
    Kunda1   
    2020-12-03 18:40   
    @LAROBERTE please reply
    (0015133)
    uwestoehr   
    2020-12-13 01:22   
    > Should your requested option be the default or not?

    I checked and asked colleagues, it is indeed the common rule not to take the drill angle into account. Here are some more documents stating the same as the French ones the bug reporter linked:
    https://www.technisches-zeichnen.net/technisches-zeichnen/grundkurs-03/gewinde-bemassen.php
    https://www.joshuanava.biz/engineering-3/draughting-conventions-associated-with-threads.html

    So I will add this option and make it default.
    (0015134)
    uwestoehr   
    2020-12-13 05:21   
    > So I will add this option and make it default.

    Here is the PR: https://github.com/FreeCAD/FreeCAD/pull/4134
    (0015230)
    uwestoehr   
    2021-01-31 00:43   
    Fixed: commit 7306ed28 ; PR https://github.com/FreeCAD/FreeCAD/pull/4134
    (0016714)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5879.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3799 [PartDesign] Feature feature always 2019-01-26 11:29 2021-02-06 06:43
    Reporter: markus51 Platform:  
    Assigned To: OS: Win7  
    Priority: low OS Version:  
    Status: feedback Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Improve the "Create a hole in the selected sketch" task (remember previous task settings)
    Description: When you have a lot of screws on different planes, it is nerved to refill the form on the "Create a hole in the selected sketch" task.

    It will be nice when the task remebers his settings from the last call.
    Tags: #pending-forum
    Steps To Reproduce: 1.) Draw a new sketch with a circle
    2.) Goto "Part Design"
    3.) Selcet the new sketch in the tree window
    4.) Press "Create a hole in the selected sketch" in the toolbar
    5.) The task contains not the last settings, but there are the init values.
    Additional Information:
    Attached Files:
    Notes
    (0012550)
    Kunda1   
    2019-01-29 18:12   
    Why are you still posting 0.17 tickets?
    Where is the forum post discussing this with the community?
    Please follow the tracker guidelines. Thanks you for your comprehension
    (0012565)
    markus51   
    2019-01-31 10:51   
    The same is on version 0.18dev ... blabla


    I don't discuss bug's and such basically unusable gui parts, with the community.
    It is wasted time. And freecad has a lot of such ugly parts. You can see it on
    the first look.

    @Kunda1@: you shoult be thankful that anyone helps to improve this software.
    If you don't want this help --> say it loud ---> then good by
    (0012566)
    Kunda1   
    2019-01-31 14:33   
    @markus51 I am thankful for people contributing and volunteering. There is a way each open source project receives help and in FreeCAD we ask people to do it in a specific way (the large shouting yellow banner at the top of the tracker). If you don't think you apply to that standard you are free to think that, But know that you will receive feedback and orientation from volunteers who need to triage your good will. Also, if you think the interface is ugly you are free to express that and you should know that is very subjective and not constructive. It also won't earn you any extra love from the community. You don't like something about FC then do something about it or deal with it. It's very simple. You are free to become part of the community and follow the guidelines or not (and be responded to accordingly) Thank you for your comprehension.
    (0013010)
    Kunda1   
    2019-04-06 19:17   
    @chrisb can you weigh in on this ticket?
    (0013021)
    chrisb   
    2019-04-09 09:03   
    For one this is clearly a feature request.

    For two OPs attitude is not helpful at all (to avoid the word "unacceptable"). The process has turned out to be sensible. It could possibly be improved, but again this should be discussed in the forum.

    For three the basic idea is sensible. Nevertheless it should be discussed in the forum. I can think immediately of different solutions, like the possibility to save current settings, have a list of them, etc. And it might have impact on other dialogs too.
    (0013995)
    Kunda1   
    2020-01-06 16:04   
    Created https://forum.freecadweb.org/viewtopic.php?f=8&t=42231 for discussion
    (0016710)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5875.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3608 [PartDesign] Feature feature have not tried 2018-09-23 17:49 2021-02-06 06:43
    Reporter: chrisb Platform:  
    Assigned To: wmayer OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Fillets with variable radius
    Description: It would be great to have fillets with variable radius in Part and PartDesign workbenches. See german forum entries, Werner is already involved.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0014748)
    wmayer   
    2020-09-13 09:45   
    https://forum.freecadweb.org/viewtopic.php?f=13&t=50170
    (0016644)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5809.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3171 [PartDesign] Feature minor have not tried 2017-08-30 18:11 2021-02-06 06:43
    Reporter: wmayer Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Advanced filleting options
    Description: Implement an advanced fillet operation: https://forum.freecadweb.org/viewtopic.php?f=13&t=24036&hilit=fillet&start=10#p188254
    Tags: fillet
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0010117)
    normandc   
    2017-09-13 14:18   
    dubstar-04 had started work on a variable radius PartDesign Fillet. However I haven't found where is code was hosted.

    https://forum.freecadweb.org/viewtopic.php?f=19&t=8022
    (0016558)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5723.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3149 [PartDesign] Bug major have not tried 2017-08-07 05:43 2021-02-06 06:43
    Reporter: ickby Platform:  
    Assigned To: ickby OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Duplicate body creates a mess
    Description: https://forum.freecadweb.org/viewtopic.php?f=3&t=15949

    While experimenting on how Part-o-magic withstands object duplication, I found a bug in PartDesign.
    1. New Part, New body
    2. New sketch. Draw rectangle. Close.
    3. Pad the sketch.
    4. Select Body and menu Edit->Duplicate... When asked whether to duplicate dependencies, click Yes.
    The body is duplicated.
    But.
    Problem No.1. Body is not added to active Part. OK, that can be fixed manually...
    Problem No.2. and all looks fine, until one dives into dependency graph. There, a total mess can be seen.

    Graph problem No.1: Duplicates of Sketch and Pad were added to original body, as well as to the copy of body.
    Graph problem No.2: Pad001 references Pad (that is, gets fused to it).
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files: Duplicate_Part.FCStd (85,368 bytes) 2019-05-09 18:30
    https://tracker.freecad.org/file_download.php?file_id=2212&type=bug
    Notes
    (0010232)
    wmayer   
    2017-10-01 21:01   
    With the implementation of scoped links the issue has been fixed. There is only a minor issue left because when duplicating the body this error comes up:
    
    Exception (Sun Oct 01 22:51:58 2017): Object can only be in a single GeoFeatureGroup  
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
    <class 'Base.FreeCADError'>: Object can only be in a single GeoFeatureGroup
    

    The question is if it can be avoided to raise the error message.
    (0010436)
    DeepSOIC   
    2017-11-20 10:29   
    IMO the bug is still very big.

    a) when I duplicate a body, a message pops up, if FreeCAD should duplicate dependencies.
    If I answer No, the contents of the body is not duplicated; errors in report view, and the new Body shares an Origin object with the old body. This is a mess.

    b) the original Body (which I deactivated before copying) got activated back. I expect that the active object should not change.

    c) the action of the "copy dependencies" question applies the old logic of isolated PartDesign of 0.16, which partly explains point a). What I expect: "No" = body should be copied with all its contents duplicated, but none of the objects outside of the body should be duplicated. "Yes" - same, but with all dependencies not in body too (e.g. master sketches). This might get really tricky if for example there is a shapebinder of a partdesign feature from another body.
    (0013096)
    Bicycle Repair Man   
    2019-05-09 18:30   
    (Last edited: 2019-05-09 18:35)
    I can verify, that this bug is still present in some form in the 0.19 daily build from today (May 9th 2019).

    1. Please open "Duplicate_Part.FCStd" - This design has one master spreadheet to parameterize all parts.
    2. Select Part "Rahmen"
    3. Edit -> Duplicate Selection
    4a. Answer "No" to "copy dependencies"
    - In this case only the Part itself without any content is duplicated. To me, this is an unneeded state and I fully agree with DeepSOIC's suggestion c) to solve this.
    4b. Answer "Yes" to "copy dependencies"
    - The Part and its contained objects are duplicated, BUT
    the duplicate references the original spreadsheet: Reference in Rahmen001 -> Rahmen_vorne001 -> Position.x now points to "Spreadsheet.w_rahmen" which is the original Spreadsheet. This should be "param001" (or "Spreadsheet001" if neccessary).
    Similar to Rahmen001 -> Rahmen_vorne001 -> Length that points to "param.h_nut" which is also the original spreadsheet

    In any case, my suggestions are
    - The original part should stay unaltered
    - Independent of saying "Yes" or "No" to copy dependencies, I expect that all objects within the selection (also recursively) appear in the resulting object tree. Anything else is not a duplicate.
    - If saying "No" only objects within the selection tree should be duplicated (but still recursively). That would mean, that the duplicate references the master spreadsheet exactly the same way like the original.
    - If saying "Yes" also dependecies outside the selection tree (e.g. master spreadsheet) should be copied and correctly referenced by the duplicate objects (again, also recursively through the tree)

    Many thanks for bringing this great tool to us!
    Best Regards,
    Stephan

    OS: Linux Mint 19.1 (X-Cinnamon/cinnamon)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.
    Build type: Release
    Python version: 3.6.7
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: German/Germany (de_DE)

    (0013985)
    SimonLitt   
    2020-01-06 06:19   
    Hi!
    When I mirror a pad,the body of the part becomes empty.
    When I delete a copy, I cannot return the pad back to the body.
    Error message is: Object can only be in a single GeoFeatureGroup

    Sometimes when creating a sketch, the message drawing during migration appears, and when choosing automatic, an empty body is created, and everything settles as before.

    When I make a mirror copy of the body - everything is fine. But so far I have understood it, I made a lot of mistakes in the drawings. Now, in order to change something, I need to make copies of the sketch and create the parts again.

    [url=https://youtu.be/aRHqHNmfftc ]youtube screen record[/url]
    Full console output


    $ freecad
    FreeCAD 0.18, Libs: 0.18RUnknown
    © Juergen Riegel, Werner Mayer, Yorik van Havre 2001-2019
      ##### #### ### ####
      # # # # # #
      # ## #### #### # # # # #
      #### # # # # # # # ##### # #
      # # #### #### # # # # #
      # # # # # # # # # ## ## ##
      # # #### #### ### # # #### ## ## ##

    'ascii' codec can't encode characters in position 13-17: ordinal not in range(128)
    Part::Mirroring / Part__Mirroring: Links go out of the allowed scope
    Part::Mirroring / Part__Mirroring: Links go out of the allowed scope
    Part::Mirroring / Part__Mirroring: Links go out of the allowed scope
    Exception (Mon Jan 6 08:34:06 2020): Object can only be in a single GeoFeatureGroup
    Exception (Mon Jan 6 08:34:07 2020): Object can only be in a single GeoFeatureGroup
    Exception (Mon Jan 6 08:34:48 2020): Object can only be in a single GeoFeatureGroup
    Exception ignored in: <bound method WebView.__del__ of <__main__.WebView object at 0x7fa1c5e362b0>>
    Traceback (most recent call last):
      File "<string>", line 18, in __del__
    AttributeError: 'WebView' object has no attribute 'webPage'
    Sketcher::SketchObject / Sketch: Links go out of the allowed scope
    Exception (Mon Jan 6 08:34:57 2020): Object can only be in a single GeoFeatureGroup
    Exception (Mon Jan 6 08:35:00 2020): Object can only be in a single GeoFeatureGroup
    Exception (Mon Jan 6 08:35:04 2020): Object can only be in a single GeoFeatureGroup
    Exception (Mon Jan 6 08:35:08 2020): Object can only be in a single GeoFeatureGroup
    Sketcher::SketchObject / Sketch001: Links go out of the allowed scope
    $

    console
    (0014639)
    abdullah   
    2020-07-08 15:07   
    There is a new "copy dialog" in FC 0.19.

    If all dependencies are selected, the body is copied. It is not copied within the part (one has to move it in manually), but the dependency graph shows an independent object.

    The error message Werner indicates is still there.
    (0016555)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5720.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3060 [PartDesign] Feature minor N/A 2017-05-30 18:38 2021-02-06 06:43
    Reporter: Kunda1 Platform:  
    Assigned To: OS:  
    Priority: low OS Version:  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: More streamlined UI for adding edges and faces (e.g. for PD Fillet tool)
    Description: Per @Abdullah in 0002227:0009194

    The UI for adding and removing edges is tedious, slow, if somebody is forced to be productive with it, there are high chances of that person ultimately committing suicide. Probably it makes sense to create a separate feature request asking for an improvement

    Abdullah
    Tools that require selection of edges and faces:

    Fillet
    Chamfer
    Draft
    Thickness
    Additive/subtractive pipe
    Tags: #lowhangingfruit, fillet, UI
    Steps To Reproduce:
    Additional Information: Forum thread: https://forum.freecadweb.org/viewtopic.php?f=34&t=22740
    Attached Files:
    Notes
    (0014387)
    uwestoehr   
    2020-04-28 23:53   
    Fixed with https://github.com/FreeCAD/FreeCAD/pull/3050, https://github.com/FreeCAD/FreeCAD/pull/3061, and further commits.
    (0016538)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5703.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1742 [PartDesign] Feature minor have not tried 2014-09-11 22:44 2021-02-06 06:43
    Reporter: quick61 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Add Reverse Fillet Tool or Option in Part / Part Design
    Description: The discussion has come up several times on the forum about the lack of a reverse fillet tool. The most recent one starting here - http://forum.freecadweb.org/viewtopic.php?f=3&t=7633&p=62333#p62329

    Attached is an image of what the end result of the reverse fillet would be. If OCE will allow the implantation of such a tool, it would be a nice feature to have in the next release.
    Tags: GUI, Part, Part Design
    Steps To Reproduce:
    Additional Information:
    Attached Files: Reverse_Fillet.png (12,608 bytes) 2014-09-11 22:44
    https://tracker.freecad.org/file_download.php?file_id=825&type=bug
    Notes
    (0005095)
    quick61   
    2014-09-13 03:39   
    An older Forum discussion on this subject is here - http://forum.freecadweb.org/viewtopic.php?f=3&t=6667&hilit=ogee#p53838

    And from this post - http://forum.freecadweb.org/viewtopic.php?f=3&t=6667&hilit=ogee&start=10#p53899 - it would seem that a proper name for the tool would be Cove.
    (0014958)
    PedjaS   
    2020-11-02 20:17   
    This seems to be forgotten?
    (0016430)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5595.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4489 [TechDraw] Feature feature always 2020-11-10 23:18 2021-02-06 06:38
    Reporter: maker Platform: PC  
    Assigned To: OS: openSUSE Leap  
    Priority: normal OS Version: 15.2  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: openSUSE Leap 15.2 (KDE//usr/share/xsessions/default)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.Unknown
    Build type: Release
    Python version: 3.6.10
    Qt version: 5.12.7
    Coin version: 4.0.0
    OCC version: 7.5.0
    Locale: German/Germany (de_DE)
    Summary: TechDraw - normative correct simplified presentation of Thread in Top View and Cross section according to ISO 6410–1 standard
    Description: There is actually no feature in Techdraw to paint a normative correct simplified presentation of Thread in Top View and Cross section according to ISO 6410–1 standard.
    Solution approaches:
    1) TechDraw
    According to the forum thread https://forum.freecadweb.org/viewtopic.php?f=35&t=46183&hilit=Threads#p397091 there are first efforts put in a macro for the Top View:
    https://github.com/reox/FreeCAD_macros/blob/master/TDThread.FCMacro
    2) PartDesign
    Another proposal could be probably realised with the PartDesign Hole feature. See the post:
    https://forum.freecadweb.org/viewtopic.php?f=35&t=51236&hilit=Threads&start=10#p449851
    Tags:
    Steps To Reproduce: According to the following forum threads:

    Threads in TechDraw
    https://forum.freecadweb.org/viewtopic.php?f=35&t=51236
    Threading Visualization in TechDraw
    https://forum.freecadweb.org/viewtopic.php?t=44319
    Feature Request: Threads
    https://forum.freecadweb.org/viewtopic ... 5&t=27376
    Additional Information: https://wiki.freecadweb.org/Wished_tools#2D drawing

    Thread - PartDesign workbench. Feature Hole: correct functionality of bore depth according to ISO 6410–1 standard
    Thread - normative correct simplified presentation of cross section in Techdraw according to ISO 6410–1 standard
    Attached Files:
    Notes
    (0015085)
    maker   
    2020-12-05 22:03   
    (Last edited: 2020-12-05 22:14)
    Allocation to part design workbench preferred. See addition to description dated 2020-12-05.
    Should be reviewed in extension and in comparison to existing ticket https://tracker.freecadweb.org/view.php?id=3369 dated 2018-03-10.
    (0016960)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6127.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4413 [TechDraw] Feature minor N/A 2020-08-02 15:03 2021-02-06 06:38
    Reporter: wandererfan Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Linux Mint 19 (X-Cinnamon/cinnamon)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.
    Build type: Release
    Branch: unknown
    Hash: e727cd37548d7f38ea120670d2a28aba871a4aa1
    Python version: 3.6.9
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/Canada (en_CA)
    Summary: Allow Selection of Print Area and Scale
    Description: Allow user to select part of display for printing. Allow user tho specify scale of printed output.

    Forum discussion.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0015156)
    clifcox   
    2020-12-17 17:58   
    Perhaps we can reuse some code from LibreCAD for this?
    https://forum.freecadweb.org/viewtopic.php?style=4&f=3&t=49094&start=20#p458468
    (0016929)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6096.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4227 [TechDraw] Feature feature N/A 2019-12-16 17:17 2021-02-06 06:38
    Reporter: svbol Platform: x86  
    Assigned To: OS: Linux  
    Priority: normal OS Version: Linux Mint 18.3  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Linux Mint 18.3 Sylvia (XFCE/xfce)
    Word size of OS: 32-bit
    Word size of FreeCAD: 32-bit
    Version: 0.19.
    Build type: Release
    Python version: 3.5.2
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: Russian/RussianFederation (ru_RU)
    Summary: TechDraw: Add new option - Filter of Feature
    Description: Add "Filter of Features" options (Panel), please.
    This Filter can help to work with selected type(s) of needed Feature.
    Draft WorkBench have it. And LibreCAD use this filter.

    As example, I select "Line" only. Then I can using lines on draw with high speed (other features can't be selected and not used). Then I unselect "Line" and select "Point". And work with points only.
    When FreeCAD run first time - selected all features. Then my choice in thin Panel write to setting file.
    Tags: TechDraw
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016851)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6017.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4208 [TechDraw] Feature minor have not tried 2019-11-29 14:30 2021-02-06 06:38
    Reporter: wandererfan Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Linux Mint 19 (X-Cinnamon/cinnamon)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.18787 +15 (Git)
    Build type: debug
    Branch: Cosmetics2
    Hash: 79fc2bdada724391cfe2b42afda42b8c379e2cc7
    Python version: 3.6.8
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/Canada (en_CA)
    Summary: Allow Adjustment of Stacking Order of Views
    Description: Views are currently stacked in the order they are drawn. It would be convenient to move a view above or below another view.

    many forum discussions. One here.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016846)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6012.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4181 [TechDraw] Feature minor have not tried 2019-10-29 17:32 2021-02-06 06:38
    Reporter: wandererfan Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Linux Mint 19 (X-Cinnamon/cinnamon)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.18632 +5 (Git)
    Build type: debug
    Branch: defaultHatch
    Hash: 4794191e69b8ab8f2c8e3aa36e0bfb0b803fe511
    Python version: 3.6.8
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/Canada (en_CA)
    Summary: Add View of Sketch with colours and dimensions
    Description: TechDraw currently draws only the geometry of Sketches. It would be much nicer if it could preserve the colours of sketch lines and automatically make dimensions from geometric constraints.

    Forum discussion 1
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0014108)
    wandererfan   
    2020-01-24 13:44   
    Similar but much broader discussion re grabbing 3D features (Draft Dimensions, Sketch Constraints, Annotations) and including them in TD Views.
    (0016836)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6002.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4122 [TechDraw] Bug minor always 2019-09-11 15:04 2021-02-06 06:38
    Reporter: wandererfan Platform: win, linux, not OSX  
    Assigned To: wandererfan OS:  
    Priority: normal OS Version:  
    Status: acknowledged Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: HLR Returns No Edges for Shape
    Description: Forum discussion

    OCC HLR (HLRBRep_Algo) returns empty result for attached shape. DRAWEXE fails to display result of HLR with message "Error: AIS_Shape::Compute() HLR Algorithm has failed ()".
    Tags: OCC 7.3, upstream
    Steps To Reproduce: Open attached FCStd file and create new View for object "Bullet". Empty view will be created with no error messages.

    Changing View to Coarse mode produces result.

    Note: FC in OSX will display bullet shape, but Windows or Linux.
    Additional Information: DRAWEXE fails to display shape in "algo" mode, but displays shape in "polyalgo" mode.
    Attached Files: Temp_noDraw_TD.FCStd (24,544 bytes) 2019-09-11 15:04
    https://tracker.freecad.org/file_download.php?file_id=2321&type=bug
    bulletShape.brep (196,201 bytes) 2019-09-11 15:04
    https://tracker.freecad.org/file_download.php?file_id=2322&type=bug
    DRAWEXELog.txt (515 bytes) 2019-09-11 15:04
    https://tracker.freecad.org/file_download.php?file_id=2323&type=bug
    Notes
    (0013577)
    wandererfan   
    2019-09-11 15:21   
    OCC bug report
    (0014580)
    wandererfan   
    2020-06-21 13:01   
    Not fixable in FreeCAD
    (0016819)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5985.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4114 [TechDraw] Feature feature N/A 2019-09-04 14:36 2021-02-06 06:38
    Reporter: PeterPNoster Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: TechDraw Workbench Intersection dimensioning.
    Description: Needed when dealing with sheet metal dimensioning.

    Related to the following discussion:
    Intersection point

    Somehow related to this disussion:
    TechDraw and Fillets/Chamfers

    And certainly related to this feature request:
    https://freecadweb.org/tracker/view.php?id=3004
    Tags: 0.19
    Steps To Reproduce:
    Additional Information: OS: Linux Mint 19.2 (X-Cinnamon/cinnamon)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.17935 (Git) AppImage
    Build type: Release
    Branch: master
    Hash: bdc229f51e959caedf24459c1b9c9de7f6567298
    Python version: 3.7.3
    Qt version: 5.12.1
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: German/Switzerland (de_CH)
    Attached Files: Intersection_point.png (133,658 bytes) 2019-09-04 14:36
    https://tracker.freecad.org/file_download.php?file_id=2310&type=bug
    Notes
    (0013583)
    wandererfan   
    2019-09-12 13:51   
    (Last edited: 2019-09-12 13:52)
    Solution via macro available here

    @PeterPNoster, @Kunda1 - does the availability of a macro justify a change to "fixed" for this issue?

    (0013585)
    PeterPNoster   
    2019-09-12 16:46   
    Yes, I can work with this solution.
    Although it's clear for me that this request will come back. Because it is essential doing this kind of dimensioning on sheet metal bendings. Implementation in a future version of the TechDraw Workbench would be certainly much appreciated by a lot of users.

    Thank you for the great work you do for FreeCAD!
    (0016815)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5981.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3911 [TechDraw] Feature minor N/A 2019-03-20 02:05 2021-02-06 06:38
    Reporter: vocx Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Autofill information in SVG page template
    Description: In Catia the Drawing workbench auto-fills certain text fields in the Page Templates that come with the software. TechDraw could implement a similar behavior.

    The usage would be something like a button in the TechDraw toolbar to open a dialog with the fields that can be filled in the page template. It could also have a button in this dialog to automatically fill at least some values like Author, Date, Title, and Page. Another option would be to right click the field in the page itself (highlighted in green) to display the options (Author, Title, Page, etc.) which will to fill the field.

    In order to implement this well, each SVG template provided by FreeCAD should conform to some standardized name for the editable fields, for example, FC_AUTHOR, FC_DATE, FC_TITLE, etc. The data to write in the fields can be taken from the General Preferences of the Document, or taken from a Spreadsheet, or calculated by Qt in some way.

    The discussion is on the forum https://forum.freecadweb.org/viewtopic.php?f=35&t=31681
    Tags: SVG, TechDraw
    Steps To Reproduce:
    Additional Information: OS: Ubuntu 18.04.2 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16093 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-18
    Hash: 690774c0effe4fd7b8d2b5e2fb2b8c8d145e21ce
    Python version: 2.7.15rc1
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    Attached Files: TD_AutoDate1.png (97,841 bytes) 2020-01-05 20:53
    https://tracker.freecad.org/file_download.php?file_id=2420&type=bug
    TD_AutoDate2.png (98,816 bytes) 2020-01-05 20:53
    https://tracker.freecad.org/file_download.php?file_id=2421&type=bug
    TD_AutoDate3.png (61,259 bytes) 2020-01-05 21:11
    https://tracker.freecad.org/file_download.php?file_id=2422&type=bug
    Notes
    (0013982)
    wandererfan   
    2020-01-05 12:46   
    additional forum discussion
    (0013983)
    svbol   
    2020-01-05 20:53   
    (Last edited: 2020-01-05 21:09)
    I think - this small but very need function.
    I add screenshots about this feature.

    May be - this order:
    1. Create list of standard field's names,
    2. Add option in TechDraw setting - "Insert information for page",
    3. Change all template (rename all fields),

    (0016738)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5903.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3692 [TechDraw] Feature minor have not tried 2018-11-14 16:05 2021-02-06 06:38
    Reporter: wandererfan Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Add Centermark for Circular BSplines
    Description: TechDraw contains code to allow diameter and radius Dimensions for circular BSplines.

    Circular BSplines do not get a centermark like true circles do. If the BSpline can be dimensioned, a centermark should be shown too.
    Tags:
    Steps To Reproduce:
    Additional Information: Forum discusion.
    Attached Files:
    Notes
    (0016671)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5836.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3609 [TechDraw] Feature minor N/A 2018-09-24 04:44 2021-02-06 06:38
    Reporter: normandc Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: TechDraw - Auxiliary View
    Description: Per Wikipedia:

    An auxiliary view is an orthographic view that is projected into any plane other than one of the six primary views. These views are typically used when an object contains some sort of inclined plane. Using the auxiliary view allows for that inclined plane (and any other significant features) to be projected in their true size and shape. The true size and shape of any feature in an engineering drawing can only be known when the Line of Sight (LOS) is perpendicular to the plane being referenced.

    Wikipedia
    https://en.wikipedia.org/wiki/Engineering_drawing#Auxiliary_views

    The auxiliary view has a "viewing plane indicator" (really no clue how it's called) which usually is a dotted line with arrows, similar to a section view. It may depend on drawing standards. The auxiliary view is usally linked and aligned to its parent view, although it may be possible to break the alignment if there is not enough space on the page besides the parent view.

    A possible work flow would be to select a linear edge on a view then launch the auxiliary view tool. A FreeCAD file with TechDraw page is attached, with a pseudo auxiliary view made with the standard NewView tool. Attached svg was edited to manually add the plane indicator with view label.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files: FreeCAD-TechDraw-AuxiliaryView-request.svg (931,136 bytes) 2018-09-24 04:44
    https://tracker.freecad.org/file_download.php?file_id=2005&type=bug
    TechDraw_Feature_Request_Auxiliary_View_Example_nc1.fcstd (101,712 bytes) 2018-09-24 04:44
    https://tracker.freecad.org/file_download.php?file_id=2006&type=bug
    Notes
    (0016645)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5810.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3378 [TechDraw] Feature feature N/A 2018-03-16 17:49 2021-02-06 06:38
    Reporter: Kunda1 Platform:  
    Assigned To: OS:  
    Priority: low OS Version:  
    Status: feedback Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Feature: BOM (Bill of Materials) functionality
    Description: https://forum.freecadweb.org/viewtopic.php?f=8&t=23592
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0011924)
    Kunda1   
    2018-10-05 12:00   
    (Last edited: 2018-10-05 12:08)
    https://github.com/openscopeproject/InteractiveHtmlBom
    Posted on Interactive Html Bom Plugin

    Edit: another BOM utility for KiCAD: KiBOM

    (0011926)
    wandererfan   
    2018-10-05 12:08   
    BOM is not core TD functionality. Displaying an existing BOM might be reasonable request, but creating the BOM is related to "assembly"(?).
    (0016604)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5769.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3369 [TechDraw] Feature feature N/A 2018-03-10 20:26 2021-02-06 06:38
    Reporter: reox Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: inner/outer Threads
    Description: Enable drawing of threads
    Tags:
    Steps To Reproduce:
    Additional Information: See discussion: https://forum.freecadweb.org/viewtopic.php?f=35&t=27376
    Attached Files:
    Notes
    (0015086)
    maker   
    2020-12-05 22:16   
    Should be reviewed in extension and in comparison to existing ticket https://tracker.freecadweb.org/view.php?id=4489 dated 2020-11-10.
    (0016601)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5766.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3345 [TechDraw] Feature minor N/A 2018-02-11 13:34 2021-02-06 06:38
    Reporter: wandererfan Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Provide Alignment Guidelines On Drawing Page
    Description: A method to assist in aligning the various Views on a Page would be nice.

    Forum Discussion
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0012655)
    wandererfan   
    2019-02-15 13:27   
    will not be included in v0.18.
    (0016597)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5762.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3077 [TechDraw] Feature minor N/A 2017-06-08 14:46 2021-02-06 06:38
    Reporter: gntech Platform: Linux  
    Assigned To: OS: Ubuntu Mate  
    Priority: normal OS Version: 17.04  
    Status: acknowledged Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: "Headless" export of SVG and PDF from TechDraw
    Description: It would be very beneficial to be able to export directly from the TechDraw module without running the GUI. This would allow for completely automated scripts to create a 3D-model generate a drawing and export as a SVG.

    My particular usecase is that I design furniture that the customer can order to their exact dimensions. I therefor want to automate the process as much as possible. Right now I can create the 3d-model and TechDraw drawing directly from Python but the last step of actually exporting the SVG/PDF requires me to open the FreeCAD app and manually click export or running a macro from whitin the GUI.

    See also https://forum.freecadweb.org/viewtopic.php?f=22&p=177330
    Tags: headless, python, SVG
    Steps To Reproduce:
    Additional Information:
    System Description
    Attached Files:
    Notes
    (0009316)
    gntech   
    2017-06-09 05:27   
    @ian.rees Your nickname was mentioned in the related forum thread as someone who has done some prior investigations on this or a similiar matter. Do you mind sharing your view on this request? It would be greatly appreciated :)
    (0009349)
    ian.rees   
    2017-06-11 19:19   
    Hi gntech, sorry about the slow reply. The main issue in this area (at least as far as I remember) is that it's not possible to compile a useful TechDraw module without the Qt GUI module, at least with Qt4. The issue is to do with the QGraphics system - we have to use it, and also have to use QObject signals/slots/etc. I spent a few solid weeks of work on trying to concoct a workable solution and failed - if it's something you really want to try I can put together some notes and provide git branches from that effort.

    All that said, I believe that the FreeCADCmd (headless) binary provides the same TechDraw scripting interface as FreeCAD (the normal GUI one), but don't have time to test at the moment. Our intent was to make the scripting interface at least as powerful as the original Drawing module, and from what I remember it is possible to script things like you describe.

    Perhaps the missing bit of information from your thread, is just that you can run any old FreeCAD script directly from the command line ala
    $FreeCADCmd some_script.FCMacro
    . Does that help?
    (0009556)
    gntech   
    2017-06-27 05:12   
    Hi Ian, Thanks for your answer, but unfortunately it doesnt work even if I run the script via $FreeCADCmd.

    It seems like the function I would like to use: App.ActiveDocument.exportPageAsSvg("filename.svg") is only available through TechDrawGui.
    (0009557)
    ian.rees   
    2017-06-27 05:16   
    Hmm, sorry that it doesn't "just work".

    Would you mind putting together a script that demonstrates what you're trying to do, which works in the GUI but not the CLI, and attaching it here? You've probably provided enough information above for me to put one together, but I'm really short on FreeCAD time lately and suspect you have already made something along those lines.
    (0009593)
    wandererfan   
    2017-06-29 00:34   
    string = TechDraw.viewPartAsSvg(DrawViewPart) was added approx 2017-06-17. TechDraw API

    This allows individual Views to be exported. At this time, there is no function to export a whole Page with Template and all its Views.

    I don't see how PDF export will be possible without the Gui. On the App side, there is nothing to "print", just the raw data. On the Gui side we are actually printing a form of QWidget and Qt widgets just don't exist on the App side.
    (0009617)
    ian.rees   
    2017-06-29 20:54   
    Hmm, I'm 90% sure that at some stage I had a scriptable interface to export a whole page just like if it were being printed - this was before my attempt to separate the UI from the QGraphics (so that it would be possible to compile a useful TechDraw without QtGUI). It's possible that got lost in the mix, I will try to make some time to look for it in the next couple weeks.

    Isn't the Gui/App distinction is a compile-time one, but not a run time one? IE, we need the QtGUI module to use TechDraw, but I don't think that implies we need a GUI to use TechDraw.
    (0009619)
    wandererfan   
    2017-06-30 00:22   
    IIRC App is not supposed to link to Gui in C++? But it is ok to load QtGui from Python?

    My Python-fu is not strong. FreeCADCmd wouldn't let me import TechDrawGui or FreeCADGui so I couldn't use FreeCADGui.setupWithoutGUI().

    It is probably possible to create MDIViews and QGraphicsViews without actually showing them, but I have no idea how to do it.

    Would be great if you can find the script.
    (0009624)
    ian.rees   
    2017-07-01 03:58   
    Aha, so the thing I was referring to did get lost in the mix. Have a look at https://github.com/ianrrees/FreeCAD_tinkering/commit/e5d2a127924f4c6720c6dab6172d7b1bdd79a5a1

    Here's a relevant forum thread: https://forum.freecadweb.org/viewtopic.php?f=10&t=15835 .

    Hopefully the situation is nicer with Qt 5; I have a vague memory of thinking it would be (and perhaps that's why it was dropped at the time?).
    (0009640)
    wandererfan   
    2017-07-01 14:58   
    I'm going to consider the SVG part solved since it is possible to export a page as SVG with some additional Python.

    As for PDF I'd say that's a "won't fix" for now, unless there's a way to convert edge geometry to PDF "code".
    (0009652)
    Kunda1   
    2017-07-03 11:38   
    @wandererfan did you benefit the code that ian shared with you?
    Also in regards to 'a way to convert edge geometry to PDF "code"', should we post that question in the forums?
    (0009655)
    wandererfan   
    2017-07-03 15:35   
    That code is from a previous design that didn't quite work out.

    Looks like PDF uses PostScript internally so it should be possible to use similar strategy to viewPartAsPdf/viewPartAsDxf.
    (0009657)
    Kunda1   
    2017-07-03 17:41   
    @wandererfan should I open a separate ticket for the PDF portion of this ticket?
    (0009717)
    Kunda1   
    2017-07-11 20:04   
    @wandererfan ping
    (0009742)
    wandererfan   
    2017-07-12 16:17   
    Unless you need an extra "tickets resolved" for the monthly stats, I'd just leave it. ;)
    (0009743)
    Kunda1   
    2017-07-12 16:38   
    @wandererfan actually I was going to decrease monthly stats based on my offer to open a new ticket 0003077:0009657
    (0010466)
    wandererfan   
    2017-11-25 01:32   
    DXF not involved. Relationship to 2882 removed.
    (0012141)
    Kunda1   
    2018-11-07 00:47   
    @wandererfan question: Can i change the status away from 'feedback' ?
    (0012145)
    wandererfan   
    2018-11-07 13:28   
    @Kunda1 - what do you want to change it to?
    (0012147)
    Kunda1   
    2018-11-07 13:31   
    @wandererfan acknowledged or assigned ?
    (I'm cleaning out the 'feedback' tickets and was wondering if this was still in the 'feedback' stage.
    (0012151)
    wandererfan   
    2018-11-08 12:29   
    Not "assigned", because it is too far down the prior list (like v0.25?).

    Not sure what "acknowledged" means in the context of a feature request. "We acknowledge that you requested this feature"?

    Maybe we need a "no now, but maybe someday" status? or "not on current roadmap"?
    (0012156)
    Kunda1   
    2018-11-09 00:24   
    Changing to 'acknowledged' and will figure out how to classify it later.
    Thanks!
    (0016545)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5710.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3014 [TechDraw] Feature minor N/A 2017-05-01 11:55 2021-02-06 06:38
    Reporter: Kunda1 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: TechDraw - 2D Geometry
    Description: A number of 2D geometry functions were recently added to the Part module. This needs to be reviewed with an eye towards replacing custom 2D geometry code in TechDraw with standard code from Part.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016530)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5695.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3011 [TechDraw] Feature minor N/A 2017-05-01 11:47 2021-02-06 06:38
    Reporter: Kunda1 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: TechDraw - "broken view" - the ability to depict very large objects on the page.
    Description: "broken view" - the ability to depict very large objects on the page.
    (https://www.freecadweb.org/wiki/index.php?title=TechDraw_Roadmap)
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0014687)
    Kunda1   
    2020-07-25 11:55   
    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=35&t=48655
    (0016529)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5694.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3008 [TechDraw] Feature feature N/A 2017-04-29 15:15 2021-02-06 06:38
    Reporter: Kunda1 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: TechDraw - Drawing Tools
    Description: This includes the ability to add leaders, callouts and detail highlights to Views. It is a prerequisite to many enhancements, particularly in the drawing annotation area, such as feature control frames and reference highlights for detail views.
    (https://www.freecadweb.org/wiki/TechDraw_Roadmap)
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0011928)
    wandererfan   
    2018-10-05 12:42   
    This ticket is not related to the linked tickets.
    (0016528)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5693.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3005 [TechDraw] Feature feature N/A 2017-04-29 14:41 2021-02-06 06:38
    Reporter: Kunda1 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: TechDraw - Internal View Consistency
    Description: It is not currently possible to create a Detail from a Section or a MultiView , or a Section from a Detail due to internal differences. Changes here would allow any View type to be a BaseView.
    (https://www.freecadweb.org/wiki/TechDraw_Roadmap/en)
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016527)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5692.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2091 [Robot] General feature N/A 2015-05-06 23:09 2021-02-06 06:37
    Reporter: philius Platform: amd64  
    Assigned To: OS: Debian  
    Priority: normal OS Version: 8.0  
    Status: new Product Version: 0.15  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: 3D printer simulator - a new nodekit?
    Description: I tried understanding how the robots example works, but as a newbie the number of external references is daunting.

    I want to create a 3D printer model in freecad that shows a delta printer, although any other printer would help, but I'm using delta printer terms below.

    Its shows its print volume - the area it can 3D print in, in a different color.
    There are a couple of sliders to change:
    Delta arm length: affects print volume width+height
    Linear actuator length: affects print height, required linear bearings diameter
    Base radius: affects print area
    Delta arm distance: affects actuactor dimensions (the actuator is connected by 3 arm-pairs) which affects the print volume width

    It looks like the 6-axis robot model was developed outside of freecad, but it would be great if such models could be developed, edited and shared through freecad!
    Tags:
    Steps To Reproduce:
    Additional Information:
    System Description Using the Ubuntu vivid ppa with jessie->vivid in freecad-maintainers-freecad-daily-jessie.list
    Attached Files:
    Notes
    (0006124)
    philius   
    2015-05-07 11:12   
    Something like http://www.thinkyhead.com/_delta/
    but with a translucent print volume with some sliders.
    (0010344)
    Kunda1   
    2017-10-23 18:35   
    Interesting developments in the Path WB: https://forum.freecadweb.org/viewtopic.php?f=10&t=24923&p=196416#p196414
    (0010620)
    abdullah   
    2017-12-19 13:36   
    @kunda1

    This is not sketcher related.

    Do we need a robot WB project?
    (0010621)
    Kunda1   
    2017-12-19 14:39   
    CC @yorik
    (0010710)
    yorik   
    2018-01-05 19:34   
    Okay I added a Robot subproject.
    (0016463)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5628.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3822 [Raytracing] Feature feature N/A 2019-02-08 19:29 2021-02-06 06:36
    Reporter: mantielero Platform:  
    Assigned To: howetuft OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: OSPRay or Embree raytracing engines
    Description: I would like to suggest using OSPRay (or Embree) raytracing engines.

    OSPRAY provides a C and C++ API. It looks like OSPRay is among the fatest ray tracing engines:

    http://www.sweethome3d.com/blog/2018/08/24/photo_rendering_engines_performance_test.html

    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0012591)
    Kunda1   
    2019-02-08 21:48   
    @mantielero Please open a forum thread and post back here, thank you.
    (0012597)
    mantielero   
    2019-02-09 13:21   
    This is the discussion in the forum.
    (0015065)
    Kunda1   
    2020-12-03 22:46   
    @howetuft shall I open tickets on Render WB for this?
    (0015083)
    howetuft   
    2020-12-05 13:03   
    @Kunda1 I have created an issue in RenderWB github repo. I think we can close the present ticket!
    (0016716)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5881.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4328 [Project Tools & Websites] General minor always 2020-04-28 15:14 2021-02-06 06:36
    Reporter: tomkcook Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Ubuntu 20.04 LTS (ubuntu:GNOME/ubuntu)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.20816 (Git)
    Build type: Unknown
    Branch: master
    Hash: bc107eacc8e020a779b2bbcb21559283ee440268
    Python version: 3.8.2
    Qt version: 5.12.8
    Coin version: 4.0.0
    OCC version: 7.3.0
    Locale: English/United Kingdom (en_GB)
    Summary: Several "Scripted objects" examples don't work
    Description: See the examples on this wiki page.

    The "Basic example" works as advertised. But the "Other more complex example", when pasted directly into the FreeCAD python console, produces a couple of triangles, not the expected octahedron.

    And when it is modified as suggested in the section "Making objects selectable", only a single red line is shown in the 3D display (which is then not selectable).

    I have pasted my modified version of this code into the "Additional information" section because I couldn't make the file attachment work.

    I have tried this on a couple of builds from source, most recently on commit bc107eacc8e020a779b2bbcb21559283ee440268, as well as the 0.18.3 that is distributed with Ubuntu 19.10 and the 0.18.4 that is distributed with Ubuntu 20.04. None of them worked as expected, though there were minor variations in the results.
    Tags: #post-to-forum
    Steps To Reproduce: Open FreeCAD. Paste the attached code into the FreeCAD python console.
    Additional Information: import FreeCAD, FreeCADGui, Part
    import pivy
    from pivy import coin

    class Octahedron:
      def __init__(self, obj):
         "Add some custom properties to our box feature"
         obj.addProperty("App::PropertyLength","Length","Octahedron","Length of the octahedron").Length=1.0
         obj.addProperty("App::PropertyLength","Width","Octahedron","Width of the octahedron").Width=1.0
         obj.addProperty("App::PropertyLength","Height","Octahedron", "Height of the octahedron").Height=1.0
         obj.addProperty("Part::PropertyPartShape","Shape","Octahedron", "Shape of the octahedron")
         obj.Proxy = self

      def execute(self, fp):
         # Define six vetices for the shape
         v1 = FreeCAD.Vector(0,0,0)
         v2 = FreeCAD.Vector(fp.Length,0,0)
         v3 = FreeCAD.Vector(0,fp.Width,0)
         v4 = FreeCAD.Vector(fp.Length,fp.Width,0)
         v5 = FreeCAD.Vector(fp.Length/2,fp.Width/2,fp.Height/2)
         v6 = FreeCAD.Vector(fp.Length/2,fp.Width/2,-fp.Height/2)
         
         # Make the wires/faces
         f1 = self.make_face(v1,v2,v5)
         f2 = self.make_face(v2,v4,v5)
         f3 = self.make_face(v4,v3,v5)
         f4 = self.make_face(v3,v1,v5)
         f5 = self.make_face(v2,v1,v6)
         f6 = self.make_face(v4,v2,v6)
         f7 = self.make_face(v3,v4,v6)
         f8 = self.make_face(v1,v3,v6)
         shell=Part.makeShell([f1,f2,f3,f4,f5,f6,f7,f8])
         solid=Part.makeSolid(shell)
         fp.Shape = solid

      # helper mehod to create the faces
      def make_face(self,v1,v2,v3):
         wire = Part.makePolygon([v1,v2,v3,v1])
         face = Part.Face(wire)
         return face

    class ViewProviderOctahedron:
      def __init__(self, obj):
         "Set this object to the proxy object of the actual view provider"
         obj.addProperty("App::PropertyColor","Color","Octahedron","Color of the octahedron").Color=(1.0,0.0,0.0)
         obj.Proxy = self

      def attach(self, obj):
         "Setup the scene sub-graph of the view provider, this method is mandatory"
         self.shaded = coin.SoGroup()
         self.wireframe = coin.SoGroup()
         self.scale = coin.SoScale()
         self.color = coin.SoBaseColor()

         self.data=coin.SoCoordinate3()
         self.face=coin.SoIndexedLineSet()

         selectionNode = coin.SoType.fromName("SoFCSelection").createInstance()
         selectionNode.documentName.setValue(FreeCAD.ActiveDocument.Name)
         selectionNode.objectName.setValue(obj.Object.Name) # here obj is the ViewObject, we need its associated App Object
         selectionNode.subElementName.setValue("Face")
         selectionNode.addChild(self.face)

         self.shaded.addChild(self.scale)
         self.shaded.addChild(self.color)
         self.shaded.addChild(self.data)
         self.shaded.addChild(selectionNode)
         #self.shaded.addChild(self.face)
         obj.addDisplayMode(self.shaded,"Shaded");
         style=coin.SoDrawStyle()
         style.style = coin.SoDrawStyle.LINES
         self.wireframe.addChild(style)
         self.wireframe.addChild(self.scale)
         self.wireframe.addChild(self.color)
         self.wireframe.addChild(self.data)
         self.wireframe.addChild(selectionNode)
         #self.shaded.addChild(self.face)
         obj.addDisplayMode(self.wireframe,"Wireframe");
         self.onChanged(obj,"Color")

      def updateData(self, fp, prop):
         "If a property of the handled feature has changed we have the chance to handle this here"
         # fp is the handled feature, prop is the name of the property that has changed
         if prop == "Shape":
            s = fp.getPropertyByName("Shape")
            self.data.point.setNum(6)
            cnt=0
            for i in s.Vertexes:
               self.data.point.set1Value(cnt,i.X,i.Y,i.Z)
               cnt=cnt+1
            
            self.face.coordIndex.set1Value(0,0)
            self.face.coordIndex.set1Value(1,1)
            self.face.coordIndex.set1Value(2,2)
            self.face.coordIndex.set1Value(3,-1)

            self.face.coordIndex.set1Value(4,1)
            self.face.coordIndex.set1Value(5,3)
            self.face.coordIndex.set1Value(6,2)
            self.face.coordIndex.set1Value(7,-1)

            self.face.coordIndex.set1Value(8,3)
            self.face.coordIndex.set1Value(9,4)
            self.face.coordIndex.set1Value(10,2)
            self.face.coordIndex.set1Value(11,-1)

            self.face.coordIndex.set1Value(12,4)
            self.face.coordIndex.set1Value(13,0)
            self.face.coordIndex.set1Value(14,2)
            self.face.coordIndex.set1Value(15,-1)

            self.face.coordIndex.set1Value(16,1)
            self.face.coordIndex.set1Value(17,0)
            self.face.coordIndex.set1Value(18,5)
            self.face.coordIndex.set1Value(19,-1)

            self.face.coordIndex.set1Value(20,3)
            self.face.coordIndex.set1Value(21,1)
            self.face.coordIndex.set1Value(22,5)
            self.face.coordIndex.set1Value(23,-1)

            self.face.coordIndex.set1Value(24,4)
            self.face.coordIndex.set1Value(25,3)
            self.face.coordIndex.set1Value(26,5)
            self.face.coordIndex.set1Value(27,-1)

            self.face.coordIndex.set1Value(28,0)
            self.face.coordIndex.set1Value(29,4)
            self.face.coordIndex.set1Value(30,5)
            self.face.coordIndex.set1Value(31,-1)

      def getDisplayModes(self,obj):
         "Return a list of display modes."
         modes=[]
         modes.append("Shaded")
         modes.append("Wireframe")
         return modes

      def getDefaultDisplayMode(self):
         "Return the name of the default display mode. It must be defined in getDisplayModes."
         return "Shaded"

      def setDisplayMode(self,mode):
         return mode

      def onChanged(self, vp, prop):
         "Here we can do something when a single property got changed"
         FreeCAD.Console.PrintMessage("Change property: " + str(prop) + "\n")
         if prop == "Color":
            c = vp.getPropertyByName("Color")
            self.color.rgb.setValue(c[0],c[1],c[2])

      def getIcon(self):
         return """
            /* XPM */
            static const char * ViewProviderBox_xpm[] = {
            "16 16 6 1",
            " c None",
            ". c #141010",
            "+ c #615BD2",
            "@ c #C39D55",
            "# c #000000",
            "$ c #57C355",
            " ........",
            " ......++..+..",
            " .@@@@.++..++.",
            " .@@@@.++..++.",
            " .@@ .++++++.",
            " ..@@ .++..++.",
            "###@@@@ .++..++.",
            "##$.@@$#.++++++.",
            "#$#$.$$$........",
            "#$$####### ",
            "#$$#$$$$$# ",
            "#$$#$$$$$# ",
            "#$$#$$$$$# ",
            " #$#$$$$$# ",
            " ##$$$$$# ",
            " ####### "};
            """

      def __getstate__(self):
         return None

      def __setstate__(self,state):
         return None

    FreeCAD.newDocument()
    a=FreeCAD.ActiveDocument.addObject("App::FeaturePython","Octahedron")
    Octahedron(a)
    ViewProviderOctahedron(a.ViewObject)
    Attached Files:
    Notes
    (0014386)
    openBrain   
    2020-04-28 19:45   
    @tomkcook : Please address your issue according our reporting guidelines by first opening a topic on our forum ("Python" subsection) so community can vet the issue and narrow down the causes. Cross-link the topic with this ticket. Thx
    (0014388)
    tomkcook   
    2020-04-29 07:59   
    @openBrain : I raised the problems described in this thread and got very little response. If that thread reaches a resolution and you want to assign me a wiki login, I'm very happy to update the documentation myself.
    (0014390)
    tomkcook   
    2020-04-30 10:52   
    Have also just verified the same result using the latest AppImage version downloaded from the FreeCAD website.
    (0016886)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6052.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4299 [Project Tools & Websites] General minor always 2020-03-30 16:06 2021-02-06 06:36
    Reporter: kkremitzki Platform:  
    Assigned To: kkremitzki OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Debian GNU/Linux bullseye/sid
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.4.
    Build type: Release
    Python version: 3.7.6
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.3.0
    Locale: English/United States (en_US)
    Summary: Non-ASCII usernames in MediaWiki not working
    Description: For example, a username containing "andrë" does not work (can't be created.) Need to make sure the database encoding is correct.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016875)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6041.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4271 [Project Tools & Websites] General feature N/A 2020-02-21 17:06 2021-02-06 06:36
    Reporter: Kunda1 Platform:  
    Assigned To: kkremitzki OS:  
    Priority: none OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:  
    Summary: Wiki: Test the Mediawiki:YouTube extension to embed videos on the wiki
    Description: https://www.mediawiki.org/wiki/Extension:YouTube

    gitter.im thread reference (link)
    Tags:
    Steps To Reproduce:
    Additional Information: Thanks @kkremitzki !
    Attached Files:
    Notes
    (0016869)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6035.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4033 [Project Tools & Websites] General major N/A 2019-06-22 22:30 2021-02-06 06:36
    Reporter: Kunda1 Platform:  
    Assigned To: yorik OS:  
    Priority: high OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Translations of External workbenches need to be incorporated in to Crowdin (import/export) translation scripts
    Description: The following workbenches
    • BIM Workbench
    • Ship workench
    • Plot workbench
    • and others (WBs and Macros) in the future
    need to be incorporated in to the Crowdin python scripts since they are now external to FreeCAD master (aka out of core).
    The script needs to pull their translations in to Crowdin and then export them back out. Perhaps this also involves creating automatic PRs or else the script has commit access to said workbenches and auto-commits the translations.

    Not sure exactly what the right solution is, but nevertheless, something needs to be done. Especially since more and more workbenches will opt to be translated in the future (now that @yorik figured out how said workbenches and macros can utilize Qt translation methods and recently posted on how to do this)
    Tags: translation
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016786)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5952.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4019 [Project Tools & Websites] Feature minor N/A 2019-06-13 17:10 2021-02-06 06:36
    Reporter: Kunda1 Platform:  
    Assigned To: yorik OS:  
    Priority: low OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FreeCAD Website - .htaccess hack to dissappear .php extension from URL
    Description: Currently the website displays
    /downloads.php
    The request is to update the
    .htaccess
    so that the extension will be invisible AKA
    /downloads

    Related Forum thread

    Github issue: https://github.com/FreeCAD/FreeCAD-Homepage/issues/42
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0013218)
    Kunda1   
    2019-06-15 14:44   
    (Last edited: 2019-06-15 14:48)
    Solution: In the .htacccess file add the following lines:
    
    #remove php file extension-e.g. https://example.com/file.php will become https://example.com/file
    RewriteEngine on 
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_FILENAME}\.php -f
    RewriteRule ^(.*)$ $1.php [NC,L]
    
    RedirectPermanent /download.php /downloads
    RedirectPermanent /download /downloads 
    
    

    (0016780)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5946.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3821 [Project Tools & Websites] General feature N/A 2019-02-08 17:25 2021-02-06 06:36
    Reporter: Kunda1 Platform:  
    Assigned To: David_D OS:  
    Priority: low OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Docker container for FreeCAD development
    Description: https://forum.freecadweb.org/viewtopic.php?f=4&t=34046&p=285576#p285576


    I tried to make something similar once, but this wasn't successful https://github.com/FreeCAD/FreeCAD_Conda/blob/master/utils/fc_conda_docker/cached_build/Dockerfile It would be nice to have a docker container including all the dependencies of freecad, an ide (like kdevelop), git, and the freecad source. Ideally everything should be compiled already (maybe in debug-mode).

    So to get started with freecad development all one has to do is:

    docker run --name freecad-dev freecad/freecad-development

    and this starts the ide.
    This would be soooo useful.

    looo
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0012631)
    David_D   
    2019-02-12 17:50   
    I'm working on this here, and working on a docker container with the up-to-date dependencies here.
    (0012632)
    Kunda1   
    2019-02-12 20:00   
    @David_D fantastic. I've elevated your privileges since this is a very important task. Cheers!
    (0012844)
    David_D   
    2019-03-04 04:22   
    I have gotten the docker image to a level that I am satisfied with it as a proof of concept. @Kunda1, would you, or some other interested party be good enough to test the docker image on their machine?

    I am aware it is missing the WebView and FEM modules. I will add them later.

    Instructions of it's use is available on it's readme.
    (0014130)
    Kunda1   
    2020-02-01 14:48   
    Update: https://forum.freecadweb.org/viewtopic.php?f=4&t=42954
    (0016715)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5880.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3797 [Project Tools & Websites] Feature minor N/A 2019-01-26 01:22 2021-02-06 06:36
    Reporter: Kunda1 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Script that checks if AppImage .zsync file is present in Github Release page
    Description: Every so often github or travisci fail in some way and in those situations there are edge cases where an AppImage .zsync file won't be uploaded to Github. This effects people who are using The AppImageUpdate scripts that can automate AppImage updates on their local machines.

    Forum thread where the phenomena is mentioned: https://forum.freecadweb.org/viewtopic.php?f=10&t=15525&start=330#p282404

    What may be needed is a script that checks to see that the appimages and their companion files are indeed on the GH release page. If not, let someone know or trigger another build in order to correc that.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016708)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5873.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3711 [Project Tools & Websites] General minor N/A 2018-12-02 23:00 2021-02-06 06:36
    Reporter: Kunda1 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FreeCAD wiki mobile friendly stylesheet
    Description: ATM the freecad wiki is not mobile friendly as described in https://forum.freecadweb.org/viewtopic.php?f=21&t=32277&start=20#p270798

    NormandC writes in the later in the thread:

    This is actually not about making only the download page look nice, but making the whole wiki usable on a smartphone. The sidebar and icons, as well as symbols like bullet points do not scale, therefore they are microscopic.

    I frequently check the wiki out on my smartphone, I think it would be useful to fix this.

    NormandC
    Tags: wiki
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016676)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5841.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3546 [Project Tools & Websites] Feature minor N/A 2018-07-24 19:46 2021-02-06 06:36
    Reporter: normandc Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: [Forum] Embed PeerTube videos with the video tag
    Description: PeerTube is an open source, distributed (peer-to-peer) video sharing platform.

    https://joinpeertube.org/en/

    While this platform is just starting, it would be relevant to make the video tag compatible with PeerTube videos.

    Use of the following in a forum post:

    [video]https://framatube.org/videos/embed/217eefeb-883d-45be-b7fc-a788ad8507d3[/video]]
    Produces a black screen with the message "Sorry, this URL is not supported".

    Embedded html code looks like this:

    <iframe width="560" height="315" sandbox="allow-same-origin allow-scripts" src="https://framatube.org/videos/embed/217eefeb-883d-45be-b7fc-a788ad8507d3" frameborder="0" allowfullscreen></iframe>
    Tags:
    Steps To Reproduce:
    Additional Information: Forum topic: https://forum.freecadweb.org/viewtopic.php?f=8&t=29669
    Attached Files:
    Notes
    (0011552)
    Kunda1   
    2018-07-27 14:12   
    Doing an initial websearch on how to add peertube to phpbb results with nothing. An upstream issue needs to be opened on phpbb forum.
    (0011553)
    Kunda1   
    2018-07-27 14:21   
    CCing @kkremitzki
    (0011894)
    Kunda1   
    2018-10-02 21:09   
    @kkremitzki ping
    (0011895)
    Kunda1   
    2018-10-02 21:09   
    Assigned to kkremitzki
    (0011900)
    kkremitzki   
    2018-10-02 23:54   
    I'm unassigning myself as I don't think issue is really actionable. The [video] tag is not actually from phpBB, it's a 3rd party extension which has been unmaintained since 2013; modifying it ourselves would involve editing this file to add the feature: http://phpbbex.com/api/bbmedia.js and while it may be possible to do so, the gain is way too small for the effort required.
    (0011902)
    Kunda1   
    2018-10-03 16:04   
    (Last edited: 2018-10-03 16:04)
    When I get a chance I'll open a phpbb forum thread and ask there if any solutions are readily available for us to use instead of code.

    (0016633)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5798.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3328 [Project Tools & Websites] Bug minor have not tried 2018-01-26 08:28 2021-02-06 06:36
    Reporter: kkremitzki Platform:  
    Assigned To: AR795 OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Make new MediaWiki skin with nav header
    Description: The FreeCAD skin for MediaWiki is based on an unsupported skin, and with the wiki upgrade to 1.30, it broke for the last time. We need to make a new skin based on the upstream-supported Vector skin, and include a navigation bar/customize the aesthetics to fit the FreeCAD color scheme.

    This can be tested on staging.freecad.io/wiki easily.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016595)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5760.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2731 [Project Tools & Websites] Feature minor N/A 2016-10-10 20:56 2021-02-06 06:36
    Reporter: krichter Platform: Linux  
    Assigned To: OS: Ubuntu  
    Priority: normal OS Version: 16.04  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Add exception stacktrace upload function (AKA crash reporting)
    Description: I'm experiencing a lot (> 10) exception following basic tutorials for the Arch, Part design and FEM module with a lot of different version from Ubuntu, PPA and source builds (both stable and unstable variants). Since I think that this is most likely due to a deeper issue (insufficient test coverage, patch review system, etc.) which takes a long time to fix, I suggest to at least profit from users wanting to contribute, but being unable to file these large amounts of reports for bugs which they encounter already at a basic, non-exotic use case level, and introduce an automatic or semi-automatic upload system for exception stacktrace which the user can activate in order to make a quick, but realistic contribution.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0008732)
    Kunda1   
    2017-03-29 12:57   
    Different discussion occurring on the forum about Breakpad: https://forum.freecadweb.org/viewtopic.php?f=10&t=21421
    (0016502)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5667.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4551 [Path] Bug minor always 2021-02-03 18:42 2021-02-06 06:33
    Reporter: sliptonic Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: <!--ATTENTION:
    COMPLETELY ERASE THIS AFTER PASTING YOUR
    Help > About FreeCAD > Copy to clipboard
    NOTE: just the snippet alone will do without anything else included.
    The ticket will not be submitted without it.
    -->
    Summary: PathGeom.edgeForCmd() function can't handle full-turn circles.
    Description: PathGeom.edgeForCmd() function is intended to take a Path Command (pseudo gcode) and return a corresponding Part Edge.

    However, has an implicit assumption about the working plane. The assumption is set by setting a G17/18/19 command to select the XY, XZ, YZ plane in which an arc will exist. Arcs in other planes are not supported at all.

    Since there are an infinte number of solutions to for a 360 degree arc that starts and ends on the same point and passes through another point at the midpoint, OCC throws an error.

    Tags:
    Steps To Reproduce:
    Additional Information: PathGeom.edgeForCmd() should take a named argument for plane which defaults to the XY plane.
    It should detect the full circle case and return a circular edge.
    Attached Files:
    Notes
    (0016987)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6155.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4545 [Path] Feature feature N/A 2021-01-29 16:13 2021-02-06 06:33
    Reporter: sliptonic Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: <!--ATTENTION:
    COMPLETELY ERASE THIS AFTER PASTING YOUR
    Help > About FreeCAD > Copy to clipboard
    NOTE: just the snippet alone will do without anything else included.
    The ticket will not be submitted without it.
    -->
    Summary: Allow engraving of 3D paths.
    Description: engraving currently assumes 2D paths. In some cases it would be useful to engrave paths that have a z axis component.
    Tags:
    Steps To Reproduce:
    Additional Information: forum thread
    https://forum.freecadweb.org/viewtopic.php?f=15&t=54860&p=472185#p472185
    Attached Files:
    Notes
    (0016985)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6153.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4532 [Path] Bug minor always 2021-01-12 19:25 2021-02-06 06:33
    Reporter: sliptonic Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Linux Mint 20 (i3/i3)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.23587 +23 (Git)
    Build type: Unknown
    Branch: (HEAD detached at mlampert/feature/toolbit-free-properties)
    Hash: e0f1829ac9238b52bc6f2050b7bf1b2a7d8a69be
    Python version: 3.8.5
    Qt version: 5.12.8
    Coin version: 4.0.0
    OCC version: 7.3.0
    Locale: English/United States (en_US)
    Summary: Canceling a dressup does not clean up properly
    Description: If user tries to add a dressup and then cancels before completing, the project is not cleaned up properly and the dressup is created anyway.
    Tags:
    Steps To Reproduce: Create a job and operation.
    Select an operation and add a dressup.
    Once the task panel opens, press 'cancel'
    note the state of the tree.
    Additional Information: This affects all dressups.
    Attached Files:
    Notes
    (0016981)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6149.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4507 [Path] Feature minor N/A 2020-12-01 23:27 2021-02-06 06:33
    Reporter: sliptonic Platform:  
    Assigned To: sliptonic OS:  
    Priority: normal OS Version:  
    Status: resolved Product Version:  
    Product Build: Resolution: fixed  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Linux Mint 19.3 (i3/i3)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.23137 +10 (Git)
    Build type: Unknown
    Branch: (HEAD detached at upstream/pr/4089)
    Hash: 0c9536df0dc63e0a650b96dc8514aba07e9ffac9
    Python version: 3.6.9
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    Summary: Add depth support to vcarve operation
    Description: Vcarve is currently 'centerline' engraving. It derives its depths from the tool geometry.
    However, the operation should have support for depths as well. This would allow the user to set a maximum depth to keep the tool from going too deep in thin material. It would also allow for step-down passes.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0015050)
    sliptonic   
    2020-12-02 21:06   
    vcarving is almost always done in a single pass.
    do not implement step-downs unless users identify a necessary use-case
    (0015051)
    sliptonic   
    2020-12-02 21:10   
    https://github.com/FreeCAD/FreeCAD/pull/4102
    (0015149)
    sliptonic   
    2020-12-16 00:07   
    https://github.com/FreeCAD/FreeCAD/pull/4143
    (0015169)
    Kunda1   
    2020-12-22 00:56   
    FreeCAD master c80adf8c
    FreeCAD master b920bbf7
    (0016968)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6135.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4476 [Path] Feature minor have not tried 2020-10-27 15:16 2021-02-06 06:33
    Reporter: sliptonic Platform:  
    Assigned To: sliptonic OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Linux Mint 19.3 (i3/i3)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.22865 +9 (Git)
    Build type: Unknown
    Branch: feature/toolbitdock
    Hash: 0a3ff2279f99b5b15925eb03aff5ab1567b1a798
    Python version: 3.6.9
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    Summary: Path Inspect tool doesn't respect user's preferred units
    Description: Inspecting gcode always shows in FreeCAD internal units (mm) rather than the user's selected unit.

    Make the inspection tool smarter about units.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016955)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6122.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4468 [Path] Feature feature N/A 2020-10-18 20:55 2021-02-06 06:33
    Reporter: sliptonic Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: <!--ATTENTION:
    COMPLETELY ERASE THIS AFTER PASTING YOUR
    Help > About FreeCAD > Copy to clipboard
    NOTE: just the snippet alone will do without anything else included.
    The ticket will not be submitted without it.
    -->
    Summary: FreeCAD Path needs a new Postprocessor architecture.
    Description: The current post-processor architecture requires individual .py files for each post. This is flexible in allowing users to copy an existing post and modify it but results in lots of duplicated code and redundant work.
    Changes and improvements made in one post don't become part of the other posts so bugs and incompatibilities persist.
    Tags:
    Steps To Reproduce:
    Additional Information: A better architecture would allow code reuse while preserving the users ability to customize the post to their needs.
    Attached Files:
    Notes
    (0016950)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6117.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4465 [Path] Bug minor always 2020-10-18 03:31 2021-02-06 06:33
    Reporter: anka Platform: MacOSx  
    Assigned To: OS: OSX  
    Priority: normal OS Version: 10.16.7  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: macOS 10.15
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.22670 (Git)
    Build type: Release
    Branch: master
    Hash: 12155f4aab09047c5697db0c1b3cf93b02edda03
    Python version: 3.8.6
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: C/Default (C)
    Summary: Path toolbox operation order fails
    Description: Using drag and drop feature when rearranging job-path operations, moved operation gets detached from operations group.
    Tags:
    Steps To Reproduce: The issue can be reproduced this way

    In comboview
    1. double-click on operations
    2. drag operation downwards and drop
    3. click OK (operation disappears from list after dropping - gets detached from operations group)

    For illustrated steps, look here
    https://forum.freecadweb.org/viewtopic.php?f=3&t=50161#p440189
    Additional Information:
    System Description
    Attached Files:
    Notes
    (0016948)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6115.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4459 [Path] Feature minor always 2020-10-15 02:31 2021-02-06 06:33
    Reporter: anka Platform: mac  
    Assigned To: OS: macosx  
    Priority: normal OS Version: 10.16.7  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: macOS 10.15
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.22670 (Git)
    Build type: Release
    Branch: master
    Hash: 12155f4aab09047c5697db0c1b3cf93b02edda03
    Python version: 3.8.6
    Qt version: 5.12.9
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: C/Default (C)
    Summary: annoying : confirmation popup window hidden behind main-window
    Description: trying to add tool-controllers if more than one path-job exists, pops up a confirmation window for selecting the path-job.
    this selection window is not modal, but hidden behind main window.

    (seems to happen only in mac version)

    see also : https://forum.freecadweb.org/viewtopic.php?f=3&t=51135
    Tags: #pending
    Steps To Reproduce: Gene gave a brief explanation that resumes best:

    'I click the tool icon, my tool library pops up, I select a tool and create a controller. I am then asked which job gets the tool.
    The popup of last step is hidden behind main-window !!!


    There'e is an alternative (described by Chris):
    Select the pathjob **, edit it (double click), select 'Tools', then 'add', tool library pops up, select a tool and create a controller
    Doing it this way, I would find more logical if selected controller is created in the pathjob ** the procedure started with. For now, freecad also asks as final step to select a job.

    Additional Information:
    Attached Files:
    Notes
    (0016947)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6114.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4458 [Path] Bug minor always 2020-10-12 17:23 2021-02-06 06:33
    Reporter: sliptonic Platform:  
    Assigned To: sliptonic OS:  
    Priority: normal OS Version:  
    Status: resolved Product Version:  
    Product Build: Resolution: fixed  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: <!--ATTENTION:
    COMPLETELY ERASE THIS AFTER PASTING YOUR
    Help > About FreeCAD > Copy to clipboard
    NOTE: just the snippet alone will do without anything else included.
    The ticket will not be submitted without it.
    -->
    Summary: [PATH] Engrave 'start at vertex' gives wrong path
    Description: The engraving operation allows for changing the vertex to start at. Some values produce correct paths. Others
    produce paths that gouge the part.
    Tags:
    Steps To Reproduce: Create a cube.
    Create a job and add an engrave operation
    Select the four edges on the top face and add them to the base tab of the engrave
    The path should generate correctly.
    change the 'start at vertex' property to '3' and recompute

    The starting position is recalculcated but the path now gouges the part and misses one edge.
    Additional Information:
    Attached Files:
    Notes
    (0015135)
    gauna   
    2020-12-13 16:28   
    (Last edited: 2020-12-13 16:28)
    PR:
    https://github.com/FreeCAD/FreeCAD/pull/4136
    (0015151)
    sliptonic   
    2020-12-16 00:09   
    https://github.com/FreeCAD/FreeCAD/pull/4136
    (0015168)
    Kunda1   
    2020-12-22 00:48   
    FreeCAD master 07e2e8fc
    (0016946)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6113.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4435 [Path] Bug major always 2020-09-14 18:20 2021-02-06 06:33
    Reporter: gauna Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Manjaro Linux (KDE//usr/share/xsessions/plasma)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.22443 (Git)
    Build type: Unknown
    Branch: master
    Hash: 3fd492fabe0868928a031507d94ff788a15286b5
    Python version: 3.8.5
    Qt version: 5.15.0
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: German/Germany (de_DE)
    Summary: Wrong cut side of profil tool
    Description: Path generated by profil tool is located on the wrong side under certain circumstances. Maybe there are some rounding issues with "Final Depth".

    Thread with a more detailed description: https://forum.freecadweb.org/viewtopic.php?f=15&t=50172
    Tags:
    Steps To Reproduce: See thread.
    Additional Information:
    Attached Files: Screenshot_20200913_111336.png (8,204 bytes) 2020-09-14 18:20
    https://tracker.freecad.org/file_download.php?file_id=2524&type=bug
    Screenshot_20200913_205322.png (32,124 bytes) 2020-09-14 18:20
    https://tracker.freecad.org/file_download.php?file_id=2525&type=bug
    Screenshot_20200913_205755.png (25,280 bytes) 2020-09-14 18:20
    https://tracker.freecad.org/file_download.php?file_id=2526&type=bug
    Screenshot_20200914_194940.png (40,058 bytes) 2020-09-14 18:20
    https://tracker.freecad.org/file_download.php?file_id=2527&type=bug
    Test2.FCStd (31,722 bytes) 2020-09-14 18:20
    https://tracker.freecad.org/file_download.php?file_id=2528&type=bug
    Notes
    (0015106)
    russ4262   
    2020-12-07 06:29   
    (Last edited: 2020-12-07 06:32)
    This behavior is not so much a bug, as a error due to improper usage for open-edge profiling.
     
    True, selection of bottom edges for combined purposes of setting geometry and Final Depth is intuitive and logical. However, due to the current implementation of the open-edge feature, it requires top edges be selected and a Final Depth to be set manually. Perhaps rethinking the approach to profiling open-edges will yield a return to the ability to select bottom edges as a means to fewer user inputs and easier, simpler usage.

    This requirement to select top edges is noted in the Usage section of the Profile wiki page and has been there since 15 September 2020 per wiki history.
    (0015107)
    Kunda1   
    2020-12-07 11:24   
    @russ4262 then should we flip this ticket to a 'feature' instead of a bug and reword it a bit to reflect why?
    (0016937)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6104.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4406 [Path] Bug minor always 2020-07-15 06:56 2021-02-06 06:33
    Reporter: janc.linders Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Ubuntu 18.04.4 LTS (LXDE/Lubuntu)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.21975 (Git)
    Build type: Unknown
    Branch: master
    Hash: 9b18c2dc196e294ed00850897894eb5d0d9435a2
    Python version: 3.6.9
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    Summary: Increasing Memory usage when using Path WB and Adaptive Processing
    Description: Using the PATH WB and Adaptive processing not releasing memory.
    Repeating the PostProcessing into a GRBL file increases the memory use until exhausted.
    Tags: #post-to-forum
    Steps To Reproduce: A simple test file is over 2 Mb. Not able to attach.
    Is there another way to share this ?

    Here are the steps.

    Goto PART WB
    Create 2 simple boxes (10,10,10) (5,5,5)
    Cut small from big box leaving a pocket in the huge box
    Switch the PATH WB.
    Process the pocket using Adaptive Processing.
    Post Process to GRBL

    Lowering the StepDown from 0,1 mm to 0,01 mm shows it even better.
    Additional Information:
    Attached Files:
    Notes
    (0014684)
    openBrain   
    2020-07-25 09:47   
    @janc.linders : please address your issue by first opening a topic in our forum (as per our reporting guidelines). Thx
    (0014688)
    janc.linders   
    2020-07-25 14:33   
    @openBrain : Hi , Sure, I'll address this is the forum first.
    Should i place the status of this in suspended ?

    Regards,
    (0014689)
    openBrain   
    2020-07-25 16:54   
    @janc.linders : don't care too much about the status. :) Please just cross-post links between here and the topic you'll open. ;) Thx
    (0014693)
    Kunda1   
    2020-07-31 13:10   
    @janc.linders has this been posted to the forum yet?
    (0014695)
    janc.linders   
    2020-07-31 19:19   
    @Kunda1 , yes it has been posted in the forum.
    See : Using the PATH WB and Adaptive processing not releasing memory. Repeating the PostProcessing into a GRBL file increases.
    (0014783)
    sliptonic   
    2020-10-06 23:07   
    I believe the issue is related to this discussion.
    https://forum.freecadweb.org/viewtopic.php?f=15&t=50583

    A PR is pending.
    (0014866)
    Kunda1   
    2020-10-15 15:58   
    Can this issue be retested since FreeCAD master ab4ab444 was committed ?
    Please update to the latest v0.19 to test.
    @sliptonic @janc.linders
    (0014870)
    janc.linders   
    2020-10-15 17:30   
    I have downloaded the latest nightly.
    Is that ok to test the resolution for this issue ?

    OS: Ubuntu 18.04.5 LTS (XFCE/xubuntu)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.
    Build type: Release
    Branch: unknown
    Hash: 71cd301ca78259c55398a0919e3277fe3cc0a390
    Python version: 3.6.9
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    (0014871)
    sliptonic   
    2020-10-15 17:49   
    In my testing, the situation is better but not completely resolved. I think there's still a memory leak related only to the adaptive operation and having nothing to do with the grbl post.
    There's still one change to the grbl post which has not been merged yet.
    (0014872)
    janc.linders   
    2020-10-15 17:54   
    First testing shows indeed an improvement. Less increase. :-)
    Also (for me at least) a strange behavior is that after you completely close the design , the memory stays high.
    I would expect that memory use drops after closing a document.
    Restarting and loading the model brings it back to the start usage.
    (0016925)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6092.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4320 [Path] Feature minor N/A 2020-04-21 14:38 2021-02-06 06:33
    Reporter: sliptonic Platform:  
    Assigned To: sliptonic OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Support incremental Gcode in postprocessors
    Description: Some machine controls require gcode to be incrmental. We currently don't have any postprocessors that work this way so there's no reference implementation.

    https://forum.freecadweb.org/viewtopic.php?f=15&t=44554&p=380569&hilit=edm#p380569
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files: relative_post.py (16,164 bytes) 2020-04-22 22:48
    https://tracker.freecad.org/file_download.php?file_id=2459&type=bug
    Notes
    (0014366)
    sliptonic   
    2020-04-22 22:48   
    I really need a sample file and gcode to work with but here's an early attempt to try.

    I made a 10x10 cube and profiled it without compensation. Use the attached postprocessor with the following parameters
    --no-header --relative --axis-modal --line-numbers

    The output looks like this:

    N105 (begin preamble)
    N110 G17 G54 G40 G49 G80 G91
    N115 G91
    N120 G21
    N125 (begin operation: Fixture)
    N130 (machine: not set, mm/min)
    N135 G54
    N140 (finish operation: Fixture)
    N145 (begin operation: Spot Drill001)
    N150 (machine: not set, mm/min)
    N155 (Spot Drill001)
    N160 M5
    N165 M6 T2
    G43 H2
    N170 M3 S0
    N175 (finish operation: Spot Drill001)
    N180 (begin operation: Contour)
    N185 (machine: not set, mm/min)
    N190 (Contour)
    N195 (Uncompensated Tool Path)
    N200 G0 Z+016000
    N205 G0 X+005000 Y+005000
    N210 G0 Z-002000
    N215 G1 Z-014000
    N220 G1 Y-010000
    N225 G1 X-010000
    N230 G1 Y+010000
    N235 G1 X+010000
    N240 G0 Z+016000
    N245 (finish operation: Contour)
    (begin postamble)
    N250 M05
    N255 G17 G54 G90 G80 G40
    N260 M2
    (0014367)
    sliptonic   
    2020-04-22 23:15   
    The attached post has two kinds of changes in it. The changes to make the relative gcode are, I think, broadly applicable and should be included in the linuxcnc reference post processor.

    The changes to format the numbers in a specific way is unique to the Geg's EDM machine and should not be included.
    (0016883)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6049.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4280 [Path] Bug major always 2020-03-05 09:20 2021-02-06 06:33
    Reporter: dubstar_04 Platform:  
    Assigned To: OS:  
    Priority: high OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Debian GNU/Linux 10 (buster) (GNOME/gnome)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.19803 (Git)
    Build type: Unknown
    Branch: master
    Hash: 1bd4a173ef1e8a68e074ef9a7e6003430eac5e2d
    Python version: 3.7.3
    Qt version: 5.11.3
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedKingdom (en_GB)
    Summary: LeadinLeadout DressUp Causes Tool Crash on Deburr Ops
    Description: Forum Post: https://forum.freecadweb.org/viewtopic.php?f=15&t=43896
    Tags:
    Steps To Reproduce: Create a deburr operation, Add a leadinleadout dressup.

    observe that part of the deburr path is likely missing and the path intersects the model.
    Additional Information:
    Attached Files: LeadIn.png (22,590 bytes) 2020-03-05 09:20
    https://tracker.freecad.org/file_download.php?file_id=2445&type=bug
    image.png (10,259 bytes) 2021-01-14 21:27
    https://tracker.freecad.org/file_download.php?file_id=2597&type=bug
    image-2.png (5,444 bytes) 2021-01-14 21:27
    https://tracker.freecad.org/file_download.php?file_id=2598&type=bug
    image-3.png (8,291 bytes) 2021-01-14 21:27
    https://tracker.freecad.org/file_download.php?file_id=2599&type=bug
    Notes
    (0014208)
    Kunda1   
    2020-03-05 19:22   
    @dubstar_04 please add the FC info in the field dedicated to it called 'FreeCAD Information' for posterity reviewers/devs etc...
    (0015208)
    dubstar_04   
    2021-01-14 21:27   
    The original issue seems to be resolved however on internal edges the path still intersects the part. This can be worked around by changing the entry point to an outside edge.

    Due to the workaround the priority could now be reduced to low but the issue could be revisited.
    (0015214)
    schildkroet   
    2021-01-19 17:04   
    The dressup isn't aware of the part shape and is just applied at the current place. To avoid problems like this, you can choose the entry point.
    (0016871)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6037.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4096 [Path] Bug major always 2019-08-23 21:17 2021-02-06 06:33
    Reporter: freman Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Material allowance does not seem to differentiate between air or unused stock and remaining parts of the model.
    Description: Face milling path tool does not clean the face, it leaves residual bits in the corners. Using "material allowance" can extend this but it will eat into other parts of the model if it is not simply the top surface of the workpiece.

    https://forum.freecadweb.org/viewtopic.php?f=15&t=38609

    I see two principal issue here:
    1. Material allowance does not seem to differentiate between air or unused stock and remaining parts of the model, meaning it will happily remove part of the work piece. I would consider that a serious bug.
    2. A facing operation by default does not clear the selected face and thus does not fulfil its primary task in any situation. It requires a specific option parameter to be set by the user to clear the corners even if there is nothing but air/stock outside the boundary. Once the above issue is resolved , this could probably be handled in a more helpful way, overstepping by the tool radius where it does not damage the surrounding part. Material allowance could then be used to set more over step if desired to get a cleaner finish ( no turns on the work ).

    If there is a step in the model, this requires some rather imaginative and ugly workarounds to clear a face, while there are obvious tools paths to achieve the result.
     
    https://forum.freecadweb.org/download/file.php?id=90043

    Tags:
    Steps To Reproduce: Open the linked FreeCAD model and look at the face mill operations. Run the sim. and note that path never goes beyond the boundary of the face. Add a "material allowance" of half tool radius to clean up and note that it takes a chunk out of the central block of the work.

    PS. Ratonlaveur notes that this is not what "material allowance" usually refers in conventional machining language. This should probably be changed so that FreeCAD is not defining a new use of standard terms.

    Additional Information:
    OS: Linux (LXDE/LXDE)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.16988 (Git)
    Build type: Unknown
    Branch: master
    Hash: ff7975291d33a88e6a8282b88a62dbcbcc01ba2b
    Python version: 2.7.15
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedKingdom (en_GB)
    Attached Files:
    Notes
    (0016812)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5978.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4071 [Path] Feature minor N/A 2019-07-26 17:54 2021-02-06 06:33
    Reporter: dhka2 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Job path visualization
    Description: Currently the Job object contains a visualization of the gcode of all child "Operations" objects and all Operations. This visualization is identical to the one shown when all "Operations" objects are visible, and also identical to the visualization that is shown when all operations (ie children of the operations object such as a drill object) are visible.

    I propose that the Job object should not contain a visualization of the child object paths as this is redundant. Additionally making the Job object invisible should make all child objects invisible, without chaingeing their visibility state, so that making the job visible again shows all objects that where visible before the hiding of the Job object and only these objects.

    I also propose that the "Operations" Object behaves in the same manner with regards to the its children (ie the operations as a drill object).
    Tags: Bountysource
    Steps To Reproduce:
    Additional Information: Note: this ticket has a Bounty (link)
    Attached Files:
    Notes
    (0013385)
    dhka2   
    2019-07-26 17:55   
    Forum thread
    (0013386)
    sliptonic   
    2019-07-26 18:54   
    How should toggling visibility of the job affect visibility of non-path child objects (stock, model, tool controllers, etc)?
    (0013387)
    dhka2   
    2019-07-26 19:31   
    (Last edited: 2019-07-26 19:36)
    In exactly the same manner as path objects.

    the general point here is that the user, after generating a path with the path wb, needs only to hide the job object (or objects for a multi-body fcstd file) if he wishes to go back to the part workbench to make further modifications to the model. Then when the modifications are complete the user only needs to unhide the job object to continue work in the path wb.

    (0013388)
    dhka2   
    2019-07-26 19:56   
    (Last edited: 2019-07-26 20:03)
    I have not looked at the code, but as a user it is my opinion, that if technically feasible, this should not be specially implemented in the path wb. As a general rule, for consistency and to avoid code duplication the behaviour should be as follows freecad wide:

    All objects are hidden except objects that have:

    A. Their visibility flag set to true AND
    B. The visibility flags of all parents up to document root (Application) are set to true.

    Also, as a general rule, objects that are expected to have children (ie are containers) should not have any visible elements at all unless there is a good reason to do otherwise, such as in the case of patterns or path dressups

    (0013390)
    sliptonic   
    2019-07-28 15:53   
    https://www.bountysource.com/issues/77869088-job-path-visualization
    (0016804)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5970.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4038 [Path] Bug minor always 2019-06-26 23:27 2021-02-06 06:33
    Reporter: sliptonic Platform:  
    Assigned To: realthunder OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: PathArea offsetting produces incorrect pocket path if shape is small relative to tool
    Description: In the attached areatest.FCStd file, I have a cylinder radius 5mm that represents a tool and another cylinder radius 14mm that represents an area to be cleared. I've created a FeatureArea to clear it.

    If the user is attempt to do 100% stepover, PathArea produces extra wires.
    Under similar conditions but with the shape radius at 28mm, the stepover looks correct.

    This is sort of difficult to describe in text so I'm adding a post to the forum discussion with some images for reference.
    Tags:
    Steps To Reproduce:
    Additional Information: See this forum discussion:
    https://forum.freecadweb.org/viewtopic.php?f=15&t=37310&sid=72e3a120b3c7bc45c08b1667ba09001e

    Attached Files: areatest.FCStd (14,587 bytes) 2019-06-26 23:27
    https://tracker.freecad.org/file_download.php?file_id=2248&type=bug
    Notes
    (0016790)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5956.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3989 [Path] Bug minor always 2019-05-28 06:07 2021-02-06 06:33
    Reporter: Andrea3 Platform:  
    Assigned To: OS: Windows 7  
    Priority: normal OS Version: 0.18.16110 (Git)  
    Status: confirmed Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Wrong simulation after setting a start point
    Description: Simulation shows that the object is cut completely but seems not possible due to the tool was not commanded under a specific Z value.
    Tags:
    Steps To Reproduce: Draw a simple cube
    Try to mill the surface
    Check the simulation --> works as expected

    Change the start point to z = xx in order that xx is above the solid
    Try to simulate --> object will cutted from the start point to the real first point where the mill should start to work.
    Additional Information: Forum link:
    https://forum.freecadweb.org/viewtopic.php?f=3&t=36523

    FreeCAD version:

    OS: Windows 7
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16110 (Git)
    Build type: Release
    Branch: (HEAD detached at upstream/releases/FreeCAD-0-18)
    Hash: f7dccfaa909e5b9da26bf50c4a22ccca9bb10c40
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Attached Files: Mill1.FCStd (692,788 bytes) 2019-05-28 06:07
    https://tracker.freecad.org/file_download.php?file_id=2228&type=bug
    Notes
    (0016769)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5935.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3914 [Path] Bug minor always 2019-03-20 23:42 2021-02-06 06:33
    Reporter: sliptonic Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Path Stock using Existing Solid not maintaining state
    Description: When the user chooses to use an existing solid as the stock object for a Job, the behaviour is inconsistent and confusing.

    1) The user selects 'use existing solid' from the combobox.
    2) The user picks the solid from the list of available choices.
    3) If the user presses 'refresh' at this point, the choice to use existing solid remains but the selected solid switches to the first one in the list.

    4) If the user selects a solid (other than the first) and then closes the Job task panel, everything is fine. But if the Job is re-opened, the selected solid switches back to the first in the list again.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0015136)
    gauna   
    2020-12-13 19:55   
    PR:

    https://github.com/FreeCAD/FreeCAD/pull/4140
    (0015223)
    gauna   
    2021-01-27 17:30   
    Fix committed to master branch.
    (0016739)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5904.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3790 [Path] Bug minor always 2019-01-24 10:35 2021-02-06 06:33
    Reporter: sleeply4cat Platform: Linux  
    Assigned To: shaiseger OS: Ubuntu  
    Priority: normal OS Version: 16.04, 18.04  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Volumetric milling simulation of arcs creating artifacts
    Description: The volumetric simulation of gear-like objects is pretty inaccurate:

    Looks like it caused by a defect of the arc's end cup: its angular size two times smaller than it should be.
    Tags: #post-to-forum, Path
    Steps To Reproduce: 1. create path contains a gear (or any non-smooth path with "left" turn like this), test project is attached
    2. start a simulation
    Additional Information: OS: Ubuntu 18.04.1 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.15694 (Git)
    Build type: Release
    Branch: master
    Hash: 96dee91d5e7d7fd37f43a4dcf406a120ae1f1b8a
    Python version: 2.7.15rc1
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)



    These changes can correct the situation, but I have paws..

    --- a/src/Mod/Path/PathSimulator/App/VolSim.cpp
    +++ b/src/Mod/Path/PathSimulator/App/VolSim.cpp
    @@ -638,7 +638,7 @@ void cStock::ApplyCircularTool(Point3D & p1, Point3D & p2, Point3D & cent, cSimT
         {
             Point3D cupCirc(xynorm.x * r, xynorm.y * r, 0);
             float rotang = (float)SIM_WALK_RES / r;
    -		int ndivs = (int)(3.1415926535 / rotang) + 1;
    +		int ndivs = (int)(2 * 3.1415926535 / rotang) + 1;
             if (!isCCW)
                 rotang = -rotang;
             cupCirc.SetRotationAngleRad(rotang);
    Attached Files: test.FCStd (143,104 bytes) 2019-01-24 10:35
    https://tracker.freecad.org/file_download.php?file_id=2110&type=bug
    Notes
    (0012507)
    Kunda1   
    2019-01-25 17:09   
    deferring to mlampert
    (0012520)
    mlampert   
    2019-01-25 23:25   
    I'm not familiar with the simulation framework in path. I believe shaise would be the best person to look at this.
    (0012521)
    Kunda1   
    2019-01-25 23:26   
    Assigning to @shaiseger
    (0012522)
    Kunda1   
    2019-01-25 23:29   
    (Last edited: 2019-01-25 23:29)
    @sleeply4cat can you do us a favor and please post first to the forum to discuss? The bugtracker doesn't get as much traffic as the forum. This is obvious from the lack of activity on 0003714

    (0014020)
    Kunda1   
    2020-01-08 18:19   
    @shaiseger ping
    (0016704)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5869.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3714 [Path] Bug minor always 2018-12-05 09:35 2021-02-06 06:33
    Reporter: sleeply4cat Platform: Linux  
    Assigned To: shaiseger OS: Ubuntu  
    Priority: normal OS Version: 18.04.1  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Milling simulation continuously stealing window focus and releases it
    Description: When Path simulation is running, FreeCAD continuously takes window focus for a short time and then releases it. It makes the whole system unresponsive.
    Tags: #post-to-forum, Path
    Steps To Reproduce: 1. Open FreeCAD
    2. Create a sample object
    3. Select Path workspace
    4. Create a job with some pathes
    5. Start a simulation
    6. Open another window (Gedit, for example)
    7. type '1234567890', something like '156780' will appear
    Additional Information: Checked on Ubuntu 18 Cinnamon/Ubuntu 18 Gnome.
    xev log:

    FocusOut event, serial 37, synthetic NO, window 0x3e00001,
        mode NotifyGrab, detail NotifyNonlinear
    
    FocusIn event, serial 37, synthetic NO, window 0x3e00001,
        mode NotifyUngrab, detail NotifyNonlinear
    
    KeymapNotify event, serial 37, synthetic NO, window 0x0,
        keys:  2   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
               0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
    
    FocusOut event, serial 37, synthetic NO, window 0x3e00001,
        mode NotifyGrab, detail NotifyNonlinear
    
    FocusIn event, serial 37, synthetic NO, window 0x3e00001,
        mode NotifyUngrab, detail NotifyNonlinear
    
    KeymapNotify event, serial 37, synthetic NO, window 0x0,
        keys:  2   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
               0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
    

    FreeCAD about:
    OS: Ubuntu 18.04.1 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.15302 (Git)
    Build type: Release
    Branch: master
    Hash: 2e03d2f298677b8212c22cbbc3cb20b7c80eabb5
    Python version: 2.7.15rc1
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    Attached Files:
    Notes
    (0012239)
    Kunda1   
    2018-12-05 13:23   
    heads up @sliptonic @mlampert
    (0012497)
    sliptonic   
    2019-01-23 00:38   
    (Last edited: 2019-01-23 00:43)
    @shaiseger Do you have anything to add?

    (0014019)
    Kunda1   
    2020-01-08 18:18   
    @shaiseger ping
    (0016678)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5843.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3676 [Path] Bug major always 2018-11-09 14:32 2021-02-06 06:33
    Reporter: gpothier Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Pocket operations in Spiral pattern sometimes leave island on face
    Description: Under some conditions, pocket operations leave islands in the middle of the face (see attached screenshots). Using the zig-zag pattern instead of spiral works around the problem.
    This has been reported on the forums here: https://forum.freecadweb.org/viewtopic.php?f=15&t=23763
    This is 100% reproducible on a freshly installed and updated Ubuntu 18.04.1 and FreeCad daily from the PPA repository.
    Tags: Path
    Steps To Reproduce: - Open the attached Latch.fcstd file
    - In Fab / UpperBodyJob / Operations001, switch between Spiral and Zig-zag patterns.
    - Observe that with Spiral pattern, there is a rather large island in the middle of the face, while with Zig-zag pattern the face is milled completely.
    Additional Information: OS: Ubuntu 18.04.1 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.15162 (Git)
    Build type: Release
    Branch: master
    Hash: 1d72ee43435fa099ae97a2f6e3d15a225d4f32d3
    Python version: 2.7.15rc1
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)

    Attached Files: Screenshot from 2018-11-06 08-51-02.png (580,894 bytes) 2018-11-09 14:32
    https://tracker.freecad.org/file_download.php?file_id=2043&type=bug
    Screenshot from 2018-11-06 08-50-42.png (638,417 bytes) 2018-11-09 14:32
    https://tracker.freecad.org/file_download.php?file_id=2044&type=bug
    Latch.fcstd (187,100 bytes) 2018-11-09 14:32
    https://tracker.freecad.org/file_download.php?file_id=2045&type=bug
    Notes
    (0012169)
    normandc   
    2018-11-11 05:22   
    Fixed typo in summary
    (0016667)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5832.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3570 [Path] Feature feature have not tried 2018-08-27 19:36 2021-02-06 06:33
    Reporter: dubstar_04 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: acknowledged Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: PATH: Facing Operations with large tools
    Description: It would be awesome if facing operations would allow the use of tools larger than the stock and had the option to make a single pass facing op.

    This would allow the use fly cutter and facemills.
    Tags:
    Steps To Reproduce: none required
    Additional Information:
    Attached Files: Facing-Flycutter.png (267,470 bytes) 2018-08-27 19:36
    https://tracker.freecad.org/file_download.php?file_id=1987&type=bug
    Facing-6mmRougher.png (321,030 bytes) 2018-08-27 19:36
    https://tracker.freecad.org/file_download.php?file_id=1988&type=bug
    Notes
    (0011668)
    Kunda1   
    2018-08-27 22:29   
    @dubstar_04 please include the link to the forum post you mentioned this in before you opened a ticket. Thanks
    (0011669)
    dubstar_04   
    2018-08-28 04:46   
    Forum post: https://forum.freecadweb.org/viewtopic.php?f=15&t=30525
    (0016636)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5801.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3481 [Path] Feature feature N/A 2018-05-16 21:34 2021-02-06 06:33
    Reporter: sliptonic Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Allow use of Draft Picker to set start points in paths.
    Description: It's sometimes desireable to specify exactly where an operation path will begin. Many operations currently allow the user to manually set a start point for the path by entering the coordinates and setting the boolean 'use start point' to True.

    This is cumbersome and error prone. The user should be able to click a button to 'set start point'. The draft-snapper tool should activate to allow picking a point on the canvas and returning the coordinates to the operation.

    Tags:
    Steps To Reproduce:
    Additional Information: Multiple start points should also be allowed. On processing, the nearest start point from the list should be found and passed to PathArea to be used.

    This is necessary for operations like Profile From Faces with the option to process holes set to true. In this case the cutter will pick up and rapid between holes. The start point for each hole should be configurable.
    Attached Files:
    Notes
    (0012840)
    Kunda1   
    2019-03-03 21:12   
    @sliptonic are you planning for this to be fixed pre 0.18 or are you bumping to 0.19 ?
    (0012843)
    sliptonic   
    2019-03-04 00:30   
    It would be a nice UI improvement but not going to happen this cycle. moved to 0.19
    (0016625)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5790.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3099 [Path] Feature feature N/A 2017-06-24 10:28 2021-02-06 06:33
    Reporter: Konstantin Platform:  
    Assigned To: sliptonic OS:  
    Priority: normal OS Version:  
    Status: acknowledged Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Tapping
    Description: I want Tapping tool.
    • I see an ability to add a tap in Tool Table, but there's no Pitch option.
    • There's a few commaands for rigid tapping:
      • Tapping cycle (mostly G84)
      • Counter tapping cycle (on some machines G84 with M4, on my Fanuc G74, maybe others commands used to, not shure)
      • Peck tapping (on some controllers only need to add Q depth to G84, on some used different command)
      • Counter peck tapping (same as previous)
    • On some controllers F is a pitch of a tap, on some it must be set as S*pitch. So, there must be an option for that in Postprocessor.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0009582)
    Kunda1   
    2017-06-28 21:45   
    Changed to 'Feature'
    (0009792)
    Kunda1   
    2017-07-22 09:57   
    Related forum thread: https://forum.freecadweb.org/viewtopic.php?f=15&t=23127&start=10#p183405
    (0010482)
    sliptonic   
    2017-11-28 00:36   
    feature moving to 0.18 version target
    (0012498)
    Kunda1   
    2019-01-23 00:51   
    bumped to 0.19
    (0015255)
    sliptonic   
    2021-02-03 18:47   
    bumped to 0.20.

    This has gotten some discussion on the gitter channel in recent weeks. The operation itself shouldn't be too difficult since much of it can build on the circularhole base classes.

    The more interesting items will be whether it can detect threading information from the geometry and whether it can use toolbit attributes to ensure a proper tool is selected.
    (0016549)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5714.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2660 [Path] Feature feature N/A 2016-08-05 02:37 2021-02-06 06:33
    Reporter: luispa Platform: X86_64  
    Assigned To: OS: Linux  
    Priority: normal OS Version: Ubuntu 16.04  
    Status: acknowledged Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Improving path surfacing object feature
    Description: This feature is partially implemented. There are useful parameters which are still not implemented, i.e. operation limits or material allowance (XY) and path angle among others.
    Due the fact HeeksCNC also uses OpenCamLib it should be easy to use the attached Python script to include these parameters in the Path Surfacing Object feature.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files: Freecad-Path-2.png (54,881 bytes) 2017-05-08 01:51
    https://tracker.freecad.org/file_download.php?file_id=1582&type=bug
    Heekscad-2.png (112,240 bytes) 2017-05-08 01:51
    https://tracker.freecad.org/file_download.php?file_id=1583&type=bug
    HeeksCNC-pocket-2.png (61,961 bytes) 2017-05-08 01:51
    https://tracker.freecad.org/file_download.php?file_id=1584&type=bug
    HeeksCNC-Script-2.txt (59,994 bytes) 2017-05-08 01:51
    https://tracker.freecad.org/file_download.php?file_id=1585&type=bug
    Notes
    (0007239)
    luispa   
    2016-08-05 02:43   
    The toolpaths in the HeeksCNC picture should be possible with FreeCAD if using the same parameters. I attached a picture with the HeeksCNC parameters, this allows to realize how these parameters are traduced to the script.
    (0008904)
    Kunda1   
    2017-05-07 14:57   
    @luispa the bugtracker recently was broken and it seems that last backup didn't transfer your attachments which is a shame. Sorry for the inconvenience biput would you be able to re-upload said attachments?
    (0008909)
    luispa   
    2017-05-08 01:51   
    Hi,
    I've attached the files again. Is there any advance on this feature?
    Thank you very much.
    (0008910)
    Kunda1   
    2017-05-08 04:31   
    Ping @sliptonic
    (0010155)
    Kunda1   
    2017-09-22 19:43   
    @mlampert do you mind weighing in?
    (0010159)
    mlampert   
    2017-09-23 00:00   
    There has been no progress on the 3d surfacing front and I doubt that's gonna change any time soon - not in 0.17.
    (0010497)
    luispa   
    2017-11-28 21:20   
    OK. Is there any chance to use 3D pocket instead?
    (0013275)
    russ4262   
    2019-06-20 05:48   
    Major improvements have been made to 3D Surface lately. Unfortunately, not all the parameters desired or mentioned here are available yet in the current version. The current version does, however, have other features not available in HeeksCNC.

    It is my goal to continue improvement on the 3D Surface op. Goals include limiting scans to selected surfaces, improving the current Waste feature, adding additional cut patterns, and maybe more. Not sure I can "fit the kitchen sink," but I just might 'surface' it. @sliptonic.

    If I think of it, I'll glance at the included script with this bug report and look into the features it contains and how they might be implemented in the FC version of the tool.
    (0016495)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5660.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4383 [FreeCAD] General text N/A 2020-06-25 10:53 2021-02-06 06:32
    Reporter: sangue Platform:  
    Assigned To: OS:  
    Priority: low OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 10
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.4 (GitTag)
    Build type: Release
    Branch: releases/FreeCAD-0-18
    Hash: 980bf9060e28555fecd9e3462f68ca74007b70f8
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: German/Switzerland (de_CH)
    Summary: Documentation: Sweep: Include "attach it to the path" step.
    Description: The documentation of the Sweep command is very misleading and misses essential steps:

    Additional recipe specified by TheMarkster should go (analogously) into the docs:
    "Center the profile to the origin of the sketch, then attach it to the path. (Select profile sketch, in properties select Map Mode property, then click the [...] button to open that attachment editor.) The map path parameter (a value from 0.0 to 1.0) can be used to position the profile along the path once it is attached as a means of testing how the profile will proceed along the path."

    Was asked to put that in the tracker according to this forum thread:
    https://forum.freecadweb.org/viewtopic.php?f=3&t=47760
    Tags: documentation
    Steps To Reproduce: https://forum.freecadweb.org/viewtopic.php?f=3&t=47760
    Additional Information:
    Attached Files:
    Notes
    (0016912)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6079.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3960 [FreeCAD] Bug minor always 2019-05-04 01:52 2021-02-06 06:32
    Reporter: Kruthers Platform:  
    Assigned To: looo OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: freecad help broken in ubuntu appimage
    Description: The help menu item plus all attempts to use the "Whats this" tool fail with the error:

    Unable to launch Qt Assistant (/home/travis/build/FreeCAD/FreeCAD-AppImage/conda/linux_stable/AppDir/usr/bin/assistant)

    X-posted to github: https://github.com/FreeCAD/FreeCAD-AppImage/issues/25
    Tags: appimage, documentation, Qt, upstream
    Steps To Reproduce: Hit "F1"
    Additional Information: appimage file: FreeCAD_0.18-16110-Linux-Conda_Py3Qt5_glibc2.12-x86_64.AppImage

    OS: Ubuntu 18.04.2 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16110 (Git) AppImage
    Build type: Release
    Branch: (HEAD detached at 0.18.1)
    Hash: f7dccfaa909e5b9da26bf50c4a22ccca9bb10c40
    Python version: 3.6.7
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    Attached Files:
    Notes
    (0013243)
    kkremitzki   
    2019-06-17 21:03   
    I'm not maintaining the appimage ATM so this would probably be better assigned to someone else.
    (0013328)
    Kunda1   
    2019-07-03 17:48   
    (Last edited: 2019-07-03 17:54)
    Pressing F1 I see
    FreeCAD help files not found (/tmp/.mount_FreeCAvVNccw/usr/doc/freecad.qhc). You might need to install the FreeCAD documentation package.

    OS: Manjaro Linux (XFCE/xfce)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.17175 (Git) AppImage
    Build type: Release
    Branch: master
    Hash: 507c40669d48ae4732268324cd0140c80cf68222
    Python version: 3.7.3
    Qt version: 5.9.7
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)

    (0013457)
    Kunda1   
    2019-08-23 02:43   
    Follow progress on https://github.com/FreeCAD/FreeCAD-AppImage/issues/25
    @triplus do you mind closing this ticket as well when the above github issue is closed ?
    (0016760)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5926.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3645 [Project Tools & Websites] General major N/A 2018-10-21 13:59 2021-02-06 06:32
    Reporter: Kunda1 Platform:  
    Assigned To: kkremitzki OS:  
    Priority: high OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Mediawiki Extension: Please install MassRegex to make sweeping changes to blocks of wiki pages at once
    Description: Ref: https://forum.freecadweb.org/viewtopic.php?f=21&t=31424
    Tags: documentation, wiki
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016655)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5820.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1756 [FreeCAD] Feature minor always 2014-09-18 20:50 2021-02-06 06:32
    Reporter: r-frank Platform:  
    Assigned To: wmayer OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.14  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Show all currently assigned Keyboard Shortcuts with commands as list
    Description: Having a command (perhaps in the Tools-Section ?) which displays in a two cloumn list command and currently assigned keyboard shortcut. Maybe with possiblity to copy the list to the clipboard for inserting in Calc or Writer and then print it.
    Tags: #lowhangingfruit, documentation, keyboard, shortcuts
    Steps To Reproduce:
    Additional Information: trimble Sketchup for example has a small ruby script that reads out this informations and writes the two column list in a HTML-File. This would be acceptable/conveniant too.

    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=23692
    Attached Files:
    Notes
    (0009869)
    Kunda1   
    2017-08-02 14:21   
    per @triplus in https://forum.freecadweb.org/viewtopic.php?f=8&t=23692&p=184937#p184933


    When the time will allow and after a few other FreeCAD related projects will be finished ShortCuts module for FreeCAD will likely gain such functionality. It's on the todo list.

    P.S. There is already such functionality in ShortCuts module. But it isn't yet extended to take "low-level" FreeCAD shortcuts into account.

    triplus
    (0009870)
    Kunda1   
    2017-08-02 16:04   
    Opened issue at triplus's repo: https://github.com/triplus/ShortCuts/issues/1
    (0011018)
    Kunda1   
    2018-03-07 21:21   
    Some good ideas here:
    Dropdown menu that opens a PDF file: https://youtu.be/PNZJox8pkls?t=5s

    Find action dialog: https://youtu.be/PNZJox8pkls?t=17s

    Keymap Preferences menu: https://youtu.be/PNZJox8pkls?t=45s

    'Key Promoter' Plugin https://youtu.be/PNZJox8pkls?t=1m10s
    (prompts you everytime you use the mouse, what keyboard shortcut you could of used instead)
    (0016431)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5596.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4387 [GCS] Bug minor always 2020-06-28 07:28 2021-02-06 06:31
    Reporter: padawan Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Debian GNU/Linux bullseye/sid
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.4.
    Build type: Release
    Python version: 3.8.3
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: English/United States (en_US)
    Summary: Popularity contest algorithm makes a poor choice for redundant removal.
    Description: Selecting the constraint common to several conflict groups for removal may lead to selecting the wrong partially redundant constraint.
    See thread https://forum.freecadweb.org/viewtopic.php?f=3&t=47861
    Tags:
    Steps To Reproduce: See the thread, and particularly the file attached in post https://forum.freecadweb.org/viewtopic.php?f=3&t=47861#p410248
    Additional Information:
    Attached Files:
    Notes
    (0015211)
    chrisb   
    2021-01-18 21:40   
    (Last edited: 2021-01-18 22:07)
    In this forum post is another one with silently dropped constraints. I link the model for convenience:
    overconstraint_cb.FCStd
    (0016913)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6080.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4066 [GCS] Bug minor always 2019-07-20 01:09 2021-02-06 06:31
    Reporter: bejant Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Sketcher - Simple example where the order of Element creation unexpectedly affects Trim results
    Description: The order in which Sketcher Elements are created can also produce unwanted results with Sketcher > Trim tool. There is a clear example posted in the forum:
    https://forum.freecadweb.org/viewtopic.php?f=3&t=37822&p=322012#p322000
    Tags:
    Steps To Reproduce: See forum example:
    https://forum.freecadweb.org/viewtopic.php?f=3&t=37822&p=322012#p322000
    Additional Information:
    Attached Files:
    Notes
    (0016803)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5969.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4045 [GCS] Bug minor always 2019-06-30 15:50 2021-02-06 06:31
    Reporter: abdullah Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: DogLeg does not consistently converge to a same solution given the same input.
    Description: https://forum.freecadweb.org/viewtopic.php?f=3&t=37369&p=317988#p317988
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016796)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5962.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4044 [GCS] Bug minor always 2019-06-30 12:29 2021-02-06 06:31
    Reporter: chrisb Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Improvement of solver's popularity contest to remove partially redundant constraints.
    Description: See forum discussion
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016795)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5961.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4042 [GCS] Bug minor always 2019-06-28 21:04 2021-02-06 06:31
    Reporter: chrisb Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Solver claims solvable sketch to be unsolved
    Description: See forum discussion
    The sketcher claims some sketches to be unsolvable, although they can be corrected manually to fulfill all constraints.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016794)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5960.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4032 [GCS] Bug minor always 2019-06-20 22:16 2021-02-06 06:31
    Reporter: chrisb Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Solver claims Sketch to be fully constrained which it isn't
    Description: See forum topic. The left vertical line of the sketch can be moved horizontally.

    After removing the lower 0mm distance the solver even claims the sketch to be overconstraint.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0013574)
    bejant   
    2019-09-11 14:40   
    (Last edited: 2019-09-11 22:00)
    Here is another example of the Solver mistakenly arriving at a Fully Constrained solution when in fact 1 DOF remains in that the upper endpoints of the vertical line segments, and the entire horizontal line segment, can be moved vertically. File is attached in the first post of the forum topic.
    https://forum.freecadweb.org/viewtopic.php?f=3&t=39233#p333307

    (0016785)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5951.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3976 [GCS] Bug major always 2019-05-15 20:13 2021-02-06 06:31
    Reporter: openBrain Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Solver falsely detects redundant constraints in specific conditions
    Description: In some specific conditions, solver falsely detects redundant constraints.
    It happens when 2 lines/curves are tangent by design but not by constraint.
    Tags:
    Steps To Reproduce: With minimal attached file :
    • Remove 2.5 mm constraint and try to add a radius constraint to the arc => The solver falsely detects a redundant constraint
    • Reset sketch to initial state, change 4 mm constraint to 3 mm then repeat same as previous step => The solver correctly find a fully constrained sketch
    Additional Information: Forum thread
    ---
    Other example file that produces the same issue by chrisb
    ---
    OS: Ubuntu 18.04.2 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.1.
    Build type: Release
    Python version: 2.7.15rc1
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: French/France (fr_FR)
    Attached Files: solver_redundant_bug.FCStd (3,694 bytes) 2019-05-15 20:13
    https://tracker.freecad.org/file_download.php?file_id=2220&type=bug
    Notes
    (0014313)
    DeepSOIC   
    2020-03-29 20:05   
    This is the same kind of problem as with coincident+tangent combo. You have enforced top line tangent to arc by means of other constraints. The point connecting the circle and the line must be computed by finding an intersection between the two, which is an ill-posed problem for the solver when they are tangent.

    The false detection of redundancy comes from vanishing of jacobi matrix row when the sketch is precisely solved. This is also exactly what a redundancy looks like. If the solution is slightly inaccurate (e.g. if you move the point away a bit before applying radius constraint), there won't be a false redundancy message.

    I'm afraid this is unfixable. Having at least some warning (i.e. a false redundancy warning) may be better than nothing, actually.
    (0014314)
    openBrain   
    2020-03-29 21:53   
    @DeepSOIC : I'm not sure this is exactly same case as coincident+tangent. In the reproducing procedure, a DOF is released by removing the "2.5 mm" length. This is super weird as if you follow the procedure and try to validate an arc radius (any value), it will refuse it with "sketch contains conflicting constraints".
    Just change the 2.5 mm length to any other before removing it, and then any value of arc radius is correctly accepted (leading to fully constrained sketch). Even a 2.5 mm radius is correct.
    (0016765)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5931.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3961 [GCS] Bug minor always 2019-05-06 17:21 2021-02-06 06:31
    Reporter: kisolre Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: DogLeg fail
    Description: Following the request in the Report View here is a situation where DogLeg fails but LevenbergMarquardt succeeds
    Tags:
    Steps To Reproduce: Repeat the steps in the video in the following post with the file m_constrained_2.fsctd from the same post: Post
    1.Open sketch01
    2.Change dimmension 10mm to 24mm
    3.Change dimmension 6mm to 20mm
    4.Exit sketch
    In report view I get:
    EigenSparseQR, Threads: 1, Vectorization: On, Pivot Threshold: 1e-13, Params: 12, Constr: 12, Rank: 12
    Sketcher::setUpSketch()-T:0.081
    DL: tolg: 1e-80, tolx: 1e-80, tolf: 1e-10, convergence: 1e-10, dogLegGaussStep: LeastNormLdlt, xsize: 1, csize: 1, maxIter: 100
    DL: stopcode: 1, Success
    DL: tolg: 1e-80, tolx: 1e-80, tolf: 1e-10, convergence: 1e-10, dogLegGaussStep: LeastNormLdlt, xsize: 1, csize: 1, maxIter: 100
    DL: stopcode: 1, Success
    DL: tolg: 1e-80, tolx: 1e-80, tolf: 1e-10, convergence: 1e-10, dogLegGaussStep: LeastNormLdlt, xsize: 1, csize: 1, maxIter: 100
    DL: stopcode: 1, Success
    DL: tolg: 1e-80, tolx: 1e-80, tolf: 1e-10, convergence: 1e-10, dogLegGaussStep: LeastNormLdlt, xsize: 1, csize: 1, maxIter: 100
    DL: stopcode: 1, Success
    DL: tolg: 1e-80, tolx: 1e-80, tolf: 1e-10, convergence: 1e-10, dogLegGaussStep: LeastNormLdlt, xsize: 1, csize: 1, maxIter: 100
    DL: stopcode: 1, Success
    DL: tolg: 1e-80, tolx: 1e-80, tolf: 1e-10, convergence: 1e-10, dogLegGaussStep: LeastNormLdlt, xsize: 1, csize: 1, maxIter: 100
    DL: stopcode: 1, Success
    DL: tolg: 1e-80, tolx: 1e-80, tolf: 1e-10, convergence: 1e-10, dogLegGaussStep: LeastNormLdlt, xsize: 1, csize: 1, maxIter: 100
    DL: stopcode: 1, Success
    DL: tolg: 1e-80, tolx: 1e-80, tolf: 1e-10, convergence: 1e-10, dogLegGaussStep: LeastNormLdlt, xsize: 1, csize: 1, maxIter: 100
    DL: stopcode: 1, Success
    Sketcher::Solve()-DogLeg-T:0
    EigenSparseQR, Threads: 1, Vectorization: On, Pivot Threshold: 1e-13, Params: 12, Constr: 12, Rank: 12
    Sketcher::setUpSketch()-T:0.019
    DL: tolg: 1e-80, tolx: 1e-80, tolf: 1e-10, convergence: 1e-10, dogLegGaussStep: LeastNormLdlt, xsize: 1, csize: 1, maxIter: 100
    DL: stopcode: 1, Success
    DL: tolg: 1e-80, tolx: 1e-80, tolf: 1e-10, convergence: 1e-10, dogLegGaussStep: LeastNormLdlt, xsize: 1, csize: 1, maxIter: 100
    DL: stopcode: 1, Success
    DL: tolg: 1e-80, tolx: 1e-80, tolf: 1e-10, convergence: 1e-10, dogLegGaussStep: LeastNormLdlt, xsize: 1, csize: 1, maxIter: 100
    DL: stopcode: 1, Success
    DL: tolg: 1e-80, tolx: 1e-80, tolf: 1e-10, convergence: 1e-10, dogLegGaussStep: LeastNormLdlt, xsize: 1, csize: 1, maxIter: 100
    DL, Iteration: 0, fx_inf(tolf): 13.9, g_inf(tolg): 13.9, delta(f(tolx)): 0.3, err(divergingLim): 96.605
    DL, Iteration: 1, fx_inf(tolf): 13.6, g_inf(tolg): 13.6, delta(f(tolx)): 0.9, err(divergingLim): 92.48
    DL, Iteration: 2, fx_inf(tolf): 12.7, g_inf(tolg): 12.7, delta(f(tolx)): 2.7, err(divergingLim): 80.645
    DL, Iteration: 3, fx_inf(tolf): 10, g_inf(tolg): 10, delta(f(tolx)): 8.1, err(divergingLim): 50
    DL, Iteration: 4, fx_inf(tolf): 1.9, g_inf(tolg): 1.9, delta(f(tolx)): 24.3, err(divergingLim): 1.805
    DL, Iteration: 5, fx_inf(tolf): 0, g_inf(tolg): 0, delta(f(tolx)): 24.3, err(divergingLim): 0
    DL: stopcode: 1, Success
    DL: tolg: 1e-80, tolx: 1e-80, tolf: 1e-10, convergence: 1e-10, dogLegGaussStep: LeastNormLdlt, xsize: 1, csize: 1, maxIter: 100
    DL: stopcode: 1, Success
    DL: tolg: 1e-80, tolx: 1e-80, tolf: 1e-10, convergence: 1e-10, dogLegGaussStep: LeastNormLdlt, xsize: 1, csize: 1, maxIter: 100
    DL: stopcode: 1, Success
    DL: tolg: 1e-80, tolx: 1e-80, tolf: 1e-10, convergence: 1e-10, dogLegGaussStep: LeastNormLdlt, xsize: 1, csize: 1, maxIter: 100
    DL: stopcode: 1, Success
    DL: tolg: 1e-80, tolx: 1e-80, tolf: 1e-10, convergence: 1e-10, dogLegGaussStep: LeastNormLdlt, xsize: 1, csize: 1, maxIter: 100
    DL: stopcode: 1, Success
    Sketcher::Solve()-DogLeg-T:0.011
    EigenSparseQR, Threads: 1, Vectorization: On, Pivot Threshold: 1e-13, Params: 12, Constr: 12, Rank: 12
    Sketcher::setUpSketch()-T:0
    DL: tolg: 1e-80, tolx: 1e-80, tolf: 1e-10, convergence: 1e-10, dogLegGaussStep: LeastNormLdlt, xsize: 1, csize: 1, maxIter: 100
    DL, Iteration: 0, fx_inf(tolf): 13.9, g_inf(tolg): 13.9, delta(f(tolx)): 0.3, err(divergingLim): 96.605
    DL, Iteration: 1, fx_inf(tolf): 13.6, g_inf(tolg): 13.6, delta(f(tolx)): 0.9, err(divergingLim): 92.48
    DL, Iteration: 2, fx_inf(tolf): 12.7, g_inf(tolg): 12.7, delta(f(tolx)): 2.7, err(divergingLim): 80.645
    DL, Iteration: 3, fx_inf(tolf): 10, g_inf(tolg): 10, delta(f(tolx)): 8.1, err(divergingLim): 50
    DL, Iteration: 4, fx_inf(tolf): 1.9, g_inf(tolg): 1.9, delta(f(tolx)): 24.3, err(divergingLim): 1.805
    DL, Iteration: 5, fx_inf(tolf): 0, g_inf(tolg): 0, delta(f(tolx)): 24.3, err(divergingLim): 0
    DL: stopcode: 1, Success
    DL: tolg: 1e-80, tolx: 1e-80, tolf: 1e-10, convergence: 1e-10, dogLegGaussStep: LeastNormLdlt, xsize: 1, csize: 1, maxIter: 100
    DL: stopcode: 1, Success
    DL: tolg: 1e-80, tolx: 1e-80, tolf: 1e-10, convergence: 1e-10, dogLegGaussStep: LeastNormLdlt, xsize: 1, csize: 1, maxIter: 100
    DL: stopcode: 1, Success
    DL: tolg: 1e-80, tolx: 1e-80, tolf: 1e-10, convergence: 1e-10, dogLegGaussStep: LeastNormLdlt, xsize: 1, csize: 1, maxIter: 100
    DL: stopcode: 1, Success
    DL: tolg: 1e-80, tolx: 1e-80, tolf: 1e-10, convergence: 1e-10, dogLegGaussStep: LeastNormLdlt, xsize: 1, csize: 1, maxIter: 100
    DL: stopcode: 1, Success
    DL: tolg: 1e-80, tolx: 1e-80, tolf: 1e-10, convergence: 1e-10, dogLegGaussStep: LeastNormLdlt, xsize: 1, csize: 1, maxIter: 100
    DL: stopcode: 1, Success
    DL: tolg: 1e-80, tolx: 1e-80, tolf: 1e-10, convergence: 1e-10, dogLegGaussStep: LeastNormLdlt, xsize: 1, csize: 1, maxIter: 100
    DL: stopcode: 1, Success
    DL: tolg: 1e-80, tolx: 1e-80, tolf: 1e-10, convergence: 1e-10, dogLegGaussStep: LeastNormLdlt, xsize: 1, csize: 1, maxIter: 100
    DL: stopcode: 1, Success
    Sketcher::Solve()-DogLeg-T:0
    EigenSparseQR, Threads: 1, Vectorization: On, Pivot Threshold: 1e-13, Params: 12, Constr: 12, Rank: 12
    Sketcher::setUpSketch()-T:0
    DL: tolg: 1e-80, tolx: 1e-80, tolf: 1e-10, convergence: 1e-10, dogLegGaussStep: LeastNormLdlt, xsize: 1, csize: 1, maxIter: 100
    DL: stopcode: 1, Success
    DL: tolg: 1e-80, tolx: 1e-80, tolf: 1e-10, convergence: 1e-10, dogLegGaussStep: LeastNormLdlt, xsize: 1, csize: 1, maxIter: 100
    DL: stopcode: 1, Success
    DL: tolg: 1e-80, tolx: 1e-80, tolf: 1e-10, convergence: 1e-10, dogLegGaussStep: LeastNormLdlt, xsize: 1, csize: 1, maxIter: 100
    DL: stopcode: 1, Success
    DL: tolg: 1e-80, tolx: 1e-80, tolf: 1e-10, convergence: 1e-10, dogLegGaussStep: LeastNormLdlt, xsize: 1, csize: 1, maxIter: 100
    DL: stopcode: 1, Success
    DL: tolg: 1e-80, tolx: 1e-80, tolf: 1e-10, convergence: 1e-10, dogLegGaussStep: LeastNormLdlt, xsize: 1, csize: 1, maxIter: 100
    DL: stopcode: 1, Success
    DL: tolg: 1e-80, tolx: 1e-80, tolf: 1e-10, convergence: 1e-10, dogLegGaussStep: LeastNormLdlt, xsize: 1, csize: 1, maxIter: 100
    DL: stopcode: 1, Success
    DL: tolg: 1e-80, tolx: 1e-80, tolf: 1e-10, convergence: 1e-10, dogLegGaussStep: LeastNormLdlt, xsize: 1, csize: 1, maxIter: 100
    DL: stopcode: 1, Success
    DL: tolg: 1e-80, tolx: 1e-80, tolf: 1e-10, convergence: 1e-10, dogLegGaussStep: LeastNormLdlt, xsize: 1, csize: 1, maxIter: 100
    DL: stopcode: 1, Success
    Sketcher::Solve()-DogLeg-T:0
    Sketcher::setUpSketch()-T:0.02
    Sketcher::Solve()-DogLeg-T:0.011
    Sketcher::setUpSketch()-T:0.002
    Sketcher::Solve()-DogLeg- Failed!! Falling back...
    Important: the LevenbergMarquardt solver succeeded where the DogLeg solver had failed.
    If you see this message please report a way of reproducing this result at
    http://www.freecadweb.org/tracker/main_page.php
    Sketcher::Solve()-LevenbergMarquardt-T:0.007
    Hide main window
    Show main window
    Hide main window
    Show main window
    
    Additional Information:
    OS: Windows 8.1
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.16624 (Git)
    Build type: Release
    Branch: master
    Hash: 222ae7305fdf1097e4ef3d050f69dff47dbd8786
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: Bulgarian/Bulgaria (bg_BG)
    
    Attached Files: m_constrained_2.FCStd (38,978 bytes) 2019-05-06 17:21
    https://tracker.freecad.org/file_download.php?file_id=2209&type=bug
    Notes
    (0016761)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5927.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3929 [GCS] General minor N/A 2019-04-07 04:11 2021-02-06 06:31
    Reporter: abdullah Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: SQP linear search second order step
    Description:
    PVS discovered that the second order step of the linear search of SQP was apparently initially intended by logari to be executed once, but it is executed in each iteration.

    A solution should be found, but requires building tests to evaluate the performance.
    https://forum.freecadweb.org/viewtopic.php?f=10&t=35469#p299489
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016746)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5912.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3791 [GCS] General minor always 2019-01-24 13:57 2021-02-06 06:31
    Reporter: chrisb Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Solver fails to find redundancy
    Description: Forum discussion.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0013578)
    bejant   
    2019-09-11 15:48   
    (Last edited: 2019-09-11 22:01)
    Here is another example of the Solver (in this example, DogLeg) failing to find redundancy.
    https://forum.freecadweb.org/viewtopic.php?f=3&t=39233#p333307
    File is attached to the first post of the forum topic.
    Steps to reproduce:
    Open Sketch and drag a vertical line segment a bit.
    Apply a Horizontal Distance Constraint of 8 mm to the horizontal line segment.
    Apply Tangency Constraints between the arc and the vertical line segments.
    Delete whichever Vertical Constraint the Solver flags as redundant.
    Result: 1 DOF remains (the horizontal lone segment can be moved vertically) but the Solver fails to detect that the Horizontal Distance Constraint of 8 mm is redundant.

    (0016705)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5870.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3773 [GCS] General minor always 2019-01-15 18:22 2021-02-06 06:31
    Reporter: chrisb Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Levenberg-Marquardt: Solver reports Sketch to be fully constrained which it isn't
    Description: Using arcs and symmetry Levenberg-Marquardt solver claims sketch to be fully constrained, see forum discussion.
    In a similar case a redundancy is not recognized, description in same forum post.

    DogLeg solver is ok.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016696)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5861.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3745 [GCS] General minor always 2018-12-23 18:54 2021-02-06 06:31
    Reporter: chrisb Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Solver failing on certain sketch
    Description: Forum discussion
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016689)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5854.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3735 [GCS] General major always 2018-12-16 10:39 2021-02-06 06:31
    Reporter: abdullah Platform:  
    Assigned To: abdullah OS:  
    Priority: high OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Arc convergence problems
    Description:
    Not sure what is the issue here, but very big arcs have problems in convergence of endpoint tangency.

    https://forum.freecadweb.org/viewtopic.php?f=3&t=32293&p=270215#p270253
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016683)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5848.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3731 [GCS] General minor N/A 2018-12-15 18:38 2021-02-06 06:31
    Reporter: abdullah Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: SQP usage / debug information
    Description:
    SQP appears not to be used for movement. It is unclear why it uses the InitParameters if it is used when there is not InitSolution.

    Debug information wrongly claims that the default algorithm is used when dragging. This can not be true, as dragging is solved with the two subsystem solution, as there are priority constraints with negative tags for programatic moves.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016682)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5847.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3730 [GCS] General feature N/A 2018-12-15 18:32 2021-02-06 06:31
    Reporter: abdullah Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Check effect of squared error in convergence
    Description:
    Study the effect of squaring the error in:

    int System::solve(bool isFine, Algorithm alg, bool isRedundantsolving)

    the error is squared before checking against the convergence parameter. This makes the error appear to be smaller than it actually is. So if the error is 10e-8 mm (distance example), 10e-16 is compared against the convergence. It may lead qualify as Success a situation that may not be successful.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016681)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5846.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3635 [GCS] General tweak always 2018-10-11 15:03 2021-02-06 06:31
    Reporter: chrisb Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Solver does not use point-line-tangency in all possible cases
    Description: Forum discussion
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files: minimal_sketch_freeze.fcstd (4,277 bytes) 2018-10-12 19:18
    https://tracker.freecad.org/file_download.php?file_id=2017&type=bug
    Notes
    (0012014)
    ulrich1a   
    2018-10-12 19:18   
    Here is a minimal example to study the behavior. The sketch has an external geometry to a Part point that lays 0.01 nm away from the Y-axis. An arc that has a coincidence constraint to this point and a tangent constraint to the Y-axis is frozen and can not be moved anymore. Tolerance values in this magnitude may happen for external geometries.
    (0012129)
    chrisb   
    2018-11-02 00:37   
    May be connected with inter line tangency as described in this forum post.
    (0016653)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5818.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3529 [GCS] General minor always 2018-07-06 05:52 2021-02-06 06:31
    Reporter: chrisb Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: feedback Product Version:  
    Product Build: Resolution: reopened  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Solver reports redundant constraints on (blue) measures in reference mode
    Description: When editing poorly constraint sketches from 0.16 version the solver can produce wrong proposals which constraints are creating redundancies.
    See forum discussion.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0011667)
    wmayer   
    2018-08-27 14:27   
    https://github.com/FreeCAD/FreeCAD/commit/96f6c46949b71d12cffb97090ed7821586d49ac6
    (0013031)
    chrisb   
    2019-04-20 10:48   
    In certain cases the solver shows the wrong constraint number in overconstraints, see forum discussion
    (0016631)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5796.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3348 [GCS] General minor always 2018-02-13 13:20 2021-02-06 06:31
    Reporter: Matael Platform:  
    Assigned To: OS:  
    Priority: low OS Version:  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Sketch constraint flips direction
    Description: see:
    https://forum.freecadweb.org/viewtopic.php?p=214793#p214793
    and
    https://forum.freecadweb.org/viewtopic.php?f=22&t=24807&p=194839#p194816

    In a nutshell:
    -To avoid constraints to flip, you have to use Levenberg Marquardt solver
    -Levenberg Marquardt solver don't care about expressions and Dogleg solver is used instead
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0010959)
    Kunda1   
    2018-02-13 16:11   
    Should I move this to GCS category ?
    (0016598)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5763.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3286 [GCS] General minor always 2017-12-18 09:45 2021-02-06 06:31
    Reporter: danidr Platform: All  
    Assigned To: abdullah OS: All  
    Priority: normal OS Version: All  
    Status: assigned Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: DogLeg bug (falling back to LevenbergMarquardt) and feature request
    Description: FreeCAD 0.17 from 12813 Git.

    I am creating a (not-so complex) sketch for an internal project in my company, which also includes expressions linked to a spreadsheet.
    The standard DogLeg solver apparently isn't able to solve the sketch when changing the parametrized dimension on first attempt, but I have to force a second recompute to let it solve correctly.

    I am attaching the drawing to give you an idea.
    Try changing the Variables.Stroke to something like 30mm and you'll notice that the two bodies are not updated correctly on first try. Console reports:
    Sketcher::Solve()-DogLeg- Failed!! Falling back...
    Important: the LevenbergMarquardt solver succeeded where the DogLeg solver had failed.
    If you see this message please report a way of reproducing this result at
    http://www.freecadweb.org/tracker/main_page.php
    Recomputing the document manually with "Mark to recompute" and the Refresh button fixes it, but on a much larger file as the one I'm working on, this requires too much time, and for our use of FreeCAD, speed is critical.

    This brings us to the second point: is it possible to force FreeCAD to use LevenbergMarquardt on recompute instead of just allowing DogLeg, which is currently bugged? I guess this would be easier and quicker to implement than fixing what ever is going wrong in DogLeg.
    Tags: Solver
    Steps To Reproduce:
    • Change Variables.Stroke to any value (e.g. 30mm)
    • Check console and bodies; not updated correctly, DogLeg not able to solve, LevenbergMarquardt can
    • Consequent manual recompute updates the file correctly
    Additional Information:
    Attached Files: DogLegBug.FCStd (65,491 bytes) 2017-12-18 09:45
    https://tracker.freecad.org/file_download.php?file_id=1773&type=bug
    Notes
    (0010616)
    Kunda1   
    2017-12-18 12:17   
    Please open a forum ticket to discuss with community. then bi-directionally link ticket<=>thread
    (0010618)
    Kunda1   
    2017-12-19 03:28   
    please link ticket to forum and vice-a-versa
    (0010619)
    danidr   
    2017-12-19 09:08   
    Link to forum: https://forum.freecadweb.org/viewtopic.php?f=8&t=25946
    (0011441)
    abdullah   
    2018-06-15 16:40   
    Very interesting project, in which it is consistently reproducible the bug "Failed to ... broken face".

    The feature request for general solver selection has also merit.
    (0016587)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5752.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2069 [GCS] General feature N/A 2015-04-25 04:18 2021-02-06 06:31
    Reporter: spike.barnett Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.15  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Display which parts of a sketch are fully constrained.
    Description: Displaying which parts of a sketch are fully constrained would make it much easier to fully constrain complex sketches. This could be done by way of color change of the points and lines which are fully constrained in the same way the sketch itself changes color when it is fully constrained.
    Tags: sketcher, Solver
    Steps To Reproduce: Create a sketch with only a line and fully constrain it, then add a second line. The whole of the sketch will change from green to the standard white lines and red dots.
    Additional Information:
    Attached Files:
    Notes
    (0011443)
    abdullah   
    2018-06-15 16:58   
    There are two things about this request:
    a) the solver is not currently able to show all the parameters that are dependent, but the ones it detects as dependent, so while it can show things that are not constraint, it can not show all the things that are not constraint.
    b) second and more important, the previous detection, that could theoretically be improved, depends on using DenseQR decomposition. I have been unable to implement the algorithm using SparseQR decomposition. DenseQR is way lower performing than SparseQR as the number of elements increases, due to the Sparse nature of the Jacobian matrices of the solver. Currently a) is requested on demand (when clicking the hyperlink in the DoFs). But implementing this feature would mean requesting it constantly. This would make the Sketcher much more slower, which I think it is not acceptable.

    All in all, implementing this feature requires implementing the DoF finder feature for SparseQR. I have failed to do it so far.
    (0016459)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5624.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    754 [GCS] General minor always 2012-06-16 06:38 2021-02-06 06:31
    Reporter: jmaustpc Platform: 32 bit  
    Assigned To: abdullah OS: Kubuntu  
    Priority: normal OS Version: 12.04  
    Status: assigned Product Version:  
    Product Build: Version: 0.13.1157 (Git) Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Sketcher doesn't report that a fully constrained sketch may have multiple (finite) solutions
    Description: This file is two lines on a circle. The way it is constrained, you can drag the "triangle" in circles around the circle, which partly works.

    A vertical or horizontal constraint set on the apex of the triangle will cause it to think it is fully constrained, when it should have two possible locations.

    The "triangle" also can be dragged with the mouse when the apex is not constrained, but after it has gone most of the way around the circle, the triangle suddenly flips to the other side of the circle.


    Tags: #pending, constraints, Solver
    Steps To Reproduce: 1) if you drag the "triangle" around the circle it goes most of the way around and then suddenly flips to the other side.... then if you keep the mouse pointer going around the circle, the triangle suddenly flips back again.
    2) If you select the apex of the "triangle" and then set either one horizontal distance or one vertical distance constraint it says the sketch is fully constrained, which it is not. If you look at the screen shots attached you will see the two valid possible out comes for a vertical distance constraint. The error is the same type of thing if you set horizontal distance constraint
    3) if you set lock constraint on the apex it complains of being over constrained ....which might or might not be the case.
    4) this point happened the first two times I tried to set vertical distance constraint but after closing and reopening the file, I have not yet managed to get it to repeat. I will test further on this point. When the apex was one the right hand position of the two possible outcomes for vertical constraint on the apex, it inserted the correct vertical value but flipped the triangle over to the lower left hand side (the second possible outcome for that vertical constraint value)



    Additional Information: Version: 0.13.1157 (Git)
    Branch: sketcher
    Hash: cad41483eb5bd175f9755eb4e21b04043207e3e3

    I am wondering if this is a problem with how "length along line constraint" works? I might well be talking complete crap, but I was wondering if the horizontal and vertical distant constraint is working of the x and y value of the length along the line constraint rather than truly working on its length. If so that could explain what is going on.
    Attached Files: circle_tangent_sketch_fully_constrained_error.FCStd (8,012 bytes) 2012-06-16 06:38
    https://tracker.freecad.org/file_download.php?file_id=270&type=bug
    circleandtwotangentlines_notreallyfullyconstrained_error_whenverticalconstraintisadded2.jpg (24,331 bytes) 2012-06-16 06:39
    https://tracker.freecad.org/file_download.php?file_id=271&type=bug
    circleandtwotangentlines_notreallyfullyconstrained_error_whenverticalconstraintisadded.jpg (25,883 bytes) 2012-06-16 06:39
    https://tracker.freecad.org/file_download.php?file_id=272&type=bug
    Triangle_around_circle.png (37,561 bytes) 2018-01-27 17:19
    https://tracker.freecad.org/file_download.php?file_id=1826&type=bug
    Notes
    (0002209)
    jmaustpc   
    2012-06-16 06:59   
    I managed to get the error 4), or something similar to be repeatable. I not sure if this is more of a problem with the undo system, hence maybe should be on a different ticket, for now it is just a note on the existing ticket in my last post above.

    1) move the apex of the triangle to point somewhere towards the lower right quadrant
    2)set a vertical distance constraint on the apex
    3) click "undo" on the tool bar to remove the last added vertical distance constraint
    4) move the apex of the triangle to point somewhere towards the lower left quadrant
    5) set a vertical distance constraint on the apex


    rather than setting the then current correct default value for vertical distance constraint, ....FreeCAD will push the apex back to the position it had been in prior to the "undo", and set the what should have been a new value default vertical constraint value back to what it had previously been prior to the undo.
    (0002210)
    jmaustpc   
    2012-06-16 07:00   
    This is a link to the topic on the forum

    http://forum.freecadweb.org/viewtopic.php?f=10&t=2706&p=20622#p20622
    (0002213)
    logari81   
    2012-06-17 09:42   
    this is a difficult one. Currently there is no mechanism in the solver for handling multiple solutions and I don't believe that we will have such a possibility soon. However, it is nice to have this test case as a reference when we decide to implement the handling of multiple solutions. Until then, users have to be a bit more clever in order to avoid ambiguous dimensioning.
    (0002215)
    jmaustpc   
    2012-06-18 00:26   
    I have added another example to the same topic in forum

    http://forum.freecadweb.org/viewtopic.php?f=10&t=2706&p=20641#p20641

    In this example I don't think its the same, I mean its not an multiple solution, I don't think.

    It is an example where an extra superfluous "=" constraint can be added without causing an over constrained error.
    (0002216)
    jmaustpc   
    2012-06-18 00:34   
    To be clear, in case it is important, the three files posted to the forum, the first I noticed the superfluous "=" constraint and thought "that's not right", used "save as" to get the second file then deleted the "=" and noticed that it was still fully constrained and I got no error messages. So I "saved as" again to get the third file and then noticed that I could put the "=" back in there even though the file had been in a fully constrained state before I clicked on "=" and it still didn't give me an error message.
    (0002217)
    jmaustpc   
    2012-06-18 00:44   
    Here is another example of where there is a multiple solution with the tangent constraint in these two examples. The tangent can be in either direction, I have included some screen shots two illustrate this particular example. Of course in this file there are more possibilities when one considers the other tangent.

    I've posted the files to the forum topic, at the above url.
    (0002218)
    jmaustpc   
    2012-06-18 01:02   
    This is the version data for the last three posts today.

    version data
    Kubuntu 12.04 32bit
    Platform: Ubuntu 12.04 LTS (32-bit)
    Version: 0.13.1162 (Git)
    Branch: master
    Hash: e05fcc7daf7d806c9766cfe75ca2b4880c3dccf0
    Python version: 2.7.3
    Qt version: 4.8.1
    Coin version: 3.1.3
    SoQt version: 1.5.0
    OCC version: 6.5.1
    (0010545)
    abdullah   
    2017-12-08 15:52   
    @kunda1
    @jmaustpc

    I am not able to reproduce this with the current master. I am not sure if I am missing something.

    May some power user check it up with a current version?
    (0010547)
    Kunda1   
    2017-12-09 01:36   
    @chrisb do you mind checking ?
    (0010564)
    Kunda1   
    2017-12-11 06:26   
    @jmaustpc please re-check ticket when you get a moment, thanks!
    (0010623)
    chrisb   
    2017-12-21 10:29   
    I can reproduce it - of course - because it's the well known behaviour. The current definition of solved is: There is no smooth transition to another solution.
    So it works as designed and is definitely not a bug. @abdullah may comment if there is a chance to get a solver where solved means: this is the one and only solution. If so this can be a feature request, if not it can be closed.
    (0010851)
    Kunda1   
    2018-01-25 16:58   
    @abdullah please take a look at chrisb's response in 0000754:0010623
    (0010880)
    abdullah   
    2018-01-27 17:19   
    @chrisb

    Man! I cannot move that triangle. I have tried dragging all the three points and the two edges, in I would say any direction.

    When you can reproduce it, what are you dragging?
    (0011442)
    abdullah   
    2018-06-15 16:49   
    Sorry, I mixed two different aspects of the bug. Yes, I can reproduce.

    To me from this example what is pending is the "flipping", which still happens even with the improved dragging implemented at the end of last year.

    Regarding the multiple solution, I do not forsee any change in behaviour. The solution is valid. It is somehow similar to x^2=4, x=2, x=-2, both solutions are valid.
    (0016390)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5555.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    704 [GCS] General feature N/A 2012-05-15 18:30 2021-02-06 06:31
    Reporter: pperisin Platform: 32 bit  
    Assigned To: abdullah OS: Win7  
    Priority: normal OS Version: latest unstable  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Sketcher Fully constrained report based on primitives (Lines, arcs)
    Description: HI,

    I do not know if this makes sense, but I know it was mentioned before somewhere.

    It would be nice that "fully constrained" report is based on single lines/arcs, and not on entire sketch. This way it would be easier to identify which parts of a sketch are not fully constrained.

    Regards
    Petar
    Tags: constraints, Solver
    Steps To Reproduce:
    Additional Information:
    System Description
    Attached Files:
    Notes
    (0002055)
    djreichel   
    2012-05-16 22:45   
    Maybe it would be useful to make lines display in a constrained color and an unconstrained color individually, rsther than making the entire sketch change to the constrained color when all degrees of freedom are removed.

    It can be difficult to find the last unconstrained elements of a complex sketch.
    (0002056)
    pperisin   
    2012-05-17 06:18   
    That is exactly what I ment. Would be very nice.
    (0002131)
    pperisin   
    2012-06-05 12:23   
    (Last edited: 2012-06-05 12:34)
    Also, it would be nice if overconstrained primitives would be drawn in red (or some other color that is not used and that will mark over-constrained primitive)

    EDIT: OR, even better, change color of conflicting constraints, so that user sees them on screen, selects one he does not need, delete it and be done with it.

    maybe pink/purple color for conflicting constraints can be good. I'm bad with colors chosing. Really bad.

    (0007867)
    Kunda1   
    2017-01-18 22:10   
    Reminder sent to: logari81
    @logari81 should this be tagged 'Solver'
    (0009406)
    Kunda1   
    2017-06-16 11:51   
    @trampas writes in 0002653

    What would be nice is to have lines change colors if they are fully constrained, or maybe have points change colors if they are matched.

    trampas
    (0009565)
    Hannu   
    2017-06-27 15:40   
    This seems as a simple solution to a problem that is easy to run into in FreeCAD - I have used FreeCAD intensely in periods (creating objects to 3D-print) and still "hit" this, and I get as baffled every time.
    (0011444)
    abdullah   
    2018-06-15 17:02   
    As for showing fully constrained elements, the problem is as in here:
    https://freecadweb.org/tracker/view.php?id=2069#c11443

    As for getting functionality to identify where the dossier is not yet constraint, the recently merged DoF Finder should help, just click on the hyperlink of the DoFs.
    (0011956)
    abdullah   
    2018-10-07 11:05   
    As with 0002069, what is not implemented is constantly adapting the colors. This is not happening in v0.18, as complex sketches would have a significant drop in performance due to constraintly solving using the DenseQR algorithm.
    (0016389)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5554.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4201 [File formats] Feature minor have not tried 2019-11-23 14:07 2021-02-06 06:31
    Reporter: wandererfan Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Linux Mint 19 (X-Cinnamon/cinnamon)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.18760 +7 (Git)
    Build type: debug
    Branch: SectionAngles5
    Hash: f18885c66cddfb97e5686a7e3384311c48a9cd38
    Python version: 3.6.8
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/Canada (en_CA)
    Summary: Add Support for Bezier Curves in Import Module Dxf Exporter
    Description: Forum discussion

    Bezier curves are used in the definitions of .ttf fonts. Without support for Bezier curves the exporter is not able to export ShapeStrings.
    Tags: bezier curve
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016842)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6008.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4099 [File formats] Bug crash always 2019-08-27 07:20 2021-02-06 06:31
    Reporter: ph.andronov Platform: Linux  
    Assigned To: abdullah OS: arch linux  
    Priority: normal OS Version:  
    Status: feedback Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FC crashes when try to make wall from segment (reason: faulty DXF file)
    Description: Crash during wall creation:
    
    FreeCAD 0.18, Libs: 0.18R16131 (Git)
    © Juergen Riegel, Werner Mayer, Yorik van Havre 2001-2019
      #####                 ####  ###   ####  
      #                    #      # #   #   # 
      #     ##  #### ####  #     #   #  #   # 
      ####  # # #  # #  #  #     #####  #   # 
      #     #   #### ####  #    #     # #   # 
      #     #   #    #     #    #     # #   #  ##  ##  ##
      #     #   #### ####   ### #     # ####   ##  ##  ##
    
    
    (freecad:24592): Gtk-WARNING **: 10:07:25.573: Theme parsing error: gtk.css:2:116: Failed to import: Error opening file /home/andrphi/.local/share/gnome-shell/extensions/no-title-bar@franglais125.gmail.com/stylesheet.css: No such file or directory
    
    (freecad:24592): Gtk-WARNING **: 10:07:25.573: Theme parsing error: gtk.css:3:122: Failed to import: Error opening file /home/andrphi/.local/share/gnome-shell/extensions/no-title-bar@franglais125.gmail.com/stylesheet-tiled.css: No such file or directory
    DraftGeomUtils.connect: unable to connect edges
    <Line object>   Vector (4960909.62788767, 1000671.647867698, 0.0)   Vector (4960909.62788767, 1000681.647867698, 0.0)
    <Line object>   Vector (4960709.62788767, 1000681.647867698, 0.0)   Vector (4960709.62788767, 1000441.647867698, 0.0)
    <Line object>   Vector (4960709.62788767, 1000441.647867698, 0.0)   Vector (4961049.62788767, 1000441.647867698, 0.0)
    DraftGeomUtils.connect: unable to connect edges
    <Line object>   Vector (4960709.62788767, 1000671.647867698, 0.0)   Vector (4960709.62788767, 1000681.647867698, 0.0)
    <Line object>   Vector (4960909.62788767, 1000681.647867698, 0.0)   Vector (4960909.62788767, 1000641.647867698, 0.0)
    <Line object>   Vector (4960909.62788767, 1000641.647867698, 0.0)   Vector (4961049.62788767, 1000641.647867698, 0.0)
    DraftGeomUtils: unable to bind wires
    DraftGeomUtils.connect: unable to connect edges
    <Line object>   Vector (4961029.627887671, 1000671.647867698, 0.0)   Vector (4961029.627887671, 1000681.647867698, 0.0)
    <Line object>   Vector (4960829.627887671, 1000681.647867698, 0.0)   Vector (4960829.627887671, 1000541.647867698, 0.0)
    DraftGeomUtils.connect: unable to connect edges
    <Line object>   Vector (4960829.627887671, 1000671.647867698, 0.0)   Vector (4960829.627887671, 1000681.647867698, 0.0)
    <Line object>   Vector (4961029.627887671, 1000681.647867698, 0.0)   Vector (4961029.627887671, 1000541.647867698, 0.0)
    DraftGeomUtils: unable to bind wires
    DraftGeomUtils.connect: unable to connect edges
    <Line object>   Vector (4960829.627887671, 1000801.647867698, 0.0)   Vector (4960829.627887671, 1000791.647867698, 0.0)
    <Line object>   Vector (4961029.627887671, 1000791.647867698, 0.0)   Vector (4961029.627887671, 1000931.647867698, 0.0)
    DraftGeomUtils.connect: unable to connect edges
    <Line object>   Vector (4961029.627887671, 1000801.647867698, 0.0)   Vector (4961029.627887671, 1000791.647867698, 0.0)
    <Line object>   Vector (4960829.627887671, 1000791.647867698, 0.0)   Vector (4960829.627887671, 1000931.647867698, 0.0)
    DraftGeomUtils: unable to bind wires
    DraftGeomUtils.connect: unable to connect edges
    <Line object>   Vector (4968449.627887669, 1002001.647867698, 0.0)   Vector (4968449.627887669, 1001991.647867698, 0.0)
    <Line object>   Vector (4968649.627887669, 1001991.647867698, 0.0)   Vector (4968649.627887669, 1002131.647867698, 0.0)
    DraftGeomUtils.connect: unable to connect edges
    <Line object>   Vector (4968649.627887669, 1002001.647867698, 0.0)   Vector (4968649.627887669, 1001991.647867698, 0.0)
    <Line object>   Vector (4968449.627887669, 1001991.647867698, 0.0)   Vector (4968449.627887669, 1002131.647867698, 0.0)
    DraftGeomUtils: unable to bind wires
    DraftGeomUtils.connect: unable to connect edges
    <Line object>   Vector (4969359.62788767, 1006881.647867699, 0.0)   Vector (4969214.342010461, 1006881.647867699, 0.0)
    <Line object>   Vector (4969214.342010461, 1006881.647867699, 0.0)   Vector (4968097.047477968, 1005548.0008129562, 0.0)
    <Line object>   Vector (4968097.047477968, 1005548.0008129562, 0.0)   Vector (4968097.047477968, 1005411.647867698, 0.0)
    <Line object>   Vector (4968097.047477968, 1005411.647867698, 0.0)   Vector (4967539.627887675, 1005411.647867698, 0.0)
    <Line object>   Vector (4967539.627887675, 1005411.647867698, 0.0)   Vector (4967539.627887669, 1004661.647867698, 0.0)
    <Line object>   Vector (4967539.627887669, 1004661.647867698, 0.0)   Vector (4968329.62788767, 1004661.647867698, 0.0)
    <Line object>   Vector (4968329.62788767, 1004661.647867698, 0.0)   Vector (4968329.62788767, 994461.6478676982, 0.0)
    <Line object>   Vector (4968329.62788767, 994461.6478676982, 0.0)   Vector (4967719.62788767, 994461.6478676982, 0.0)
    <Line object>   Vector (4967719.62788767, 994461.6478676982, 0.0)   Vector (4967719.62788767, 993711.6478676982, 0.0)
    <Line object>   Vector (4967719.62788767, 993711.6478676982, 0.0)   Vector (4968069.62788767, 993711.6478676982, 0.0)
    <Line object>   Vector (4968069.62788767, 993711.6478676982, 0.0)   Vector (4968069.627887673, 992261.6478676983, 0.0)
    <Line object>   Vector (4968069.627887673, 992261.6478676983, 0.0)   Vector (4969359.62788767, 992261.6478676982, 0.0)
    <Line object>   Vector (4969359.62788767, 992461.6478676982, 0.0)   Vector (4968719.62788767, 992461.6478676982, 0.0)
    DraftGeomUtils.connect: unable to connect edges
    <Line object>   Vector (4969359.62788767, 1006681.647867699, 0.0)   Vector (4969307.698343353, 1006681.647867699, 0.0)
    <Line object>   Vector (4969307.698343353, 1006681.647867699, 0.0)   Vector (4968297.047477968, 1005475.2949224397, 0.0)
    <Line object>   Vector (4968297.047477968, 1005475.2949224397, 0.0)   Vector (4968297.047477968, 1005211.647867698, 0.0)
    <Line object>   Vector (4968297.047477968, 1005211.647867698, 0.0)   Vector (4967739.627887673, 1005211.647867698, 0.0)
    <Line object>   Vector (4967739.627887673, 1005211.647867698, 0.0)   Vector (4967739.627887671, 1004861.647867698, 0.0)
    <Line object>   Vector (4967739.627887671, 1004861.647867698, 0.0)   Vector (4968529.62788767, 1004861.647867698, 0.0)
    <Line object>   Vector (4968529.62788767, 1004861.647867698, 0.0)   Vector (4968529.62788767, 994261.6478676982, 0.0)
    <Line object>   Vector (4968529.62788767, 994261.6478676982, 0.0)   Vector (4967919.62788767, 994261.6478676982, 0.0)
    <Line object>   Vector (4967919.62788767, 994261.6478676982, 0.0)   Vector (4967919.62788767, 993911.6478676982, 0.0)
    <Line object>   Vector (4967919.62788767, 993911.6478676982, 0.0)   Vector (4968269.62788767, 993911.6478676982, 0.0)
    <Line object>   Vector (4968269.62788767, 993911.6478676982, 0.0)   Vector (4968269.627887673, 992461.6478676983, 0.0)
    <Line object>   Vector (4968269.627887673, 992461.6478676983, 0.0)   Vector (4969359.62788767, 992461.6478676982, 0.0)
    <Line object>   Vector (4969359.62788767, 992261.6478676982, 0.0)   Vector (4968719.62788767, 992261.6478676982, 0.0)
    DraftGeomUtils: unable to bind wires
    Program received signal SIGSEGV, Segmentation fault.
    #0  /usr/lib/libc.so.6(+0x3a7e0) [0x7f0a75e8e7e0]
    #1  0x7f0a04b7f798 in Geom_TrimmedCurve::Geom_TrimmedCurve(opencascade::handle<Geom_Curve> const&, double, double, bool, bool) from /usr/lib/libTKG3d.so.7+0x1b8
    0000002  0x7f09fb92c7db in GC_MakeSegment::GC_MakeSegment(gp_Pnt const&, gp_Pnt const&) from /usr/lib/libTKGeomBase.so.7+0xeb
    0000003  0x7f0a01d8fcc4 in Part::LineSegmentPy::PyInit(_object*, _object*) from /usr/lib/freecad/lib/Part.so+0x984
    0000004  /usr/lib/libpython3.7m.so.1.0(_PyObject_FastCallKeywords+0x11a) [0x7f0a76ef2f5a]
    0000005  /usr/lib/libpython3.7m.so.1.0(+0x138362) [0x7f0a76ef4362]
    0000006  /usr/lib/libpython3.7m.so.1.0(_PyEval_EvalFrameDefault+0x4fda) [0x7f0a76f2e40a]
    0000007  /usr/lib/libpython3.7m.so.1.0(_PyEval_EvalCodeWithName+0x2f8) [0x7f0a76ee2768]
    0000008  /usr/lib/libpython3.7m.so.1.0(_PyFunction_FastCallKeywords+0x2a3) [0x7f0a76ee37d3]
    0000009  /usr/lib/libpython3.7m.so.1.0(+0x1381d0) [0x7f0a76ef41d0]
    0000010  /usr/lib/libpython3.7m.so.1.0(_PyEval_EvalFrameDefault+0x1748) [0x7f0a76f2ab78]
    0000011  /usr/lib/libpython3.7m.so.1.0(_PyEval_EvalCodeWithName+0x2f8) [0x7f0a76ee2768]
    0000012  /usr/lib/libpython3.7m.so.1.0(_PyFunction_FastCallKeywords+0x2a3) [0x7f0a76ee37d3]
    0000013  /usr/lib/libpython3.7m.so.1.0(+0x1381d0) [0x7f0a76ef41d0]
    0000014  /usr/lib/libpython3.7m.so.1.0(_PyEval_EvalFrameDefault+0x4fda) [0x7f0a76f2e40a]
    0000015  /usr/lib/libpython3.7m.so.1.0(_PyEval_EvalCodeWithName+0x2f8) [0x7f0a76ee2768]
    0000016  /usr/lib/libpython3.7m.so.1.0(_PyFunction_FastCallKeywords+0x2a3) [0x7f0a76ee37d3]
    0000017  /usr/lib/libpython3.7m.so.1.0(+0x1381d0) [0x7f0a76ef41d0]
    0000018  /usr/lib/libpython3.7m.so.1.0(_PyEval_EvalFrameDefault+0xb40) [0x7f0a76f29f70]
    0000019  /usr/lib/libpython3.7m.so.1.0(_PyEval_EvalCodeWithName+0x2f8) [0x7f0a76ee2768]
    0000020  /usr/lib/libpython3.7m.so.1.0(_PyFunction_FastCallDict+0x2ef) [0x7f0a76ee3e7f]
    0000021  /usr/lib/libpython3.7m.so.1.0(_PyObject_Call_Prepend+0x68) [0x7f0a76eb7ce8]
    0000022  /usr/lib/libpython3.7m.so.1.0(PyObject_Call+0x7e) [0x7f0a76ee43be]
    0000023  0x7f0a77548f80 in App::FeaturePythonImp::execute() from /usr/lib/freecad/lib/libFreeCADApp.so+0x5d0
    0000024  0x7f0a01d49fa7 in App::FeaturePythonT<Part::Feature>::execute() from /usr/lib/freecad/lib/Part.so+0x17
    0000025  0x7f0a774f9589 in App::DocumentObject::recompute() from /usr/lib/freecad/lib/libFreeCADApp.so+0xb9
    0000026  0x7f0a01d481ba in Part::Feature::recompute() from /usr/lib/freecad/lib/Part.so+0xa
    0000027  0x7f0a774ac2b5 in App::Document::_recomputeFeature(App::DocumentObject*) from /usr/lib/freecad/lib/libFreeCADApp.so+0x55
    0000028  0x7f0a774b589b in App::Document::recompute() from /usr/lib/freecad/lib/libFreeCADApp.so+0x19b
    0000029  0x7f0a77528ef5 in App::DocumentPy::recompute(_object*) from /usr/lib/freecad/lib/libFreeCADApp.so+0x45
    0000030  0x7f0a77528feb in App::DocumentPy::staticCallback_recompute(_object*, _object*) from /usr/lib/freecad/lib/libFreeCADApp.so+0x3b
    0000031  /usr/lib/libpython3.7m.so.1.0(_PyMethodDef_RawFastCallKeywords+0x25f) [0x7f0a76ec25df]
    0000032  /usr/lib/libpython3.7m.so.1.0(_PyCFunction_FastCallKeywords+0x24) [0x7f0a76ec2714]
    0000033  /usr/lib/libpython3.7m.so.1.0(+0x1382ec) [0x7f0a76ef42ec]
    0000034  /usr/lib/libpython3.7m.so.1.0(_PyEval_EvalFrameDefault+0x4fda) [0x7f0a76f2e40a]
    0000035  /usr/lib/libpython3.7m.so.1.0(_PyFunction_FastCallDict+0x11b) [0x7f0a76ee3cab]
    0000036  /usr/lib/libpython3.7m.so.1.0(_PyObject_Call_Prepend+0x68) [0x7f0a76eb7ce8]
    0000037  /usr/lib/libpython3.7m.so.1.0(PyObject_Call+0x7e) [0x7f0a76ee43be]
    0000038  /usr/lib/freecad/lib/libFreeCADBase.so(PP_Run_Method+0xec) [0x7f0a772c0e0c]
    #39  0x7f0a77252bfc in Base::InterpreterSingleton::runMethodVoid(_object*, char const*) from /usr/lib/freecad/lib/libFreeCADBase.so+0x2c
    #40  0x7f0a77b0925a in Gui::PythonCommand::activated(int) from /usr/lib/freecad/lib/libFreeCADGui.so+0xaa
    0000041  0x7f0a77b0cb2c in Gui::Command::invoke(int) from /usr/lib/freecad/lib/libFreeCADGui.so+0x5c
    0000042  0x7f0a764d6a11 in QMetaObject::activate(QObject*, int, int, void**) from /usr/lib/libQt5Core.so.5+0x7c1
    0000043  0x7f0a76877e93 in QAction::triggered(bool) from /usr/lib/libQt5Widgets.so.5+0x43
    0000044  0x7f0a7687a624 in QAction::activate(QAction::ActionEvent) from /usr/lib/libQt5Widgets.so.5+0x104
    0000045  /usr/lib/libQt5Widgets.so.5(+0x253c2d) [0x7f0a76978c2d]
    0000046  0x7f0a76978e56 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) from /usr/lib/libQt5Widgets.so.5+0xe6
    0000047  0x7f0a76a6dceb in QToolButton::mouseReleaseEvent(QMouseEvent*) from /usr/lib/libQt5Widgets.so.5+0xb
    0000048  0x7f0a768c1cb6 in QWidget::event(QEvent*) from /usr/lib/libQt5Widgets.so.5+0x256
    0000049  0x7f0a76a6dd95 in QToolButton::event(QEvent*) from /usr/lib/libQt5Widgets.so.5+0x35
    0000050  0x7f0a7687e4d5 in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /usr/lib/libQt5Widgets.so.5+0x85
    0000051  0x7f0a76887c6c in QApplication::notify(QObject*, QEvent*) from /usr/lib/libQt5Widgets.so.5+0x57c
    0000052  0x7f0a77adac39 in Gui::GUIApplication::notify(QObject*, QEvent*) from /usr/lib/freecad/lib/libFreeCADGui.so+0x89
    0000053  0x7f0a764aa9c2 in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /usr/lib/libQt5Core.so.5+0x182
    0000054  0x7f0a76886d4b in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool, bool) from /usr/lib/libQt5Widgets.so.5+0x1bb
    0000055  /usr/lib/libQt5Widgets.so.5(+0x1b9211) [0x7f0a768de211]
    0000056  /usr/lib/libQt5Widgets.so.5(+0x1bc154) [0x7f0a768e1154]
    0000057  0x7f0a7687e4d5 in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /usr/lib/libQt5Widgets.so.5+0x85
    0000058  0x7f0a76887a21 in QApplication::notify(QObject*, QEvent*) from /usr/lib/libQt5Widgets.so.5+0x331
    0000059  0x7f0a77adac39 in Gui::GUIApplication::notify(QObject*, QEvent*) from /usr/lib/freecad/lib/libFreeCADGui.so+0x89
    0000060  0x7f0a764aa9c2 in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /usr/lib/libQt5Core.so.5+0x182
    0000061  0x7f0a74693789 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) from /usr/lib/libQt5Gui.so.5+0x709
    0000062  0x7f0a7469505b in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) from /usr/lib/libQt5Gui.so.5+0x27b
    0000063  0x7f0a7466d37c in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /usr/lib/libQt5Gui.so.5+0xbc
    0000064  /usr/lib/libQt5XcbQpa.so.5(+0x6bfec) [0x7f0a70198fec]
    0000065  /usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x294) [0x7f0a73a11cf4]
    0000066  /usr/lib/libglib-2.0.so.0(+0x6ab11) [0x7f0a73a13b11]
    0000067  /usr/lib/libglib-2.0.so.0(g_main_context_iteration+0x31) [0x7f0a73a13b51]
    0000068  0x7f0a765029a3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /usr/lib/libQt5Core.so.5+0x63
    0000069  0x7f0a764a95ec in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) from /usr/lib/libQt5Core.so.5+0x12c
    0000070  0x7f0a764b1326 in QCoreApplication::exec() from /usr/lib/libQt5Core.so.5+0x96
    0000071  0x7f0a77a674c3 in Gui::Application::runApplication() from /usr/lib/freecad/lib/libFreeCADGui.so+0x1753
    0000072  freecad(main+0x6e7) [0x562892a60407]
    0000073  /usr/lib/libc.so.6(__libc_start_main+0xf3) [0x7f0a75e7aee3]
    0000074  freecad(_start+0x2e) [0x562892a6071e]
    
    Tags: #pending-forum
    Steps To Reproduce: - Open attached file
    - Try to make a wall from any segment on the basement floor plan

    Note: It is still possible to create wall from SOME segments, but I've failed to figure out any pattern
    Additional Information: OS: Arch Linux
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16131 (Git)
    Build type: Release
    Branch: makepkg
    Hash: 3129ae4296e40ed20e7b3d460b86e6969acbe1c3
    Python version: 3.7.4
    Qt version: 5.13.0
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/United States (en_US)
    Attached Files: дом5кв2.FCStd (375,328 bytes) 2019-08-27 07:20
    https://tracker.freecad.org/file_download.php?file_id=2286&type=bug
    plans.dxf (1,241,647 bytes) 2019-09-02 10:50
    https://tracker.freecad.org/file_download.php?file_id=2293&type=bug
    Notes
    (0013472)
    openBrain   
    2019-08-27 18:47   
    @ph.andronov : thanks for reporting. However, according guidelines (big yellow banner), could you please first open a forum topic so the community can help validate and identify ? Thanks
    (0013516)
    ph.andronov   
    2019-09-02 10:50   
    After community review it seems that crash caused by bad DXF (added to attach)

    However I guess issue still valid as no matter how bad result DXF import produced, FC shouldn't be crashed during operations with a model
    (0013923)
    Kunda1   
    2019-12-17 04:09   
    (Last edited: 2019-12-17 04:12)
    @ph.andronov please link to the forum thread
    https://forum.freecadweb.org/viewtopic.php?f=3&t=38897

    (0013924)
    Kunda1   
    2019-12-17 04:15   
    Moved to 'File Formats' category.
    Workaround in the meantime: https://forum.freecadweb.org/viewtopic.php?f=3&t=38897&p=329930#p330256
    (0014529)
    abdullah   
    2020-06-13 15:09   
    I cannot reproduce the crash anymore with:
    OS: Ubuntu 18.04.4 LTS (MATE/mate)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.
    Build type: Release
    Branch: unknown
    Hash: 8ed90c858645e7562d9534265b6025d39ab4ffd6
    Python version: 3.6.9
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0

    I have posted to the forum.
    (0014530)
    abdullah   
    2020-06-13 15:30   
    Could you please check if this is reproducible (the crash), with a current version of FC?
    (0015040)
    Kunda1   
    2020-12-01 11:37   
    @ph.andronov please try to reproduce on latest v0.19 and report back
    (0016813)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5979.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3834 [File formats] Feature feature have not tried 2019-02-13 18:01 2021-02-06 06:31
    Reporter: wmayer Platform:  
    Assigned To: realthunder OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Support of AXIS2_PLACEMENT_3D entities in STEP files
    Description: A STEP file can contain AXIS1_PLACEMENT_3D or AXIS2_PLACEMENT_3D entities that should be read-in when loading such a file.
    Tags: STEP
    Steps To Reproduce:
    Additional Information: https://forum.freecadweb.org/viewtopic.php?f=3&t=34162
    Attached Files:
    Notes
    (0012759)
    wmayer   
    2019-02-24 21:04   
    See also: http://opencascade.wikidot.com/entitynames
    (0012760)
    wmayer   
    2019-02-24 21:53   
    The named AXIS2_PLACEMENT_3D are part of a PRESENTATION_LAYER_ASSIGNMENT entity.
    (0013708)
    Kunda1   
    2019-10-04 00:52   
    I've assigned this ticket to @realthunder per https://forum.freecadweb.org/viewtopic.php?f=3&t=34162&p=338358#p338358
    (0016717)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5882.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3606 [File formats] Feature feature always 2018-09-21 08:09 2021-02-06 06:31
    Reporter: berndhahnebach Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Point Cloud files *.asc with huge coordinates could be imported with wrong coordinates.
    Description: https://forum.freecadweb.org/viewtopic.php?f=10&t=31031

    happens for example with geo coordinates. See the linked forum topic. The problem is in coin or even in OpenGL. As a workaround it is possible to read the point cloud by Python move the point cloud to some smaller coordinates, may be the coordinates origin.

    See https://forum.freecadweb.org/viewtopic.php?f=10&t=31031&start=10#p257373

    An idea would be:
    - if one opens a pcl with huge coordinates FreeCAD warns the user and asks him if he would like to move the pcl to the coordinate orgin or by a user given vector.

    bernd
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016643)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5808.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3070 [File formats] General minor always 2017-06-05 01:02 2021-02-06 06:31
    Reporter: Krishty Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: VRML 2 crashes with corner cases
    Description: 1. FreeCAD crashes whenever VRML files contain recursive structures.
    2. It crashes after some time if files contain very long names.

    Recursive structures are not allowed in VRML, and they should not appear in the wild. However, FreeCAD shouldn't just crash either. Same for long names.
    Tags: VRML
    Steps To Reproduce: 1. load one of the attached files with "crash" prefix
    2. crash immediately

    OR

    1. click Open File
    2. select the file with "corrupts memory" prefix
    3. Open
    4. file seems to load file
    5. click Open File again
    6. FreeCAD crashes a fraction of a second after that (which indicates a memory corruption)
    Additional Information: running 0.16 on Windows 7
    Attached Files: corrupts memory - name too long.wrl (65,620 bytes) 2017-06-05 01:02
    https://tracker.freecad.org/file_download.php?file_id=1629&type=bug
    crash - recursive PROTO.wrl (296 bytes) 2017-06-05 01:02
    https://tracker.freecad.org/file_download.php?file_id=1630&type=bug
    crash - recursive USE.wrl (409 bytes) 2017-06-05 01:02
    https://tracker.freecad.org/file_download.php?file_id=1631&type=bug
    corrupts memory - name too long (VRML 1).wrl (65,571 bytes) 2017-06-05 01:10
    https://tracker.freecad.org/file_download.php?file_id=1632&type=bug
    crash - recursive USE (VRML 1).wrl (77 bytes) 2017-06-05 01:10
    https://tracker.freecad.org/file_download.php?file_id=1633&type=bug
    Notes
    (0009285)
    Krishty   
    2017-06-05 01:10   
    same crashes with VRML 1 recursive structures & VRML 1 long name
    (0009331)
    Kunda1   
    2017-06-10 11:35   
    Discussion thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=22875
    (0009343)
    wmayer   
    2017-06-11 12:16   
    <quote>
    2. It crashes after some time if files contain very long names.
    </quote>
    That's a bug in the Coin library. Inside the class SbName the function find_string_address is called (over several steps) and this raises an assert if the string is longer than 65004 characters. Many systems already crash there (when Coin was built with the debug option). On Windows in release mode it crashes at a later point because the internal string buffer seems to be corrupted.

    Does the VRML standard say anything about the maximum length of a name?
    (0009344)
    Krishty   
    2017-06-11 12:33   
    The VRML 2 standard defines a limit of 50 Bytes per name:
    http://tecfa.unige.ch/guides/vrml/vrml97/spec/part1/conformance.html#7.3.3

    VRML 1 standard does not mention anything.

    I recommend aborting after 50 B if you’re strict or after 127 B if you want to avoid problems with 3rd party libraries.
    (0009345)
    wmayer   
    2017-06-11 12:46   
    Thanks for the link.
    > I recommend aborting after 50 B if you’re strict or after 127 B if you want to avoid problems with 3rd party libraries.

    Currently we rely on Coin's VRML importer here. So as a workaround we must implement our own parser that verifies the DEF's of a VRML file.
    (0009346)
    Krishty   
    2017-06-11 13:01   
    Yes, a separate verification pass would also solve the recursive DEF/USE crash. However, given that VRML 1 & 2 are vastly different in grammar and the bug exists in both versions, that’s probably TWO parsers to be written.

    It should definitely be reported to the COIN maintainers and they need to fix that.
    (0009347)
    wmayer   
    2017-06-11 14:49   
    (Last edited: 2017-06-11 15:36)
    I pushed a fix https://github.com/FreeCAD/FreeCAD/commit/a405b4dae05fc55d784cc485723f278b83ea64ee the solves the crash when loading the file crash - recursive USE.wrl Having this function inside FreeCAD makes sense because cyclic graphs can also happen outside the scope of reading in a file.

    The fix doesn't prevent FreeCAD from crashing when reading in crash - recursive PROTO.wrl because there is already a stack overflow during the read process.

    Btw, MeshLab handles the cases with recursive PROTO and too long names but crashes with recursive USE. Blender handles all three cases.

    (0009348)
    Krishty   
    2017-06-11 18:09   
    > Btw, MeshLab handles the cases with recursive PROTO and too long names but crashes with recursive USE. Blender handles all three cases.

    Good thing to know! I don’t actually use FreeCAD, I was just fuzz-testing my own VRML implementation and wondered how other software suites do (considering we live in the age of exploits). It’s just fair to give other developers every chance to improve their software, so I reported the crashes outright. You should report them to MeshLab as well; use my test files at will.
    (0016542)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5707.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2940 [File formats] Feature minor N/A 2017-03-03 21:23 2021-02-06 06:31
    Reporter: ian.rees Platform:  
    Assigned To: ian.rees OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Add material information to exported AMFs
    Description: Following issue 0000608 - once material improvements are made to PartDesign, add material information in to exported AMFs.

    https://github.com/ianrrees/FreeCAD_tinkering/commit/b3626ed055f4aeaa2e2d473a30bb1108ad65521a
    Tags: AMF, file format
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016520)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5685.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2336 [File formats] Feature feature have not tried 2015-11-12 08:48 2021-02-06 06:31
    Reporter: douardda Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: importing .obj file should use the object names as labels
    Description: When importing objects from a Wavefront .obj file format, the object names ib the .obj file are not used as labels in Freecad.

    eg. a myfile.obj file like:

     
      # FreeCAD v0.15 build4671 (Git) Arch module
      # http://www.freecadweb.org [^]
      o MonCube
      v 18.881188 4.8209 4.903852
      v 18.881188 4.8209 -5.096148
      v 18.881188 14.8209 4.903852
      v 18.881188 14.8209 -5.096148
      v 28.881188 4.8209 4.903852
      v 28.881188 4.8209 -5.096148
      v 28.881188 14.8209 4.903852
      v 28.881188 14.8209 -5.096148
      f 1 2 4 3
      f 5 6 8 7
      f 6 2 1 5
      f 8 4 3 7
      f 4 2 6 8
      f 3 1 5 7


    will be imported with the cube's label being 'myfile' instead of the expected 'MonCube'.

    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0007898)
    Kunda1   
    2017-01-20 21:37   
    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=10&t=20088
    (0016471)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5636.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2335 [File formats] Feature feature always 2015-11-12 08:43 2021-02-06 06:31
    Reporter: douardda Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: feedback Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: export in .obj file should use the objects labels
    Description: When exporting objects in a Wavefront .obj file format, the object labels are not used to identify them in the generated file, but are generated from the object type.

    eg. a scene with a cube named 'MonCube' in FreeCad will be exported as:

     
      # FreeCAD v0.15 build4671 (Git) Arch module
      # http://www.freecadweb.org
      o Box
      v 18.881188 4.8209 4.903852
      v 18.881188 4.8209 -5.096148
      v 18.881188 14.8209 4.903852
      v 18.881188 14.8209 -5.096148
      v 28.881188 4.8209 4.903852
      v 28.881188 4.8209 -5.096148
      v 28.881188 14.8209 4.903852
      v 28.881188 14.8209 -5.096148
      f 1 2 4 3
      f 5 6 8 7
      f 6 2 1 5
      f 8 4 3 7
      f 4 2 6 8
      f 3 1 5 7


    I would have expected the line:

      o Box

    to be:

      o MonCube


    Tags: #post-to-forum, OBJ
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0006553)
    damian   
    2015-11-25 13:41   
    (Last edited: 2015-11-25 16:30)
    Hello douardda:

    I wrote a solution in
     
    https://github.com/caceres/FreeCAD/commits/importOBJ

    commit 21 nov 2015 "enable obj Label"

    (0007818)
    Kunda1   
    2017-01-16 09:55   
    @damian did you submit a PR for this? BTW the repo link is 404
    (0007897)
    Kunda1   
    2017-01-20 21:36   
    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=10&t=20088
    (0008509)
    Kunda1   
    2017-03-02 12:16   
    @damian ping
    (0016470)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5635.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1558 [File formats] Feature minor have not tried 2014-05-19 20:04 2021-02-06 06:31
    Reporter: petebachant Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Save CAD data as text (JSON) for version control
    Description: This may be too drastic of a change, but it would be really great to be able to use Git, or some other text-based version control tool with CAD data.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0004702)
    petebachant   
    2014-05-19 21:02   
    I just found out that the FreeCAD format is actually a compressed archive containing XML files. Maybe an option to load/save uncompressed would suffice.
    (0004720)
    normandc   
    2014-05-22 01:33   
    Revision control is a long-term goal of the FreeCAD developers, see http://www.freecadweb.org/wiki/index.php?title=Assembly_project#Revision_control
    (0004723)
    shoogen   
    2014-05-22 07:17   
    We save zip files, which contain different type of data.
    What you could do is to extract the FCStd file to a directory and add the whole directory to your version control.

    Putting everything into one text based file, (XML, JSON...) makes not much sense if we had to embed our BREP files.

    We could try to use OCAF to get an XML representation of shapes.
    (0005145)
    shoogen   
    2014-09-22 13:24   
    It seems that OCAF XML just includes she Shapes as CDATA
    (0011216)
    Kunda1   
    2018-04-28 02:48   
    Related: https://github.com/reox/FreeCAD_gitproject
    (0013410)
    freelibre   
    2019-08-11 05:57   
    (Last edited: 2019-08-11 17:03)
    Version control with git in a gitlab or github project repo would be a great feature to improve open hardware projects team members collaboration.

    The most usefull feature would be to be able to see live versions & branches of the different parts designed in a project by the different project members.

    That's a feature Onshape has implemented and a short demo is available there:
    https://www.youtube.com/watch?v=ggL9IQSo4VI

    (0016420)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5585.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1156 [File formats] Feature minor N/A 2013-06-22 16:46 2021-02-06 06:31
    Reporter: templatearray Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: feedback Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: JT File Format
    Description: Specification of the JT file format 8.1
    Tags: file format
    Steps To Reproduce:
    Additional Information:
    Attached Files: PLM_Solutions_a.pdf (973,422 bytes) 2013-06-23 05:09
    https://tracker.freecad.org/file_download.php?file_id=503&type=bug
    PLM_Solutions_b.pdf (928,306 bytes) 2013-06-23 05:12
    https://tracker.freecad.org/file_download.php?file_id=504&type=bug
    PLM_Solutions_c.pdf (1,357,924 bytes) 2013-06-23 05:13
    https://tracker.freecad.org/file_download.php?file_id=505&type=bug
    PLM_Solutions_d.pdf (1,440,514 bytes) 2013-06-23 05:15
    https://tracker.freecad.org/file_download.php?file_id=506&type=bug
    JT_File_Format_81_a.pdf (927,550 bytes) 2013-06-23 05:25
    https://tracker.freecad.org/file_download.php?file_id=507&type=bug
    JT_File_Format_81_b.pdf (841,818 bytes) 2013-06-23 05:27
    https://tracker.freecad.org/file_download.php?file_id=508&type=bug
    JT_File_Format_81_c.pdf (860,283 bytes) 2013-06-23 05:28
    https://tracker.freecad.org/file_download.php?file_id=509&type=bug
    JT_File_Format_81_d.pdf (895,020 bytes) 2013-06-23 05:36
    https://tracker.freecad.org/file_download.php?file_id=510&type=bug
    Jt2Go_Example_1.jt (51,417 bytes) 2013-06-23 06:35
    https://tracker.freecad.org/file_download.php?file_id=511&type=bug
    Jt2Go_Example_1.brep (815,464 bytes) 2013-06-23 06:36
    https://tracker.freecad.org/file_download.php?file_id=512&type=bug
    Jt2Go_Example_1.step (417,700 bytes) 2013-06-23 06:36
    https://tracker.freecad.org/file_download.php?file_id=513&type=bug
    Jt2Go_Example_2.jt (182,090 bytes) 2013-06-23 06:39
    https://tracker.freecad.org/file_download.php?file_id=514&type=bug
    Jt2Go_Example_2.step (1,519,983 bytes) 2013-06-23 06:43
    https://tracker.freecad.org/file_download.php?file_id=515&type=bug
    Jt2Go_Example_2.iges (1,031,049 bytes) 2013-06-23 06:52
    https://tracker.freecad.org/file_download.php?file_id=516&type=bug
    124.pdf (33,637 bytes) 2019-07-11 10:23
    https://tracker.freecad.org/file_download.php?file_id=2260&type=bug
    Notes
    (0003239)
    Jriegel   
    2013-06-26 09:08   
    There is already a JT import module in FreeCAD. but it need the JtOpenLib to work which is proprietary....

    I don't think jt is implementable in OpenSource...
    (0003241)
    Jriegel   
    2013-06-26 09:12   
    Anyone think we should do that?

    I think we should not....
    (0007147)
    lukasubo   
    2016-06-15 03:27   
    (Last edited: 2016-06-15 03:45)
    Why does it matter so much, anyway? Is JT commonly used? Supporting interchange of proprietary file formats from a company which has a stake in their use (Siemens) is generally a bad practice, and if you have a bunch of files in this format, you can just use some other CAD (OnShape, for instance - no download, free account, and runs on any OS) to convert them to STEP.

    EDIT: GrabCAD should also work as an online service to convert from proprietary file types.

    (0007148)
    lukasubo   
    2016-06-15 03:29   
    Oh, I just realized I bumped this from 3 years ago... sorry. I saw it in the "Unassigned" list and didn't check the date.
    (0008507)
    Kunda1   
    2017-03-02 12:07   
    @yorik do you mind weighing in on this?
    (0008514)
    yorik   
    2017-03-02 13:16   
    It is very unlikely to be implemented, but we can also just leave the ticket open, someone might get interested in working on this in the future...
    (0016400)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5565.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    337 [File formats] Feature minor have not tried 2011-04-14 06:13 2021-02-06 06:31
    Reporter: e-ndy Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: acknowledged Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: add support for Rhino3D files
    Description: available library from developers of Rhino3D (http://opennurbs.org/). it should be nice to have capability to load/save Rhino3D models, together with https://sourceforge.net/projects/libnurbs/ it should be good replacement for Rhino3D in linux
    Tags: file format, NURBS
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0000827)
    Jriegel   
    2011-05-17 07:35   
    Actually I dont like myself to struggle with commercial file formats. But If someone have coding time - be welcome.
    (0000857)
    normandc   
    2011-05-21 11:51   
    It is unclear to me reading the OpenNURBS Initiative website whether the 3DM file format is open source or commercial. But it seems to be completely documented, which I think means it would be much less of a struggle to incorporate in FreeCAD as other proprietary and closed formats. It would indeed be really nice to have a CAD program on Linux able to open 3DM files. But there is no NURBS support or tools in FreeCAD at the moment, maybe Blender (which supports NURBS surfaces) would be best suited?
    (0000859)
    Jriegel   
    2011-05-22 18:25   
    OCC support NURBS, but we lack the tools to model it.
    So we could do boolean operation on loaded NURBS, buts
    thats around it.

    Actually I'm not a big fan of NURBS. IMO subdevision surfaces are
    the way of the future...
    (0000868)
    yorik   
    2011-05-29 13:54   
    Actually since freecad supports nurbs, 3DM format should be possible to handle without problems (and IIRC Rhino also supports brep-like objects)... On the openNurbs website there is a C++ toolkit which can read/write 3DM files, and appears to be compatible with GPL license ( http://www.opennurbs.org/docs.htm ):

    "Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software."

    I'm downloadiing the toolkit right now to have a look...
    (0000869)
    yorik   
    2011-05-29 13:59   
    Interesting quotes from the FAQ included inside the toolkit:

    "Excellent compilers and make utilities are available from
    The Free Software Foundation <http://www.fsf.org> You have
    the option of using these tools free of charge."

    "Internally, Rhino stores all surfaces as some type of b-rep and the
    openNURBS toolkit reads these objects as b-reps."
    (0000870)
    yorik   
    2011-05-29 14:04   
    Hm reading a file looks actually pretty simple, if we can include the opennurbs code!
    (0000879)
    unauthenticated   
    2011-06-01 14:30   
    Reading the file should not be the problem.
    You have to transfer each entity to a OCC object.
    Not only the NURBS, also the trimming curves and all
    other entities like planes and so on...

    Its posible, but a lot of work an tuning to get it run....
    (0004909)
    keithsloan52   
    2014-08-02 23:06   
    I have a skeleton FreeCAD importer that is using the OpenNurbs library to parse a 3dm file. I will now try and add code to create nurbs etc
    (0007625)
    Kunda1   
    2017-01-11 12:56   
    (Last edited: 2017-02-10 12:15)
    Picking up the trail here...a forum thread mentioning this topic:
    Nurbs Editor - http://forum.freecadweb.org/viewtopic.php?f=3&t=16473&start=30#p132955
    Import 3DM files with OpenNurbs - https://forum.freecadweb.org/viewtopic.php?f=3&t=16473&start=130#p153127
    GitHub repo where the development is happening; https://github.com/KeithSloan/FreeCAD_ImportNurbs

    (0008763)
    Kunda1   
    2017-04-26 00:52   
    @travm1 wrote:
    Here is the wiki page for Rhino3D
    (0008764)
    Kunda1   
    2017-04-26 00:55   
    @keithsloan52 wrote:
    Yorik has done some work on using CAD Exchanger see https://github.com/yorikvanhavre/CADExchanger So should be able to import Rhino 3DM files using it. Note CAD Exchanger is commercial so one needs to pay. Not sure how much as you seem to have to contact them to get a quote.
    (0008765)
    Kunda1   
    2017-04-26 00:57   
    @yorik wrote:
    They told me they are setting up a new page that will have prices on it. In any case, implementing our own might still be an interesting option.
    (0014268)
    Kunda1   
    2020-03-23 12:10   
    Update: Chris_G on the forum utilizing rhino3dm python bindings:
    https://forum.freecadweb.org/viewtopic.php?f=8&t=11970&p=379662#p379662
    (0014286)
    keithsloan52   
    2020-03-24 16:46   
    A new Workbench has been started using Chris's code and use of the new rhino3dm python bindings see https://github.com/KeithSloan/ImportNURBS
    (0016379)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5544.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4480 [Expressions] Bug minor have not tried 2020-10-30 07:54 2021-02-06 06:30
    Reporter: mapeze Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Debian GNU/Linux 10 (buster) (XFCE/lightdm-xsession)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.22846 (Git) AppImage
    Build type: Release
    Branch: master
    Hash: 1f46b72491a0008384a6db4f2615a656249f6f08
    Python version: 3.8.6
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: English/United States (en_US)
    Summary: Cross-document linking does not update on Recompute
    Description: Hello,

    This Bug report refers to the discussion https://forum.freecadweb.org/viewtopic.php?f=8&t=51594&p=443097#p443097

    The cross-document linking feature stopped working properly from an unspecified 0.19 version and above. I have detected the issue in the Spreadsheets only (I have never been able to make the cross-document linking work outside the Spreadsheet environment). The cross-document linkng feature is described here: https://wiki.freecadweb.org/Expressions

    The expected behaviour of the cross-document linking, as it was working in FreeCAD old versions is:

    - Having one Master file with a Spreadheet inside, an alias and a value is given to a cell
    - Having a Slave file with a Spreadsheet inside, an expression is given to a cell with the expression "=Master_file_name#Master_Spreadsheet_name.alias_name"
    - The value of the Master cell is changed
    - The value of the slave cell is updated when Recompute action is done.

    However in new Freecad versions, to update the slave cell value one of the next two actions is needed:
    - Enter the slave cell to edit it, leave it as it is and press Enter
    - Reopen the slave file
    Tags:
    Steps To Reproduce: 1- Open the attached Master.FCStd and Slave.FCStd files in this order
    2- Open the Spreadsheet on Master file and change the B1 cell value to something diferent
    3- Open the Spreadsheet on the Slave file and press the Recompute button on the toolbar
    4- The B1 cell on Slave's Spreadsheet should be updated, but it is not.
    Additional Information:
    Attached Files: Slave.FCStd (1,866 bytes) 2020-10-30 07:54
    https://tracker.freecad.org/file_download.php?file_id=2556&type=bug
    Master.FCStd (1,783 bytes) 2020-10-30 07:54
    https://tracker.freecad.org/file_download.php?file_id=2557&type=bug
    Notes
    (0016956)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6123.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4325 [Expressions] General minor always 2020-04-27 11:17 2021-02-06 06:30
    Reporter: lc03 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: feedback Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 10 (10.0)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.20738 (Git)
    Build type: Release
    Branch: master
    Hash: 0c96f77184edc0a6747483b2ff1462fc6dae46ff
    Python version: 3.6.8
    Qt version: 5.12.1
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: French/France (fr_FR)
    Summary: Strange character after bracket, appear in expression input field for a constraint in sketcher
    Description: When I type in expression containing bracket in the expression editor a strange character appear at the end of the entered text.
    Tags: #pending-forum
    Steps To Reproduce: 1) Create a new sketch
    2) Create 2 new line.
    3) Create a dimension constraint on the first line.
    4) Create a dimension constraint on the second line and then enter the “=” sign to edit expression.
    5) Type in the expression “Constraints[0]”
    Result: just after you type in the last character (that is “]”) the strange character appear in the expression editor
    Additional Information:
    Attached Files: Strange character in expression editor.JPG (60,221 bytes) 2020-04-27 11:17
    https://tracker.freecad.org/file_download.php?file_id=2463&type=bug
    Notes
    (0014385)
    openBrain   
    2020-04-28 19:43   
    @lc03 : Please address your issue according our reporting guidelines by first opening a topic on our forum ("Help on using FreeCAD" subsection in English or "Forum français" in French) so community can vet the issue and narrow down the causes. Cross-link the topic with this ticket. Thx
    (0014389)
    openBrain   
    2020-04-29 09:50   
    Forum thread
    (0015115)
    Kunda1   
    2020-12-08 01:25   
    Moved to Expressions category
    (0016885)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6051.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4261 [Expressions] Bug major always 2020-02-04 14:20 2021-02-06 06:30
    Reporter: openBrain Platform:  
    Assigned To: realthunder OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 7 SP 1 (6.1)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.19461 (Git)
    Build type: Release
    Branch: master
    Hash: da71719896847b0e2a5716e7afb5d4cb4b326990
    Python version: 3.6.8
    Qt version: 5.12.1
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: French/France (fr_FR)
    Summary: Bad behavior when using '°' unit in expressions
    Description: Using the sign '°' to denote degrees in expressions causes expression engine malfunction.
    Tags:
    Steps To Reproduce:   - Create a new document, select PartDesign WB
      - Add a sketch (you can just let it empty)
      - Create a DatumPlane (locate it at any position)
      - Try to enter as expression for DatumPlane/AttachmentOffset/Angle the following :'90°-atan(Sk' => You'll notice first that 'Sketch' is only proposed when you enter the 'k', then that if you select 'Sketch' proposal with down arrow, it is replaced by 'SSketch' in the expression (doubled 'S')

    If you use 'deg' instead of '°' in the expression, the 2 issues described aren't present : 'Sketch' is proposed as soon as 'S' is entered, and it is correctly entered in the expressions if you select the proposal with down arrow.
    Additional Information: I have no evidence but I'm afraid this issue causes more severe damages to the expression engine when a document is loaded.
    Attached Files:
    Notes
    (0014159)
    vocx   
    2020-02-16 19:40   
    Forum thread: Bad behavior when using '°' unit in expressions
    (0014185)
    realthunder   
    2020-02-27 04:09   
    Will be solved by this PR. See here.
    (0016861)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6027.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4196 [Expressions] Bug minor always 2019-11-18 20:00 2021-02-06 06:30
    Reporter: babaroga Platform: Linux  
    Assigned To: OS: Manjaro  
    Priority: normal OS Version: 18.1.3  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Manjaro Linux (KDE//usr/share/xsessions/plasma)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.18753 (Git)
    Build type: Release
    Branch: master
    Hash: c0a80e1a9a5683404fe506201d0ee74b28ea819d
    Python version: 3.7.4
    Qt version: 5.13.2
    Coin version: 4.0.0a
    OCC version: 7.4.0
    Locale: English/United States (en_US)
    Summary: Expression parser does not allow "/" after first member
    Description: If someone try to enter eg. 12/2 in any field for X, Y, Z, constrain in sketcher, parser will not allow to type "/" sign just after first member in expression. All other operations works as expected.
    Everything works OK if entered as formula.

    Issue is described in

    Forum thread
    Tags: expressions
    Steps To Reproduce: Try to change X, Y or Z position of eg. body with

    12/2 - does not work
    (12)/2 - does not work
    0+12/2 - works

    Additional Information:
    Attached Files:
    Notes
    (0013830)
    openBrain   
    2019-11-22 16:49   
    @babaroga : thanks for reporting. However please notice that per our guidelines (big yellow banner) you should have open a topic in our forum before reporting.
    Though your report is correctly filled in, bug can be confirmed and seems unknown up to now, we'll keep this ticket as is without further request to post to forum. ;)
    (0013833)
    babaroga   
    2019-11-22 16:55   
    (Last edited: 2019-11-22 16:57)
    Hello,

    @openBrain It was reported in forums on

    https://forum.freecadweb.org/viewtopic.php?f=3&t=40995

    Somehow, link is not visible in my first post.

    (0013835)
    openBrain   
    2019-11-22 17:23   
    @babaroga :there was no text in the url tag in the description. I fixed it. ;)
    Could you edit the title of the forum thread and prepend "[Bug 4196]" to it (thread title is actually OP title)? Thx
    (0013849)
    Kunda1   
    2019-11-28 12:52   
    Moved to 'Expressions' category
    (0013964)
    ulrich1a   
    2019-12-31 16:07   
    (Last edited: 2019-12-31 16:08)
    The reported bug is not caused by FreeCAD-Expressions. Expressions are used in the dialog reachable via the blue "fx"-symbol: This dialog is not affected by the bug here and behaves different and uses different code.
    The bug is related to the input field of the Gui, which uses a different parser. The formula typed in the input field is gone after its calculation.

    Both usages uses "expressions" but are coded in different areas of FreeCAD.

    Ulrich

    (0013965)
    openBrain   
    2020-01-01 17:47   
    @ulrich1a : would you be able to give a pointer to involved parser code in GitHub ?
    (0016841)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6007.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4192 [Expressions] Feature feature always 2019-11-09 11:23 2021-02-06 06:30
    Reporter: t.lemaitre Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Ubuntu 18.04.3 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.4.
    Build type: Release
    Python version: 3.6.8
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: French/France (fr_FR)
    Summary: Set an expression with many objects at the same time
    Description: Hi,

    As described in the following thread, I propose a new feature to be able to set an expression with many objects at the same time.

    https://forum.freecadweb.org/viewtopic.php?f=8&t=40408&p=345646#p343573
    Tags:
    Steps To Reproduce: See forum's thread https://forum.freecadweb.org/viewtopic.php?f=8&t=40408&p=345646#p343573
    Additional Information: See forum's thread https://forum.freecadweb.org/viewtopic.php?f=8&t=40408&p=345646#p343573
    Attached Files:
    Notes
    (0013813)
    Kunda1   
    2019-11-09 12:28   
    Thanks! FYI, we do have a category for Expressions/Spreadsheet called 'Expressions'. I moved your ticket there
    (0016840)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6006.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4119 [Expressions] Bug crash always 2019-09-09 04:41 2021-02-06 06:30
    Reporter: cbruner Platform: linux-mint  
    Assigned To: realthunder OS: linux  
    Priority: high OS Version: 19.2  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: spaces in names cause fail to parse expressions.
    Description: Forum discussion. https://forum.freecadweb.org/viewtopic.php?f=3&t=39153
    OS: Linux Mint 19.2
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16131 (Git) AppImage
    Build type: Release
    Branch: (HEAD detached at 0.18.3)
    Hash: 3129ae4296e40ed20e7b3d460b86e6969acbe1c3
    Python version: 3.6.7
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/Canada (en_CA)
    Tags: expressions
    Steps To Reproduce: Follow the Freecad tutorial video.
    https://www.youtube.com/watch?v=C1JG6l1uIJw&t=773s at 18:06 he has created a master sketch with a rectangle and a line, which is called "HeightOfBlock".
    I typed "Height of Block", which led to subsequent errors of "fail to parse expressions" Later in the tutorial
    Figuring out the root cause was difficult and wasted many hours I had dedicated to learning freecad.

    It can be resolved by several ways.
    1. Give an error when spaces are used in names. (Either use them or don't, but don't accept them and then complain about it!)
    2. Substitute "_" for " " whenever a name is added. This resolves the problem pretty simply and allows for names that look like they have spaces without actually having spaces.
    3. Change the parser to handle names with spaces. (I think this is the worst solution).
    Additional Information: The Failure to parse expressions error occurred when trying to use the part, but it seemed to be referring to a cyclic redundancy problem, not the actual root cause.
    Attached Files:
    Notes
    (0013561)
    cbruner   
    2019-09-09 13:40   
    I forgot to mention a crash which occurred due to this bug. I believe this to be a separate issue, but possibly related so I'm mentioning it here.

    From the forum notes:
    I started deleting the CC and noticed that the master was grey now, with a new sketch001 under it. Deleted that and got a segfault.

    Show.TempoVis.isIn3DView error: Object has been removed from documentViewProviderSketch::setEdit: visibility automation failed with an error:
    Traceback (most recent call last):
    File "<string>", line 7, in <module>
    File "/tmp/.mount_freecatHpNXG/usr/Mod/Show/TempoVis.py", line 118, in hide
    self.modifyVPProperty(doc_obj_or_list, 'Visibility', False)
    File "/tmp/.mount_freecatHpNXG/usr/Mod/Show/TempoVis.py", line 99, in modifyVPProperty
    if not hasattr(doc_obj.ViewObject, prop_name):
    <class 'RuntimeError'>: Object has been removed from document
    App::Document::recompute(): cyclic dependency detected
    Exception (Sat Sep 7 13:15:07 2019): Invalid constraint
    App::Document::recompute(): cyclic dependency detected
    App::Document::recompute(): cyclic dependency detected
    Exception (Sat Sep 7 13:15:28 2019): Invalid constraint
    App::Document::recompute(): cyclic dependency detected
    Program received signal SIGSEGV, Segmentation fault.
    /tmp/.mount_freecatHpNXG/AppRun: line 12: 12528 Segmentation fault (core dumped) ${HERE}/usr/bin/FreeCAD "$@"
    (0013962)
    graffy   
    2019-12-30 17:28   
    Can you describe a quick example that reproduces the error? I know you referenced the video you were following at the time, but it would help to have a simple example that can be reproduced in a minimum number of steps.
    (0013963)
    cbruner   
    2019-12-31 05:40   
    (Last edited: 2019-12-31 05:49)
    Create a sketch call it "Master" with a line in it.
    Give the line a dimension and the line "Height of block". https://youtu.be/C1JG6l1uIJw?t=1079

    Create a new sketch (from the same body that the Master was created from).
    Put a properly constrained square on this new sketch. Then Pad it.
    The length of the pad is ="Master.Height of block"
    I think this will show the error.
    You can name things with spaces in them, but can't use those names to reference things.
    Hope this is clear enough.

    (0013967)
    Kunda1   
    2020-01-02 14:19   
    Moved to 'Expressions' category
    (0014184)
    realthunder   
    2020-02-27 04:05   
    Will be solved by this PR. See here for details.
    (0016817)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5983.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4037 [Expressions] Feature feature always 2019-06-25 23:36 2021-02-06 06:30
    Reporter: uwestoehr Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: rewrite unit handling so that unit prefixes will be recognized
    Description: Currently we have the case that the expression parser knows units with prefixes, e.g. "mA". For other units like e.g. "j", it does not know any prefix.

    To overcome this, the expression parser must be rewritten so that it recognizes these prefixes:
    n, mu/µ, m, k, M, G
    and connects them automatically to the unit that follows directly on the prefix letter.

    So "ncd" will be recognized as "we have 'n' -> nano (10^-9), the next letter is 'c' which could be part of a known unit that begins with 'c', the next letter is 'd' so we know we have the unit "cd" with the prefix 'n'.
    However "n A" will be recognized as "we have 'n' -> nano (10^-9), the next letter is ' ' (space), so we don't have a unit connected to the prefix letter 'n' and we issue an error.

    This method would lead to
    - consistent handling of all units
    - support for unit prefixes for all units
    Tags: expressions, units
    Steps To Reproduce:
    Additional Information: Forum thread: https://forum.freecadweb.org/viewtopic.php?f=38&t=37164

    The idea was approved as useful by @berndhahnebach
    Attached Files:
    Notes
    (0013313)
    berndhahnebach   
    2019-06-26 20:20   
    https://en.wikipedia.org/wiki/Unit_prefix
    (0013321)
    openBrain   
    2019-06-30 14:15   
    Be very careful to side effects ! I'd not want that 'min' unit being considered as "milli-inch" instead of the correct "minute". ;)
    (0013326)
    uwestoehr   
    2019-07-01 09:07   
    > I'd not want that 'min' unit being considered as "milli-inch"

    Yes, the procedure should be
    1. read the whole given unit and if it is known like "min" then nothing is done and the unit is taken as it is
    2.1 if the unit is unknown, check if it begins with a known letter of unit prefixes
    2.2 if yes, read the unit beginning with the second character and if this is a known unit, use it multiplied with the factor according to the read unit prefix
    3. if 1. and 2. did not lead to a known unit, deny the unit and issue an error message
    (0013851)
    ezzieyguywuf   
    2019-11-29 13:40   
    I think a better approach is perhaps to hard-code a set of given prefixes to units that they are compatible with.

    For example, “milli”, “kilo”, etc, are commonly accepted with metric units.

    Not so much for imperial- I’ve never heard of a milli-inch
    (0016789)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5955.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4031 [Expressions] Bug crash always 2019-06-20 13:03 2021-02-06 06:30
    Reporter: dhka2 Platform: Linux  
    Assigned To: OS: Arch  
    Priority: normal OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Crash upon solving expression referencing named Constraint
    Description: Freecad git build as of 18.06.2019 sometimes crashes with signal 11 upon referencing a named constraint in an expression. This is width python 3 and qt5.

    stdout output:

    Program received signal SIGSEGV, Segmentation fault.
    #0  /lib/libc.so.6(+0x378b0) [0x7f160e65a8b0]
    #1  0x7f160fe90f76 in App::ObjectIdentifier::Component::get(Py::Object const&) const from /usr/lib/freecad/lib/libFreeCADApp.so+0x1c6
    0000002  0x7f160fe96638 in App::ObjectIdentifier::access(App::ObjectIdentifier::ResolveResults const&, Py::Object*) const from /usr/lib/freecad/lib/libFreeCADApp.so+0x1b8
    0000003  0x7f160fe9ae14 in App::ObjectIdentifier::getPyValue(bool, bool*) const from /usr/lib/freecad/lib/libFreeCADApp.so+0x84
    0000004  0x7f160fe04ca2 in App::VariableExpression::_getPyValue(int*) const from /usr/lib/freecad/lib/libFreeCADApp.so+0x62
    0000005  0x7f160fdf3e2c in App::Expression::getPyValue(int, int*) const from /usr/lib/freecad/lib/libFreeCADApp.so+0x4c
    0000006  0x7f160fdf4f62 in App::Expression::eval(int) const from /usr/lib/freecad/lib/libFreeCADApp.so+0x42
    0000007  0x7f16105e2cfc in Gui::Dialog::DlgExpressionInput::textChanged(QString const&) from /usr/lib/freecad/lib/libFreeCADGui.so+0x1fc
    0000008  0x7f160ec388e7 in QMetaObject::activate(QObject*, int, int, void**) from /lib/libQt5Core.so.5+0x777
    0000009  0x7f160f15c963 in QLineEdit::textChanged(QString const&) from /lib/libQt5Widgets.so.5+0x33
    0000010  /lib/libQt5Widgets.so.5(+0x29c662) [0x7f160f163662]
    0000011  0x7f160ec388e7 in QMetaObject::activate(QObject*, int, int, void**) from /lib/libQt5Core.so.5+0x777
    0000012  0x7f160f164276 in QWidgetLineControl::textChanged(QString const&) from /lib/libQt5Widgets.so.5+0x36
    0000013  0x7f160f167710 in QWidgetLineControl::finishChange(int, bool, bool) from /lib/libQt5Widgets.so.5+0x2a0
    0000014  0x7f160f16abaf in QWidgetLineControl::processKeyEvent(QKeyEvent*) from /lib/libQt5Widgets.so.5+0xebf
    0000015  0x7f160f15caeb in QLineEdit::keyPressEvent(QKeyEvent*) from /lib/libQt5Widgets.so.5+0x1b
    0000016  0x7f161053668f in Gui::ExpressionLineEdit::keyPressEvent(QKeyEvent*) from /usr/lib/freecad/lib/libFreeCADGui.so+0x1f
    0000017  0x7f160f060b88 in QWidget::event(QEvent*) from /lib/libQt5Widgets.so.5+0x258
    0000018  0x7f160f162ebb in QLineEdit::event(QEvent*) from /lib/libQt5Widgets.so.5+0xab
    0000019  0x7f160f01fda4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /lib/libQt5Widgets.so.5+0x84
    0000020  0x7f160f02833c in QApplication::notify(QObject*, QEvent*) from /lib/libQt5Widgets.so.5+0x118c
    0000021  0x7f1610539019 in Gui::GUIApplication::notify(QObject*, QEvent*) from /usr/lib/freecad/lib/libFreeCADGui.so+0x89
    0000022  0x7f160ec0def9 in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /lib/libQt5Core.so.5+0x179
    0000023  /lib/libQt5Widgets.so.5(+0x1b7b42) [0x7f160f07eb42]
    0000024  0x7f160f01fda4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /lib/libQt5Widgets.so.5+0x84
    0000025  0x7f160f0273c1 in QApplication::notify(QObject*, QEvent*) from /lib/libQt5Widgets.so.5+0x211
    0000026  0x7f1610539019 in Gui::GUIApplication::notify(QObject*, QEvent*) from /usr/lib/freecad/lib/libFreeCADGui.so+0x89
    0000027  0x7f160ec0def9 in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /lib/libQt5Core.so.5+0x179
    0000028  0x7f160ce9a50d in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) from /lib/libQt5Gui.so.5+0x16d
    0000029  0x7f160ce9f526 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) from /lib/libQt5Gui.so.5+0x116
    0000030  0x7f160ce7a55c in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /lib/libQt5Gui.so.5+0xbc
    0000031  /lib/libQt5XcbQpa.so.5(+0x6db7c) [0x7f16088f2b7c]
    0000032  /lib/libglib-2.0.so.0(g_main_context_dispatch+0x2bf) [0x7f160c2ca90f]
    0000033  /lib/libglib-2.0.so.0(+0x6d869) [0x7f160c2cc869]
    0000034  /lib/libglib-2.0.so.0(g_main_context_iteration+0x2e) [0x7f160c2cc8ae]
    0000035  0x7f160ec63079 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /lib/libQt5Core.so.5+0x69
    0000036  0x7f160ec0cabc in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) from /lib/libQt5Core.so.5+0x13c
    0000037  0x7f160f21864e in QDialog::exec() from /lib/libQt5Widgets.so.5+0x1de
    0000038  0x7f153a96cc92 in openEditDatumDialog(Sketcher::SketchObject*, int) from /usr/lib/freecad/lib/SketcherGui.so+0x422
    #39  0x7f153a96d77f in finishDistanceConstraint(Gui::Command*, Sketcher::SketchObject*, bool) from /usr/lib/freecad/lib/SketcherGui.so+0x19f
    #40  0x7f153a970f66 in CmdSketcherConstrainDistanceY::activated(int) from /usr/lib/freecad/lib/SketcherGui.so+0xb86
    0000041  0x7f161056a30c in Gui::Command::invoke(int, Gui::Command::TriggerSource) from /usr/lib/freecad/lib/libFreeCADGui.so+0x36c
    0000042  0x7f160ec388e7 in QMetaObject::activate(QObject*, int, int, void**) from /lib/libQt5Core.so.5+0x777
    0000043  0x7f160f0195e3 in QAction::triggered(bool) from /lib/libQt5Widgets.so.5+0x43
    0000044  0x7f160f01bcca in QAction::activate(QAction::ActionEvent) from /lib/libQt5Widgets.so.5+0xfa
    0000045  0x7f160f01c5d5 in QAction::event(QEvent*) from /lib/libQt5Widgets.so.5+0x55
    0000046  0x7f160f01fda4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /lib/libQt5Widgets.so.5+0x84
    0000047  0x7f160f0273c1 in QApplication::notify(QObject*, QEvent*) from /lib/libQt5Widgets.so.5+0x211
    0000048  0x7f1610539019 in Gui::GUIApplication::notify(QObject*, QEvent*) from /usr/lib/freecad/lib/libFreeCADGui.so+0x89
    0000049  0x7f160ec0def9 in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /lib/libQt5Core.so.5+0x179
    0000050  0x7f160cec8890 in QShortcutMap::dispatchEvent(QKeyEvent*) from /lib/libQt5Gui.so.5+0x110
    0000051  0x7f160cec8973 in QShortcutMap::tryShortcut(QKeyEvent*) from /lib/libQt5Gui.so.5+0x63
    0000052  0x7f160ce7dedc in QWindowSystemInterface::handleShortcutEvent(QWindow*, unsigned long, int, QFlags<Qt::KeyboardModifier>, unsigned int, unsigned int, unsigned int, QString const&m /lib/libQt5Gui.so.5+0x18c
    0000053  0x7f160ce9a42e in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) from /lib/libQt5Gui.so.5+0x8e
    0000054  0x7f160ce9f526 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) from /lib/libQt5Gui.so.5+0x116
    0000055  0x7f160ce7a55c in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /lib/libQt5Gui.so.5+0xbc
    0000056  /lib/libQt5XcbQpa.so.5(+0x6db7c) [0x7f16088f2b7c]
    0000057  /lib/libglib-2.0.so.0(g_main_context_dispatch+0x2bf) [0x7f160c2ca90f]
    0000058  /lib/libglib-2.0.so.0(+0x6d869) [0x7f160c2cc869]
    0000059  /lib/libglib-2.0.so.0(g_main_context_iteration+0x2e) [0x7f160c2cc8ae]
    0000060  0x7f160ec63079 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /lib/libQt5Core.so.5+0x69
    0000061  0x7f160ec0cabc in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) from /lib/libQt5Core.so.5+0x13c
    0000062  0x7f160ec14c46 in QCoreApplication::exec() from /lib/libQt5Core.so.5+0x96
    0000063  0x7f16104ba880 in Gui::Application::runApplication() from /usr/lib/freecad/lib/libFreeCADGui.so+0x1570
    0000064  freecad(main+0x6ef) [0x55727def245f]
    0000065  /lib/libc.so.6(__libc_start_main+0xf3) [0x7f160e646ce3]
    0000066  freecad(_start+0x2e) [0x55727def277e]
    Tags:
    Steps To Reproduce: 1. open TestPlate.FCStd
    2. go to part design workbench
    4. create sketch
    5. draw circle somewhere
    5. create vertical constraint between center and origin.
    6. click on expression button
    7. type in Sketch.Constraints.w
    8. observe crash
    Additional Information: OS: Arch Linux
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.18336 (Git)
    Build type: Release
    Branch: makepkg
    Hash: 52d0f1db0905f11497241aa2ed35d5d990eda53f
    Python version: 3.7.3
    Qt version: 5.12.4
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/United States (en_US)
    Attached Files: TestPlate.FCStd (32,769 bytes) 2019-06-20 13:03
    https://tracker.freecad.org/file_download.php?file_id=2246&type=bug
    Notes
    (0013279)
    openBrain   
    2019-06-20 16:34   
    @dhka2 : thanks a lot for reporting with valuable information.
    However as requested in the bug reporting policy (in the giant yellow banner on top of this page, and in the "Read this before reporting" on the left), it is advised to first open a dedicated topic on the Help subforum. This will allow other forumers to confirm the issue and help finding the root cause. Once issue is eventually confirmed, forum thread & ticket can be crosslinked to ease bug fixing.
    Thanks
    (0013280)
    openBrain   
    2019-06-20 16:44   
    Looks to me as a duplicate of 0004003 thus of 0003379 as 'w' is unit symbol for Watt.
    @dhka2 : according previous tickets, it should work with "Sketch.Constraints.<<w>>". Could you please confirm ?
    (0013281)
    dhka2   
    2019-06-20 18:06   

    However as requested in the bug reporting policy (in the giant yellow banner on top of this page, and in the "Read this before reporting" on the left), it is advised to first open a dedicated topic on the Help subforum. This will allow other forumers to confirm the issue and help finding the root cause. Once issue is eventually confirmed, forum thread & ticket can be crosslinked to ease bug fixing.

    openBrain

    The forum sticky suggests a forum post is only necessary if it is unclear if encountered behaviour is a bug or a featureTM. "2. If you are unsure, discuss the problem on the forum first. ". As a segmentation fault is always a bug i thought it not necessary. If the intent is to always have a forum post before a bug report this is a documentation bug.

    Indeed this is related to 0004003 and 003379 however these bug reports do not state that a crash occurs. Indeed all reserved letters input into the expression window in this manner result in a crash.
    (0013282)
    openBrain   
    2019-06-20 19:08   

    The forum sticky suggests a forum post is only necessary if it is unclear if encountered behaviour is a bug or a featureTM. "2. If you are unsure, discuss the problem on the forum first. ". If the intent is to always have a forum post before a bug report this is a documentation bug.

    dhka2
    Indeed a forum post is always expected. The flow diagram of the bug submission guidelines topic is clear about it. And you can see in the posts following the OP that there is a discussion to clarify also that in the text. :)

    As a segmentation fault is always a bug i thought it not necessary.

    dhka2
    The reason for which a forum thread is asked is more than a bug can have external reason or specificity (OS, libraries, hardware, ...). This is what we try to identify in the forum so the ticket is as precise as possible. ;)

    Just ways to improve your next bug reporting. ;)
    (0013317)
    Kunda1   
    2019-06-28 10:47   
    @eivindkvedalen care to take a look at this ?
    (0013853)
    ezzieyguywuf   
    2019-12-01 04:52   
    I'm struggling to reproduce this: what is the "expression button" referenced in step 6?
    (0013854)
    Kunda1   
    2019-12-01 05:44   
    @ezzieyguywuf
    I believe it's this: https://www.freecadweb.org/wiki/File:Sketcher_Expressions.png
    (0014611)
    mikeprice99   
    2020-07-02 11:54   
    (Last edited: 2020-07-02 12:01)
    Just a few observations:
    1/ A vertical constraint does not take a parameter, so no expression button is available. Did you mean vertical distance constraint?
    2/ 'Sketch' in your sample file does not include a constraint called 'w' (Did you mean Spreadsheet.w )?
    3/ If I use a vertical distance constraint and enter the value Sketch002.Constraints.Nw (which does exist!) it works.

    So I guess either
    a) the bug does not affect Windows
    b) it has been fixed since revision 18336
    c) it is particular to branch makepkg


    My test environment:
    OS: Windows 10 (10.0)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.21769 (Git)
    Build type: Release
    Branch: master
    Hash: 801bfe4ba5f0910e9b2885917c521ab7fd8e9020
    Python version: 3.6.8
    Qt version: 5.12.1
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/United Kingdom (en_GB)
    (0016784)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5950.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3981 [Expressions] Feature minor always 2019-05-19 05:42 2021-02-06 06:30
    Reporter: chrisb Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Add Expression support to certain fields
    Description: Some fields do not support expressions, see the forum discussion.
    It would be natural to support them too.

    Added: The ratio in snells law constraint should be added to the list, see https://forum.freecadweb.org/viewtopic.php?p=331817#p331817
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0013116)
    uwestoehr   
    2019-05-19 15:55   
    The missing expressions lead actually to bugs, take for example the case I described here: https://forum.freecadweb.org/viewtopic.php?f=3&t=36458#p308966
    (0014255)
    uwestoehr   
    2020-03-21 04:17   
    The PartDesign primitives dialog edits get expressions by this PR: https://github.com/FreeCAD/FreeCAD/pull/3225
    (0016767)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5933.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3839 [Expressions] Feature minor have not tried 2019-02-15 15:32 2021-02-06 06:30
    Reporter: wmayer Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Support to update sketch when changing values in a spreadsheet
    Description: Support to update sketch when changing values in a spreadsheet. It would be nice to at least activate the Refresh button so that the sketch can be updated manually.
    Tags:
    Steps To Reproduce:
    Additional Information: https://forum.freecadweb.org/viewtopic.php?f=13&t=33614&sid=f6023ab75ecaa26377d3e1472d50cd9c
    Attached Files:
    Notes
    (0016718)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5883.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3696 [Expressions] General major always 2018-11-16 19:01 2021-02-06 06:30
    Reporter: TheRainHarvester Platform: win  
    Assigned To: OS: 8.1  
    Priority: normal OS Version: pro  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Constraints lose values upon reloading file.
    Description: When you use the "formula button" when typing in a constraint, it works only if you don't reload the file! When reloading, the constraint reverts to the value that was saved. It doesn't follow the formula anymore, so if you change a parameter, the linked constraint does not get updated.
    Tags:
    Steps To Reproduce: Open the attached file. Open the Sketcher window.
    Notice the 44mm dimention to the VERY right. it has the label "Global".
    Notice the 44 mm dimension next to it (just left). We'll call this "LinkedVersion". I saved it's formula's constraint as "Constraints.Global" but when you load the program, it gets set to the 44mm value.

    You can repeat the bug by updating the "LinkedVersion" constraint by clicking the blue formula icon and typing "Constraints.Global".

    Now change the "Global" value (the length constraint to the VERY right).
    The "LinkedVersion" will update as it should.
    Now save the file. Close. And reload the file.

    Now change the "Global" value (the length constraint to the Very right).
    Notice that the "LinkedVersion" will not get updated!!

    This bug can hide itself and ruin CNC paths if one is not aware of the problem.
    Additional Information: OS: Windows 8.1
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.15214 (Git)
    Build type: Release
    Branch: master
    Hash: b3721f8613b975be13e1801f499fa06f6f0ad836
    Python version: 2.7.14
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.2.0
    Locale: English/UnitedStates (en_US)
    Attached Files: BugLinkedConstraintsDontSurviveASave.FCStd (347,917 bytes) 2018-11-16 19:01
    https://tracker.freecad.org/file_download.php?file_id=2053&type=bug
    Notes
    (0012202)
    abdullah   
    2018-11-16 19:09   
    @Normandc
    @Kunda1

    Can somebody from the CAD experts check this case to confirm?
    (0012205)
    normandc   
    2018-11-17 16:40   
    IMO this should have been discussed in the forum first before a report was created; just as is already explained in the GIGANTIC yellow banner at the top.

    This file document has multiple user errors. One not pertaining to this issue is starting a sketch in a Body then going to Part to create an Extrude. This produces the following warning in the Report view after a recompute:

    Part::Extrusion: Links go out of the allowed scope
    

    One other thing hinting at an error is that at load time, the Report view prints the error "Failed to parse expression".

    Notice the 44 mm dimension next to it (just left). We'll call this "LinkedVersion".

    TheRainHarvester
    It is NOT called "LinkedVersion" in your file, its label is "Edge Vert 1 of 2". I highly doubt that spaces are allowed in contraint names. When I try to refer through it in an expression, it fails with "Failed to parse expression".

    This file is a very poor case for a bug, and should have been simplified to only contain the elements to reproduce the issue. The whole Path job is irrelevant here. BTW it is completely inefficient to create such a sketch with >225 constraints and repeated circles. Posting on the forum before creating this bug, you would have received this advice.

    I recommend that the next steps should be for the reporter to:
    1. Register to the forum and create a topic to discuss the issue.
    2. Following discussion and insight from forum regulars, provide a streamlined FreeCAD document that follows recommended practice, uses proper labels and still reproduces the issue.
    (0012206)
    normandc   
    2018-11-17 16:41   
    (Last edited: 2018-11-17 16:42)
    As per comment above, please post on the forum for advice. There may be usage errors that are actually resulting in the issue.

    (0012207)
    abdullah   
    2018-11-17 19:46   
    Thank you very much Normand. It saves me time when things are streamlined :)
    (0012224)
    TheRainHarvester   
    2018-11-26 15:20   
    I added a simple file and started a discussion at:
    https://forum.freecadweb.org/viewtopic.php?f=8&t=32437
    (0012226)
    abdullah   
    2018-11-27 14:28   
    Thank you everybody for taking the time to streamline this.

    I have moved this ticket to "Expressions", as the problem lies in the Expression Engine. It is not specific to the Sketcher.

    Almost 40 years after the boom of the personal computer, spaces keep being a problem...
    (0012765)
    Kunda1   
    2019-02-25 13:35   
    @eivindkvedalen care to take a look at this?
    (0016672)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5837.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3487 [Expressions] Feature feature N/A 2018-05-18 17:10 2021-02-06 06:30
    Reporter: clarkitect Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Add ability to copy objects with expressions linked to spreadsheet
    Description: As discussed in this thread https://forum.freecadweb.org/viewtopic.php?p=232149&sid=592cce21db486df260e6f8e1b91b2edc#p232149

    When copying objects that have expressions using an alias controlled by a spreadsheet, the copies always reference the original spreadsheet. There is no way to deep copy and point the expressions to the new, copied spreadsheet. Users should be given the choice whether expressions point to original, or copied spreadsheet.
    Tags: expressions
    Steps To Reproduce: Files and further detailed description are in the forum thread.
    Additional Information: OS: Mac OS X
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.13450 (Git)
    Build type: Release
    Branch: (HEAD detached at 129e2f7)
    Hash: 129e2f7a1b55c91880f2db2da264746acdc14d38
    Python version: 2.7.14
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.1.0
    Locale: English/UnitedKingdom (en_GB)
    Attached Files:
    Notes
    (0016626)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5791.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3466 [Expressions] Feature feature N/A 2018-05-08 14:52 2021-02-06 06:30
    Reporter: silopolis Platform: Intel x86_64  
    Assigned To: OS: Debian 9 "Stretch" Linux  
    Priority: normal OS Version: 4.9  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Control objects visibility via expressions and spreadsheets cells
    Description: Feature would allow to control object visibility via expressions and/or spreadsheets cells returning 0/1 or True/False.
    Tags: expressions
    Steps To Reproduce:
    Additional Information: This would be valuable in many cases as witnessed by users interest in the following threads:
    * https://forum.freecadweb.org/viewtopic.php?f=3&t=18681
    * https://forum.freecadweb.org/viewtopic.php?f=10&t=18065

    AFAIC, in a woodworker/cabinetmaker use case, this feature would make my base parametric parts, cabinets/furnitures, assemblies much more powerful:
    * cabinets with/without shelves/separations,...
    * panels with/without edge banding, face veneering

    For BoM/cutlist generation, an "Enabled" boolean property (even a "dumb" one) would be further empowering by allowing to manage visibility and "existence" independently.

    System Description
    Attached Files:
    Notes
    (0016624)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5789.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3448 [Expressions] Bug minor always 2018-04-29 20:06 2021-02-06 06:30
    Reporter: JCR84J Platform: Microsoft  
    Assigned To: eivindkvedalen OS: Windows 10  
    Priority: normal OS Version: 1709  
    Status: assigned Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Failed to parse expression
    Description: refer to Forum post with subject:
    "Failed to parse expression on opening a file"
    https://forum.freecadweb.org/viewtopic.php?f=3&t=28431

    Bug referred on demand of :

    In my opinion this is a bug, so please register it in the tracker and reference this thread.

    Eivind
    Tags:
    Steps To Reproduce: Full Description, details and file are in Forum post with subject:

    "Failed to parse expression on opening a file"
    https://forum.freecadweb.org/viewtopic.php?f=3&t=28431

    Don't hesitate to ask to forum member JCR84J if any difficulty.
    Additional Information:
    Attached Files:
    Notes
    (0013855)
    ezzieyguywuf   
    2019-12-03 01:30   
    This is a duplicate of 3272. Please see my discussion on this post in the forum.

    Specifically, (and quoting from that thread):


    the issue, therefore, is not specific to the Spreadsheet module, but rather in one of:

        

    1. The Sketcher Module (perhaps it should not allow spaces in the names of constraints)
    2. The ExpressionParser itself (should a valid Path be allowed to have a space in it?)
    3. (maybe) App::ObjectIdentifier - should not allow spaces in path

    ezzieyguywuf
    (0016621)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5786.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3391 [Expressions] Bug minor always 2018-03-24 10:28 2021-02-06 06:30
    Reporter: eivindkvedalen Platform:  
    Assigned To: realthunder OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Array and dictionary lookup does not work in expressions
    Description: See discussion on https://forum.freecadweb.org/viewtopic.php?f=3&t=26876#p214826
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0013858)
    ezzieyguywuf   
    2019-12-03 04:29   
    Is this a bug or a feature request?

    As discussed in this post, it sounds like there is a true security bug related to this, but I don't fully understand how to reproduce the issue that results in the security vulnerability.

    Can someone provide a step-by-step to reproduce the fix posted by triplus here, and describe how this leads to the security issue mentioned by elvind?
    (0014178)
    Kunda1   
    2020-02-23 19:53   
    @realthunder pardon, just wondering if your pending FreeCAD Pull Request 3062 addresses this ?
    (0014179)
    realthunder   
    2020-02-23 21:47   
    Yes, the PR addressed this. And it shall have completion support for that. And no, there won't be any security concern as mentioned in the referenced post, because I have already modified Expression/ObjectIdentifier to not use the Python interpreter.
    (0014180)
    Kunda1   
    2020-02-23 23:03   
    (Last edited: 2020-02-23 23:05)
    @realthunder wow, that's awesome news! There are other expression/spreadsheet issues here on the tracker. I wonder, and I want to be mindful of your time, if we can go through them and see if your PR also addresses them ?

    Edit: If the PR does address and solve them, would it be possible to use the MantisBT wildcard triggers in the Git commit to remotely close said issues ?
    See https://www.freecadweb.org/wiki/Tracker#GitHub_and_MantisBT
    (0014182)
    realthunder   
    2020-02-24 01:53   
    I'll go through them when I get time. But some of them may be fixed already in upstream. I can't modify the commit message there. Would it be enough for me to just refer to the relevant commit in the issue comment?
    (0014187)
    realthunder   
    2020-02-27 05:56   
    Extended indexing support is added with this commit in upstream.
    (0016606)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5771.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3379 [Expressions] Bug crash always 2018-03-17 12:53 2021-02-06 06:30
    Reporter: chrisb Platform:  
    Assigned To: eivindkvedalen OS:  
    Priority: high OS Version:  
    Status: assigned Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Certain identifiers (like h, rad) cannot be used as names for constraints for usage in expressions
    Description: Certain identifiers like h, rad, ... cannot be used as names for constraints for usage in expressions
    A warning would help.
    Tags:
    Steps To Reproduce: Create a sketch. Give the name "h" to a constraint
    Use "h" in an expression like Sketch.Constraints.h
    Additional Information: Forum discussion
    Attached Files:
    Notes
    (0012465)
    Kunda1   
    2019-01-19 11:58   
    @eivindkvedalen quick question, this ticket is targeted for 0.18 will it in fact make it in to the 0.18 release ?
    (0013263)
    Kunda1   
    2019-06-19 20:33   
    Updated ticket name for better readability
    (0013264)
    openBrain   
    2019-06-19 22:12   
    Looks to me as if 0004003 is (technically speaking) a duplicate of this one.
    (0013318)
    Kunda1   
    2019-06-28 10:51   
    Duplicate 0004031 usecase actually crashes FC. Elevating the priority of this ticket
    (0016605)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5770.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3272 [Expressions] General major always 2017-11-27 01:32 2021-02-06 06:30
    Reporter: bgoodr Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Failed to parse expression occurs when referencing an alias in an external spreadsheet document
    Description: Version info:

    OS: Ubuntu 17.04
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.12643 (Git)
    Build type: None
    Branch: master
    Hash: 868d9cc6c215ce3a2ab20d454378ec00e1b9ed26
    Python version: 2.7.13
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.1.0
    Locale: English/UnitedStates (en_US)

    By "external" I mean a spreadsheet that is not a part of the FreeCAD document I am working on. I am choosing to use a separate master spreadsheet because I want that central spreadsheet to control dimensions in constraints used in sketches in multiple FreeCAD documents in the current working directory, such that when I update the values in the "master spreadsheet", the objects in the dependent FreeCAD documents are updated (well, right now they are not updated automatically, and I have to press a button in Assembly2, but that is off-topic from this bug).

    After working around the bug in 0003271 by manually opening the external spreadsheet file, the fx button does seem to show that it recognizes the syntax and even shows the value, but when I click ok to use that value, I get a "Failed to parse expression" error.

    Use the same attachments as in 0003271

    The GIF in 0003271 also shows this problem.
    Tags: expressions, spreadsheet
    Steps To Reproduce:
    1. Extract the tarball.
    2. cd into the directory that is extracted so that the current working directory can resolve paths to other files in the set of files.
    3. Open up the file: freecad-daily UpsideDownMonitorMount.fcstd
    4. Open up the Leg.fcstd file using the button.
    5. Open up the MasterSpreadshet.fcstd to work around the bug in 0003271
    6. Double click on the sketcher
    7. Double click on the constraint with 1.5yd ("Shelf Depth")
    8. Click on the fx button.
    9. Type in a reference to the alias that is in the spreadsheet: MasterSpreadsheet#Spreadsheet.Sd
    10. Notice it says Result: 12.00 " which is correct: the spreadsheet has 12in in the Sd alias
    11. Click Ok
    12. Notice the Length field also shows 12.00 " which is correct so far.
    13. Click Ok
    14. Now see a popup error with window title "Dimensional constraint" and "Failed to parse expression". There is also "Failed to parse expression" in the Report view.
    Additional Information:
    Attached Files:
    Notes
    (0010478)
    Kunda1   
    2017-11-27 12:05   
    per the workflow that we ask bug reporters (big yellow banner at the top of this page), please discuss this in the forum before you open a ticket. Nevertheless, since this report took time and effort, we can tackle it here.
    @chrisb care to weigh in?
    (0010552)
    Kunda1   
    2017-12-09 12:20   
    (Last edited: 2017-12-09 12:50)
    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=25797

    (0016585)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5750.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3255 [Expressions] Feature tweak N/A 2017-11-11 17:54 2021-02-06 06:30
    Reporter: reox Platform:  
    Assigned To: eivindkvedalen OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Use consistent angle measure for expressions
    Description: When inserting values into fields, radians are used for trigonometric functions.
    But in the expression window (f(x) button), grad are used.
    IMO Only the latter one is documented in the wiki: https://www.freecadweb.org/wiki/Expressions

    I think both fields should be unified for the angle measurement. For example both should use grad by default.
    Tags: expressions, UI
    Steps To Reproduce: See also images in the forum.

    in normal mode cos(30) gives 0.15 (30 as radians)
    in expression mode cos(30) gives 0.87 (30 as grad)
    Additional Information: Discussion https://forum.freecadweb.org/viewtopic.php?f=3&t=25275
    Attached Files:
    Notes
    (0016582)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5747.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2766 [Expressions] Bug minor have not tried 2016-11-11 09:23 2021-02-06 06:30
    Reporter: FFW Platform: x86-64  
    Assigned To: eivindkvedalen OS: Linux Debian  
    Priority: normal OS Version: 4.8.0-1-amd64  
    Status: assigned Product Version: 0.16  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Expression link is cuting by creating new object
    Description: When using an expression linked to a certain object, creating another object with a close name cause the link to switch to this last created.
    Tags: expressions
    Steps To Reproduce: - Create a Part Design/Cube, named Cube by default
    - Create another object
    - Link a property of this object to Cube.Length
    - Create another Part Design/Cube, named Cube001 by default
    - Show the property of the object, it is now linked to Cube001.Length and break the model.
    Additional Information:
    Attached Files:
    Notes
    (0007447)
    wmayer   
    2016-11-11 12:23   
    Hint: this only happens with using the Label value of an object (Cube). When using its internal name (in this case "Box") it works correctly.

    The same problem still exists in 0.17.
    (0007452)
    eivindkvedalen   
    2016-11-13 21:55   
    This happens because the GUI tries to assign e.g 'Cube' to the second object when it is created. This in turn triggers a relabelObject signal, and the expression engine happily renames the expression when the GUI changes the label because duplicate labels are not allowed (before this happens there are two object with the label 'Cube'; this is why it can be renamed to Cube001; not sure why this is so predictable, though).

    Not sure how to fix this, because I also found another thing that probably should be looked into first: The "Allow duplicate label" handling is done in the Gui part of FreeCAD. Shouldn't this really be in the App part?
    (0007453)
    wmayer   
    2016-11-14 17:53   
    > Shouldn't this really be in the App part?
    True, since ObjectLabelObserver anyway only accesses App stuff this class could be moved to FreeCADApp.
    (0010291)
    wmayer   
    2017-10-11 12:52   
    See also:
    https://forum.freecadweb.org/viewtopic.php?f=10&t=24839&p=195041
    https://forum.freecadweb.org/viewtopic.php?f=10&t=24595&p=194633#p194633
    (0016507)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5672.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2477 [Expressions] Bug minor always 2016-03-15 17:40 2021-02-06 06:30
    Reporter: Hastux Platform: Linux  
    Assigned To: realthunder OS: Ubuntu  
    Priority: normal OS Version: 15.10  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Copy of sub objects with expression pointing to a spreadsheet shall not create a new spreadsheet
    Description: Version: 0.16
    Revision: 6621 (Git)
    System: Ubuntu with ppa/daily

    When copying an object with expression linked to a spreadsheet (containing alias as variables), the dialog box ask to copy or not linked objects. When we answer yes, it copies the objects, and also create a new spreadsheet. The original object is pointing to the new spreadsheet and the new one to the original spreadsheet. It is not clearly a bug, because all is copied as asked, but it is really annoying to change all expression to point to a single spreadsheet.

    Proposition: ask to not copy or not the spreadsheet when a link between an expression and a spreadsheet is detected

    PS: A great thanks to all of you, working in the shadow, this software is better and better
    Tags: expressions, spreadsheet
    Steps To Reproduce: -Create a spreadsheet ('var') with an alias ('x') pointing to a value
    -Create an object an set and expression pointing to this alias (length = var.x)
    -Create an array of this object
    -Copy the array and answer yes to copy dependencies
    Additional Information:
    Attached Files:
    Notes
    (0009824)
    eivindkvedalen   
    2017-07-26 09:52   
    I'm not able to recreate this problem in 0.16r6706. I get the objects duplicated, but no dependencies are created to the new spreadsheet, so this can easily be removed afterwards.
    (0009826)
    Kunda1   
    2017-07-26 10:59   
    @eivindkvedalen FYI, the latest stable 0.16 is revision 6712
    (0010408)
    Kunda1   
    2017-11-10 16:57   
    @eivindkvedalen can this issue be closed ?
    (0010409)
    eivindkvedalen   
    2017-11-11 09:12   
    No, I see room for improvement on this one, so we shouldn't close it.
    (0012236)
    Sergei Kulik   
    2018-12-04 00:15   
    I confirm this issue as described is present on 0.18.15316_x64_dev_win. Let me know if you need a detailed scenario or project.
    (0014189)
    realthunder   
    2020-02-27 08:59   
    After this commit in upstream, a dialog will popup when the user copies any object with dependency. User has full control on which dependencies to copy.

    The commit is huge as it is done during the big merge. The object selection is done with DlgObjectSelection. Just search the source tree for usage of this class.

    In addition, with this commit (inside a pending PR), the expression can auto change its reference to/from internal/external reference depending on whether the referenced object is copied to the external document or not.

    For example, assuming there is a spreadsheet referencing a sketch in the same document (DocA) as 'Sketch.Constraints.myConstraint'. And now if the spreadsheet is copied into an external document, but the referenced sketch object is not copied together. The expression will be auto changed to 'DocA#Sketch.Constraints.myConstraint'.
    (0016482)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5647.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2467 [Expressions] Bug major always 2016-03-07 23:54 2021-02-06 06:30
    Reporter: eivindkvedalen Platform:  
    Assigned To: eivindkvedalen OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.16  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Expression auto-completer slows down FreeCAD
    Description: When working with documents with a large number of objects, it takes a very long time to build the internal data structure for the auto-completer when an expression input field is used.
    Tags: expressions, slow
    Steps To Reproduce:
    Additional Information: See http://forum.freecadweb.org/viewtopic.php?f=8&t=11557&start=100#p116315 for suggested solution.
    Attached Files:
    Notes
    (0006906)
    wmayer   
    2016-03-13 13:48   
    See also comment on: http://forum.freecadweb.org/viewtopic.php?f=8&t=11557&start=160#p117650
    (0010248)
    Kunda1   
    2017-10-05 15:44   
    @eivindkvedalen is it the same thing for 0.17
    (0010632)
    Kunda1   
    2017-12-29 18:18   
    Another thread referencing this issue: https://forum.freecadweb.org/viewtopic.php?f=3&t=22232
    (0013857)
    ezzieyguywuf   
    2019-12-03 04:09   
    Can someone please provide a sample file, or a step-by-step procedure for reproducing this issue?
    (0014190)
    realthunder   
    2020-02-28 06:15   
    The expression completer has been refactored by this commit in upstream for performance improvement.

    It has since been refactored again in this PR for more functionalities but with the same performance improvement. There is no noticeable delay for completion with 1000+ objects.
    (0016479)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5644.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3354 [Draft] Bug minor always 2018-02-25 09:10 2021-02-06 06:29
    Reporter: abdullah Platform:  
    Assigned To: yorik OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Draft Clone does not maintain the colours of the original
    Description: I am not sure how difficult is this to handle as it is in the Python realm, but it would be great if the original colors where maintained.
    Tags: colors
    Steps To Reproduce: 1. Make a part of your choice.
    2. Colour it using the "Shape Color" property.
    3. Make a clone of it.

    The result is with the default system color (grey).
    Additional Information:
    Attached Files:
    Notes
    (0011392)
    gift   
    2018-06-10 08:47   
    (Last edited: 2018-06-10 13:38)
    Hello @abdullah,

    The provider copy the color. So it is not a Draft topic rather PartDesign. I don't know it good enough in the part design next source and I can't find the pdn provider. We must implement this Darft source code in PartDesign:

    class _ViewProviderClone:
        "a view provider that displays a Clone icon instead of a Draft icon"
    
        def __init__(self,vobj):
            vobj.Proxy = self
    
        def getIcon(self):
            return ":/icons/Draft_Clone.svg"
    
        def __getstate__(self):
            return None
    
        def __setstate__(self, state):
            return None
    
        def getDisplayModes(self, vobj):
            modes=[]
            return modes
    
        def setDisplayMode(self, mode):
            return mode
    
        def resetColors(self, vobj):
            colors = []
            for o in getGroupContents(vobj.Object.Objects):
                if o.isDerivedFrom("Part::Feature"):
                    if len(o.ViewObject.DiffuseColor) > 1:
                        colors.extend(o.ViewObject.DiffuseColor)
                    else:
                        c = o.ViewObject.ShapeColor
                        c = (c[0],c[1],c[2],o.ViewObject.Transparency/100.0)
                        for f in o.Shape.Faces:
                            colors.append(c)
                elif o.hasExtension("App::GeoFeatureGroupExtension"):
                    for so in vobj.Object.Group:
                        if so.isDerivedFrom("Part::Feature"):
                            if len(so.ViewObject.DiffuseColor) > 1:
                                colors.extend(so.ViewObject.DiffuseColor)
                            else:
                                c = so.ViewObject.ShapeColor
                                c = (c[0],c[1],c[2],so.ViewObject.Transparency/100.0)
                                for f in so.Shape.Faces:
                                    colors.append(c)
            if colors:
                vobj.DiffuseColor = colors
    

    (0011403)
    gift   
    2018-06-11 18:56   
    Using grep I found that the clone is small solution in pdn(src/Mod/PartDesign/Gui/Command.cpp). Look on commit: 600b736 Please keep in mind that not included a update service of color analogy to the placement.
    (0012644)
    yorik   
    2019-02-15 00:00   
    Just add a look at this one, indeed by cloning an App::Part the clone doesn't take the individual face colors. But, it's not possible to set individual face colors to an App::Part. Only to its child objects. If you clone the child objects, it works correctly.

    So the App::Part doesn't know of individual face colors. Should the clone go through the different children to make up the colors? Not realy sure that would be the proper way... Isn't the App::Part that should hold a colors list instead?
    (0016600)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5765.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4145 [Assembly] Bug major always 2019-09-25 16:37 2021-02-06 06:29
    Reporter: efferre79 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: build failure with assembly module enabled
    Description: when building freecad I get the following error related to the Assembly module:

    [ 95%] Building CXX object src/Mod/TechDraw/Gui/CMakeFiles/TechDrawGui.dir/ViewProviderSymbol.cpp.o
    cd /var/tmp/portage/media-gfx/freecad-9999/work/freecad-9999_build/src/Mod/TechDraw/Gui && /usr/bin/ccache /usr/bin/x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H
     -DHAVE_LIMITS_H -DMOD_TECHDRAW_HANDLE_FACES=1 -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_PRINTSUPPORT_LIB -DQT_SVG_LIB
     -DQT_UITOOLS_LIB -DQT_WIDGETS_LIB -DQT_XMLPATTERNS_LIB -DQT_XML_LIB -DTechDrawGui_EXPORTS -D_OCC64 -I/var/tmp/portage/media-gfx/freecad-9999/work/freecad-
    9999_build -I/var/tmp/portage/media-gfx/freecad-9999/work/freecad-9999_build/src -I/var/tmp/portage/media-gfx/freecad-9999/work/freecad-9999/src -I/var/tmp
    /portage/media-gfx/freecad-9999/work/freecad-9999_build/src/Mod/TechDraw/Gui -I/var/tmp/portage/media-gfx/freecad-9999/work/freecad-9999/src/Mod/TechDraw/G
    ui -I/usr/include/coin -I/usr/include/python2.7 -I/usr/lib64/opencascade-7.3.0/ros/lin/inc -isystem /usr/include/qt5 -isystem /usr/include/qt5/QtXmlPattern
    s -isystem /usr/include/qt5/QtNetwork -isystem /usr/include/qt5/QtCore -isystem /usr/lib64/qt5/mkspecs/linux-g++ -isystem /usr/include/qt5/QtXml -isystem /
    usr/include/qt5/QtWidgets -isystem /usr/include/qt5/QtGui -isystem /usr/include/qt5/QtOpenGL -isystem /usr/include/qt5/QtPrintSupport -isystem /usr/include
    /qt5/QtSvg -isystem /usr/include/qt5/QtUiTools -DNDEBUG -Wall -Wextra -Wno-write-strings -march=core2 -O2 -pipe -ggdb -fPIC -fPIC -std=gnu++11 -o CMake
    Files/TechDrawGui.dir/ViewProviderSymbol.cpp.o -c /var/tmp/portage/media-gfx/freecad-9999/work/freecad-9999/src/Mod/TechDraw/Gui/ViewProviderSymbol.cpp
    /var/tmp/portage/media-gfx/freecad-9999/work/freecad-9999/src/Mod/Assembly/Gui/ViewProviderConstraint.cpp: In member function ‘void AssemblyGui::ViewProvid
    erConstraintInternal::updateVis(const TopoDS_Shape&)’:
    /var/tmp/portage/media-gfx/freecad-9999/work/freecad-9999/src/Mod/Assembly/Gui/ViewProviderConstraint.cpp:85:23: error: no matching function for call to ‘A
    ssemblyGui::ViewProviderConstraintInternal::updateVisual(const TopoDS_Shape&)’
         updateVisual(shape);
                           ^
    In file included from /var/tmp/portage/media-gfx/freecad-9999/work/freecad-9999/src/Mod/Part/Gui/ViewProvider.h:28,
                     from /var/tmp/portage/media-gfx/freecad-9999/work/freecad-9999/src/Mod/Assembly/Gui/ViewProviderConstraint.h:27,
                     from /var/tmp/portage/media-gfx/freecad-9999/work/freecad-9999/src/Mod/Assembly/Gui/ViewProviderConstraint.cpp:24:
    /var/tmp/portage/media-gfx/freecad-9999/work/freecad-9999/src/Mod/Part/Gui/ViewProviderExt.h:150:10: note: candidate: ‘void PartGui::ViewProviderPartExt::u
    pdateVisual()’
         void updateVisual();
              ^~~~~~~~~~~~
    /var/tmp/portage/media-gfx/freecad-9999/work/freecad-9999/src/Mod/Part/Gui/ViewProviderExt.h:150:10: note: candidate expects 0 arguments, 1 provided
    /var/tmp/portage/media-gfx/freecad-9999/work/freecad-9999/src/Mod/Assembly/Gui/ViewProviderConstraint.cpp: In member function ‘virtual void AssemblyGui::Vi
    ewProviderConstraint::setDisplayMode(const char*)’:
    /var/tmp/portage/media-gfx/freecad-9999/work/freecad-9999/src/Mod/Assembly/Gui/ViewProviderConstraint.cpp:110:57: warning: unused parameter ‘ModeName’ [-Wu
    nused-parameter]
     void ViewProviderConstraint::setDisplayMode(const char* ModeName)
                                                 ~~~~~~~~~~~~^~~~~~~~
    /var/tmp/portage/media-gfx/freecad-9999/work/freecad-9999/src/Mod/Assembly/Gui/ViewProviderConstraint.cpp: In member function ‘void AssemblyGui::ViewProvid
    erConstraint::draw()’:
    /var/tmp/portage/media-gfx/freecad-9999/work/freecad-9999/src/Mod/Assembly/Gui/ViewProviderConstraint.cpp:255:20: error: no matching function for call to ‘AssemblyGui::ViewProviderConstraint::updateVisual(TopoDS_Shape&)’
         updateVisual(s1);
                        ^
    In file included from /var/tmp/portage/media-gfx/freecad-9999/work/freecad-9999/src/Mod/Part/Gui/ViewProvider.h:28,
                     from /var/tmp/portage/media-gfx/freecad-9999/work/freecad-9999/src/Mod/Assembly/Gui/ViewProviderConstraint.h:27,
                     from /var/tmp/portage/media-gfx/freecad-9999/work/freecad-9999/src/Mod/Assembly/Gui/ViewProviderConstraint.cpp:24:
    /var/tmp/portage/media-gfx/freecad-9999/work/freecad-9999/src/Mod/Part/Gui/ViewProviderExt.h:150:10: note: candidate: ‘void PartGui::ViewProviderPartExt::updateVisual()’
         void updateVisual();
              ^~~~~~~~~~~~
    /var/tmp/portage/media-gfx/freecad-9999/work/freecad-9999/src/Mod/Part/Gui/ViewProviderExt.h:150:10: note: candidate expects 0 arguments, 1 provided
    /var/tmp/portage/media-gfx/freecad-9999/work/freecad-9999/src/Mod/Assembly/Gui/ViewProviderConstraint.cpp: In member function ‘virtual void AssemblyGui::ViewProviderConstraint::onSelectionChanged(const Gui::SelectionChanges&)’:
    /var/tmp/portage/media-gfx/freecad-9999/work/freecad-9999/src/Mod/Assembly/Gui/ViewProviderConstraint.cpp:336:78: warning: unused parameter ‘msg’ [-Wunused-parameter]
     void ViewProviderConstraint::onSelectionChanged(const Gui::SelectionChanges& msg)
                                                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~
    /var/tmp/portage/media-gfx/freecad-9999/work/freecad-9999/src/Mod/Assembly/Gui/ViewProviderConstraint.cpp: In member function ‘virtual TopoDS_Shape AssemblyGui::ViewProviderConstraint::getConstraintShape(int)’:
    /var/tmp/portage/media-gfx/freecad-9999/work/freecad-9999/src/Mod/Assembly/Gui/ViewProviderConstraint.cpp:353:61: warning: unused parameter ‘link’ [-Wunused-parameter]
     TopoDS_Shape ViewProviderConstraint::getConstraintShape(int link)
                                                             ~~~~^~~~
    /var/tmp/portage/media-gfx/freecad-9999/work/freecad-9999/src/Mod/Assembly/Gui/ViewProviderConstraint.cpp: In member function ‘virtual bool AssemblyGui::ViewProviderConstraint::setEdit(int)’:
    /var/tmp/portage/media-gfx/freecad-9999/work/freecad-9999/src/Mod/Assembly/Gui/ViewProviderConstraint.cpp:416:42: warning: unused parameter ‘ModNum’ [-Wunused-parameter]
     bool ViewProviderConstraint::setEdit(int ModNum)
                                          ~~~~^~~~~~
    /var/tmp/portage/media-gfx/freecad-9999/work/freecad-9999/src/Mod/Assembly/Gui/ViewProviderConstraint.cpp: In member function ‘virtual void AssemblyGui::ViewProviderConstraint::unsetEdit(int)’:
    /var/tmp/portage/media-gfx/freecad-9999/work/freecad-9999/src/Mod/Assembly/Gui/ViewProviderConstraint.cpp:440:44: warning: unused parameter ‘ModNum’ [-Wunused-parameter]
     void ViewProviderConstraint::unsetEdit(int ModNum)
                                            ~~~~^~~~~~
    make[2]: *** [src/Mod/Assembly/Gui/CMakeFiles/AssemblyGui.dir/build.make:182: src/Mod/Assembly/Gui/CMakeFiles/AssemblyGui.dir/ViewProviderConstraint.cpp.o] Error 1
    make[2]: Leaving directory '/var/tmp/portage/media-gfx/freecad-9999/work/freecad-9999_build'
    make[1]: *** [CMakeFiles/Makefile2:4735: src/Mod/Assembly/Gui/CMakeFiles/AssemblyGui.dir/all] Error 2
    make[1]: *** Waiting for unfinished jobs....


    If the assembly module is deprecated probably it's better to remove it from the tree to avoid such kind of problems or by making it impossible to enable during configuration time.
    Tags: #pending-forum
    Steps To Reproduce: compile freecad below linux by enabling Assembly module with the cmake option -DBUILD_ASSEMBLY=ON
    Additional Information: I am using latest version from github repository

    OS: Gentoo/Linux
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.16776 (Git)
    Build type: Release
    Branch: (HEAD detached at refs/git-r3/HEAD)
    Hash: b547373f35c3fd2a12fca5035af575c835062056
    Python version: 2.7.15
    Qt version: 5.11.3
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/United Kingdom (en_GB)


    Attached Files:
    Notes
    (0013687)
    Kunda1   
    2019-09-26 17:03   
    Please post this ticket to the forums. Especially because it's a build issue and we don't know what dependency version your distro is using. Also, please follow our tracker guidelines (large yellow banner at the top of the page) Thank you.
    (0013698)
    efferre79   
    2019-09-30 09:56   
    probably the build failure is related to this commit in master (6da72b9859f6d21119831d44a8d132c8e2dfb544), it seems that not all lines of code in freecad have been updated accordingly

    here is the forum thread
    (0014051)
    Kunda1   
    2020-01-11 13:07   
    workaround ? https://forum.freecadweb.org/viewtopic.php?f=4&t=39716&p=359686#p356015
    (0016827)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5993.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2076 [Assembly] General minor have not tried 2015-05-01 00:49 2021-02-06 06:29
    Reporter: tanderson69 Platform: amd64  
    Assigned To: OS: Kubuntu  
    Priority: normal OS Version: 14.10  
    Status: new Product Version: 0.16  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Assembly Merge: remove automatic App::Part functionality
    Description: http://forum.freecadweb.org/viewtopic.php?f=20&t=10735
    Tags:
    Steps To Reproduce:
    Additional Information:
    System Description OS: Ubuntu 14.10
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.15.4427 +22 (Git)
    Branch: *
    Hash: *
    Python version: 2.7.8
    Qt version: 4.8.6
    Coin version: 4.0.0a
    OCC version: 6.8.0.oce-0.17-dev
    Attached Files:
    Notes
    (0006106)
    ickby   
    2015-05-01 13:47   
    Sorry for the assignment confusion, I did try to add it to the assembly project but did not succeed
    (0006113)
    ickby   
    2015-05-03 11:22   
    As jriegel started work again I think it would be useful to first make everything work again with the App::Part object. Then we can decide if we merge completely or without the App::Part, dependend of the overall state.
    (0007650)
    Kunda1   
    2017-01-11 20:44   
    This ticket labeled 'assigned' but it isn't assigned to anybody? @wmayer please advise
    (0007656)
    wmayer   
    2017-01-11 21:30   
    ickby by accident assigned it to him but wanted to move it to the Assembly project. So, I set back the status to "New".
    (0016460)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5625.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1176 [Assembly] Feature feature N/A 2013-07-12 17:14 2021-02-06 06:29
    Reporter: project4 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.13  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Add visual indication when long tasks are performed
    Description: I think there is a need to add a visual indication when something long is done by the program (like recalculation of the whole object for example).

    An icon in the status bar of the main window might be a good idea.

    I didn't try to work with really complex designs yet, but was experiencing some lags already...
    An indication might be a bonus to the user experience.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0003393)
    wmayer   
    2013-07-12 19:49   
    For many operations where the number of steps is known we show a progress bar (heavily used e.g. in the Mesh module).

    With OCC this is hardly possible because the algorithms there doesn't support a progress bar. The only exception I know of is the STEP/IGES importer.

    As long as you don't need an animated icon this should be no problem. Otherwise all the used OCC algorithms need to be moved into worker threads.
    (0003395)
    project4   
    2013-07-13 05:09   
    I don't know what OCC means, but I think if it's a long algorithm, it should be run apart from the GUI processing.
    This way it might be easier to break the process into multi-thread implementation when needed, which might speed up the whole thing alot for complex parts.

    My thought was to add a simple icon that changes the color when something is processing... a flashing one might be even better.
    Showing a progress bar when possible is even better.
    (0003397)
    wmayer   
    2013-07-13 08:02   
    OCC is the abbreviation for OpenCascade -- the CAD kernel. Unfortunately, most of the algorithms in OCC can't be multi-threaded because internally many global variables are used and thus makes it impossible in many situations to work with more than one thread.

    Furthermore, threads should only be used if it's known that the operations will take a long time because spawning a thread is an expensive operation and thus should be avoided for fast operations which will take e.g. less the 1-2 sec.

    A flashing icon is an absolutely no-go IMHO. Then I prefer something more decent like for example the animated icon of Firefox that appears when loading a heavy web page.
    (0003399)
    project4   
    2013-07-13 08:42   
    We are talking about the same thing... Animated icon showing a progress is a very good solution.

    Thanks for OCC explanation.
    If it's a separate project, than someone might optimize it one day...
    (0007604)
    clel   
    2017-01-10 15:28   
    If this is still relevant - another possibility would be to show a small bar moving from side to side or cycling through the progress bar.
    (0011414)
    Kunda1   
    2018-06-12 19:36   
    An example of a progress bar in an FC macro can be seen in https://forum.freecadweb.org/viewtopic.php?f=22&t=28831&p=238026#p238391
    (0011865)
    Kunda1   
    2018-09-28 00:13   
    Also in the Lithophane WB: https://github.com/furti/FreeCAD-Lithophane/commit/3446e5038977c53021ead4571f8a408797ea1cae
    (0016401)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5566.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    83 [Assembly] Feature minor have not tried 2010-04-07 10:51 2021-02-06 06:29
    Reporter: Jriegel Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: acknowledged Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Assembly group feature
    Description: Compound creating feature in the Assembly module.

    Create a compound shape of all the linked childes.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0001381)
    nonlimited   
    2011-12-01 19:08   
    (Last edited: 2011-12-01 19:12)
    does this mean something like children of a group do have a coordinate system relative to the group's system? So that you could rotate or translate a group's system and all children will stay relative to it?

    Using the boolean Fusion is a little less powerfull for this action as it is virtually not possible to add more objects after creating the fusion and on top of this colors and stuff will not be adopted.

    (0011426)
    Kunda1   
    2018-06-13 13:28   
    Unassigning Jriegel
    (0016376)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5541.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    16 [Assembly] Feature minor have not tried 2009-09-28 15:40 2021-02-06 06:29
    Reporter: Jriegel Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: acknowledged Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Basic Assembly stuff
    Description: Basic function in the assembly module like:

    Moving parts around
    simple constraints like:
    * contact
    * axle
    * offset

    There for we need the Navigator and usage of the ODE lib
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0003707)
    mntc   
    2013-10-01 18:15   
    May be assembly constraints can be:

    a) scriptable (One can rewrite standard primitive constraints by complex python script determining behaviour of constrained objects)
    b) hierarhical (In Autodesk Inventor parts in subassemblies are frozen when we open assembly of higher order. It is sometimes useful, sometimes not. It could be good to switch between styles of assembly behaviour inside of a superassembly.)
    c) built into special objects (may be instead of adding constraints, we should add special objects - bearings, etc. E.g. like in Algodoo, where constraints are determined by nature of objects.)
    (0004689)
    Pauvres_honteux   
    2014-05-18 07:26   
    (Last edited: 2014-05-18 20:02)
    Hi Jürgen, would it be too bold to ask for a more elaborate explanation/overview of what you want to accomplish with this assembly feature?
    I got a picture in my head, when I read the headline, of something similar to what you have in the big french program. Or do you have bolder ideas in mind?

    Regards Pauvres honteux.

    (0011427)
    Kunda1   
    2018-06-13 13:28   
    Unassigning Jriegel
    (0016373)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5538.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4548 [Arch] Bug minor have not tried 2021-01-31 18:08 2021-02-06 06:28
    Reporter: balrobs Platform:  
    Assigned To: paullee OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Ubuntu 20.04.2 LTS (ubuntu:GNOME/ubuntu)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.
    Build type: Release
    Branch: unknown
    Hash: 497ecbe0eb399dd2b873762e4406aa9569976870
    Python version: 3.8.5
    Qt version: 5.12.8
    Coin version: 4.0.0
    OCC version: 7.3.0
    Locale: English/United States (en_US)
    Summary: Arch:Stair - Connection issue between landing and second flight
    Description: ATM using the Arch stair tool to create a HalfTurnLeft/HalfTurnRight stair with a single line as base element leads to a connection result between the landing and the seconf flight that can be improved!
    See forum discussion with picture at https://forum.freecadweb.org/viewtopic.php?f=22&t=53018&start=30#p472079
    Tags:
    Steps To Reproduce: 1) model an Arch Stair by creating a single line with a length i.e. 4500mm
    2) change to the Arch workbench and select the line
    3) press the Arch Stair button to generate an Arch Stair
    4) in the Structure properties set Flight = HalfTurnLeft
    5) observe the connection between landing and second flight
    Additional Information:
    Attached Files:
    Notes
    (0015247)
    paullee   
    2021-01-31 18:32   
    Another similar issue discussed in same thread -

    2nd Issue in Post - RC stairs macro
    (0016986)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6154.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4516 [Arch] Bug minor have not tried 2020-12-19 14:30 2021-02-06 06:28
    Reporter: balrobs Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Ubuntu 20.04.1 LTS (ubuntu:GNOME/ubuntu)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.
    Build type: Release
    Branch: unknown
    Hash: 5cea165a6691a3dc7d0830510115fbf50b81ee00
    Python version: 3.8.5
    Qt version: 5.12.8
    Coin version: 4.0.0
    OCC version: 7.3.0
    Locale: English/United States (en_US)
    Summary: Arch Space, showing wrong "Line Spacing" in 3d-View
    Description: Changing the view-properties "First Line" or "Font Size" of an Arch Space object leads to correct text heights rappresentations but not to the correct "Line spacing" in the 3d-View. To achieve this it's neccessary to reset the view-property "Line spacing" too.
    See forum topic: https://forum.freecadweb.org/viewtopic.php?f=23&t=53364
    Tags:
    Steps To Reproduce:
    1. Create Arch Space with Arch WB
    2. Set Space view-properties to "First Line=200mm", "Font Size=200mm", "Line Spacing=1"
    3. 3d-View changes consequently
    4. Change Space view-properties to "First Line=400mm", "Font Size=400mm"
    5. 3d-View changes, but "Room label" and "Room area" are shown vertivally overlaped
    6. To correct the 3d-View the view-property "Line Spacing" must be changed e.g to another value then 1 and then reset to 1
    Additional Information: Expected behaviour: Changing view-properties "First Line" or "Font Size" without changing "Line Spacing" should be enough to get a correct rapresentation in the 3d-View.
    Attached Files:
    Notes
    (0016973)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6140.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4490 [Arch] Bug major always 2020-11-11 14:23 2021-02-06 06:28
    Reporter: Kunda1 Platform:  
    Assigned To: yorik OS:  
    Priority: high OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: v0.19
    Summary: Arch Fence broken due to Draft WB refactoring
    Description: Forum thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=51016#p438321

    @furti who coded Arch Fence is 'missing in action'.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0015002)
    yorik   
    2020-11-18 15:17   
    Will take a look...
    (0016961)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6128.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4418 [Arch] Bug minor always 2020-08-15 05:18 2021-02-06 06:28
    Reporter: brickmaker Platform: macOS  
    Assigned To: OS: Catalina  
    Priority: normal OS Version: 10.15.5  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: macOS 10.15
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.22246 (Git)
    Build type: Release
    Branch: master
    Hash: abd18ff88f7682e9b1160c36bb785b14a33473ef
    Python version: 3.8.5
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: C/Default (C)
    Summary: osx line width not getting wider
    Description: I have currently tried to draw a simple line in a couple different workbenches including Arch and Draft. My issue I am having is when I draw a line and I want to change the line width it can't get wider than 7px? I ran the same test on a Ubuntu computer I have and it was able to draw a line with a width bigger than 7px. Thank you for your help.

    Forum thread
    Tags:
    Steps To Reproduce: 1. click the create a 2 lines tool.
    2. Draw a straight line
    3. Make sure line is selected
    4. In toolbar try and increment the width of the line past 7px or on view tab click line width and increment it.
     
    Additional Information: Report View
    18:54:33 /Applications/FreeCAD.app/Contents/Resources/lib/python3.8/site-packages/mpmath/ctx_mp_python.py:892: SyntaxWarning: "is" with a literal. Did you mean "=="?
      if other is 0:
    18:54:33 /Applications/FreeCAD.app/Contents/Resources/lib/python3.8/site-packages/mpmath/ctx_mp_python.py:986: SyntaxWarning: "is" with a literal. Did you mean "=="?
      if other is 0:
    18:55:59 ----------------
    18:55:59 GuiCommand: Line
    18:55:59 Pick first point
    18:56:01 Pick next point
    22:43:10 ----------------
    22:43:10 GuiCommand: Toggle grid
    22:43:22 ----------------
    22:43:22 GuiCommand: Line
    22:43:22 Pick first point
    22:43:35 Pick next point

    Python Console
    Python 3.8.5 | packaged by conda-forge | (default, Jul 31 2020, 02:25:36)
    [Clang 10.0.1 ] on darwin
    Type 'help', 'copyright', 'credits' or 'license' for more information.
    >>> Gui.runCommand('Std_Workbench',20)
    >>> Gui.runCommand('Std_ViewStatusBar',1)
    >>> ### Begin command Std_Workbench
    >>> Gui.activateWorkbench("DraftWorkbench")
    >>> ### End command Std_Workbench
    >>> MRU="0"
    >>> exec(open('/Applications/FreeCAD.app/Contents/Resources/share/Mod/Start/StartPage/LoadMRU.py').read())
    >>> FreeCAD.openDocument('/Users/Mom and Dads house.FCStd')
    >>> # App.setActiveDocument("Mom_and_Dads_house")
    >>> # App.ActiveDocument=App.getDocument("Mom_and_Dads_house")
    >>> # Gui.ActiveDocument=Gui.getDocument("Mom_and_Dads_house")
    >>> Gui.runCommand('Std_OrthographicCamera',1)
    >>> Gui.runCommand('Draft_Line',0)
    >>> import Draft
    >>> pl = FreeCAD.Placement()
    >>> pl.Rotation.Q = (0.0, 0.0, 0.0, 1.0)
    >>> pl.Base = FreeCAD.Vector(0.0, 2.0, 0.0)
    >>> points = [FreeCAD.Vector(0.0, 2.0, 0.0), FreeCAD.Vector(10.0, 2.0, 0.0)]
    >>> line = Draft.makeWire(points, placement=pl, closed=False, face=True, support=None)
    >>> # Gui.Selection.addSelection('Mom_and_Dads_house','Line')
    >>> Draft.autogroup(line)
    >>> FreeCAD.ActiveDocument.recompute()
    >>> # Gui.Selection.clearSelection()
    >>> # Gui.Selection.addSelection('Mom_and_Dads_house','Line','Vertex2',10,2,0)
    >>> # Gui.Selection.clearSelection()
    >>> # Gui.Selection.addSelection('Mom_and_Dads_house','Line','Edge1',5.67005,2,0)
    >>> FreeCAD.getDocument('Mom_and_Dads_house').getObject('Line').Length = '25.4 mm'
    >>>
    >>> FreeCAD.getDocument('Mom_and_Dads_house').getObject('Line').Length = '7.62 mm'
    >>>
    >>> FreeCAD.getDocument('Mom_and_Dads_house').getObject('Line').Length = '8.89 mm'
    >>>
    >>> Gui.runCommand('Std_WhatsThis',0)
    >>> Gui.runCommand('Std_About',0)
    >>> # Gui.Selection.clearSelection()
    >>> # Gui.Selection.addSelection('Mom_and_Dads_house','Line','',1.91164,2,0)
    >>> ### Begin command Std_Workbench
    >>> Gui.activateWorkbench("ArchWorkbench")
    >>> ### End command Std_Workbench
    >>> FreeCADGui.getDocument('Mom_and_Dads_house').getObject('Line').LineWidth = 7.00
    >>>
    >>> FreeCADGui.getDocument('Mom_and_Dads_house').getObject('Line').LineWidth = 8.00
    >>>
    >>> FreeCADGui.getDocument('Mom_and_Dads_house').getObject('Line').LineWidth = 7.00
    >>>
    >>> FreeCADGui.getDocument('Mom_and_Dads_house').getObject('Line').LineWidth = 6.00
    >>>
    >>> FreeCADGui.getDocument('Mom_and_Dads_house').getObject('Line').LineWidth = 5.00
    >>>
    >>> FreeCADGui.getDocument('Mom_and_Dads_house').getObject('Line').LineWidth = 4.00
    >>>
    >>> FreeCADGui.getDocument('Mom_and_Dads_house').getObject('Line').LineWidth = 3.00
    >>>
    >>> FreeCADGui.getDocument('Mom_and_Dads_house').getObject('Line').LineWidth = 4.00
    >>>
    >>> FreeCADGui.getDocument('Mom_and_Dads_house').getObject('Line').LineWidth = 5.00
    >>>
    >>> FreeCADGui.getDocument('Mom_and_Dads_house').getObject('Line').LineWidth = 6.00
    >>>
    >>> FreeCADGui.getDocument('Mom_and_Dads_house').getObject('Line').LineWidth = 7.00
    >>>
    >>> FreeCADGui.getDocument('Mom_and_Dads_house').getObject('Line').LineWidth = 8.00
    >>>
    >>> FreeCADGui.getDocument('Mom_and_Dads_house').getObject('Line').LineWidth = 9.00
    >>>
    >>> FreeCADGui.getDocument('Mom_and_Dads_house').getObject('Line').LineWidth = 10.00
    >>>
    >>> FreeCADGui.getDocument('Mom_and_Dads_house').getObject('Line').LineWidth = 11.00
    >>>
    >>> FreeCADGui.getDocument('Mom_and_Dads_house').getObject('Line').LineWidth = 10.00
    >>>
    >>> FreeCADGui.getDocument('Mom_and_Dads_house').getObject('Line').LineWidth = 9.00
    >>>
    >>> FreeCADGui.getDocument('Mom_and_Dads_house').getObject('Line').LineWidth = 8.00
    >>>
    >>> FreeCADGui.getDocument('Mom_and_Dads_house').getObject('Line').LineWidth = 7.00
    >>>
    >>> FreeCADGui.getDocument('Mom_and_Dads_house').getObject('Line').LineWidth = 6.00
    >>>
    >>> FreeCADGui.getDocument('Mom_and_Dads_house').getObject('Line').LineWidth = 5.00
    >>>
    >>> FreeCADGui.getDocument('Mom_and_Dads_house').getObject('Line').LineWidth = 6.00
    >>>
    >>> FreeCADGui.getDocument('Mom_and_Dads_house').getObject('Line').LineWidth = 7.00
    >>>
    >>> FreeCADGui.getDocument('Mom_and_Dads_house').getObject('Line').LineWidth = 8.00
    >>>
    >>> FreeCADGui.getDocument('Mom_and_Dads_house').getObject('Line').LineWidth = 9.00
    >>>
    >>> FreeCADGui.getDocument('Mom_and_Dads_house').getObject('Line').LineWidth = 10.00
    >>>
    >>> FreeCADGui.getDocument('Mom_and_Dads_house').getObject('Line').LineWidth = 11.00
    >>>
    >>> FreeCADGui.getDocument('Mom_and_Dads_house').getObject('Line').LineWidth = 12.00
    >>>
    >>> FreeCADGui.getDocument('Mom_and_Dads_house').getObject('Line').LineWidth = 13.00
    >>>
    >>> # Gui.Selection.clearSelection()
    >>> # Gui.Selection.addSelection('Mom_and_Dads_house','Line')
    >>> # Gui.Selection.clearSelection()
    >>> # Gui.Selection.addSelection('Mom_and_Dads_house','Line')
    >>> Gui.runCommand('Std_DlgCustomize',0)
    >>> FreeCADGui.getDocument('Mom_and_Dads_house').getObject('Line').LineWidth = 7.00
    >>>
    >>> FreeCADGui.getDocument('Mom_and_Dads_house').getObject('Line').LineWidth = 6.00
    >>>
    >>> FreeCADGui.getDocument('Mom_and_Dads_house').getObject('Line').LineWidth = 9.00
    >>>
    >>> App.closeDocument("Mom_and_Dads_house")
    >>> # App.setActiveDocument("")
    >>> # App.ActiveDocument=None
    >>> # Gui.ActiveDocument=None
    >>> # Gui.Selection.clearSelection()
    >>> MRU="0"
    >>> exec(open('/Applications/FreeCAD.app/Contents/Resources/share/Mod/Start/StartPage/LoadMRU.py').read())
    >>> FreeCAD.openDocument('/Users/Mom and Dads house.FCStd')
    >>> # App.setActiveDocument("Mom_and_Dads_house")
    >>> # App.ActiveDocument=App.getDocument("Mom_and_Dads_house")
    >>> # Gui.ActiveDocument=Gui.getDocument("Mom_and_Dads_house")
    >>> Gui.runCommand("Draft_ToggleGrid")
    >>> Gui.runCommand('Draft_Line',0)
    >>> pl = FreeCAD.Placement()
    >>> pl.Rotation.Q = (0.0, 0.0, 0.0, 1.0)
    >>> pl.Base = FreeCAD.Vector(0.0, 10.0, 0.0)
    >>> points = [FreeCAD.Vector(0.0, 10.0, 0.0), FreeCAD.Vector(20.0, 10.0, 0.0)]
    >>> line = Draft.makeWire(points, placement=pl, closed=False, face=True, support=None)
    >>> # Gui.Selection.addSelection('Mom_and_Dads_house','Line')
    >>> Draft.autogroup(line)
    >>> FreeCAD.ActiveDocument.recompute()
    >>> # Gui.Selection.clearSelection()
    >>> # Gui.Selection.addSelection('Mom_and_Dads_house','Line','Vertex2',20,10,0)
    >>> Gui.runCommand('Std_Copy',0)
    >>>
    Attached Files:
    Notes
    (0014705)
    Kunda1   
    2020-08-21 20:43   
    Confirmed on the forum thread
    (0016932)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6099.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4404 [Arch] Bug minor always 2020-07-08 18:10 2021-02-06 06:28
    Reporter: lambda Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: The info here is completely irrelevant. Any FreeCAD version since the introduction of Space objects is affected.
    OS: Debian GNU/Linux bullseye/sid
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.21705 (Git)
    Build type: Unknown
    Branch: rtSiteFix
    Hash: bcfdb5936366ab32bf00f7d35fe5d090c5b59d63
    Python version: 3.8.3
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: German/Austria (de_AT)
    Summary: Space object doesn't work with non-convex models
    Description: The current algorithm, which is based on trimming down the common bounding box of all space boundaries, doesn't work in the general case. I see two possible solutions:

    1) Find all space boundaries necessary to create a closed shape and construct the space object shape from that.
    2) Keep the current algorithm, but segment the space into multiple virtual spaces that each are convex and build a compound out of them.

    See this thread in the forum for more information: https://forum.freecadweb.org/viewtopic.php?f=23&t=47505
    Tags: Arch
    Steps To Reproduce: Just try to create any non convex space object. Or see the thread in the forum.
    Additional Information:
    Attached Files:
    Notes
    (0016924)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6091.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4370 [Arch] Bug minor always 2020-06-11 17:20 2021-02-06 06:28
    Reporter: vocx Platform: Linux  
    Assigned To: OS: Ubuntu  
    Priority: normal OS Version: 18.04  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Ubuntu 18.04.4 LTS (ubuntu:GNOME/ubuntu)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.21562 (Git)
    Build type: Release
    Branch: master
    Hash: 11a2b948ea55b19efe7515f730035027a7822e06
    Python version: 3.6.9
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    Summary: Duplicated window object when using expression with wall width
    Description: An Arch Window can be embedded into an Arch Wall. Normally in the tree view this relationship is shown as the Window being inside the Wall.

    If using expressions to define some properties of the Window, the Window is duplicated in the tree view, although only one Window object actually exists.

    The bug may be in the base system actually, that is, in the code that handles the viewproviders or the tree view, and not in the Arch Wall or Arch Window object.

    Forum thread: Bug: duplicated window object when using expression with wall width
    Tags:
    Steps To Reproduce: 1. Click on Arch Wall, and create a wall 3 m, 3 m, and 0.2 m. The wall should be big enough to hold a standard window.
    2. Click on Arch Window, Fixed, and place it on the wall.
    3. In the tree view click on the Window, go to the property editor, choose "Hole Depth", and click on the rightmost "f(x)" symbol to set an expression (expressions).
    4. The expression is just the Wall's width, so enter Wall.Width in the expression field, and click OK.
    5. The Window will show the blue mark indicating the need for recomputing, so recompute, F5 (Std_Refresh).
    6. The Wall doesn't show a blue mark. Nevertheless, right click on it on the tree view, and then choose "Recompute object".
    7. The Window will appear a second time in the tree view. There will be two windows, and both will have the blue checkmark.
    Additional Information:
    Attached Files:
    Notes
    (0016907)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6074.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4317 [Arch] Bug minor always 2020-04-18 23:29 2021-02-06 06:28
    Reporter: azure Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: feedback Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Ubuntu 19.10 (KDE/plasma)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.20634 (Git)
    Build type: Debug
    Branch: master
    Hash: ba34cc6a96c15d64224e8f0c8b5da874f1e03a07
    Python version: 3.7.5
    Qt version: 5.12.4
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/United States (en_US)
    Summary: Draft grid visible through an arch wall
    Description: See the attached screenshot wallbug.png. When looking at an arch wall from the top, the top of the wall appears "open" and you can see the draft grid through it.

    The problem seems to occur only if grid spacing is below 5mm. The smaller the spacing is, the larger area of the grid can be seen through the wall.

    If spacing is 5mm or larger, as in the screenshot wallbug_grid_50mm.png, the wall looks normal to me.

    If I turn the grid off, a black area appears on top of the wall as seen in the screenshot wallbug_grid_off.png
    Tags: #pending-forum
    Steps To Reproduce: - Use FreeCAD version from git shown in the section FreeCAD information.
    - Ensure the grid settings are "factory default".
    - Select Arch workbench.
    - Load the attached wallbug.FCStd file.
    - Make the grid visible (for me the grid is not always visible at first even though I believe it is "on" - I have to turn if off first and then back on).
    - Try changing the grid spacing and turning the grid off.
    Additional Information:
    Attached Files: wallbug.png (168,608 bytes) 2020-04-18 23:29
    https://tracker.freecad.org/file_download.php?file_id=2453&type=bug
    wallbug.FCStd (8,805 bytes) 2020-04-18 23:29
    https://tracker.freecad.org/file_download.php?file_id=2454&type=bug
    wallbug_grid_50mm.png (261,118 bytes) 2020-04-18 23:29
    https://tracker.freecad.org/file_download.php?file_id=2455&type=bug
    wallbug_grid_off.png (168,666 bytes) 2020-04-18 23:29
    https://tracker.freecad.org/file_download.php?file_id=2456&type=bug
    Notes
    (0014359)
    openBrain   
    2020-04-19 09:46   
    @azure : when encountering issue with FreeCAD, please process according our reporting guidelines by first opening a topic in our forum.
    Here looks like a graphical issue. Does the problem vanish if you select 'Fit all' view ?
    (0014377)
    Kunda1   
    2020-04-25 14:04   
    @azure please follow-up by posting a thread to the forum and posting the URL here.
    (0014500)
    Kunda1   
    2020-06-07 14:23   
    @azure ping
    (0014678)
    mikeprice99   
    2020-07-22 19:26   
    I occasionally dive in to see if I can help with a bug/issue. I've looked at the sample file for this bug: the "Walltrace" is for a wall 50mm long, 3m high and 200mm thick - and I can't reproduce the 'error'. I wouldn't expect a reasonable interpretation.
    (0014733)
    Kunda1   
    2020-09-10 14:54   
    (Last edited: 2020-09-10 14:55)
    Thanks @mikeprice99. Appreciate any help triaging that you'd offer :)
    I'll open a thread on the forum for this since OP ( @azure ) hasn't responded.

    Edit: forum thread: https://forum.freecadweb.org/viewtopic.php?f=23&t=50121
    (0016882)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6048.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3951 [Arch] Bug major always 2019-04-30 14:53 2021-02-06 06:28
    Reporter: Geoplace Platform:  
    Assigned To: yorik OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Floor/Building container don't keep objects hidden
    Description: Floor Container has an impact of not maintaining the desired object visibility (hide) when you edit other objects inside it, the hided ones are shown again.

    Also when you save the file with the rectangle hidden and when re-open it again it will show everything. (Don’t save the hide status of the children objects)


    Link to the forum discussion
    Tags:
    Steps To Reproduce:
    1.-Choose the Arch workbench.
    2.-Draw a line (one or more) and a rectangle (its face property is true)
    3.-Create a floor object.
    4.-Drag and Drop the line and rectangle inside the floor object.
    5.-Select the Rectangle object and hit spacebar key (to toggle visibility) hide it.


    6.-Draw a new line or trim extend one existent. Or change its length and clic recompute button (F5).
    7.-The rectangle show again without request. (If it is the base of a slab, the slab will show)
    Additional Information: When all the elements are outside the Floor Container you can modify the line elements and the visibility of the rectangle stays as needed (hide)

    This a very annoying bug when you are editing the elements inside a Floor or building object. You have to be hiding and hiding over and over every edition made in order to could work.

    There's is no work around beside avoid using the floor container and lacking the levels functionality of it.

    Here is a sample file where you just need to do step 5 and 6 to view the bug.

    Tested with:
    OS: Windows 8.1
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16110 (Git)
    Build type: Release
    Branch: (HEAD detached at upstream/releases/FreeCAD-0-18)
    Hash: f7dccfaa909e5b9da26bf50c4a22ccca9bb10c40
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0

    OS: Windows 8.1
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.16502 (Git)
    Build type: Release
    Branch: master
    Hash: 06962535fa9ff348acca1b893cc4239908fb8bae
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0

    Attached Files: Hide Arch Shown unexpected Bug.FCStd (14,274 bytes) 2019-04-30 14:53
    https://tracker.freecad.org/file_download.php?file_id=2203&type=bug
    Notes
    (0013075)
    yorik   
    2019-05-02 17:04   
    Assigning this to me for now, but I thnk the problem lies somewhere in the group extension...
    (0013080)
    Geoplace   
    2019-05-03 21:04   
    Related to Bug 3664

    That is a more general test case compared to the bug in this report.
    (0013589)
    Roy_043   
    2019-09-13 09:30   
    This V0.19 issue seems related:
    https://forum.freecadweb.org/viewtopic.php?f=3&t=39255
    (0016757)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5923.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3909 [Arch] Bug major always 2019-03-17 08:54 2021-02-06 06:28
    Reporter: brjhaverkamp Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Arch remove does not work correctly for creating subtractions/holes
    Description: As discussed in forum thread https://forum.freecadweb.org/viewtopic.php?f=23&t=34747
    Arch_subtract gives misalligned results when one of the objects has an offset.

    In the added example this is the case where I subtracted "Thick roof dormer holes" from Thick roof for cutting walls" The roof is raised by .80m compared to the sketch and it looks like this is not taken correctly into account.

    A second problem seems to be that nesting subtractions doesnt work correctly.
    In the added example I subtract "Thick roof for cutting walls" from "Interior walls. This works correctly, except for the places where the dormer holes should have kept the Interior walls intact.
    Apparently the "Thick roof dormer holes" are not taken into account in this subtraction.

    Tags:
    Steps To Reproduce: See attached example
    Additional Information: OS: Ubuntu 18.10
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16093 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-18
    Hash: 690774c0effe4fd7b8d2b5e2fb2b8c8d145e21ce
    Python version: 2.7.15+
    Qt version: 5.11.1
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    Attached Files: example misplaced subtract.FCStd (637,473 bytes) 2019-03-17 08:54
    https://tracker.freecad.org/file_download.php?file_id=2158&type=bug
    Notes
    (0015212)
    paullee   
    2021-01-18 23:02   
    Similar / related Forum Discussion-

    1. Arch Window create Wrong Opening Position Bug?

    2. Copying and moving a window to opposite wall
    (0015215)
    Roy_043   
    2021-01-20 10:20   
    The reported bug has already been fixed:
    https://github.com/FreeCAD/FreeCAD/pull/4054
    (0016736)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5901.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3882 [Arch] Bug major always 2019-03-04 20:41 2021-02-06 06:28
    Reporter: brjhaverkamp Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Add and subtract in Arch workbench don't follow object selection order
    Description: When trying to subtract 2 structures in the Arch workbench, the order in which the 2 objects are selected is not used. Therefore in the attached example there is no way to subtract structure 2 from structure 1.

    This is related to forum thread https://forum.freecadweb.org/viewtopic.php?f=23&t=34293
    and possibly to https://forum.freecadweb.org/viewtopic.php?f=23&t=34429 where a similar issue is discussed with the add button in Arch.
    I tested this in a couple of the latest builds, currently running

    OS: Windows 10
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.15998 (Git)
    Build type: Release
    Branch: master
    Hash: 5791c341be797ff2eee99eccac53df71db510fae
    Python version: 2.7.14
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.2.0
    Locale: English/UnitedStates (en_US)

    Tags:
    Steps To Reproduce: How to reproduce: open the simplified example file attached.
    Select structure 1, ctrl+ select structure 2, hit substract, and you end up with structure 2 minus structure 1.
    Selecg structure 2, ctrl+ select structure 1, hit substract, and you end up with structure 2 minus structure 1.
    There is no way to create structure 1 minus structure 2 with the subtract function!
    Additional Information:
    Attached Files: example subtract.FCStd (11,399 bytes) 2019-03-04 20:41
    https://tracker.freecad.org/file_download.php?file_id=2149&type=bug
    example subtract 2.FCStd (16,709 bytes) 2019-03-07 07:24
    https://tracker.freecad.org/file_download.php?file_id=2151&type=bug
    Notes
    (0012852)
    Kunda1   
    2019-03-06 00:32   
    @brjhaverkamp Please also confirm in Python3/Qt5 build. Thanks
    (0012855)
    brjhaverkamp   
    2019-03-07 07:24   
    Hi Kunda1, I hadn't realised the build I downloaded was without QT5/Python3.
    So here the update, I confirm it is also happening in the QT5/Python3 build.
    I added a bit more realistic example (example subtract 2) that comes from an actual project I am working on. I want to cutout a stairwell hole in a floor structure. But all I manage is to cut out the floor from the hole structure. Irrespective from which object is selected first and which one is added with Ctrl pressed.

    Mind you that this is _only_ if I use the big blue minus sign button on the arch workbench toolbar. I meanwhile found a workaround by manually adding the subtracting object in the data view of the floor structure. That way it works perfectly. But the minus sign should do the same thing.
    OS: Windows 10
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16028 (Git)
    Build type: Release
    Branch: master
    Hash: 9079de7516eca945587e18f6076ec74eb7bd043c
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)
    (0012856)
    Kunda1   
    2019-03-07 13:21   
    @brjhaverkamp thank you. BTW, next time you encounter an issue, please open a forum thread dedicated to it first. it's easier and more efficient to get direct help and possibly a bug fix if you first post because the amount of exposure.
     
    @paullee care to weigh in on this ticket?
    (0012860)
    brjhaverkamp   
    2019-03-08 08:16   
    Hi Kunda1
    The Forum thread is mentioned in my first submission
    .
    Regis an Roy weight in on the matter and there was quite some discussion on it.

    The second thread I mentioned in the initial bug submission looks related in my view, but I could be wrong.

    Regards,

    Bert
    (0012863)
    paullee   
    2019-03-08 13:41   
    Hi all, I had checked the thread previously and noted Regis etc. are helping.

    See discussion thread - should be a bug.
    (0016725)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5890.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3802 [Arch] Feature feature N/A 2019-01-27 10:23 2021-02-06 06:28
    Reporter: danreb Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: aggregative function in the Schedule value field
    Description:
    any chance aggregative functions could be used inside schedule-way of computing stuff ?

    e.g. in the value field being able to use this kind of expression:
    max(edge.Length for edge in object.Shape.Edges)
    ?

    cf
    Tags:
    Steps To Reproduce:
    Additional Information: linked forum thread
    https://forum.freecadweb.org/viewtopic.php?f=8&t=31190&p=259272#p259272
    Attached Files:
    Notes
    (0016711)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5876.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3664 [Arch] Bug major always 2018-11-01 07:34 2021-02-06 06:28
    Reporter: djmccorrie Platform:  
    Assigned To: yorik OS:  
    Priority: high OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Visibility not preserved after making edits in building tree
    Description: Using the BIM workbench, if you have several floors as building parts within a building. Hide the floors your not working on. Make an edit, such as moving an object, changing the width of a wall. The whole building becomes visible and have to go through hiding the levels not working on again.

    This seems to be a general thing, after any edit the visibilities are lost... making it quite frustrating if you need to make a few edits to a layer obscured by others. Another scenario where the same issue exists is where you need to hide a wall to get a good side profile of an internal wall. Same happens again... keep having to hide the outer wall on every edit.
    Tags: BIM, Visibility
    Steps To Reproduce:
    1. open FreeCAD
    2. open BIM workbench
    3. Create Building
    4. Create 2x Building Parts
    5. Create 2x Wall
    6. Put one wall in each building part and the building parts in the building
    7. Hide a building part
    8. Edit the width of the wall in the other building part
    9. Both Walls visible
    Additional Information: OS: Windows 7
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.15113 (Git)
    Build type: Release
    Branch: master
    Hash: e86f7caea866db5b78cfa78e5d3a10b735b205f9
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedKingdom (en_GB)
    Attached Files: bugreport_visibility.FCStd (20,913 bytes) 2018-11-01 07:34
    https://tracker.freecad.org/file_download.php?file_id=2034&type=bug
    Notes
    (0012122)
    djmccorrie   
    2018-11-01 07:36   
    Apologies If I've categorised this wrong, I'm new to this. Fairly sure this is a bug, rather than a feature...
    (0012123)
    djmccorrie   
    2018-11-01 07:51   
    Found a workaround... it seems this only affects the visabilities with the same parent. So if I move the Ifc floor (building part) out from under the Ifc building. Hide the building and make edits to the floor in the root of the tree, the building object stays hidden. When the series of edits are finished I can move the building part back under the building.

    This will remove some of the frustration, and allow faster work flow.

    btw, thank you for your effort in putting this excellent program together. I am a developer, so when I've got some free time I might have a look over the source code and see if I can help.
    (0012128)
    yorik   
    2018-11-01 20:48   
    (Last edited: 2018-11-01 20:49)
    Doing some tests here, the behaviour still happens if you use 2 groups instead of the 2 buildingParts, but not if the host is a group too instead of a Building.

    If you place a third object directly inside the building, the bug happens with it too.

    So the problem seems to be that the host building (which is actually also a building part) forces the visibility of its children on/off when you change a property of one of its children... This is weird. There is nothing related to visibility inside the BuildingPart code, but there might be a problem with the Gui::ViewProviderGroupExtensionPython...

    Investigating further.

    (0013590)
    Roy_043   
    2019-09-13 09:31   
    This V0.19 issue seems related:
    https://forum.freecadweb.org/viewtopic.php?f=3&t=39255
    (0016661)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5826.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3289 [Arch] Feature minor always 2017-12-24 16:13 2021-02-06 06:28
    Reporter: paullee Platform: Fedora27  
    Assigned To: OS: Linux  
    Priority: normal OS Version: 4.14.7-300.fc27.  
    Status: new Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Mirror of Sketch (Arch Section Plane) not Shown in TechDraw / ArchView
    Description: Forum thread

    Mirrors of sketch, though included in the Arch Section Plane, not shown in TechDraw ArchView.

    Tags:
    Steps To Reproduce: 1. Make a sketch
    2. Draft Mirror the sketch
    3. Make a Arch Section Plane
    4. Include the Mirror (etc.) in the Arch Section Plane
    5. Make a TechDraw ArchView
    6. All other objects including the original sketch, except Mirror of the sketch, are shown.

    Additional Information:
    Attached Files: Test _ TechDraw _ ArchView-ArchSection_ Mirror Sketch_ Bug.FCStd (28,898 bytes) 2017-12-24 16:13
    https://tracker.freecad.org/file_download.php?file_id=1776&type=bug
    Test _ TechDraw _ ArchView-ArchSection_ Mirror Sketch_ Bug_ More Tests_ 2.FCStd (28,842 bytes) 2017-12-24 17:08
    https://tracker.freecad.org/file_download.php?file_id=1777&type=bug
    Notes
    (0010626)
    paullee   
    2017-12-24 16:18   
    Sorry, should have posted to Project TechDraw.

    and

    OS: Linux
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.12852 (Git)
    Build type: None
    Branch: master
    Hash: 8e3b2d7e84924444bc219133a7e0bbd07413cf4f
    Python version: 2.7.6
    Qt version: 4.8.6
    Coin version: 4.0.0a
    OCC version: 7.1.0
    Locale: English/UnitedStates (en_US)
    (0010627)
    Kunda1   
    2017-12-24 16:20   
    Moved to Techdraw.
    @paullee please customize the url name instead of using the default text (https://freecadweb.org/tracker/bug_revision_view_page.php?rev_id=1992#r1992)
    (0010628)
    paullee   
    2017-12-24 17:01   
    Thanks! Would study the url usage.
    (0010629)
    paullee   
    2017-12-24 17:08   
    Try downgrade the Mirror as discussed in the forum, but still not included ArchView.

    Discussion Forum about 'exploding' the mirror
    (0010706)
    wandererfan   
    2018-01-05 00:20   
    This isn't really a TechDraw issue. Not sure it's even an issue for Arch. Can be fixed by setting a property on the ArchSection.

    see Forum discussion
    (0010716)
    Kunda1   
    2018-01-05 21:54   
    please advise the fate of this ticket...thanks
    (0010721)
    paullee   
    2018-01-06 08:00   
    Thanks, seems not really a TechDraw issue, but some kind of 'feature not implemented' in Arch.

    See Discussion

    Thanks for taking time in checking!
    (0010726)
    Kunda1   
    2018-01-07 12:16   
    Moved to Arch
    (0016588)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5753.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3248 [Arch] Feature minor N/A 2017-11-07 00:05 2021-02-06 06:28
    Reporter: Kunda1 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Add option to make Length autofocused when drawing line/walls, so one can indicate a direction with the mouse and type a length
    Description: As per http://yorik.uncreated.net/guestblog.php?2017=414
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016580)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5745.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3246 [Arch] Bug minor always 2017-11-06 23:59 2021-02-06 06:28
    Reporter: Kunda1 Platform:  
    Assigned To: yorik OS:  
    Priority: high OS Version:  
    Status: assigned Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Fix IV mode in Sketchfab exporter
    Description: Issue mentioned in http://yorik.uncreated.net/guestblog.php?2017=414
    Tags: export
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016579)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5744.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3243 [Arch] Feature minor N/A 2017-11-05 11:17 2021-02-06 06:28
    Reporter: yorik Platform:  
    Assigned To: yorik OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Allow to auto make a Window from solids (auto recreate base wires and extrusions)
    Description: Per http://yorik.uncreated.net/guestblog.php?2017=414
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016578)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5743.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3241 [Arch] Feature minor N/A 2017-11-04 12:40 2021-02-06 06:28
    Reporter: yorik Platform:  
    Assigned To: yorik OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Level marks
    Description: Per http://yorik.uncreated.net/guestblog.php?2017=414
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016577)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5742.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3240 [Arch] Feature minor N/A 2017-11-04 12:39 2021-02-06 06:28
    Reporter: yorik Platform:  
    Assigned To: yorik OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Door/Window marks
    Description: Per http://yorik.uncreated.net/guestblog.php?2017=414
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016576)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5741.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3239 [Arch] Feature minor N/A 2017-11-04 12:38 2021-02-06 06:28
    Reporter: yorik Platform:  
    Assigned To: yorik OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Room finish marks
    Description: Per http://yorik.uncreated.net/guestblog.php?2017=414
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016575)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5740.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3238 [Arch] Feature minor N/A 2017-11-04 12:37 2021-02-06 06:28
    Reporter: yorik Platform:  
    Assigned To: yorik OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Auto section/elev marks from section plane
    Description: Per http://yorik.uncreated.net/guestblog.php?2017=414
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016574)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5739.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3237 [Arch] Feature minor N/A 2017-11-04 12:36 2021-02-06 06:28
    Reporter: Kunda1 Platform:  
    Assigned To: yorik OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: RCP plan
    Description: Per http://yorik.uncreated.net/guestblog.php?2017=414
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016573)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5738.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3231 [Arch] Feature minor N/A 2017-11-04 12:23 2021-02-06 06:28
    Reporter: Kunda1 Platform:  
    Assigned To: yorik OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Export meshes to IFC and handle hi-res objects
    Description: Per http://yorik.uncreated.net/guestblog.php?2017=414
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016571)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5736.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3229 [Arch] Feature minor N/A 2017-11-04 12:15 2021-02-06 06:28
    Reporter: Kunda1 Platform:  
    Assigned To: yorik OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Add "fill shape" to Arch sections
    Description: Per http://yorik.uncreated.net/guestblog.php?2017=414
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016570)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5735.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3228 [Arch] Feature minor N/A 2017-11-04 12:10 2021-02-06 06:28
    Reporter: Kunda1 Platform:  
    Assigned To: yorik OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Taper for structural objects
    Description: Mentioned in http://yorik.uncreated.net/guestblog.php?2017=414
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016569)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5734.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3208 [Arch] Bug minor always 2017-10-03 19:56 2021-02-06 06:28
    Reporter: mandichjr Platform: Ubuntu  
    Assigned To: OS: Zesty Zapus  
    Priority: low OS Version: 17.04  
    Status: confirmed Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Wall additions can not be set to auto (floor height).
    Description: When a wall is composed of additions and placed in a floor... the hight of the composed wall can be set to automatic (i.e. resulting in the floor's height). However, this does not carry through to the additions. While the additions' heights can be altered, when set to automatic and recomputed, they remain whatever they were last at.

    I recommend that when a a parent wall is changed it doesn't automatically change the child's, (because internal wall may intentionally be unique) - however, the children should at least be allowed to be set to automatic as well.

    **First time submitter, anxious, and sorry if broke any rules... really like this software and want to start participating. Using daily build.
    Tags: #lowhangingfruit, Arch
    Steps To Reproduce: 1. Create multiple walls
    2. Merge walls by adding to a parent (plus sign) [not sure about MergeWalls()]
    3. Place in a floor
    4. Set parent wall's height to '0'
    5. Modify floor height (note only parent wall changes)
    6. Modify child wall (note change)
    7. Set child wall to '0' (not no change)
    Additional Information: OS: Ubuntu 17.04
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.12289 (Git)
    Build type: None
    Branch: master
    Hash: 53168d39d6ea03a21f38337363ae0669f1f31507
    Python version: 2.7.13
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.1.0
    Locale: English/UnitedStates (en_US)
    Attached Files: screenshot.png (252,489 bytes) 2017-10-03 19:56
    https://tracker.freecad.org/file_download.php?file_id=1736&type=bug
    Notes
    (0010241)
    mandichjr   
    2017-10-03 20:10   
    Sorry, example .fcstd attached. Had to remove personal info about my home first.
    (0010242)
    Kunda1   
    2017-10-04 00:02   
    @mandichjr No worries :) The way we do it here is first you open a forum thread and get the attention of the community. When they ascertain that it's a bug then we open a ticket and link the thread to the ticket and vice-a-versa. Conversations are recommended to happen on the thread. Check out https://freecadweb.org/wiki/Tracker for more guidance.
    (0010868)
    Kunda1   
    2018-01-26 18:56   
    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=23&t=26597
    (0013614)
    Roy_043   
    2019-09-17 14:51   
    The issue also occurs with walls nested in other containers such as an Arch_BuildingPart.
    F.e. this does not work:
    Arch_Floor (height=2960) > Arch_BuildingPart (height=0) > Arch_Wall (height=0).

    Forum thread: https://forum.freecadweb.org/viewtopic.php?f=3&t=39302
    (0016567)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5732.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2880 [Arch] Feature minor N/A 2017-01-29 16:39 2021-02-06 06:28
    Reporter: yorik Platform: PC  
    Assigned To: yorik OS: Debian  
    Priority: normal OS Version: Testing 64bit  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Make father walls handle multilayer walls
    Description: When creating a "father" wall (when inserting windows), multilayer walls are disregarded. This should be handled properly.
    Tags:
    Steps To Reproduce:
    Additional Information: Discussion topic: https://forum.freecadweb.org/viewtopic.php?f=23&t=20316
    System Description
    Attached Files:
    Notes
    (0010371)
    Kunda1   
    2017-11-04 12:34   
    @yorik does the issue also cover "Allow to convert multilayer wall to multiple walls and vice-versa" mentioned in http://yorik.uncreated.net/guestblog.php?2017=414 or should I open a separate ticket for that?
    (0016515)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5680.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2581 [Arch] Feature minor N/A 2016-06-10 20:45 2021-02-06 06:28
    Reporter: yorik Platform: PC  
    Assigned To: yorik OS: Debian  
    Priority: normal OS Version: Testing 64bit  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Support material properties in IFC
    Description: Materials in FreeCAD can have many properties. In IFC however, materials can't have properties. These need to be packed into a PropertySet, which must be added to each object that uses the material.

    On import, we should detect properties that can be mapped to material values, and do so accordingly.
    Tags: IFC
    Steps To Reproduce:
    Additional Information:
    System Description
    Attached Files:
    Notes
    (0016492)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5657.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2543 [Arch] Feature minor N/A 2016-05-12 01:31 2021-02-06 06:28
    Reporter: yorik Platform: PC  
    Assigned To: yorik OS: Debian  
    Priority: normal OS Version: Testing 64bit  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Implement GBXML export
    Description: Implement the possibility to export a BIM model as GBXML
    Tags: Bountysource, fundable, funded
    Steps To Reproduce:
    Additional Information: Started in https://github.com/FreeCAD/FreeCAD/blob/master/src/Mod/Arch/importGBXML.py
    Downstream ticket: https://github.com/yorikvanhavre/BIM_Workbench/issues/6
    Bountysource: https://www.bountysource.com/issues/65465675-implement-gbxml-export
    System Description
    Attached Files:
    Notes
    (0007346)
    yorik   
    2016-10-06 22:45   
    (Last edited: 2016-10-06 22:47)
    Some more ideas to implement before actual export:

    - Add some general settings to the project (site or building), maybe linked/embedded osm file?
    - Add tool to subdivide solid faces with another solid (useful for FEM too)
    - Base everything on spaces. What gets exported are spaces.
    - Ability to mark faces of spaces as 1) shared 2) exterior 3) ground 4) window
    - Ability to define thermal zones and add spaces to these thermal zones (use floors maybe?)
    - Ability to retrieve a building's floor area

    Also check the .osm format of openstudio. Openstudio itself will allow to set many more settings and do the necessary export to radiance and energyplus.

    Basically from FreeCAD we should be able to do the same as what sketchup does, that is:

    - create simple geometry (spaces)
    - define what is shared wall, what is window, etc (a way to do that easily/automatically?)
    - create shadowing devices (not sure how to do that, creates non-solid/manifold objects)
    - give these spaces a name, a use/function, a thermal zone.

    (0011918)
    Kunda1   
    2018-10-04 12:54   
    Added https://github.com/yorikvanhavre/BIM_Workbench/issues/6 to the summary
    (0016489)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5654.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2448 [Arch] Feature minor have not tried 2016-02-11 19:51 2021-02-06 06:28
    Reporter: yorik Platform: PC  
    Assigned To: yorik OS: Debian  
    Priority: normal OS Version: Testing 64bit  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Support for IfcProfileDef
    Description: Structural elements that are based on a profile should be translated to/from IFC as IfcProfileDef objects.
    Tags: IFC
    Steps To Reproduce:
    Additional Information: https://github.com/IndustryFoundationClasses/Questions/issues/3
    System Description
    Attached Files:
    Notes
    (0016476)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5641.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2356 [Arch] Feature minor have not tried 2015-12-07 13:39 2021-02-06 06:28
    Reporter: yorik Platform: PC  
    Assigned To: yorik OS: Debian  
    Priority: normal OS Version: Testing 64bit  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Add a set of structural nodes tools
    Description: A set of tools to manipulate the structural nodes of Arch Structure objects:

    - Ability to have a structural plane instead of a wire (for slabs)
    - Tool to manually edit the nodes (like Draft Edit)
    - Tool to join the endnodes of two structural elements
    - Tool to trim or extend one structural node to touch another (like Draft Trimex)
    - Turn nodes on automatically (of all structures?) when in edit mode
    - Ability to export to PyBar (maybe others?)
    - Ability to export to structural analysis view IFC
    Tags: IFC
    Steps To Reproduce:
    Additional Information:
    System Description
    Attached Files:
    Notes
    (0009081)
    Kunda1   
    2017-05-22 14:00   
    @yorik any of these features implemented yet?
    (0009135)
    yorik   
    2017-05-25 14:00   
    Yes:

    - Ability to have a structural plane instead of a wire (for slabs)
    - Tool to join the endnodes of two structural elements
    - Tool to trim or extend one structural node to touch another (like Draft Trimex)
    - Turn nodes on automatically (of all structures?) when in edit mode

    are done

    - Tool to manually edit the nodes (like Draft Edit)
    - Ability to export to PyBar (maybe others?)
    - Ability to export to structural analysis view IFC

    still need to be done
    (0009136)
    Kunda1   
    2017-05-25 15:34   
    Thanks yorik, I've updated the ticket to reflect this
    (0016473)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5638.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1844 [Arch] Feature minor have not tried 2014-12-01 01:14 2021-02-06 06:28
    Reporter: bofhjr Platform:  
    Assigned To: OS:  
    Priority: low OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Integrate a client for the buildingSMART Data Dictionary web service
    Description: This would allow to classify the different FreeCAD Arch model with the vocabulary and semantics of the IFCs --- It may also help for i18n
    Tags: IFC
    Steps To Reproduce:
    Additional Information: http://bsdd.buildingsmart.org
    http://catenda.no/archives/2001
    Attached Files:
    Notes
    (0016442)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5607.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1843 [Arch] Feature minor have not tried 2014-12-01 00:59 2021-02-06 06:28
    Reporter: bofhjr Platform:  
    Assigned To: OS:  
    Priority: low OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Integrate a BIMSie server into FreeCAD
    Description: This would allow an IFC Structure Validator to act as a WIMSie client of FreeCAD.
    It would also allow any enabled BIMSie viewer to display IFC views of the currently opened FreeCAD ARCH models.
    Tags: IFC
    Steps To Reproduce:
    Additional Information: http://www.nibs.org/?page=bsa_bimsie
    Attached Files:
    Notes
    (0008430)
    yorik   
    2017-02-25 04:18   
    The given URL seems disabled. Not sure this project is still alive...
    (0008442)
    Kunda1   
    2017-02-26 12:31   
    (Last edited: 2017-02-26 12:31)
    @yorik i can load the webpage. What is 'disabled' for you about it?
    there is an email for the project coordinator:
    > The project is being organized into a core technical team and corresponding user members membership who will review and comment on the work of the core team. United States and international data modelers and API developers are also supporting the team to ensure the work accomplished will be consistent with other efforts of the buildingSMART alliance and buildingSMART international. To participate in this project, please contact Leon van Berlo from the Netherlands organisation for applied scientific research TNO: leon.vanberlo@tno.nl

    (0008448)
    yorik   
    2017-02-26 15:22   
    This page doesn't work anymore (which would contian the specification): http://bimsie.openbimstandards.org/

    That's why I think the project is not active anymore...
    (0008463)
    Kunda1   
    2017-02-27 01:46   
    @yorik found https://github.com/openBIMstandards/
    Looks like there is sporadic activity but not necessarily on bimsie AFAICT
    (0016441)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5606.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1842 [Arch] Feature minor have not tried 2014-12-01 00:50 2021-02-06 06:28
    Reporter: bofhjr Platform:  
    Assigned To: OS:  
    Priority: low OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Add the capability to communicate as a client with a BIMSie server
    Description: This would allow for example to directly checkout, checkin IFC Files from the open source BIMServer.

    However It seems that there is not (yet ?) a python client for BIMSie web services
    Tags:
    Steps To Reproduce:
    Additional Information: http://www.nibs.org/?page=bsa_bimsie
    Attached Files:
    Notes
    (0016440)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5605.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    515 [Arch] Feature minor N/A 2011-12-05 12:53 2021-02-06 06:28
    Reporter: yorik Platform:  
    Assigned To: yorik OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Arch module - Auto dimension tool
    Description: A tool that automatically adds dimensions to a set of objects:

    Select objects, select a point, another point, and the selected objects are measured, with dimensions passing through the 2 points. The result is a "Dimension set" object containing Draft dimensions, where you can change later on which objects are measured, and which "style" of measurement to apply (only biggest exterior dimension, including windows, interior style, etc...)
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016385)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5550.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4395 [FEM] Feature tweak have not tried 2020-06-30 14:31 2021-02-06 06:23
    Reporter: HoWil Platform:  
    Assigned To: HoWil OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: <!--ATTENTION:
    COMPLETELY ERASE THIS AFTER PASTING YOUR
    Help > About FreeCAD > Copy to clipboard
    NOTE: just the snippet alone will do without anything else included.
    The ticket will not be submitted without it.
    -->
    Summary: Homogenise/update selection dialogues in FEM
    Description: Selection dialogues in FEM for e.g. boundary conditions like "ConstraintFixed" and e.g. "ConstraintElectrostaticPotential" have different features like highlighting of the selected element in the "Select Faces -> Add-> Remove" task panel.
    This is probably due to the fact that some of them like the fixed-constraint are programmed in c++ while the others are used in python?

    The attached screenshots do show that e.g. for the constraint ElectrostaticPotential no face is highlighted when there is an entry selected in the task panel.

    See also
    https://github.com/HoWilgh/FreeCAD/blob/femelmeresforce/src/Mod/Fem/femguiobjects/_ViewProviderFemConstraintElectrostaticPotential.py

    https://github.com/HoWilgh/FreeCAD/blob/femelmeresforce/src/Mod/Fem/femguiobjects/ViewProviderFemConstraint.py
    https://github.com/HoWilgh/FreeCAD/blob/femelmeresforce/src/Mod/Fem/Gui/TaskFemConstraintFixed.ui
    https://github.com/HoWilgh/FreeCAD/blob/femelmeresforce/src/Mod/Fem/Gui/TaskFemConstraintFixed.h
    Tags: boundary conditions, FEM, highlighting, selection
    Steps To Reproduce: Create a solid cube in Part-wb
    Create a analysis in FEM-wb
    Add a Model->Mechanical constraints->Fixed constraints and enter it by doubleclicking it in the combo-view/tree-view
    Select a face and 'Add' the face into the list of elements in the "FEM constraint parameters" dialogue
    Click somewhere else to de-select the face and than click the element in the "FEM constraint parameters" list -> the selected face gets highlighted again!
    Additional Information:
    Attached Files: Screenshot from 2020-06-30 16-05-40.png (221,585 bytes) 2020-06-30 14:31
    https://tracker.freecad.org/file_download.php?file_id=2500&type=bug
    Screenshot from 2020-06-30 16-05-13.png (238,036 bytes) 2020-06-30 14:31
    https://tracker.freecad.org/file_download.php?file_id=2501&type=bug
    Notes
    (0016918)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6085.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4394 [FEM] Feature tweak always 2020-06-30 13:54 2021-02-06 06:23
    Reporter: HoWil Platform:  
    Assigned To: HoWil OS:  
    Priority: low OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: <!--ATTENTION:
    COMPLETELY ERASE THIS AFTER PASTING YOUR
    Help > About FreeCAD > Copy to clipboard
    NOTE: just the snippet alone will do without anything else included.
    The ticket will not be submitted without it.
    -->
    Summary: Clean up the ElectrostaticPotential task panel, make it smart and pretty.
    Description: The task panel for the ElectrostaticPotential setting for the Elmer solver in FEM has to be cleaned up.
    Currently it is very non-intuitive to use.
    Furthermore, some checks have to be added to enable elements like the one for the capacitance body only if the capacitance calculation is enabled in the electrostatics-solver.
    GUI-Elements like the capacitance body count should be disabled if the 'unspecified' Box is enabled (as done for the Potential value).

    https://github.com/HoWilgh/FreeCAD/blob/howilnewsolver/src/Mod/Fem/PyGui/TaskPanelFemElectrostaticPotential.ui
    https://github.com/HoWilgh/FreeCAD/blob/howilnewsolver/src/Mod/Fem/femsolver/elmer/equations/electrostatic.py
    Tags: Elmer, FEM, GUI
    Steps To Reproduce:
    Additional Information:
    Attached Files: Screenshot from 2020-06-30 15-52-24.png (194,658 bytes) 2020-06-30 13:54
    https://tracker.freecad.org/file_download.php?file_id=2499&type=bug
    Notes
    (0016917)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6084.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4391 [FEM] General tweak always 2020-06-29 19:01 2021-02-06 06:23
    Reporter: HoWil Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: acknowledged Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: <!--ATTENTION:
    COMPLETELY ERASE THIS AFTER PASTING YOUR
    Help > About FreeCAD > Copy to clipboard
    NOTE: just the snippet alone will do without anything else included.
    The ticket will not be submitted without it.
    -->
    Summary: Minor updates to the messages of the Elmer solver-framework
    Description: The following messages are missing in the 'Solver Control' window of at least the SolverElmer-element :
    + if one presses 'Write' for exporting the mesh and the solver input file des .sif no message indicates the the export/writing process was completed
    + The title of the 'Run' button should change and/or indicate the also the mesh is additionally exported. Like 'Run without remeshing' if mesh-related parameters were changed but one wants to run the already exported model.
    Tags: #lowhangingfruit, Elmer, FEM, Solver(FEM)
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0014602)
    HoWil   
    2020-06-29 19:06   
    https://forum.freecadweb.org/viewtopic.php?f=18&t=45887#p393584
    (0014603)
    HoWil   
    2020-06-29 19:07   
    I think the above wanted behavior was originally implemented bud was broken somehow.
    For the CCX solver it still works.
    (0016916)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6083.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4390 [FEM] Feature feature always 2020-06-29 18:49 2021-02-06 06:23
    Reporter: HoWil Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: <!--ATTENTION:
    COMPLETELY ERASE THIS AFTER PASTING YOUR
    Help > About FreeCAD > Copy to clipboard
    NOTE: just the snippet alone will do without anything else included.
    The ticket will not be submitted without it.
    -->
    Summary: Save FEM Clipping Plane as different elements in the model/tree
    Description: In FEM-wb a Clipping Plane can be used to look into the model or the mesh. Unfortunately, this clipping-plane element can only be created and removed to the 3D-view but it is not saved with/in the model. This would be very helpful for selecting/changing interior faces after e.g. saving and reopening the model.
    Especially after saving the model and exiting FC the clipping plane is gone.
    More than one clipping plane-element would be also helpful for selecting different interior faces.
    Tags: clipping plane, FEM
    Steps To Reproduce:
    Additional Information: https://forum.freecadweb.org/viewtopic.php?f=18&t=30876&p=258447&hilit=clipping#p258447
    "Clipping plane on face" under "Menu: Utilities" on https://wiki.freecadweb.org/FEM_Module
    Attached Files:
    Notes
    (0015028)
    berndhahnebach   
    2020-11-30 10:12   
    this would be a good add for sure
    (0016915)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6082.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4388 [FEM] Feature feature have not tried 2020-06-29 16:02 2021-02-06 06:23
    Reporter: HoWil Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: <!--ATTENTION:
    COMPLETELY ERASE THIS AFTER PASTING YOUR
    Help > About FreeCAD > Copy to clipboard
    NOTE: just the snippet alone will do without anything else included.
    The ticket will not be submitted without it.
    -->
    Summary: Start paraview with selected result from within FC
    Description: I would like to have the possibility to use paraview from (within) FC. Paraview is 'the' tool for visualizing FEM-Results so why shouldn't we use it in combination with FC-FEM.
    Paraview is already heavily in use for Cfd-OF/Openfoam within the FC-community.
    The results created by Elmer when used in FC-FEM are stored in .vtk format. By storing e.g. a paraview-state-file pvsm with the same filename next to the .vtk file one could automate nice post processing. In future such paraview-state-information or equivalent python-code could be stored and edited within FreeCAD in a document-object.
    Tags: Elmer, FEM, Paraview, postprocessing, VTK
    Steps To Reproduce:
    Additional Information: https://forum.freecadweb.org/viewtopic.php?f=18&t=43278#p367842
    Attached Files:
    Notes
    (0016914)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6081.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4366 [FEM] Bug minor always 2020-06-08 09:19 2021-02-06 06:23
    Reporter: FreeCAD97990 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: Windows 10 (10.0)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.21514 (Git)
    Build type: Release
    Branch: master
    Hash: 89ddab33f692a9bd739171689f9ab0eb58d64b35
    Python version: 3.6.8
    Qt version: 5.12.1
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/United Kingdom (en_GB)
    Summary: Tube does not show Fixed or Force Constraints
    Description: I've noticed that Fixed Constraints and Force Constraints are not displayed when they are specifed on the end faces of a Tube.

    Please see the attached file.

    I've looked at a number of different cross sections, like a solid bar, and also tubes with square, hexagonal, and octagonal hollow profiles, and they all show Fixed Constraints and Force Constraints properly.

    I was at first concerned that because the Constraints were not shown on the screen then the Constraints had not been applied to the Calculix model either. But when I went on to mesh and solve the Analysis, then there is deformation that shows that the Fixed and Force Constraints have actually been applied. They also appear in the Calculix inp file.

    I put out a Forum post on this issue on Thu May 14, 2020 6:26 pm and bernd replied on Thu May 14, 2020 8:34 pm to confirm the bug and to say that it seemed to occur when the walls of the Tube are thin (less than around 10mm). He said we should make a entry on mantis and post a link to it here.

    Now, I'm not too good at making links, so please refer to these posts if I haven't managed to put a link into this bug report.
    Tags:
    Steps To Reproduce: Just load the attached file. No constraints are shown. I've just tested it with the latest 0.19 release, and the problem is still there.
    Additional Information:
    Attached Files: Tube does not show Fixed or Force Constraints.FCStd (12,842 bytes) 2020-06-08 09:19
    https://tracker.freecad.org/file_download.php?file_id=2485&type=bug
    Notes
    (0016906)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6073.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4064 [FEM] Feature minor always 2019-07-18 22:25 2021-02-06 06:23
    Reporter: uwestoehr Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Allow to select datums as direction for acting forces
    Description: When setting the direction of a force it is not possible to select in the force setting one of the main axes or a datum line.

    This seems to be only an UI issue.

    This feature would be very helpful because no matter how you need to change your model later on, the main axes and datums remain as they are.
    Tags: constraints
    Steps To Reproduce:
    Additional Information: Forum thread: https://forum.freecadweb.org/viewtopic.php?f=18&t=37816

    OS: Windows 7
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.17331 (Git)
    Build type: Release
    Branch: master
    Hash: cf18161dc26267c259ac21675cb9637263bf4152
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: German/Germany (de_DE)
    Attached Files:
    Notes
    (0016802)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5968.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4060 [FEM] Feature minor N/A 2019-07-17 15:39 2021-02-06 06:23
    Reporter: Kunda1 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FEM - Export transient FEM results to vtk/vtu for ParaView
    Description: User Luftschraube created a macro and announced it in https://forum.freecadweb.org/viewtopic.php?f=22&t=37650

    To give a little back to the community, I would like to share my macro with you: I used to perform quite a lot FEM analyses with FreeCAD, however, I prefer to export the results to VTK and then to visualise them using ParaView, which has a lot more options for that. Unfortunately, FreeCAD can only export one VTK file at a time, so I came up with a little macro that I use for transient analyses. The macro exports the FEM results and also writes a VTU file in the same folder. The VTU file can be simply opened in ParaView, and that way you directly have the transient results with the correct timestamps.

    Luftschraube
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016800)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5966.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3937 [FEM] Bug minor always 2019-04-18 15:51 2021-02-06 06:23
    Reporter: salmat Platform: x86-64  
    Assigned To: berndhahnebach OS: ubuntu  
    Priority: normal OS Version: 18.04 LTS  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: DataAlongLine Create Plot Always plot Magnitude
    Description: In DataAlongLine
    The "Create Plot" Always plot only Magnitude. Witch ever Vector your are chosen to plot.
    I need to have only X data for example.

    I have seen the bug in any versions.

    I have looks the code, it seems to me it is in :
    src/Mod/Fem/App/FemPostFilter.cpp line 267

    When not "if(pdata->GetNumberOfComponents() == 1)"
    It always does the mean square, not looking selected Vector value
    (Not sure I understand everything ...)

    line 267 :
    void FemPostDataAlongLineFilter::GetAxisData() {
    
        std::vector<double> coords;
        std::vector<double> values;
    
        vtkSmartPointer<vtkDataObject> data = m_probe->GetOutputDataObject(0);
        vtkDataSet* dset = vtkDataSet::SafeDownCast(data);
        vtkDataArray* pdata = dset->GetPointData()->GetArray(PlotData.getValue());
        vtkDataArray *tcoords = dset->GetPointData()->GetTCoords("Texture Coordinates");
    
        int component = 0;
    
        const Base::Vector3d& vec1 = Point1.getValue();
        const Base::Vector3d& vec2 = Point2.getValue();
        const Base::Vector3d diff = vec1 - vec2;
        double Len = diff.Length();
    
        for(int i=0; i<dset->GetNumberOfPoints(); ++i) {
    
            double value = 0;
            if(pdata->GetNumberOfComponents() == 1)
                value = pdata->GetComponent(i, component);
            else {
                for(int j=0; j<pdata->GetNumberOfComponents(); ++j)
                    value += std::pow(pdata->GetComponent(i, j),2);
    
                value = std::sqrt(value);
            }
            values.push_back(value);
            double tcoord = tcoords->GetComponent(i, component);
            coords.push_back(tcoord*Len);
        }
        YAxisData.setValues(values);
        XAxisData.setValues(coords);
    }
    Tags:
    Steps To Reproduce: Attached an project example, with the print screens showing the bug.

    1: Open the example
    2: double click on DataAlongLine in Pipeline
    3: in Field, select StrainVectors
    4: in Vector, select any value

    In 3d Print, all seems to plot normaly along the line colors, but in AlonLine plot (curve) always shows mean square ...
    Additional Information: OS: Ubuntu 18.04.2 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16093 (Git)
    Build type: Release
    Branch: releases/FreeCAD-0-18
    Hash: 690774c0effe4fd7b8d2b5e2fb2b8c8d145e21ce
    Python version: 2.7.15rc1
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: French/France (fr_FR)
    Attached Files: Freecad 3D strain X along line X.png (704,281 bytes) 2019-04-18 15:51
    https://tracker.freecad.org/file_download.php?file_id=2184&type=bug
    Freecad 3D strain X along line Y.png (659,633 bytes) 2019-04-18 15:51
    https://tracker.freecad.org/file_download.php?file_id=2185&type=bug
    Freecad 3D strain Y along line X.png (793,915 bytes) 2019-04-18 15:51
    https://tracker.freecad.org/file_download.php?file_id=2186&type=bug
    Freecad 3D strain Y along line Y.png (769,870 bytes) 2019-04-18 15:51
    https://tracker.freecad.org/file_download.php?file_id=2187&type=bug
    Report Bug.FCStd (1,154,491 bytes) 2019-04-18 15:51
    https://tracker.freecad.org/file_download.php?file_id=2188&type=bug
    Notes
    (0013032)
    Kunda1   
    2019-04-22 13:56   
    @salmat thank you for the report. We ask folks to first post on the forum before opening a ticket, especially in regards to FEM because it is heavily developed.

    Also consider using the 0.19 development version when you're using FEM.

    punting to bernd
    (0013036)
    salmat   
    2019-04-22 20:42   
    How to install 0.19 ?
    I have looked : https://www.freecadweb.org/wiki/Install_on_Unix/id
    Installed freecad-daily, and just tried to update now ... nothing new ?
    (0013037)
    Kunda1   
    2019-04-23 11:21   
    @salmat Try the appimages.
    I guess I need to update the documentation to help folks understand this better. Here is the link to the latest dev release: https://github.com/FreeCAD/FreeCAD/releases/tag/0.19_pre
    You can use the appimage update tool to stay up to date with the latest dev release. That is what the FEM dev recommends to have the FEM workbench working correctly.
    (0016750)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5916.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3932 [FEM] Feature major always 2019-04-12 06:14 2021-02-06 06:23
    Reporter: AndreiTsayukov Platform: 64-bit  
    Assigned To: berndhahnebach OS: Windows 10  
    Priority: urgent OS Version: 1809  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FEM - Selecting the interior solids of CompSolid
    Description: I'm going to simulate composite materials but I've come across with inability to select the interior solids of CompSolid.

    This problem arises when asigning mesh region and/or material to the interior solid.

    Adding a clipping plane to see the interior shapes and selecting either the edge or the face that belong to the interior solid yields a message "Edge (Face) belongs to more than one solid".

    I was following this tutorial.

    OS: Windows 10
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.16274 (Git)
    Build type: Release
    Branch: master
    Hash: 7c760259a389b38b76da78e4f6e1f9be66714842
    Python version: 2.7.14
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.2.0
    Locale: Russian/RussianFederation (ru_RU)
    Tags: #pending-forum, FEM, material, mesh region
    Steps To Reproduce: FEM Workbench. Analysis is activated.

    0. Create a clipping plane via Utilities -> Clipping plane on face to see the interior
    1. Highlight the CompSolid in the tree view
    2. Select Mesh -> FEM mesh form shape by Gmsh and then leave the dialog by clicking OK button
    3. Highlight FEMMeshGmsh in the tree view and create a Mesh Region via Mesh -> FEM mesh region
    4. Enter max element size
    5. Toggle the selection mode to Solid and press "Add" button
    6.1. In 3D view select edge/face that belongs to the interior solid
    6.2. Use SelectingTools and select any solid in the list
    Additional Information: I think the feature of selecting the interior solids must be.

    How I see this feature. When selecting vertext/edge/face of the interior solid somewhat context menu or window with contiguous shapes listed comes up. There shoud be edges, faces or solids corresponding to the selection mode chosen. Hovering on the item of the list makes this item highlighted in 3D view. Selecting the solid in the list adds it correctly to the list of mesh region/material assignment.

    The similar functionality is implemented here but selecting the interior solid form the list yields an error in the Report view.
    Attached Files: 1.png (236,079 bytes) 2019-04-12 06:14
    https://tracker.freecad.org/file_download.php?file_id=2180&type=bug
    2.png (253,999 bytes) 2019-04-12 06:14
    https://tracker.freecad.org/file_download.php?file_id=2181&type=bug
    3.png (265,118 bytes) 2019-04-12 06:14
    https://tracker.freecad.org/file_download.php?file_id=2182&type=bug
    Notes
    (0013027)
    Kunda1   
    2019-04-15 11:19   
    Fixed typo in title.
    @AndreiTsayukov thanks for the well written report. In the future please first post to the FEM forum to get the FEM core devs attention as we suggest in the guidelines posted in the yellow banner at the top of this page.
    Bernd, assigning to you so you see this.
    (0013571)
    berndhahnebach   
    2019-09-11 03:58   
    https://forum.freecadweb.org/viewtopic.php?f=18&t=34542
    (0016747)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5913.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3906 [FEM] Bug minor always 2019-03-14 23:10 2021-02-06 06:23
    Reporter: uwestoehr Platform:  
    Assigned To: berndhahnebach OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: missing feedback when exporting to FEM mesh formats
    Description: - open an analysis
    - select the "CalculiX_static_results" in the model tree
    - export it to VTK

    result: this is error-prone:
    Users might accidentally not choose "FEM result VTK" but "FEM mesh formats".
    Yes, a result is no mesh, however in the export dialog these 2 entries are above each other so one can quickly make a mistake. The problem is that the user don't get any info. He exports but nothing will in fact be exported. No file will be written and he doesn't get info that nothing was output.
    If possible, if the user selected a result object either the export to mesh option won't be available or he gets the info that the selection is not compatible with the selected object.
    Tags: export, FEM, VTK
    Steps To Reproduce:
    Additional Information: Forum thread: https://forum.freecadweb.org/viewtopic.php?f=18&t=34815&start=10#p293375

    OS: Windows 7
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16078 (Git)
    Build type: Release
    Branch: master
    Hash: 67df9f3a828fbb0fec29d039792d4baf3d9ee8e0
    Python version: 3.6.6
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: German/Germany (de_DE)
    Attached Files:
    Notes
    (0016733)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5898.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3902 [FEM] General text always 2019-03-12 17:02 2021-02-06 06:23
    Reporter: kazan417 Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Translation: "displacement" in ship.ts and fem.ts have different meaning and need differentiation in the sourcecode
    Description: I found some bad translation in fem.ts. First of all displacement (водоизмещение) automatically copied by crowdin from ship.ts, but here should be different word - смещение. This is true for many languages, not just Russian.
    I think we can solve it by changing "displacement" in ship.ts source string to "ship displacement"
    Tags: FEM, ship, translation
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0012899)
    kazan417   
    2019-03-12 17:12   
    https://forum.freecadweb.org/viewtopic.php?f=10&t=32573&p=291900#p291900
    (0016730)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5895.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3883 [FEM] Feature minor N/A 2019-03-05 09:47 2021-02-06 06:23
    Reporter: berndhahnebach Platform:  
    Assigned To: berndhahnebach OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FEM, add group info to the GUI tool show mesh information
    Description: see summary
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016726)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5891.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3879 [FEM] Feature minor N/A 2019-03-03 15:45 2021-02-06 06:23
    Reporter: berndhahnebach Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FEM, vtk result pipeline, drag and drop for filter objects
    Description: it would be helpful if filter obj would support drag and drop in and out of pipeline objects.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0012835)
    berndhahnebach   
    2019-03-03 20:21   
    (Last edited: 2019-03-03 20:22)
    python example code for calculix cantilever example.
    - load example
    - delete pipeline object
    - create a new pipeline object
    - use this code to move the warp inside the pipeline

    App.ActiveDocument.Pipeline.Filter = [App.ActiveDocument.WarpVector]

    (0012836)
    berndhahnebach   
    2019-03-03 20:22   
    C++ drag and drop example for analysis container

    https://github.com/FreeCAD/FreeCAD/blob/2b0d3477cb5700f5188be0ee5152e50ad6766e9c/src/Mod/Fem/Gui/ViewProviderAnalysis.cpp#L188-L211
    (0012837)
    berndhahnebach   
    2019-03-03 20:23   
    FreeCAD 0.18.16028
    (0016724)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5889.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3874 [FEM] Feature minor sometimes 2019-03-01 00:14 2021-02-06 06:23
    Reporter: HarryvL Platform: PC  
    Assigned To: berndhahnebach OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: scaling of eigenmodes in free vibration analysis
    Description: see: https://forum.freecadweb.org/viewtopic.php?f=18&t=34048&start=10#p289517

    I would recommend that initial scaling is applied to eigenmodes, e.g. scale_factor=0.01*mesh_size/max_displacement
    Tags:
    Steps To Reproduce: N/A
    Additional Information:
    Attached Files:
    Notes
    (0016723)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5888.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3783 [FEM] Bug minor always 2019-01-20 03:59 2021-02-06 06:23
    Reporter: uwestoehr Platform:  
    Assigned To: uwestoehr OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: several faces cannot be added at once in some FEM dialogs
    Description: - add a FEM solid material
    - You need to select e.g. 20 faces for this material, therefore you open the material dialog

    result: there is no way to add more than one face at once. So you can click on Add and then click on a face while keeping Ctrl pressed to select another face because the first face you select is always directly added. Therefore it is extremely annoying if you have to add tens of faces.

    This bug does not occur in other FEM dialogs, like e.g. the constraint displacement dialog. There you can select all faces and finally press Add to get them all added at once.

    The bug occurs in the following FEM dialogs:
    - ElementGeometry2D
    - SolidMaterial
    - FemConstraintForce
    - FemConstraintForc

    The bug does not occur in these FEM dialogs:
    - FemConstraintFixed
    - FemConstraintDisplacement
    - FemConstraintPressure
    - FemConstraintTemperature
    - FemConstraintHeatflux
    Tags: FEM
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0012490)
    Kunda1   
    2019-01-22 23:36   
    @uwestoehr please follow the guidelines (enormous yellow banner at the top of the page) when opening tickets. There is no extensive FC version info, no forum thread. Please open a thread to discuss this with bernd, the FEM maintainer. OR else what happens is that these tickets create tracker-bloat. Thanks for your comprehension.
    (0012501)
    uwestoehr   
    2019-01-23 23:31   
    > There is no extensive FC version info

    @Kunda1, I specified that I use version 0.18, see this bug report header. I also use the latest development snapshot as given in the yellow banner when reporting bugs.

    > no forum thread. Please open a thread to discuss this with bernd, the FEM maintainer.

    Sorry, but I don't have that much time. I reported a bug I saw and checked that it is not yet reported as best as possible. feel free to ignore my bug reports or close them immediately if you don't think it is a real bug.

    I am an Open Source software developer too and know that some bug reports are not valid, thus I checked carefully not to report already existing issues. But you cannot expect people to discuss at first in a forum - waiting for replies, respond, waiting again... So I collected all bugs I found and reported them that they are not forgotten. (I don't use FC regularly, maybe once a month.)
    (0012511)
    Kunda1   
    2019-01-25 17:21   
    My response 0003781:0012509

    Deferring to @berndhahnebach
    (0012527)
    berndhahnebach   
    2019-01-26 21:27   
    0003782:0012525 the mentioned love includes to make all reference shape gui work the same way in all constraints ...
    (0014944)
    uwestoehr   
    2020-10-24 22:00   
    Still the case. I'll have a look.
    (0016701)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5866.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3782 [FEM] Bug tweak always 2019-01-20 03:40 2021-02-06 06:23
    Reporter: uwestoehr Platform:  
    Assigned To: uwestoehr OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: impossible to remove several references from FEM references lists
    Description: - create a FEM shell plate thickness and add several reference surfaces
    - now you have e.g. 10 references in the list and need to remove 8 of them. Thus you try to select them

    result: You cannot select more than one reference in the list, neither by pressing the Ctrl or Shift key or by mouse dragging etc. So you have to right-click on every reference to delete it -> this is very annoying and time consuming

    Attached is a screenshot as example. I need to delete there Face 11 to Face 17.

    This issue appears for all FEM reference lists (e.g. also for the FEM material).
    Tags: FEM
    Steps To Reproduce:
    Additional Information:
    Attached Files: FEM-Shell-reference-list.jpg (305,893 bytes) 2019-01-20 03:40
    https://tracker.freecad.org/file_download.php?file_id=2106&type=bug
    Notes
    (0012470)
    uwestoehr   
    2019-01-20 03:43   
    It would at least be helpful if pressing DEL would remove the references.
    (0012491)
    Kunda1   
    2019-01-22 23:36   
    @uwestoehr please follow the guidelines (enormous yellow banner at the top of the page) when opening tickets. There is no extensive FC version info, no forum thread. Please open a thread to discuss this with bernd, the FEM maintainer
    (0012500)
    uwestoehr   
    2019-01-23 23:31   
    > There is no extensive FC version info

    @Kunda1, I specified that I use version 0.18, see this bug report header. I also use the latest development snapshot as given in the yellow banner when reporting bugs.

    > no forum thread. Please open a thread to discuss this with bernd, the FEM maintainer.

    Sorry, but I don't have that much time. I reported a bug I saw and checked that it is not yet reported as best as possible. feel free to ignore my bug reports or close them immediately if you don't think it is a real bug.

    I am an Open Source software developer too and know that some bug reports are not valid, thus I checked carefully not to report already existing issues. But you cannot expect people to discuss at first in a forum - waiting for replies, respond, waiting again... So I collected all bugs I found and reported them that they are not forgotten. (I don't use FC regularly, maybe once a month.)
    (0012512)
    Kunda1   
    2019-01-25 17:22   
    My response 0003781:0012509

    Deferring to @berndhahnebach
    (0012525)
    berndhahnebach   
    2019-01-26 21:18   
    Hi uwe and welcome to FreeCAD FEM. I must admit you are right. All the reference shape gui work flow needs some love. It is on my TODO for a long time. But not in very front position ...

    cheers bernd
    (0012528)
    berndhahnebach   
    2019-01-26 21:28   
    (Last edited: 2019-01-26 21:28)
    related 0003783

    (0012530)
    uwestoehr   
    2019-01-27 04:02   
    Hi Bernd, thanks for having a look. I also found other FC issues and tried to go the way to open a forum discussion first. But whenever I want to post something, I only get a message
    "You cannot make another post so soon after your last."
    What Am I doing wrong? Why can't I post anything to the forum despite I successfully created and activated an account?
    (0012531)
    uwestoehr   
    2019-01-27 04:03   
    Hi Bernd, thanks for having a look. I also found other FC issues and tried to go the way to open a forum discussion first. But whenever I want to post something, I only get a message
    "You cannot make another post so soon after your last."
    What Am I doing wrong? Why can't I post anything to the forum despite I successfully created and activated an account?
    (0012532)
    wmayer   
    2019-01-27 13:39   
    > What Am I doing wrong? Why can't I post anything to the forum despite I successfully created and activated an account?

    After posting the very first time on the forum a moderator must approve your initial post. This is because there are a lot of spammers these days and this way a spammer cannot flood the forum with crap.
    (0012535)
    uwestoehr   
    2019-01-27 15:02   
    > After posting the very first time on the forum a moderator must approve your initial post.
    OK, but please inform new people about this. I did not get any information despite the senseless message that I cannot post soon again despite not a single post was yet made.
    I propose a message like this after pressing the first time Submit:
    "Thanks for your first post. To avoid spam the first post of new users will be reviewed by our maintainers. Until it was approved you cannot made further posts."
    Should I report this issue as a separate bug or post this in the forum?
    (0014943)
    uwestoehr   
    2020-10-24 21:57   
    Meanwhile the situation improved. On can now use DEL to delete references. However, selecting several references and deleting them at once does not yet work. I will have a look.
    (0016700)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5865.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3742 [FEM] Feature minor always 2018-12-19 15:53 2021-02-06 06:23
    Reporter: berndhahnebach Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FEM, make elmer writer fully compatipble with FreeCAD unit system
    Description: It seams Elmer solver uses SI units, which means meter. We gone use milli meter which works well but could result in some problems. There is a forum topic about this, see https://forum.freecadweb.org/viewtopic.php?f=18&t=32211

    Best would be if Elmer writer would use units, and the user could decide if he wants to write SI units or mm.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016686)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5851.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3706 [FEM] Feature minor N/A 2018-11-22 00:57 2021-02-06 06:23
    Reporter: berndhahnebach Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FEM, constraints, a very general constraint property setter
    Description: There are hundreds of FEM solvers and hundreds of constraint types. An general setter would allow to use FreeCAD for such solvers without supporting them in FreeCAD FEM.

    May be the FreeCAD FEM constraints could be based on such a setter?

    See forum https://forum.freecadweb.org/viewtopic.php?f=18&t=32120&start=10#p268044
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0014293)
    berndhahnebach   
    2020-03-26 13:23   
    this implements something in this regard ...

    https://forum.freecadweb.org/viewtopic.php?f=18&t=33124
    (0016673)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5838.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3633 [FEM] Feature minor N/A 2018-10-10 18:55 2021-02-06 06:23
    Reporter: berndhahnebach Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FEM, post processing, read, store and display cell (element) results
    Description: post processing, result data in integration points of elements

    see forum topics:

    - https://forum.freecadweb.org/viewtopic.php?f=18&t=32030
    - https://forum.freecadweb.org/viewtopic.php?f=24&t=31997#p266475
    - https://forum.freecadweb.org/viewtopic.php?f=18&t=30822
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0012035)
    berndhahnebach   
    2018-10-16 06:21   
    related https://forum.freecadweb.org/viewtopic.php?f=18&t=31499
    (0012184)
    berndhahnebach   
    2018-11-13 07:05   
    duplicate of
    (0014294)
    berndhahnebach   
    2020-03-26 19:41   
    related https://forum.freecadweb.org/viewtopic.php?f=18&t=29085&start=30
    (0014295)
    berndhahnebach   
    2020-03-26 19:43   
    related https://forum.freecadweb.org/viewtopic.php?f=18&t=30822&start=10
    (0014296)
    berndhahnebach   
    2020-03-26 19:49   
    related https://forum.freecadweb.org/viewtopic.php?f=18&t=29060
    (0016652)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5817.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3628 [FEM] Feature minor have not tried 2018-10-10 09:42 2021-02-06 06:23
    Reporter: berndhahnebach Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FEM, export vtk pipeline to vtk file format directly
    Description: some helpful links ...

    https://forum.freecadweb.org/viewtopic.php?f=18&t=31288&start=30#p261202

    https://github.com/FreeCAD/FreeCAD/blob/6178c795817e7f513c9ed1f5673565a4c17fdc5b/src/Mod/Fem/feminout/importVTKResults.py#L71

    https://github.com/FreeCAD/FreeCAD/blob/6178c795817e7f513c9ed1f5673565a4c17fdc5b/src/Mod/Fem/App/FemPostPipeline.h#L42-L68

    https://github.com/FreeCAD/FreeCAD/blob/6178c795817e7f513c9ed1f5673565a4c17fdc5b/src/Mod/Fem/App/FemPostPipelinePyImp.cpp#L40-L49
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016651)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5816.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3624 [FEM] Bug minor have not tried 2018-10-05 04:45 2021-02-06 06:23
    Reporter: berndhahnebach Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: new Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FEM, GUI, mesh VP, element colors
    Description: It seams setting element colors does not work as aspected in some cases.

    see https://forum.freecadweb.org/viewtopic.php?f=18&t=31123&start=30#p258911
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0012435)
    wmayer   
    2019-01-15 20:33   
    This fixes the colouring of the nodes:
    https://github.com/FreeCAD/FreeCAD/commit/bdbea25d0d7e00cad5d71184a63e9c9e270df2aa
    (0016650)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5815.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3622 [FEM] Feature feature always 2018-10-03 18:08 2021-02-06 06:23
    Reporter: berndhahnebach Platform:  
    Assigned To: berndhahnebach OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FEM, calculix, support analysis type 'no analysis' for model checking
    Description: https://forum.freecadweb.org/viewtopic.php?f=18&t=31303#p260032
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0012816)
    berndhahnebach   
    2019-03-01 15:23   
    https://github.com/FreeCAD/FreeCAD/commit/40d0db3

    but it needs to be added to the task panel too.
    (0016649)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5814.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3615 [FEM] Feature feature N/A 2018-09-25 18:42 2021-02-06 06:23
    Reporter: berndhahnebach Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FEM, post processing, integrate glyph filter implementation
    Description: forum topic:
    - https://forum.freecadweb.org/viewtopic.php?f=18&t=24637

    open issues:
    - https://forum.freecadweb.org/viewtopic.php?f=18&t=24637&start=20#p255599
    - https://forum.freecadweb.org/viewtopic.php?f=18&t=24637&start=20#p256037

    branch (will be rebased regulary):
    - https://github.com/berndhahnebach/FreeCAD_bhb/commits/fempostglyph

    the implementation is from user amstuff (does not rebase on master):
    - https://github.com/AMstuff/FreeCAD/commits/GlyphFilter
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016648)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5813.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3614 [FEM] Feature feature always 2018-09-25 18:19 2021-02-06 06:23
    Reporter: berndhahnebach Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FEM, GUI, mesh VP, highlight selected elements of a FEM mesh
    Description: selection of FEM mesh elements or even whole FEM meshes is possible, but they are not highligted.

    See forum topics:
    - https://forum.freecadweb.org/viewtopic.php?f=10&t=31150
    - https://forum.freecadweb.org/viewtopic.php?f=18&t=31123
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016647)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5812.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3612 [FEM] Feature minor always 2018-09-25 10:53 2021-02-06 06:23
    Reporter: berndhahnebach Platform:  
    Assigned To: berndhahnebach OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FEM, be able to run a analysis with a given CalculiX input file
    Description: see https://forum.freecadweb.org/viewtopic.php?f=18&t=31130&p=258442#p258421
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0012817)
    berndhahnebach   
    2019-03-01 15:27   
    https://github.com/FreeCAD/FreeCAD/commit/3f8c524609405fc5bce2a142f4049702b34300ed

    https://www.freecadweb.org/wiki/FEM_Tutorial_Python#Step_by_step

    it should work with this ... I need to test and than it could be closed.
    (0016646)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5811.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3375 [FEM] Feature feature always 2018-03-14 21:11 2021-02-06 06:23
    Reporter: HarryvL Platform: PC  
    Assigned To: OS: Ubuntu  
    Priority: normal OS Version: 16.04  
    Status: confirmed Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FEM, GUI, constraint force, scale factor
    Description: Object FemConstraintForce. See post:https://forum.freecadweb.org/viewtopic.php?f=18&t=27401

    Forces of equal size are displayed differently. Changing the Scale parameter in the FemConstraintForce object Data Panel has no effect.

    Displacement boundary conditions cannot be scaled at all and are sometimes so small that they are invisible for a model that fits the display window
    Tags:
    Steps To Reproduce: Always
    Additional Information: Version:

    OS: Ubuntu 16.04.4 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.13346 (Git)
    Build type: None
    Branch: master
    Hash: 22ee06de8441bfcc9fded2c6de4232d763fb11bc
    Python version: 2.7.12
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.1.0
    Locale: English/UnitedStates (en_US)
    Attached Files:
    Notes
    (0011780)
    berndhahnebach   
    2018-09-18 06:02   
    Mhh, since this was never really implemented it is more a feature request, IMHO.
    (0016603)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5768.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3315 [FEM] Bug minor always 2018-01-16 03:38 2021-02-06 06:23
    Reporter: HarryvL Platform: Oracle VM  
    Assigned To: berndhahnebach OS: Ubuntu  
    Priority: normal OS Version: 16.04.3 LTS  
    Status: assigned Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FEM, mesh groups only work after calling gmsh again
    Description: After adding mesh groups the mesh needs to be regenerated by GMSH for the Export INP option to export them properly.
    Tags: FEM
    Steps To Reproduce: 1) generate mesh
    2) add mesh groups
    3) export to INP
    gives wrong results
    1) generate mesh
    2) add mesh groups
    3) export to INP
    4) generate mesh
    gives right results
    Additional Information:
    Attached Files:
    Notes
    (0010771)
    HarryvL   
    2018-01-16 17:54   
    OS: Ubuntu 16.04.3 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.12960 (Git)
    Build type: None
    Branch: master
    Hash: b6304d16a77f65f94aa5ec79f69688be61a42961
    Python version: 2.7.12
    Qt version: 4.8.7
    Coin version: 4.0.0a
    OCC version: 7.1.0
    Locale: English/UnitedStates (en_US)
    (0010824)
    berndhahnebach   
    2018-01-23 17:02   
    It's not a bug it's a feature. ATM FreeCAD FEM does not search for the group data inside the mesh. This is on my LongTermToDo. ATM we gone use GMSH to generate groups. That is why groups can only be used with GMSH mesh. That is why elmer FEM needs a GMSH mesh. That is why with groups one needs to remesh.

    I will close this. We may open a feature to extend the FEMMesh Python API in the regard of creating groups from an existing mesh by searchting the mesh for the approbriate data. It is not a big deal. Anything is there in either SMESH or FreeCAD FEM.

    Bernd
    (0010825)
    berndhahnebach   
    2018-01-23 17:03   
    We may add an print or message box after a change on a group as a hint for the user that he needs to remesh. I will leave the ticked open.

    bernd
    (0013378)
    Kunda1   
    2019-07-23 23:43   
    Discussion thread: https://forum.freecadweb.org/viewtopic.php?f=18&t=37937
    (0016594)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5759.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3145 [FEM] Feature minor have not tried 2017-07-30 19:06 2021-02-06 06:23
    Reporter: berndhahnebach Platform:  
    Assigned To: berndhahnebach OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FEM, VTK post processing, data at point filter, some issues
    Description: issues to be fixed before merge into master:
    - the marker is not saved to the document, or not loaded from the document
    - if the point for result plot is changed, the marker is not deleted at the old point.-
    - probably a crash ? ... https://forum.freecadweb.org/viewtopic.php?f=18&t=20801&start=30#p184399
    - svg icon ... https://forum.freecadweb.org/viewtopic.php?f=34&t=31029
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0011782)
    berndhahnebach   
    2018-09-18 06:15   
    it has been merged into master, but there are a few problems anyway. I will have a look if i can find this forum posts. As long as no new is opened I leave this open.
    (0016554)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5719.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3126 [FEM] Feature feature have not tried 2017-07-13 21:39 2021-02-06 06:23
    Reporter: berndhahnebach Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FEM, post processing, results, sectional forces for line and shell meshes
    Description: section forces:
    - add them to the result object
    - add the possibility to create them by the solver (solver input file)
    - read them and store them in the result object
    - post process them
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0011366)
    berndhahnebach   
    2018-06-08 08:21   
    AFAIK reaction forces can be saved easily in dat file. But they would not be imported in FreeCAD ATM.
    (0011771)
    berndhahnebach   
    2018-09-18 05:45   
    (Last edited: 2018-09-18 05:46)
    line meshes:
    https://forum.freecadweb.org/viewtopic.php?f=18&t=18273
    https://forum.freecadweb.org/viewtopic.php?t=19428#p150848
    https://forum.freecadweb.org/viewtopic.php?f=18&t=22383

    (0011772)
    berndhahnebach   
    2018-09-18 05:46   
    (Last edited: 2018-09-18 05:46)
    graphical result view for line meshes: 0002950

    (0011773)
    berndhahnebach   
    2018-09-18 05:47   
    shell meshes:
    http://forum.freecadweb.org/viewtopic.php?f=18&t=18125#p142233
    (0011784)
    berndhahnebach   
    2018-09-18 06:22   
    related 0002934
    (0013467)
    berndhahnebach   
    2019-08-26 12:19   
    section forces are possible on solid meshes too: https://forum.freecadweb.org/viewtopic.php?f=18&t=38575
    (0016553)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5718.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3057 [FEM] Feature feature N/A 2017-05-28 22:08 2021-02-06 06:23
    Reporter: berndhahnebach Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FEM, console output, get rid of so much console output
    Description: There is much console output in FEM especially on
    - ccx inp file writing
    - gmsh meshing
    - unit test

    there should be many of them be moved to loggin instead of prints ...

    FreeCAD.Console.PrintError('error\n')
    FreeCAD.Console.PrintMessage('message\n')
    FreeCAD.Console.PrintLog ('logging\n')
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016537)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5702.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3056 [FEM] Feature feature have not tried 2017-05-28 21:45 2021-02-06 06:23
    Reporter: berndhahnebach Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FEM, 1D beam analysis example for Start WB and wrong results for 1D beam
    Description: The start wb only has FEM 3D and 2D analysis example of CalculiX cantilever. This is because the 1D example gives results an engineer would not expect. At the moment no example is added but the 1D beams are still supported.

    I opened the bug report to have a reference. I have been in contact with the developer of CalculiX, the FEM solver we use. There seems to be some mathematical reasons for the problem.

    Everything could be read at the forum topic:
    https://forum.freecadweb.org/viewtopic.php?f=18&t=16044
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0014025)
    berndhahnebach   
    2020-01-09 10:59   
    related: https://forum.freecadweb.org/viewtopic.php?f=18&t=42294
    (0016536)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5701.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3055 [FEM] Feature feature N/A 2017-05-27 21:22 2021-02-06 06:23
    Reporter: berndhahnebach Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FEM, scripting FEM module without the need of adding document objects
    Description: If one would like to script with FEM he has to add document object for each instance he would work with. If one works with Shapes or Meshes or FEMMeshes one does not need to add a document object for each instance he would work with.

    The original idea was from @ickby. I didn't even know what he was talking about when he came up with it but he explained it and YEAH we sure need it. If you get it it is just obvious we need this !

    Ahh Forum posts:
    https://forum.freecadweb.org/viewtopic.php?f=18&t=16944#p134521
    https://forum.freecadweb.org/viewtopic.php?f=18&t=16944&start=10#p134582
    Tags: python
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016535)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5700.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3049 [FEM] Feature feature N/A 2017-05-26 21:40 2021-02-06 06:23
    Reporter: berndhahnebach Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FEM, mesh, support for meshing quads and hexa element for FEM
    Description: At the moment the mesher in FEM only supports Tetraeder volume elements and triangle face elements. Both the SMESH netgen and GMSH mesher support meshing quad and hexa elements. Thus it would be great if FreeCAD would do too.

    https://forum.freecadweb.org/viewtopic.php?f=18&t=20796
    https://forum.freecadweb.org/viewtopic.php?f=22&t=20351
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0012223)
    berndhahnebach   
    2018-11-26 02:40   
    https://forum.freecadweb.org/viewtopic.php?f=18&t=32106&start=10#p269334
    (0016533)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5698.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2988 [FEM] Bug minor always 2017-03-28 06:08 2021-02-06 06:23
    Reporter: kkremitzki Platform:  
    Assigned To: berndhahnebach OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FEM, GUI, Netgen and GMSH FEM mesh creation buttons don't clean up on error or cancel
    Description: Currently Netgen is disabled on my build, so when I click on e.g. a Part Cube, I get a "Meshing failure" error, and yet a mesh is dumped into my active FEM Analysis.

    Similarly, if I were to click the button to create a GMSH mesh instead, but decided I didn't want one and hit Cancel, I would find my Analysis with cluttered up with a useless FEM Mesh that should have been cleaned up by its creating code.
    Tags:
    Steps To Reproduce: 1. Part WB > Part Cube.
    2. FEM WB > Create Analysis.
    3. Select cube. Create Netgen or GMSH mesh button. Observe error or hit cancel. Note the extra mesh in Analysis object.
    Additional Information: OS: Linux
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.17.10653 (Git)
    Build type: Release
    Branch: master
    Hash: 64754a655e003db16161b58d04febb19a87bdb3d
    Python version: 2.7.13
    Qt version: 4.8.7
    Coin version: 3.1.3
    OCC version: 7.1.0
    Attached Files:
    Notes
    (0008729)
    berndhahnebach   
    2017-03-29 11:49   
    For sure a clean mesh is not useless! The clean mesh has the adjustments (properties) to create the mesh. Quite a few times in FEM we gone post a file with a mesh object with the properties to create the mesh and the mesh is cleared. There is even a tool to clear a mesh ... Create a GMSH mesh object --> create a mesh --> leave the mesh object --> select the mesh object --> right click --> clear mesh --> clears the mesh but keeps the mesh object and its properties

    bernd
    (0008741)
    kkremitzki   
    2017-03-31 01:58   
    @berndhahnebach That's a good point, and I think that workflow should be supported. In the case of the disabled netgen mesh, though, it really should not be getting created. Although the user could indeed adjust the parameters of the mesh in the data view, you can't even test the mesh/FEM setup if you wanted to. In that instance, although it's possible someone would want to prepare a mesh for someone else to use, I think it's much more appropriate to just clean up what's left on an error, since that is much more likely.

    Perhaps a better way to support what you're describing is a checkbox at the top of the mesh task panel: "Store parameters without (re)creating mesh"

    Then, clicking 'Ok', 'Apply', and 'Cancel' can be made to behave in a standard way while still supporting the option to prepare FEM files for other people without needing to create the mesh.
    (0009160)
    berndhahnebach   
    2017-05-26 21:48   
    (Last edited: 2017-05-26 21:50)
    https://forum.freecadweb.org/viewtopic.php?f=18&t=21770

    It still is on my list to have a look at this.


    https://github.com/kkremitzki/FreeCAD/tree/fem_gmsh_on_ok
    https://github.com/kkremitzki/FreeCAD/tree/fem_gmsh_on_ok_2

    (0011785)
    berndhahnebach   
    2018-09-18 06:24   
    I will try to have a look at this.
    (0016526)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5691.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2969 [FEM] Feature feature have not tried 2017-03-15 20:14 2021-02-06 06:23
    Reporter: berndhahnebach Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FEM, GUI, mesh VP, faces of all elements should be shown, not only the faces of the volume elements
    Description: If a FEM mesh has mixed meshed geometry for example meshed solids and meshed faces, only the faces of the volume elements are shown. The faces of the shell elements are missing.

    See forum topic:
    - https://forum.freecadweb.org/viewtopic.php?f=4&t=21233#p165189 and following posts

    and related:
    - in post https://forum.freecadweb.org/viewtopic.php?f=4&t=21233&start=10#p165575 is explained how to create such mesh
    - might be interested in the regard of creating such meshes too ... https://forum.freecadweb.org/viewtopic.php?f=8&p=175915#p175895
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0008808)
    Kunda1   
    2017-04-28 16:18   
    bernd wrote:
    as a note, lonley nodes (not belonging to an element) or nodes which belong to a face or edge but not to a volume are not shown too ...

    see topic: http://forum.freecadweb.org/viewtopic.php?f=18&t=21571#p168066
    (0009167)
    berndhahnebach   
    2017-05-27 10:14   
    (Last edited: 2017-06-04 09:40)
    https://github.com/berndhahnebach/FreeCAD_bhb/commits/femvolumeshell

    Works but is more or less a hack. It needs some love before a merge could be done.

    Edit: branch has moved see Note later in issue

    (0009173)
    berndhahnebach   
    2017-05-28 01:11   
    At the moment it works as follows in Master 0.17.11160

    If the mesh only has edges the edges and the nodes of the edges are shown
    If the mesh has faces or/volumens the faces and the faces of the volumes are shown as well as the nodes of the faces and the nodes of the volumes are shown.
    Means no lonley nodes.
    (0009174)
    berndhahnebach   
    2017-05-28 01:13   
    (Last edited: 2017-05-28 01:39)
    It could work this way:

    Show all Nodes, Edgeelements, Faceelements and Volumeelements.

    This way we would have all nodes, all edges (including the edges of the facecreation and volumecreation), all faces (including the faces of volumecreation).

    Add 3 Attributes to the ViewProvider to tongle on/off the elements
    - edges of the mesh
    - faces of the mesh
    - faces of volumes the mesh

    Add the two missing Display Modes to the MeshViewProvider:
    - Nodes and Wireframe
    - Nodes and Faces

    (0009176)
    berndhahnebach   
    2017-05-28 01:16   
    (Last edited: 2017-06-04 09:40)
    updated the branch https://github.com/berndhahnebach/FreeCAD_bhb/commits/femvolumeshell

    It shows all nodes, edges, faces, faces of volumes

    But still it is some sort of a hack. It comments lots of code because it just iterates above all and shows it.

    I'm not yet convinced to delete all this code. I need to have a closer look. Means the branch is usable to test mixed meshes but not ready to merge into master.

    I may implement the two missing display modes. If I'm gone do this I need to digg into the MeshViewProvider and can fix the other too.

    bernd

    Edit: branch has moved see Note later in issue

    (0009282)
    berndhahnebach   
    2017-06-04 09:41   
    new branch together with mixed mesh analysis ...
    https://github.com/berndhahnebach/FreeCAD_bhb/commits/femmixedmeshes
    (0016524)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5689.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2950 [FEM] Feature feature always 2017-03-06 19:05 2021-02-06 06:23
    Reporter: berndhahnebach Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FEM, GUI, post processing, graphical output of line mesh results
    Description: See forum topics:

    graphical:
    https://forum.freecadweb.org/viewtopic.php?f=18&t=21013
    https://forum.freecadweb.org/viewtopic.php?f=18&t=20076&start=40#p162519

    section forces
    see issue https://www.freecadweb.org/tracker/view.php?id=3126
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016521)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5686.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2934 [FEM] Feature feature always 2017-03-01 13:00 2021-02-06 06:23
    Reporter: berndhahnebach Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FEM, post processing, results, reaction forces
    Description: reaction forces:
    - add them to the result object
    - add the possibility to create them by the solver (solver input file)
    - read them and store them in the result object
    - post process them

    forum topic:
    http://forum.freecadweb.org/viewtopic.php?f=18&t=20664
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0008654)
    berndhahnebach   
    2017-03-19 21:21   
    related post but in German:
    https://forum.freecadweb.org/viewtopic.php?p=166225#p166225
    (0008728)
    berndhahnebach   
    2017-03-29 11:45   
    interesting post in this regard:
    http://forum.freecadweb.org/viewtopic.php?p=167047#p167047
    (0011783)
    berndhahnebach   
    2018-09-18 06:21   
    related 0003126
    (0013146)
    berndhahnebach   
    2019-06-06 07:14   
    another forum topic: https://forum.freecadweb.org/viewtopic.php?f=18&p=312643#p312643
    (0016519)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5684.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2547 [FEM] Feature feature always 2016-05-12 17:36 2021-02-06 06:23
    Reporter: HoWil Platform:  
    Assigned To: OS:  
    Priority: normal OS Version:  
    Status: confirmed Product Version: 0.16  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: FEM, GUI, all TaskPanels, input from spreadsheet-Data in expressions
    Description: All values dialogs in the FEM WB do not use input from spreadsheet-Data. The part-design WB does accept them and it would be great if FEM would do also. For instance it would help if in the FEM-mesh dialog one could specify a max. size value derived form a spreadsheet value used in part design.
    Tags: #lowhangingfruit, expressions, FEM, GUI, spreadsheet
    Steps To Reproduce:
    Additional Information:
    Attached Files: Capture.PNG (75,089 bytes) 2016-05-13 13:37
    https://tracker.freecad.org/file_download.php?file_id=1262&type=bug
    Notes
    (0007089)
    user2853   
    2016-05-13 13:38   
    It's there in 0.17
    (0008397)
    Kunda1   
    2017-02-21 16:08   
    > It's there in 0.17
    @sgrogan what do you mean ?
    (0008400)
    user2853   
    2017-02-22 00:05   
    I meant the feature exists in 0.17. But re-reading more carefully it exists in the property editor not the creation dialog. So the feature request stands. The work around is to create the feature and then edit the numerical property from the data tab. I think it should be possible to do directly from python but I didn't test.
    (0009495)
    HoWil   
    2017-06-23 20:28   
    Is there a reason why my screenshot was deleted?
    (0009500)
    Kunda1   
    2017-06-24 01:14   
    @HoWil yes, because it wasn't good enough... j/k
    Real reason: recently when we restored the tracker from backup many attachments didn't make it.
    (0011793)
    berndhahnebach   
    2018-09-18 15:51   
    It would be nice to have. But in my ToDo this is for sure some piece away from the beginning.
    (0016490)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5655.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4126 [Sketcher] Bug major always 2019-09-13 10:35 2021-02-06 05:55
    Reporter: baltic Platform: 64  
    Assigned To: OS: Ubuntu  
    Priority: normal OS Version: 18.04  
    Status: new Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: 0 length lines in sketch introduce bugs at Part-> Revolve time
    Description: Trying to Part->Revolve a sketch, which contains 0 length lines produces wrong results.
    And Validate Sketch tool does not catch 0 length lines.
    Tags:
    Steps To Reproduce: Create a simple sketch in XY plane like that:

    img here...

    On the top part of it add 2 fillets:

    img here...

    Constrain their radiuses to 1mm

    img here...

    Constrain the thickness of the wall to 2mm

    img here...

    Now you effectively have 0 length line between the 2 arcs.
    When you rotate it through Part->Revolve tool around Y axis, you get a non hollow object:

    img here...

    But it supposed to be hollow. When you delete the 0 length line from sketch, the tool works correct.
    Additional Information: OS: Ubuntu 18.04.3 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.16131 (Git) AppImage
    Build type: Release
    Branch: (HEAD detached at 0.18.3)
    Hash: 3129ae4296e40ed20e7b3d460b86e6969acbe1c3
    Python version: 3.6.7
    Qt version: 5.6.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/UnitedStates (en_US)


    forum link
    Attached Files: test.FCStd (5,720 bytes) 2019-09-13 10:35
    https://tracker.freecad.org/file_download.php?file_id=2326&type=bug
    bug3.png (36,396 bytes) 2019-09-14 17:25
    https://tracker.freecad.org/file_download.php?file_id=2335&type=bug
    bug4.png (38,528 bytes) 2019-09-14 17:25
    https://tracker.freecad.org/file_download.php?file_id=2336&type=bug
    bug5.png (34,099 bytes) 2019-09-14 17:25
    https://tracker.freecad.org/file_download.php?file_id=2337&type=bug
    bug1-2.png (412,542 bytes) 2019-09-14 18:07
    https://tracker.freecad.org/file_download.php?file_id=2338&type=bug
    bug2-2.png (400,067 bytes) 2019-09-14 18:07
    https://tracker.freecad.org/file_download.php?file_id=2339&type=bug
    bug3-2.png (407,808 bytes) 2019-09-14 18:07
    https://tracker.freecad.org/file_download.php?file_id=2340&type=bug
    bug4-2.png (435,477 bytes) 2019-09-14 18:07
    https://tracker.freecad.org/file_download.php?file_id=2341&type=bug
    bug5-2.png (361,448 bytes) 2019-09-14 18:07
    https://tracker.freecad.org/file_download.php?file_id=2342&type=bug
    Notes
    (0013593)
    openBrain   
    2019-09-13 17:21   
    According forum, community proposal is to add a tool in ValidateSketch to find/fix this 0-length lines.
    (0013600)
    baltic   
    2019-09-14 18:07   
    Original ones, instead of scaled down copies
    (0016821)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5987.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4538 [Sketcher] Bug minor always 2021-01-17 20:17 2021-02-06 05:55
    Reporter: chrisb Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: <!--ATTENTION:
    COMPLETELY ERASE THIS AFTER PASTING YOUR
    Help > About FreeCAD > Copy to clipboard
    NOTE: just the snippet alone will do without anything else included.
    The ticket will not be submitted without it.
    -->
    Summary: Redundant constraint is ignored by the solver
    Description: The sketch from this forum discussion shows no error on opening but when the 25.7mm constraint is removed it shows an overconstraint error.

    My guess is that the user had ignored the message and continued constraining.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016983)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6151.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4530 [Sketcher] Feature minor N/A 2021-01-07 17:55 2021-02-06 05:55
    Reporter: abdullah Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: <!--ATTENTION:
    COMPLETELY ERASE THIS AFTER PASTING YOUR
    Help > About FreeCAD > Copy to clipboard
    NOTE: just the snippet alone will do without anything else included.
    The ticket will not be submitted without it.
    -->
    Summary: Explore geometry element based block constraint
    Description:
    When implementing the new Block constraint, it became clear the constraint has potential for blocking individual elements of a geometry (none, start, end, mid) as opposed to the whole geometry.

    A cost-benefit analysis is needed for this possibility of extension, which may make sense or not.

    First the current new Block constraint needs to settle.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016979)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6147.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4519 [Sketcher] Feature minor have not tried 2020-12-24 11:49 2021-02-06 05:55
    Reporter: abdullah Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: <!--ATTENTION:
    COMPLETELY ERASE THIS AFTER PASTING YOUR
    Help > About FreeCAD > Copy to clipboard
    NOTE: just the snippet alone will do without anything else included.
    The ticket will not be submitted without it.
    -->
    Summary: Formalise the Sketcher solve(), update and signaling
    Description:
    In the meantime, rethink the solverNeedsUpdate mechanism, and maybe work at solver level with non-cloned geometry pointers.

    Rethink geometry and constraints update before starting dragging operation.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016974)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6141.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4512 [Sketcher] Feature minor N/A 2020-12-16 15:24 2021-02-06 05:55
    Reporter: abdullah Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: <!--ATTENTION:
    COMPLETELY ERASE THIS AFTER PASTING YOUR
    Help > About FreeCAD > Copy to clipboard
    NOTE: just the snippet alone will do without anything else included.
    The ticket will not be submitted without it.
    -->
    Summary: Alternative constructions methods for B-Spline
    Description:
    Look at this post from Werner:
    https://forum.freecadweb.org/viewtopic.php?f=10&t=51716&start=60#p456903

    Look at this user example of DIY poly-bezier:
    https://forum.freecadweb.org/viewtopic.php?p=460270#p460270
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016972)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6139.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4419 [Sketcher] Bug minor always 2020-08-18 15:36 2021-02-06 05:55
    Reporter: chrisb Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: macOS High Sierra (10.13)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.22246 (Git)
    Build type: Release
    Branch: master
    Hash: abd18ff88f7682e9b1160c36bb785b14a33473ef
    Python version: 3.8.5
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: C/Default (C)
    Summary: Trim of ellipse creates invalid constraints
    Description: As the title says, trim of ellipse creates invalid constraints, sometimes sort of unattended by the solver.
    See german forum post and
    forum post.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016933)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6100.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4398 [Sketcher] Feature minor N/A 2020-07-03 18:31 2021-02-06 05:55
    Reporter: abdullah Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: N/A
    Summary: Improve the sketcher clone tool
    Description: Chrisb describes here an improved version of the sketcher clone tool:
    https://forum.freecadweb.org/viewtopic.php?f=10&t=48268#p413637
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016920)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6087.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4292 [Sketcher] Bug minor always 2020-03-20 13:52 2021-02-06 05:55
    Reporter: chrisb Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: macOS High Sierra (10.13)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.20052 (Git)
    Build type: Release
    Branch: master
    Hash: 6291921e9abe737e4440ff5814ca58547defadef
    Python version: 3.8.2
    Qt version: 5.12.5
    Coin version: 4.0.0
    OCC version: 7.4.0
    Locale: C/Default (C)
    Summary: Dimension values are displayed from reverse
    Description: See the file attached to forum discussion. Double clicking on "Hole Base" shows the numbers from behind.
    This vanishes as soon as something is changed in the sketch, e.g. a dimension is added. But will reoccur on close/reopen

    Note that the sketches do not belong to the body.
    The phenomenon vanishes if the loft is deleted and the sketches are shown in the tree on top level again.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0014288)
    chrisb   
    2020-03-25 06:14   
    Here is another one. It is again a sketch used for a feature inside of the body, while the sketch lives outside.
    (0014289)
    leoheck   
    2020-03-25 16:12   
    Here is a second file with the same issue.
    https://forum.freecadweb.org/viewtopic.php?p=380205#p380152

    The issue does not happen in 0.18.4 but does happen in 0.19.

    OS: Ubuntu 19.10 (ubuntu:GNOME/ubuntu)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.
    Build type: Release
    Python version: 3.7.3
    Qt version: 5.12.2
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/United States (en_US)
    (0014290)
    leoheck   
    2020-03-25 16:18   
    The Sketch is inside the Body at least looking from the Model view.

    The Dependency graph tells a different story. The revolution is inside the Body and the Sketch is outside of it (does not represent what the Model menu shows)

    However, version FreeCad 0.18.4 interprets the Sketch correctly and the 0.19 shows the values mirrored.
    (0016874)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 6040.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4173 [Sketcher] Feature minor always 2019-10-24 10:01 2021-02-06 05:55
    Reporter: chrisb Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information: OS: macOS High Sierra (10.13)
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.19.18589 (Git)
    Build type: Release
    Branch: master
    Hash: 3500451a040989d00693eab85b2a7c13ce4dad67
    Python version: 3.7.3
    Qt version: 5.12.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: English/Germany (en_DE)
    Summary: Error in Sketch not showing in tree nor solver messages
    Description: In this forum post there is a model which has a sketch containing errors. The errors come from references to external geometry.

    The error shows in report view on a recompute.
    It does not show in the tree with the well known exclamation mark and it does not show in the solver messages.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016832)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5998.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    4053 [Sketcher] Feature feature have not tried 2019-07-12 06:36 2021-02-06 05:55
    Reporter: chrisb Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: CarbonCopy should use names of constraints if available.
    Description: Instead of referencing dimensions by their constraint number, CarbonCopy should use the names where the user provided them.
    See forum discussion
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016799)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5965.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3863 [Sketcher] Bug minor always 2019-02-25 19:45 2021-02-06 05:55
    Reporter: openBrain Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Point-on-line not correctly auto-removed when redundant
    Description: When "Auto Remove Redundants" is enabled, a "Point-on-line" constraint isn't removed when redundant if the superseding constraint is applied in continue mode. Solver displays an error message about redundancy instead. Everything becomes OK if a sketch item is dragged.
    It works well in preselect mode.
    It seems that this faulty behavior is specific to this "Point-on-line" constraint.
    Tags:
    Steps To Reproduce:
    1. Create a new sketch and check "Auto Remove Redundants" is enabled
    2. Create 2 lines (let's call them A & B, and their respective endpoints x.1 & x.2)
    3. Select line A and endpoint B.1, then add a Point-on-line constraint
    4. (Preselect mode): Select endpoints A.1 & B.1, then add a Coincident constraint => Everything's fine, Point-on-line constraint is removed
    5. Come back to the state at the end of step 3
    6. (Postselect mode): Select Coincident constraint (w/o anything selected), then click on A1 & B1 => Ouch ! Sketch isn't updated and solver displays "Sketch contains redundant constraints". Now just drag any line/endpoint with the mouse => Sketch is now updated and redundant constraint is removed
    Additional Information: Forum thread : https://forum.freecadweb.org/viewtopic.php?f=3&t=34451
    ---
    OS: Ubuntu 18.04.2 LTS
    Word size of OS: 64-bit
    Word size of FreeCAD: 64-bit
    Version: 0.18.15860 (Git)
    Build type: Release
    Branch: master
    Hash: 3b708c7f84b0425076b520e1d95627b20fd75fe0
    Python version: 2.7.15rc1
    Qt version: 5.9.5
    Coin version: 4.0.0a
    OCC version: 7.3.0
    Locale: French/France (fr_FR)
    Attached Files:
    Notes
    (0016722)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5887.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3743 [Sketcher] Feature feature always 2018-12-20 00:15 2021-02-06 05:55
    Reporter: chrisb Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Control log output of solver
    Description: Forum discussion.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016687)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5852.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3718 [Sketcher] Feature feature always 2018-12-08 14:22 2021-02-06 05:55
    Reporter: abdullah Platform:  
    Assigned To: abdullah OS:  
    Priority: low OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Block constraint does not work on GeomPoints
    Description:
    Not sure if it should or not. As block constraint should be reviewed because it seems to be possible to improve it, I put this here to remember to take a look.

    Forum:
    https://forum.freecadweb.org/memberlist.php?mode=viewprofile&u=8738
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016679)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5844.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3708 [Sketcher] Feature feature N/A 2018-11-24 20:39 2021-02-06 05:55
    Reporter: normandc Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Add an Offset tool to the Sketcher
    Description: Offset is an essential tool of sketching. The offset tool should minimally work on lines, arcs, circles, and polylines made of lines and arcs. Making it work on complex curves (conics, B-splines) may prove difficult and be put aside for the initial implementation. Geometric constraints should be automatically added (coincident constraints for arcs, parallel constraints for lines, add appropriate constraints for polylines), as well as a distance constraint defining the offset value.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0012227)
    abdullah   
    2018-11-27 14:33   
    Offset curves will be implemented for all existing geometry in v0.19. I am uncertain ATM how to treat constraints though. I will definitely start a thread on this at the beginning of the v0.19 development cycle.
    (0012228)
    abdullah   
    2018-11-27 14:38   
    I realise now that you refer to the constraints making the offset. We do not need those constraints. An offset curve, which exist in OCC, is defined as a point on curve A plus a vector perpendicular to the curve on the plane (there is a vector product involved with the normal of the plane). Something like: Po(u)=P(u)+ alpha*(t x n).

    Let's discuss it anyway in due time (the sooner v0.18 gets release, the sooner the v0.19 development cycle starts)...
    (0013586)
    Kunda1   
    2019-09-12 21:28   
    Discussion thread: https://forum.freecadweb.org/viewtopic.php?f=8&t=39269
    (0014360)
    Kunda1   
    2020-04-22 11:12   
    Other discussion threads:
    "Sketch offset tool"
    "Feature requests: Enabling FreeCAD for sewing pattern making"
    (0016674)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5839.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3684 [Sketcher] Feature minor N/A 2018-11-12 13:27 2021-02-06 05:55
    Reporter: abdullah Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Support for trimming arcs of hyperbola and arcs of parabola
    Description: It is not supported yet, so support it.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016670)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5835.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3682 [Sketcher] Feature minor have not tried 2018-11-11 06:20 2021-02-06 05:55
    Reporter: abdullah Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Sketch Analysis new tests
    Description:
    Automatic detection of dimensions dynamic range in a sketch, in order to automatically drive the tolerance of the missing constraint detection.

    Make Roland run in a separate thread for automatic detection.

    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016669)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5834.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3681 [Sketcher] Feature minor N/A 2018-11-11 05:34 2021-02-06 05:55
    Reporter: abdullah Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Valid profile validation at sketch exit
    Description: Work out a final check on exit, in order to get confirmation on exiting edit mode that the user intends to have an "open" profile.

    Rationale:
    - 99% of the profiles must be extrudable
    - 1% may be open, like paths to sweep.

    Benefit:
    - Increase productivity by avoiding to have to come back to the Sketcher.
    - Better detection of bugs relating to closed profiles that are not so detected.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0012333)
    luchete80   
    2018-12-23 02:09   
    Hi, i think this could be shown by darkening the profile one is closed, like in new solidworks versions. Just an idea. I'm begining to study source in order to try to do at least something about it. Regards!
    (0016668)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5833.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3671 [Sketcher] Feature minor N/A 2018-11-05 19:03 2021-02-06 05:55
    Reporter: abdullah Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Sketcher Analysis interface improvements
    Description:
    Werner's comments on PR 0001554:

    It's indeed a bit odd to have many new methods added to SketchObject just to have a convenient Python interface. Since the "analyser" member doesn't do anything else and to keep things a bit cleaner you can:

        keep the functions of SketchObjectPy but create each time a new instance of SketchAnalysis when one of these Python functions is invoked. This way you can remove the analyser member from SketchObject and all the methods. Also, this reduces possible side-effects in case of consecutive calls of validation functions unless you explicitly need this. But then it suffices to add a single method to SketchObject to return the SketchAnalysis instance.

        instead of putting the validation functions to SketchObjectPy you can create the class SketchAnalysisPy. In the long term this might be the better option since many new methods could be added. In order to invoke the validation functions from Python we have to add a single method to SketchObject(Py) to create and return a SketchAnalysis instance.

    Nevertheless, I am going to merge the PR now and things can still be changed at a later time.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016665)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5830.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3668 [Sketcher] Feature minor N/A 2018-11-03 13:16 2021-02-06 05:55
    Reporter: abdullah Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Implement offset curves in the sketcher
    Description: Never realised how useful they may become.
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0012477)
    chrisb   
    2019-01-21 17:38   
    Is this a doublette of 3708?
    (0016663)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5828.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3667 [Sketcher] Bug minor always 2018-11-02 00:45 2021-02-06 05:55
    Reporter: chrisb Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: wrong normals of tangents of ellipses
    Description: The normal of an arc which is tangent to an ellipse is not calculated correctly. Seen when investigating filleting ellipse-ellipse intersections.
    forum discussion
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016662)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5827.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3660 [Sketcher] Feature minor N/A 2018-10-29 10:45 2021-02-06 05:55
    Reporter: abdullah Platform:  
    Assigned To: abdullah OS:  
    Priority: none OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Infinite lines in Sketcher
    Description: Consider the impact of infinite lines in the sketcher vs its convenience.

    This can be effected in several ways, from including a new geometric type, to introducing a new constraint to constraint unused DoFs of an element.

    Just see if it makes sense within the whole FC.

    https://forum.freecadweb.org/viewtopic.php?f=8&t=31854&p=265469#p265439
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0012116)
    normandc   
    2018-10-30 02:24   
    I have no objection to it, but I hope you still allow construction lines to have finite length as what we have now. IMO seemingly infinite lines would clutter a sketch real fast.
    (0016660)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5825.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3649 [Sketcher] Bug tweak always 2018-10-24 08:33 2021-02-06 05:55
    Reporter: chrisb Platform:  
    Assigned To: abdullah OS:  
    Priority: low OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Improve handling of block constraint if dimensional constraints are involved
    Description: If a block constraint is applied after a dimensional constraint it is possible to change the value of the dimension but the block constraint prohibits the change. Such a sketch looks inconsistent.
    This could be solved e.g. by
    - appropriate solver message
    - notify the user
    - change the dimensional constraint to a driven (blue) one

    See forum discussion
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0012109)
    abdullah   
    2018-10-28 14:33   
    Consider making the dimensional constraints reference and moving them after the block constraint. This combination should trigger a solver conflict message if afterwards the user actively tries to change it.
    (0016658)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5823.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3438 [Sketcher] Feature feature have not tried 2018-04-21 10:30 2021-02-06 05:55
    Reporter: chrisb Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.18  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Show in Sketcher if the sketch is closed
    Description: It would be helpful if a closed sketch is displayed in a different color.
    Forum discussion
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016619)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5784.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    3110 [Sketcher] Feature minor N/A 2017-07-01 08:45 2021-02-06 05:55
    Reporter: normandc Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.17  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Sketcher: add support of relevant constraints to B-splines
    Description: The current implementation of B-splines only support constraints on the B-spline vertices. It would be useful to use other constraints as well (point on object, tangent, perpendicular on the curve).
    Tags: b-splines, constraints
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0012229)
    JulianTodd   
    2018-11-29 11:14   
    Back-link to relevant forum topic https://forum.freecadweb.org/viewtopic.php?f=10&t=28896

    Can this be broken down into two parts?

    (1) BSpline is immutable and the other simpler geometry is forced to conform to it -- eg lines are forced equal length or forced perpendicular at point of intersection while the BSpline remains constant.

    (2) BSpline can be fully effected and changed by the constraints.

    I am looking to use the Length Equality between line and BSpline, which should be the easiest thing, it has to measure it and then apply it.
    (0016551)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5716.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2078 [Sketcher] Feature minor have not tried 2015-05-01 10:17 2021-02-06 05:55
    Reporter: wmayer Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version:  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Support to apply equality constraint on angles
    Description: The related forum post (in German):
    http://forum.freecadweb.org/viewtopic.php?f=13&t=10765
    Tags: constraints
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016462)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5627.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    2052 [Sketcher] Feature minor N/A 2015-04-13 10:39 2021-02-06 05:55
    Reporter: r-frank Platform: Windows  
    Assigned To: abdullah OS: Windows 7  
    Priority: normal OS Version: 64 bit  
    Status: assigned Product Version: 0.14  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Add Chamfer Edge-Tool
    Description: Like the already existing "Fillet Edge" tool to apply a fillet to two lines, there should be a tool to apply a chamfer as well. Could use the same logic (workflow) as the "Fillet Edge" Tool.
    See discussion here:
    http://forum.freecadweb.org/viewtopic.php?p=83906#p83906
    Tags:
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0016458)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5623.


    View Issue Details
    ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
    1560 [Sketcher] Feature minor N/A 2014-05-20 20:41 2021-02-06 05:55
    Reporter: CABrouwers Platform:  
    Assigned To: abdullah OS:  
    Priority: normal OS Version:  
    Status: assigned Product Version: 0.13  
    Product Build: Resolution: open  
    Projection: none      
    ETA: none Fixed in Version:  
        Target Version: 0.20  
    FreeCAD Information:
    Summary: Provide ability to fine-tune auto constraints.
    Description: It could be nice to be able to select which constraints are automatically added when using auto constraints. For example, I usually would set the coincidence constraint on but I would rather turn the tangent constraint off because I find it is often creates unwanted constraints.
    Tags: constraints, Solver
    Steps To Reproduce:
    Additional Information:
    Attached Files:
    Notes
    (0009079)
    Kunda1   
    2017-05-22 13:32   
    @Abdullah do you mind weighing in on this ticket?
    (0009093)
    abdullah   
    2017-05-22 21:47   
    It is a rightful request. I also find tangency is sometimes getting in the way. It is just a new feature request... I assign it to myself ;)
    (0016421)
    yorik   
    2022-03-03 13:55   
    This ticket has been migrated to GitHub as issue 5586.