Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

beso_main.py unable to run as macro #16

Open
ruzko opened this issue Jul 19, 2021 · 3 comments
Open

beso_main.py unable to run as macro #16

ruzko opened this issue Jul 19, 2021 · 3 comments

Comments

@ruzko
Copy link

ruzko commented Jul 19, 2021

Since I began using beso half a year ago, i haven't been able to 'run optimization' in fc-gui freecad macro, or run beso_main.py as a freecad macro at all.

I've found a workaround to this, by writing a conf file with fc-gui macro, and then running beso_main.py in the terminal.
After issuing the command python beso_main.py in the .Freecad/Macro/ directory, an empty window with title '11' shows up. Closing window '11', opens window '12', and so forth until i close window '15'. Only now, the actual optimization would start.

I experienced this problem while using Freecad 0.18, 0.19 and 0.20 in both Linux Mint and Manjaro.

Report view output when pressing 'run optimization' from fc-gui macro:

22:55:46 Traceback (most recent call last):
22:55:46 File "/home/jacob/.FreeCAD/Macro/beso_fc_gui.py", line 829, in on_click23
22:55:46 exec(open(os.path.join(beso_gui.beso_dir, "beso_main.py")).read())
22:55:46 File "", line 6, in
22:55:46 File "/home/jacob/.FreeCAD/Mod/retr3d/multiprocessing/init.py", line 64, in
22:55:46 from multiprocessing.process import Process, current_process, active_children
22:55:46 File "/home/jacob/.FreeCAD/Mod/retr3d/multiprocessing/process.py", line 262
22:55:46 except SystemExit, e:
22:55:46 ^
22:55:46 SyntaxError: invalid syntax

@fandaL
Copy link
Collaborator

fandaL commented Jul 21, 2021 via email

@ruzko
Copy link
Author

ruzko commented Aug 7, 2021

I tried uninstalling the Retr3d workbench, and beso now runs properly as a macro

@luzpaz
Copy link
Contributor

luzpaz commented Apr 24, 2022

@fandaL you can use package.xml file to indicate what other addons this macro conflicts with

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants