matthiaswm / iotaslicer Goto Github PK

optimize memory and speed by clipping the framebuffer

Override default formatting using custom FLTK widgets in Fl_Tree

Write JSON files that describe a printer. Allow inheritance from super printers. Create minimal diff printers.

select and render all stages of constructing a slice (range slider left-right?)

calculate total filament used.

test

optimize travel to not cross already built outsides and leave extrusion dirt

and keep loading debug libraries in debug mode.

disable z buffer in IAFramebuffer unless explicitly requested.

Add a priming line a few mm away from the object's foot

Add a flat surface around the foot to improve first layer adhesion.

extrusion must be connected to layer height

to Fl_Preferences. Allow arrays using unnamed keys.

when moving the slider, calculate toolpath in bg and show when done.

Milestone reached, but no on Win and Linux yet

can we use 8-bit colormaps instead of 32-bits?

This would reduce memory use quite drastically in IAFramebuffer. However, I am afraid that no OpenGL driver will be optimized for this (or maybe not even be capable).

Adapt OpenGL to the functionality that is actually available. Add glError calls to find out what's going on.

optimize travel and loop start

Smokestack on Benchy is melting away when printng rapidly. We probably need at least 10 or 20 seconds break to have the ABS cool a little before we stack more filament.

Maybe we can also create a horizon and a background.

Create new presets, save presets hierarchically, load and manage.

Add a test scene for bridging, for extrusion width, and for the retraction speed and depth. Tests for Stringing, Details, and other stress tests.

select and render all stages of constructing a slice (range slider left-right?)

Separate the path and the label.
Add optional units after input field.
Optional width of input field, calculate for pulldown menus?
Optional vertical alignment or y offset
Read from Prefs, write to prefs.
More types as we go.
Alternative menus for the same setting for derived printer classes.
Sub menus, should remember if they were open
Tool tips and even html links.

To make optimizing toolpaths easier, we should know which paths are loops and how they can be optimized. We also need a priority list and possibly grouping to keep a certain order of execution.

Vertices that hang down like icicles need their own kind of support structure.

Maybe expand layers first to merge small errors together and then start creating extrusion?

serial port writer and monitor (see Repetier)

Add function to copy files form fresh FLTK build.

We can start a loop anywhere, so why not optimize for even less travel

Lid and infill should not overlap, but just touch