Closed zbhujwala closed 6 years ago
Incorrect file type chosen (non-STL file type)
Steve mentioned we can use the serial.list() // Serial.list() // this will populate an array of strings of the ports on the user computer https://processing.org/reference/libraries/serial/Serial_list_.html
The file name gets chopped off @peralta013 should we put it below the choose file button?
"The createGraphics() function should almost never be used inside draw() because of the memory and time needed to set up the graphics. One-time or occasional use during draw() are acceptable, but code that calls createGraphics() at 60 frames per second will run out of memory or freeze your sketch." https://processing.org/reference/createGraphics_.html
Line 88 we do this
yea, none of this code should be in draw()
if (confirmedClicked){
rendering = createGraphics(250, 250, P3D); //size of render
vis = new RenderControler(100,100,100);
vis.ResetCamera();
STLParser parser = new STLParser(STLFile);
ArrayList<Facet> data = parser.parseSTL();
/*test = new Model(data, .1, .1);
test.Slice(); // Create gcode in Model object
gcode = test.getGCode();
Console window is good
Now need status label
@GeorgeVentura rendering = createGraphics(250, 250, P3D); //size of render // P3D Should we stick that into the confirm file button event handler?
My laptop fan goes full speed and battery drops like crazy when running the UI. I wonder if it has to do with having createGraphics() in draw()?
rendering = createGraphics(250, 250, P3D); //size of render // P3D Should we stick that into the confirm file button event handler?
yea
It looks like our status label has attended to the original checklist I posted up here with the exception of Rendering (not sure when Rendering team will be done nor do I know if they throw exceptions/errors to be caught so).
Should we close this issue and focus on documentation/testing now?
Yeah, let's close it.
Errors/Status progress will be caught and updated into the "Status Bar" label
Statuses to account for: