[V1 -25] Code Not Generated (solved in V1 RC1)

[Bob La Londe]

Sometimes CamBam fails to generate code, but doesn't seem tell you or tell you why.  

If you have already generated that code file once you may find yourself using the same defective code file you thought you corrected.  If its the first time you don't know you don't have the code file until you look for it.  

[Bob La Londe]

I did find an indication buried in the diagnostic data.  Had to scan back line by line to find it.   It would be nice if it generated a pop-up warning. 

[Bob La Londe]

I should add that I have had a part cut incorrectly, fixed the problem, had something cause a failure to generate code, thinking it was fixed, run the new code, and found after another part was ruined it was still the old code.  

Failure to generate code is a pretty big deal.  I think it should pop up and say failed to generate code in big red flashing letters.  LOL.  Ok, maybe not that dramatic, but a single line buried in the diagnostic data 20 lines back just doesn't cut it.  Pun intended.  

[lloydsp]

I agree.  A failure like that deserves a 'banner' message one cannot miss.

But I can't stand your PUNishment!

Lloyd

[dh42]

Hello Bob

Do you have an example file where this problem appears ?

I never see that ; except with waterline mop ... but I always get an alert in the log windows saying "GCode not generated"

are Waterline Safety Check enabled in the options.

++
David

[Bob La Londe]

I run across it when for some reason a MOP doesn't have any assigned geometry. 

[dh42]

Ok, so a test to insure that mops have drawing object assigned, and why not, the right type of object for the mop (*) can be a good idea.

* I have seen that a 2d shape can be assigned to a 3D mop without any warning from CB

++
David