Documentation updates. Adding some developer centric docs #4807
Conversation
|
|
||
| ## [`Tab`](../../src/slic3r/GUI/Tab.hpp) | ||
|
|
||
| Refers to the pop windows that open when you click the edit preset button |
There was a problem hiding this comment.
This also refers to the options section on the sidebar (TabPrint I believe)
There was a problem hiding this comment.
you are right. I corrected that. Also realized that just like TabPrint, TabPrintModel is also not a popup.
|
|
||
| each one of these contains a collection of processes, filaments and printers respectively.\ | ||
|
|
||
| #### Clarification Needed: It is unclear to me if `printers` contain different nozzle sizes of the same printer model or all different printers models by the same vendor or something else. Feel free to add clarification. |
There was a problem hiding this comment.
Each nozzle size is a different preset
There was a problem hiding this comment.
Yes. I also understood that PresetBundle is just a bundle of whatever presets without regard for compatibility with each other. Compatibility is taken care of later while loading the presets to the UI.
There was a problem hiding this comment.
Sorry. My previous answer wasn't very clear. The printers preset bundle contains all printer presets. It isn't sorted by nozzle size or vendor.
There was a problem hiding this comment.
yes. I also realized that while digging through the code earlier today. I have already made that update.
There was a problem hiding this comment.
Each nozzle size is a different preset
I want to change this and so many other things if I'm honest. As someone relatively new to 3d printing the way slicers deal with their presets and poor override systems is really frustrating. I assume it's historic but I want one preset where some of the values will change if I just select a different nozzle.
I want to be able to say things like if this is PETG then just add some z offset. All my PETG has the same Z_ADJUST custom code.
There is no developer reference for the code at all. This is a small start to that. Looking into more ways of code base documentation to make things more comprehensive.