search

satovey / heekscad

Automatically exported from code.google.com/p/heekscad
Other
0 stars 0 forks source link

Text Generation MissmatchError #257

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.Generating Text Kochi Font
2.this does not look like Qcad output with the same font
3.http://www.pictureupload.de/originals/pictures/200410132430_font_error.png

What is the expected output? What do you see instead?
A picture perfect Letter

What version of the product are you using? On what operating system?
newest build 1110

Please provide any additional information below.
picture shows the same font and size in Qcad
Heekscad uses the same font 
also some lines are not correct on the generating of other fonts

Original issue reported on code.google.com by lot...@foengarage.de on 20 Apr 2010 at 11:27

GoogleCodeExporter commented 9 years ago 
Can you add your heeks file to this fault.  When I add this text using English
settings, it presents alright.  I was wondering if you were entering the text 
using
something other than ASCII character sequences.

I recently fixed a problem that made the arc elements fall in the wrong place 
once
the text was converted to a sketch but I don't think that's what you're 
reporting.

See the attached file for my version of this example.

Original comment by David.Ni...@gmail.com on 21 Apr 2010 at 2:56

Attachments:

GoogleCodeExporter commented 9 years ago 
This does not work for me

Original comment by lot...@foengarage.de on 22 Apr 2010 at 11:26

Attachments:

GoogleCodeExporter commented 9 years ago 
i forgot i'am on ubuntu Karmic 9.10 amd64

Original comment by lot...@foengarage.de on 22 Apr 2010 at 11:28

GoogleCodeExporter commented 9 years ago 
I'm also on Ubuntu Karmic 9.10 but I'm running the Intel processor.  I doubt 
that
will cause this difficulty.  I was wondering if your settings use the comma (,)
character as a decimal point in a floating point number.  The QCAD files have
floating point numbers separated by comma characters.  I was wondering if the
difference will be in our locale settings.

I don't know how to change my local computer's settings to test this theory and 
I
would be a little nervous to do so as I don't want to frustrate my other tasks.

If you do use the comma as the decimal point, please let me know.  I will look 
into
the routines that read the font definition files to make sure they're reading
correctly.  Perhaps I could compile a copy of HeeksCAD that has some extra 
debugging
in it to display the values read in from the font definition file.

It's just an idea.

The text.heeks file you attached displayed correctly on my machine with no 
changes. 
I will attach a screenshot of it.  That's why I began wondering about the locale
settings.

Thanks
David Nicholls

Original comment by David.Ni...@gmail.com on 22 Apr 2010 at 1:19

Attachments:

GoogleCodeExporter commented 9 years ago 
Thanks i think that is the case  its a German Thing!
also all CNC fail if i import from stl error is float there are comma instet of 
dot

so for overcomming this problem shoudent there be a function that cheks the 
comma or
point in the value bevore giving that to the float 
for example in post.py -< the file witch generates this shoudt care of the 
problem

Original comment by lot...@foengarage.de on 22 Apr 2010 at 5:53

GoogleCodeExporter commented 9 years ago 
I believe I have fixed this problem.  I reversed the logic regarding the 
conversion
of dots to commas and the graphics I produced (attached) looked like your 
original
graphics.

This leads me to wonder whether the Excellon and RS274X files generated by 
KiCAD will
have the same problem.  The sample files I have here use commas as field 
separators
and dots as decimal points.  If KiCAD generates this same format when the locale
settings are reversed then it will exhibit the same fault.

Do you use KiCAD by any chance?  If so, do the RS274X files generated by it 
import
correctly into Heeks for you?  I may need to apply the same type of fix for 
that code
too.

Original comment by David.Ni...@gmail.com on 22 Apr 2010 at 11:31

Attachments:

GoogleCodeExporter commented 9 years ago 
This issue is fixt with the R1122

Original comment by lot...@foengarage.de on 3 May 2010 at 1:15

GoogleCodeExporter commented 9 years ago 
Thanks for checking it.

Original comment by David.Ni...@gmail.com on 3 May 2010 at 1:26