I think a low alpha may be enough to draw attention to it so that the user can fix it in the source file. I’m all for giving cues to issues but when you try to code for every possible user error you end up with a difficult to maintain code base while trying to accommodate edge cases.
10% looks reasonable. done.
Looks great, Thanks! I can see I have a few glitches in my document now as well which is good since I know what to go fix.
+Peter van der Walt The checkmarks and red for selected items seems confusing. Maybe try something else?
White text on blue is very common
Would it be possible in the tree view of the paths to allow user to reorder paths? I had a problem with the CAM in that holes in small parts were cut after the outside was cut and blown away by the air assist. So I would like to cut the hole first.
This brings up another idea to have the CAM work from inside out…
Additionally it might be just me but this DXF did not load with the CAM: http://www.thingiverse.com/download:1568460
I would be glad to help with any algorithm development, but you most likely do not want me coding javascript.
Thanks!
Trampas
+Peter van der Walt That’s better, except the check mark is confusing. Check marks are for check boxes, not selections. I used checkboxes in jscut because I never got around to implementing true selection behavior like I did here.
@Trampas_Stern The CAM ignores path order. You can create order by using multiple operations and ordering them.
@Todd_Fleming I beleive that what @Trampas_Stern request could be solved with what was implemented as operation reorder. He can drag individual path and reorder them.
Ok, seems that I need to start the comms part now.