-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Slic3r not opening when executing stl file #3803
Comments
This issue tracker is for upstream Slic3r version. You must report it in the Prusa's fork: https://github.com/prusa3d/Slic3r |
Closing. If you can reproduce with current build from http://dl.slic3r.org/dev I will reopen. This is, however, probably normal behavior. If we don't do that then programs like repetierhost will break (and all of the command line interface). |
As best I remember, the prusa3d fork uses 2 shell execs, one with a command line window and one without. While we could adjust shell.cpp to build two copies one that forces --gui and one that doesn't (slic3r-gui.exe and slic3r.exe), I'm sure someone else would get confused. Reclosing until @diegoolavarria provides a test case with upstream slic3r. |
Ok I created an executable of the source code provided here, and tested by executing the .stl file into the slic3r.exe. It opened a command prompt window (which it happens when you execute a .exe created with perl), showing the process of creating a .gcode file. The final result is a .gcode file with the presets. |
How did you create the executable? |
pp -x -o slic3r.exe slic3r.pl |
Then it's normal. |
Yes, I've tried with different versions and releases, so I also figured out it's a normal setting. Although, I'm trying to configure the code so when I double click a .stl file, it opens Slic3r showing the model instead of automatically create a .gcode file. |
@diegoolavarria I have a modified version of the exes being produced for upstream, it's not quite done yet. There will be a slic3r.exe and slic3r-console.exe. slic3r.exe, when I'm done, should always load the GUI. |
@lordofhyphens slic3r.exe by itself always opens the GUI. The problem is when executing a .stl file asociated with slic3r.exe |
Don't know if it has something to do, but in GNU/Linux, % slic3r file.stl # this process file.stl in the command line
% slic3r --gui file.stl # this opens slic3r and load file.stl IMO, this should be the intended behavior. |
I know, I haven't fixed that yet
|
*sigh*
I will fix it. Please wait for me to say it is fixed before continuing on.
Hopefully that will be tonight.
|
force --gui for shell during compilation if -DFORCE_GUI is set for compile wrapper. Fixes #3803
Version
Prusa Version
Operating system type + version
Windows 8.1
Behavior
When I asociated .stl files into executing Slic3r, is expected to open Slicer with the .stl file already loaded, but it creates a .gcode output file without opening the software. Is it a common problem?
The text was updated successfully, but these errors were encountered: