Scorch,
I'm very impressed with your software. I only found it a few days ago and have been able to make some great looking signs. Okay, they have all been test runs, but they will look great when I'm finished. Just have to figure out all of the "Cleanup" settings.
I do have a few questions for you...
First, is there a reason that you limit the line spacing to 1.0?
I modified the code to change the lower limit to 0 and it still seems to render fine. I just haven't tested the G-code that was generated to see if it messed up when the text crossed over.
Code:
def Entry_Lspace_Check(self):
try:
value = float(self.LSPACE.get())
if value < 0.0:
self.statusMessage.set(" Line space should be greater or equal to 1 ")
return 2 # Value is invalid number
except:
return 3 # Value not a number
return 0 # Value is a valid number
def Entry_Lspace_Callback(self, varName, index, mode):
self.entry_set(self.Entry_Lspace, self.Entry_Lspace_Check() )
See the Attached Images, the first has the line spacing set to 1, the second one has the spacing set to 0.8
Line Spacing 1.0
Attachment 198346
Line Spacing 0.8
Attachment 198348
On this default font is not a huge difference, but some I've look at just leave too much white space. Some fonts I looked at only used Capital letters so there is no need to leave space below the line.
Second question.
Is there anyway to display the "Bounding Box" information again?
It show up in the status bar when you hit recalculate, but then is gone with the Calc V-Carve button press. This is very handy information to have around. Maybe you could find some area of the screen to leave it displayed, or on a about box. It would be really great if it would be in the G-code file, so you could know how big the sign will be when you open the g-code file up in future to make another sign.
Finally,
Where did you find the Aztec Calendar that you milled? I've found a few on line in different formats, but nothing that imports correctly. I'm not sure if this is a bug in the F-Engrave software, or a problem with the original image. I'm not sure that I'd ever take the 20 hours needed to generate the g-code for it, but it would be nice to know that it worked.
Attachment 198350
Thanks
-Chuck