Everything was great until I had to cover the slicing process. I wanted to continue to cover Slic3r for the PEEK and layer fan shrouds. Unfortunately, while MC uses the Slic3r engine (which version? There's no way to tell! The Slice Engine dropdown should include the version #.) the way Slic3r manages settings has been left out.
It appears that the Print, Filament and Printer settings have all been quashed into the ambiguously named "Quality" dropdown. Managing the three separate categories of settings that Slic3r uses like this is a mess. I applaud the work you guys have done here, but if you're going to include three different slicing engines, you need to manage their settings like the stand-alone versions do. Right now it's a mess and doesn't make any sense at all from the standpoint of the user.
I'd even be up for fixing this myself, but then I discovered that MatterControl uses some custom widget framework that I've never heard of and can't find any documentation on. I have not the time nor inclination to learn yet another framework, especially when the default .Net/Mono control framework would have been perfectly suitable for this application.
Until the slicer configuration system is cleaned up, there's really no point in me continuing the work on a MC specific version of the build manual. It basically boils down to the fact that if it doesn't make any sense to ME, there's no way in hell I have a chance to explain it to someone that's never used it before.
Right now it appears that "clever" is trumping "usability" and that's a problem.
g.
)
