3f9c7c55dc
When scrolling the setting list, it was clearing the focus in order to close the pop-ups in the setting list. If pop-ups like for the infill pattern or extruder selection settings are not closed, the pop-up part is still rendered even if the user scrolls those settings out of view, causing the pop-up to appear somewhere on top of completely unrelated interface elements. It scrolls all the way to the top of the screen, effectively. I couldn't find a way to cause pop-ups to be clipped with the rest of the contents of the ListView. They are always rendered on top due to the nature of the pop-up. I could find a way to trigger pop-ups to close upon changing the scrolled position without changing the focus, but that method was fairly complex with a bunch of `Connection`s and an extra signal. This is by far the simplest solution. Contributes to issue CURA-9070. |
||
|---|---|---|
| .github | ||
| cmake | ||
| cura | ||
| docker | ||
| docs | ||
| icons | ||
| plugins | ||
| resources | ||
| scripts | ||
| tests | ||
| .dockerignore | ||
| .gitignore | ||
| .pylintrc | ||
| build.sh | ||
| CITATION.cff | ||
| CMakeLists.txt | ||
| com.ultimaker.cura.appdata.xml | ||
| com.ultimaker.cura.desktop.in | ||
| contributing.md | ||
| cura-logo.PNG | ||
| cura.sharedmimeinfo | ||
| cura_app.py | ||
| Dockerfile | ||
| Jenkinsfile | ||
| LICENSE | ||
| pytest.ini | ||
| README.md | ||
| requirements.txt | ||
| run_coverage.py | ||
| run_in_docker.sh | ||
| run_mypy.py | ||
| SECURITY.md | ||
| test-in-docker.sh | ||
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.
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 usuallyC:\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
For additional support, you could also ask in the #cura channel on libera.chat. For help with development, there is also the #cura-dev channel.
Dependencies
- Uranium Cura is built on top of the Uranium framework.
- CuraEngine This will be needed at runtime to perform the actual slicing.
- fdm_materials Required to load a printer that has swappable material profiles.
- PySerial Only required for USB printing support.
- python-zeroconf Only required to detect mDNS-enabled printers.
For a list of required Python packages, with their recommended version, see requirements.txt.
This list is not exhaustive at the moment, please check the links in the next section for more details.
Build scripts
Please check out cura-build for detailed building instructions.
If you want to build the entire environment from scratch before building Cura as well, cura-build-environment might be a starting point before cura-build. (Again, see cura-build for more details.)
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
Cura is released under the terms of the LGPLv3 or higher. A copy of this license should be included with the software.