yang686526

mtext explode
mtext explode
i exploded the mtext entity inside the attached file and the resulting oddbtext->position.x entities varies between -0.06 and 0.078. all the odbtext entities should have had a position().x value of 0.1250. the mtext is top-left aligned. do you know what the problem might be?
attached files
probably problem is with applying font.
here is a result of explode mtext with using simlex.shx font.
quantity=3|
posx = 0.125000, posy = 11.666667
name = simplex, fontname =
part_name=|
posx = 0.125000, posy = 10.000000
name = simplex, fontname =
material=a572|
posx = 0.125000, posy = 8.333334
name = simplex, fontname =
thickness=.75|
posx = 0.125000, posy = 6.666667
name = simplex, fontname =
etc.
here is a dump with using simplex_.ttf font.
quantity=3|
posx = -0.000440, posy = 11.666667
name = , fontname = simplex
part_name=|
posx = -0.046500, posy = 10.000000
name = , fontname = simplex
material=a572|
posx = -0.046500, posy = 8.333334
name = , fontname = simplex
thickness=.75|
posx = -0.057280, posy = 6.666667
name = , fontname = simplex
etc.
the oddbmtextfragment->font is filled then using shx font and
oddbmtextfragment->fontname is filled then using ttf font.
--
best regards,
sergey zaitcev
work around?
is this a bug? how do i work around this?
quote:
originally posted by rauli
is this a bug? how do i work around this?
no, it isn't bug. dd need correct font file for calculate fragments right. dd gets it by call oddbhostappservices::findfile(). this function has default implementation and can be overrided by client. the alternate font is used if font is not found (oddbhostappservices::getalternatefontname() method). by default this method return the value of system variable "fontalt" (default in acad: simplex.shx). if alternate font is not found odamfcapp substitutes build in font like simplex.
see also:
thank you. it just could not find the simplex font.