Joris Burger

Issue visualizing mesh with colors in compas ghpython

2

I can't manage to correctly visualize a mesh with colors using compas ghpython in Grasshopper. Using Rhino, the artists work correctly but in ghpython different colors passed to the `draw_faces`...

* Output nested printpoints * Added reverse_open_paths argument to seams_align to control if the direction of open paths should be reversed or not. Defaults to False. * Added reverse_open_paths argument...

Add the envisioned compas slicer workflow to the documentation - Export STL/OBJ from your favorite software - Run the Python slicing file (outside of Rhino) - Json files with slicing...

It seems like 'unify paths orientation' is not always giving the intended behaviour. I found this out by investigating the behaviour of `close_paths(self)` in the Base Slicer. I thought it...

Compas slicer webpage is not correct everywhere

2

Some links on the compas slicer pages still have outdated urls such as: - Github link the top right corner - This page https://compas.dev/compas_slicer/citing.html Needs to be changed

There seems to be something wrong with generating a brim and sorting into vertical layers. I just discovered this when making some screenshots for the presentation so I did not...

When sorting into vertical layers, a safety_printpoint is always added even if it's not always necessary

2

A safety printpoint should be added if there are multiple Vertical Layers on the same height, however if there is only one VerticalLayer (so one branch) it is not necessary...

Currently, it is inconsistent how compas slicer is described in text. Sometimes it is compas_slicer (with an underscore), sometimes COMPAS_SLICER (with capitals) and sometimes just compas slicer (no capitals). I...

see title

It could be useful to store a list of the slicing parameters (layer height, generate_brim or not, simplify_points or not) that can then be accessed during the process, as well...