【转帖】oddbentmod behavior
 

oddbentmod behavior
oddbentmod behavior
for portability reasons i'm using oddbentmod to change xdata for some regappname.
the normal behavior with acad is to change only the xdata for the regappnames given as an input in the resbuf.
dwgdirect changes the xdata for the regappnames and also erase all the other regappnames that are not in the odresbuf.
is dwgdirect implementation not a source of misunderstanding ?
i think the more natural behavior should be acad's one and dwgdirect version should be corrected.
am i wrong ?
thanks in advance
jean-robert
we'll fix it in 2.5
sergey slezkin
hi dev team
thank you very much.
currently i've implemented a work around using oddbobject::xdata and oddbobject::setxdata, before and after (resp.) calling oddbentmod.
best regards
jean-robert
jean-robert