forked from prusa3d/PrusaSlicer
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Workaround GitHub's single fork limitation: Create "manual" fork of SuperSlicer in this fork repository #1
Merged
TheSlashEffect
merged 10,000 commits into
TheSlashEffect:superslicer-fork
from
supermerill:master
Jun 22, 2024
Merged
Workaround GitHub's single fork limitation: Create "manual" fork of SuperSlicer in this fork repository #1
TheSlashEffect
merged 10,000 commits into
TheSlashEffect:superslicer-fork
from
supermerill:master
Jun 22, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
and also when no perimeters #3997
set s_seam_position to disable if no perimeters. add is_enabled as script function (still experimental)
fix seam notch with spiral vase some gui stuff for scripted settings.
- can be with custom line widget, like the substitution - can't be a simple field, need next commits to do so.
allow all vector types in text field (';' separated, to avoid problem with ',' vs '.' locales) Change `post_process` to use the new way (no "serialized" needed anymore) Remove "one_string" gui type, as it's now a supported as vector with no id. Need to set all filament-setting id to 0, as the gui need them to update the first elt only (and always that one) for field <-> config pipe: - config now have get_any(id) and set_any(any, id). No need to special optiongroup or gui method. - any will carry a type that is in sync with the config type and the id. - if id is set or type is scalar, the any is scalara. else the any is a vector of scalar. - fields are responsible to cast the any correctly and to set it correctly. no more mess of wxstring & double
…a real default_fan_speed - updated helper text. - now default will be used when a field is deactivated. - default_fan_speed =0 is a bit like the old fan_always_on to false. - min fan speed is a real min for fan speed (if not stopped) Should be easier to understand. #4009
remove setInt for not-enum config
…speed & volumetric speed.
#4208) Currently the symlink target is hardcoded as slic3r, which is not the binary name of SuperSlicer. Change it to use the variable for application command name instead. Signed-off-by: Icenowy Zheng <uwu@icenowy.me>
was sending gcode data when refreshing for a preview.
supermerill/SuperSlicer/#4305
Actually, all those deprecated functions were internally called those new functions. So there isn't any risk to use them directly.
(introduced by fill_aligned_z, caa4a0) #4306
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR creates a branch of SuperSlicer pointing to SuperSlicer's head. This is to work around the fact that GitHub will not let you have multiple forks of a repository. I want to work on PrusaSlicer, SuperSlicer, and OrcaSlicer at the same time, and they are all forks of PrusaSlicer.
To manage this is simply create a branch from an arbitrary point BEFORE SuperSlicer was forked, and then merged SuperSlicer's main branch onto it.
Git-wise everything is sane and proper, the branch is exactly up to date with SuperSlicer, which is a fork of PrusaSlicer. If it works it works.