yang686526

oddbtext::getboundingpoints return incorrect values ?
oddbtext::getboundingpoints return incorrect values ?
we have problems with oddbtext::getboundingpoints when the text is an oddbattributedefinition.
values return are the bounding points of the oddbattributedefinition::textstring() or we want oddbattributedefinition::tag().
is it a bug or a right behavior ?
the fix is in the latest posted release (1.12.01).

quote:
originally posted by open design alliance
the fix is in the latest posted release (1.12.01).
we use the lastest release 1.12.01 and the bug is still there !
it is the getboundingpoint of an acdbattributedefinitionfff"> !
it return the bounding point of the textstring() in place of the tag()
i can try to do an example if you want ?
constant attribute definition is rendered as textstring() if it's owned by block different from model or paper space.
if it's inserted into layout block (ms or ps) it's rendered as tag().
so i think that the bug is "attribute definition owned by layout block returns wrong data from getboundingpoints"
attribute definition owned by "normal" block is ok.
sergey slezkin

sorry if you don't understand my question but for me
code:
attribute definition owned by "normal" block
is an acdbattribute !
and
code:
attribute definition owned by layout block
is an acdbattributedefinition !
other acdbattributedefinition owned by blocktablerecord are not rendered.
but you are right, it's what i wanted to say !
oddbattribute is owned by oddbblockreference not by oddbblocktablerecord.
oddbattributedefinition owned by non-layout oddbblocktablerecord is rendered if it's "constant" and "visible" (as textstring(), not as tag()) .
sergey slezkin