3D-printing/Cura
1
0
Fork 0
mirror of https://github.com/Ultimaker/Cura.git synced 2025-08-07 22:13:58 -06:00
Code Issues Projects Releases Packages Wiki Activity Actions 9
3D printer / slicing GUI built on top of the Uranium framework
29861 commits 313 branches 275 tags 718 MiB
Find a file
joeydelarago fd8d6498ee When changing to an intent with infillDensity > 100 in recommended settings the RecommendedInfillDensitySelector would set infillDensity=100. 
This is because the onValueChanged function checks if the slider has a different value from the settings and updates the settings if it does. The slider has a max value of 100, so when setting the sliders value to 1000 the slider would update to have a value of 100. This would then update the setting to value to 100.

The fix is as follows. When updating the slider value > 100 just ignore the first onValueChanged. Following onValueChanged, which are triggered by the user sliding the slider, will still trigger.

CURA-9488
2022-08-10 16:45:16 +02:00
.github fixed ill-formed version exclusion 2022-08-10 10:42:30 +02:00
cmake Use modern >=3.12 cmake find_package Python logic 2022-03-24 14:44:07 +01:00
cura Use is not operator rather than not ... is 2022-08-08 10:04:46 +02:00
docs Add Conan generated deps graph for documentation 2022-06-18 17:20:45 +02:00
packaging Merge branch 'main' into GH-12582_fix_uninstall_by_other 2022-07-21 15:24:57 +02:00
plugins Use is not operator rather than not ... is 2022-08-08 09:36:53 +02:00
resources When changing to an intent with infillDensity > 100 in recommended settings the RecommendedInfillDensitySelector would set infillDensity=100. 2022-08-10 16:45:16 +02:00
scripts Delete fix_app_qt_folder_names_for_codesign.py 2022-07-12 13:42:21 +02:00
tests Mock HttpRequestManager while changing sync state 2022-07-27 11:43:31 +02:00
.gitignore Update .gitignore 2022-07-12 14:09:55 +02:00
.pylintrc Fix regex for private & long functions 2020-01-10 17:43:40 +01:00
CITATION.cff update CITATION to latest version (.cff and Cura) 2022-06-15 18:30:11 +02:00
CMakeLists.txt Set cmake policies for MSVC flags 2022-06-07 16:28:55 +02:00
com.ultimaker.cura.appdata.xml Update master branch to main in XML file link 2022-05-30 16:41:30 +02:00
com.ultimaker.cura.desktop.in Rename metadata files to conform with appstream spec 2021-02-03 00:27:16 +01:00
conandata.yml Use new pysavitar as package 2022-08-02 15:47:17 +02:00
conanfile.py Make sure build and generate steps are present 2022-08-03 17:49:13 +02:00
contributing.md Add contribution guidelines 2019-03-05 14:24:31 +01:00
cura-logo.PNG Update readme 2021-11-04 14:49:06 +01:00
cura.sharedmimeinfo Update desktop and mimeinfo to add gcode mime type 2018-11-22 15:47:12 +01:00
cura_app.py Merge branch '4.13' of github.com:Ultimaker/Cura 2022-05-17 15:32:48 +02:00
CuraVersion.py.jinja Initial set-up of deploy functionality 2022-06-27 13:51:50 +02:00
GitVersion.yml Fix version number matching 2022-07-13 11:28:09 +02:00
Jenkinsfile Use generated Makefiles to run tests 2018-11-20 09:53:17 +01:00
LICENSE Changing AGPLv3 to LGPLv3 2017-09-28 13:00:43 +02:00
pytest.ini Added unit test stub 2016-04-29 11:32:33 +02:00
README.md Update README 2022-06-18 20:01:42 +02:00
requirements-dev.txt Fixed nsis build script 2022-07-15 12:03:51 +02:00
requirements-ultimaker.txt Use only pip in conan requirements 2022-06-16 19:55:56 +02:00
requirements.txt Add missing Python requirements.txt 2022-07-27 14:28:14 +02:00
run_coverage.py Add convenience script for running complete coverage 2019-08-30 16:32:11 +02:00
run_mypy.py Show error code if MyPy failed 2021-02-09 13:48:57 +01:00
SECURITY.md Add security policy 2022-03-23 09:51:36 +01:00
Ultimaker-Cura.spec.jinja Add Path to the imports 2022-07-19 11:16:34 +02:00

README.md

Cura

Ultimaker Cura is a state-of-the-art slicer application to prepare your 3D models for printing with a 3D printer. With hundreds of settings and hundreds of community-managed print profiles, Ultimaker Cura is sure to lead your next project to a success.

Screenshot

Logging Issues

For crashes and similar issues, please attach the following information:

  • (On Windows) The log as produced by dxdiag (start -> run -> dxdiag -> save output)
  • The Cura GUI log file, located at
    • %APPDATA%\cura\<Cura version>\cura.log (Windows), or usually C:\Users\<your username>\AppData\Roaming\cura\<Cura version>\cura.log
    • $HOME/Library/Application Support/cura/<Cura version>/cura.log (OSX)
    • $HOME/.local/share/cura/<Cura version>/cura.log (Ubuntu/Linux)

If the Cura user interface still starts, you can also reach this directory from the application menu in Help -> Show settings folder. An alternative is to install the ExtensiveSupportLogging plugin this creates a zip folder of the relevant log files. If you're experiencing performance issues, we might ask you to connect the CPU profiler in this plugin and attach the collected data to your support ticket.

Running from Source

Please check our Wiki page for details about running Cura from source.

Plugins

Please check our Wiki page for details about creating and using plugins.

Supported printers

Please check our Wiki page for guidelines about adding support for new machines.

Configuring Cura

Please check out Wiki page about configuration options for developers.

Translating Cura

Please check out Wiki page about how to translate Cura into other languages.

License

License
Cura is released under terms of the LGPLv3 or higher. A copy of this license should be included with the software. Terms of the license can be found in the LICENSE file. Or at http://www.gnu.org/licenses/lgpl.html

But in general it boils down to:
You need to share the source of any Cura modifications