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

SuperSlicer quits when configuring Repetier. #594

Closed
thierryzoller opened this issue Oct 22, 2020 · 12 comments
Closed

SuperSlicer quits when configuring Repetier. #594

thierryzoller opened this issue Oct 22, 2020 · 12 comments
Labels
bug Something isn't working as intended fix is live in the last release Please download /build the last release and try to reproduce.

Comments

@thierryzoller
Copy link

Version

Latest

SuperSlicer crashes when I try to configure Repetier (it quits without error message).
Are there debug logs somewhere?

@NickRno77
Copy link

me too, it does this when I paste in the API Key.

@supermerill
Copy link
Owner

supermerill commented Oct 22, 2020

no logs.
I didn't test the repetier, as i don't know how to use it. I trust the pull request.
Tell me how to reproduce, and i'll see how to fix it.

I shouldn't have use repetier as the name for the release....

@supermerill supermerill added the bug Something isn't working as intended label Oct 22, 2020
@thierryzoller
Copy link
Author

same then NickRno77

@NickRno77
Copy link

NickRno77 commented Oct 22, 2020

no logs.
I didn't test the repetier, as i don't know how to use it. I trust the pull request.
Tell me how to reproduce, and i'll see how to fix it.

I shouldn't have use repetier as the name for the release....

Similar to OctoPrint I think except there’s a server name option which I never get to anyway. I pick repetier from server list, enter IP address of the repetier server, enter the API key then crash....

Thanks

@supermerill
Copy link
Owner

supermerill commented Oct 22, 2020

image

maybe i need a real repetier server to make it crash?

@NickRno77
Copy link

image

maybe i need a real repetier server to make it crash?

Yes I think you need valid API key, if I put 1234567 it doesn’t crash but obviously doesn’t connect. Couldn’t Boris Pruessmann help ?

@LuckyTurtleDev
Copy link

LuckyTurtleDev commented Oct 22, 2020

I can reproduce this with my local repetier-server and the live demo.
Until commit db99b09 superslicer does not crash.
Only newer version since 3ec7dec crash.

Superslicer does not crash if you had configure repetier-server before commit 3ec7dec.
First time I update to a newer version it does still work. But now after finding the last running version and updating back to to the newest version it does crash with the reptier-server config.

May def->gui_type = "select_open"; is needed nevertheless.

@LuckyTurtleDev
Copy link

LuckyTurtleDev commented Oct 22, 2020

Tell me how to reproduce, and i'll see how to fix it.

  • Open the live demo
  • press the "open repetier server live demo" button
  • gear icon -> Global Settings -> Connectivity (you can see the API-key here)
  • In Superslicer: change Host Typ, enter URL with port and the API-key from the live demo

supermerill pushed a commit that referenced this issue Oct 23, 2020
revert 3ec7dec
add passtrough on the Workaround for a correct rendering of the control without Bitmap
select first option by default
@supermerill supermerill added the fixed for the next version That means that you should be able to test it in the latest nightly build label Oct 23, 2020
@supermerill
Copy link
Owner

supermerill commented Oct 23, 2020

Someone can test the lastest nightly? It's in the action menu.

@NickRno77
Copy link

Someone can test the lastest nightly? It's in the action menu.

that works, thanks

@LuckyTurtleDev
Copy link

I test this too and it does work. Thanks

Please remember that I was not able to reproduce the crash, you had mentioned here.

@supermerill
Copy link
Owner

supermerill commented Oct 23, 2020

that's a crash from an assert in wxwidget, it only happen in debug.
But i'm not confident enough to let it slip through, so I finally "fixed" it by removing a hacky ui-bugfix in this exact case.
I also took the time to set the combo box to the first value on initialisation.

@supermerill supermerill added fix is live in the last release Please download /build the last release and try to reproduce. and removed fixed for the next version That means that you should be able to test it in the latest nightly build labels Oct 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working as intended fix is live in the last release Please download /build the last release and try to reproduce.
Projects
None yet
Development

No branches or pull requests

4 participants