Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Feat: flow per print-feature #4561
…ine width any more They are not even in the same unit, so it cannot be a child. A parent setting should be exactly equal to all child settings combined.
that's because we should override the per-feature flow settings with one global material_flow_layer_0 setting to rule them all. The flow per feature is more accurate to these features, so the initial layer should expand all these seaprately.
Ah thanks! I see where to find the error now.
(Minor remark: it's a bit weird that you have to specify the category in the default setting visibility file. I don;t really see the reason.)
The Jira ticket says that it would be discussed with Ultimaker's Materials & Processing team. A few months ago I asked if this had happened yet but nobody seems to read that (and then I forgot about it too).
I don't know why the M&P team needs to get involved with this, really, other than by telling them that this is now an option, and they can use it if they like, or not if they don't like...
Ok, thanks for the info, yes it doesn't make much sense.... hopefully they will just add the functionality and then let the M&P team play around with it!