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

object has no attribute 'slic3r_configs' #865

Closed
SteveDC2 opened this issue Dec 11, 2017 · 6 comments
Closed

object has no attribute 'slic3r_configs' #865

SteveDC2 opened this issue Dec 11, 2017 · 6 comments
Labels
2.x Non-breaking features and fixes suitable for inclusion in future Printrun 2.x minor releases Fix commited

Comments

@SteveDC2
Copy link

I am using the Windows binary distributions from http://kliment.kapsi.fi/printrun/

I have tried both 2015 and 2017 versions but both give me the following error when I try to load an STL file.

Thoughts?

File "printrun\pronterface.pyc", line 1298, in slice_func
AttributeError: 'PronterWindow' object has no attribute 'slic3r_configs'

@rockstorm101
Copy link
Collaborator

Hi, I am trying to reproduce this behaviour, could you state the version of windows you are using and paste here the exact line of Settings > Options > External commands > Slice command ?

Thanks

@SteveDC2
Copy link
Author

So, I can't seem to repeat the error now either!!

I was experimenting with various other builds and other slicers (Repetier, Cura etc...) and now Printrun seems to work fine.

I will try doing a clean install on another PC to see if I can 'recover' the failure.

By the way, I really appreciate you responding to my issue so quickly.

BR,
Steve

@helaan
Copy link

helaan commented Jan 27, 2018

I've just hit this myself, repro steps:

  1. Disable Slic3r integration in Settings -> User Interface -> [ ] Enable Slic3r integration
  2. Restart Pronterface
  3. Enable Slic3r integration in Settings -> User Interface -> [ ] Enable Slic3r integration
  4. Load an STL file.

(When starting pronterface with slic3r integration enabled, it works fine, which is why OP couldn't reproduce)

OS: Gentoo

@kliment
Copy link
Owner

kliment commented Mar 23, 2018

I believe this is now fixed in the 2.x branch (that requires python3 and wxpython 4). At least I can no longer reproduce there with the above repro steps.

@hroncok hroncok added the 2.x Non-breaking features and fixes suitable for inclusion in future Printrun 2.x minor releases label Mar 23, 2018
@rockstorm101
Copy link
Collaborator

I can't reproduce this either.

@SteveDC2
Copy link
Author

Thanks for looking at this. I will check ASAP.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.x Non-breaking features and fixes suitable for inclusion in future Printrun 2.x minor releases Fix commited
Projects
None yet
Development

No branches or pull requests

5 participants