Bug 237987
| Summary: | cad/freecad: Errors from the Path Workbench | ||
|---|---|---|---|
| Product: | Ports & Packages | Reporter: | denverh |
| Component: | Individual Port(s) | Assignee: | Christoph Moench-Tegeder <cmt> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | Flags: | bugzilla:
maintainer-feedback?
(cmt) |
| Priority: | --- | ||
| Version: | Latest | ||
| Hardware: | amd64 | ||
| OS: | Any | ||
Uhoh. Did you ever try that on 0.18 or 0.18.1, and did it work there? (Is this a recent regression?) At first glance, I don't see any relevant changes in that area - and it's reproducable. The FreeCAD 0.18.1 AppImage for Linux does not have this problem (you'll need Linux to test that, I guess) - but they have a much older Qt (5.6, if I'm not mistaken), so perhaps it's that? Upstream Bug: https://www.freecadweb.org/tracker/view.php?id=3984 (In reply to Christoph Moench-Tegeder from comment #1) I saw the errors on 18.1, but that's the oldest version I've used. I did try the Linux version, which works ok, so perhaps it is the version of Qt. The 32 bit Windows version also works using wine, but that's not a very satisfactory solution. (In reply to Christoph Moench-Tegeder from comment #2) Ok, well at least it's not my imagination, or something unique to my situation. Hopefully someone with more experience with Qt than I have can track this down. Thanks. A commit references this bug: Author: cmt Date: Sun Jun 16 20:09:14 UTC 2019 New revision: 504361 URL: https://svnweb.freebsd.org/changeset/ports/504361 Log: cad/freecad: improve pyside2 detection pyside2 changed the way it reported it's variables (they're cmake target properties now, not variables) sometime over the last releases. FreeCAD did not support pyside2's new way of doing thing, resulting in certain dialogs not working. PR: 237987 Reported by: denverh at comcast dot net Changes: head/cad/freecad/Makefile head/cad/freecad/files/patch-CMakeLists.txt This seems to improve things. Please check FreeCAD 0.18.2_1 and report back if it's still broken (which I don't expect). Ok, that seems to have fixed it. Thanks. |
Starting the Tool Manager: Running the Python command 'Path_ToolLibraryEdit' failed: Traceback (most recent call last): File "/usr/local/FreeCAD/Mod/Path/PathScripts/PathToolLibraryManager.py", line 627, in Activated self.edit() File "/usr/local/FreeCAD/Mod/Path/PathScripts/PathToolLibraryManager.py", line 609, in edit editor = EditorPanel(job, cb) File "/usr/local/FreeCAD/Mod/Path/PathScripts/PathToolLibraryManager.py", line 397, in __init__ self.loadTable() File "/usr/local/FreeCAD/Mod/Path/PathScripts/PathToolLibraryManager.py", line 460, in loadTable self.form.ToolsList.setModel(tooldata) 'PySide2.QtWidgets.QDialog' object has no attribute 'ToolsList' And starting a new Path Job: Running the Python command 'Path_Job' failed: Traceback (most recent call last): File "/usr/local/FreeCAD/Mod/Path/PathScripts/PathJobCmd.py", line 64, in Activated dialog = PathJobDlg.JobCreate() File "/usr/local/FreeCAD/Mod/Path/PathScripts/PathJobDlg.py", line 55, in __init__ self.dialog.templateGroup.hide() 'PySide2.QtWidgets.QDialog' object has no attribute 'templateGroup' Steps to Reproduce: 1. Start a new file with ^N 2. Select the Path workbench 3. Start a new Path Job using menu Path -> Job (or type pj) 4. Start the Tool Manager using menu Path-> Tool Manager (or type pt) All other normal CAD functions appear to work properly. Only those directly associated with the Path Workbench report errors. Version: FreeCAD-0.18.2 FreeBSD 11.2-RELEASE-p9 r345733 amd64 I'm not sure what other information may be helpful at this point.