yang686526

proxy binary data
proxy binary data
i need to access a proxy's binary data to search it.
if i knew the data format (which i don't), i'd create a custom class to read it. in the past, i read the blob data and searched it for viable data.
i know the raw binary data contains a list of doubles, but i don't know how many.
i have unsuccessfully tried the following code to read the binarychunk in the xdata:
oddbproxyentityptr pproxy(pent);
cstring name = pproxy->originalclassname(); // looking for "aeccdbcontour"
if(!name.comparenocase("aeccdbcontour"))
{
odresbuf* xiter = pproxy->xdata(); /// aaarrrggghh this returns 0x0000!
for (; xiter != 0; xiter = xiter->next())
{
int code = xiter->restype();
switch (oddxfcode::_gettype(code))
{
case oddxfcode::binarychunk:
// process binary chunk here - this is where i think i need to get to
break;
default:
break;
}
}
}
when i use odmfcapp i am able to see that there exists an aeccdbcontour proxy. when i select the tree item "<<proxy>:aeccdbcontour>" (under acdbblocktable/model_space/acdbblockbegin), it appears to show the odresbuf information. in this is a line listing "binary: (432){...}" which is exactly the block of data i need to search.
yet, the above code returns null for the xdata iterator. ???? am i not looking at the xdata information using odmfcapp? how do i access this apparent binarychunk that i can see using odmfcapp????
in odamfcapp you see dxf output for the entity not extended data returned by xdata() method.
it's possible to write a class implementing dxf filer interface and call entity's dxfoutfields() function - like list filer in odamfcapp.
but aeccontour is implemented in adtdirect and using adtdirect you'll get aeccontour not proxy entity.
sergey slezkin
that sounds great.
my question then may seem too simple. do i have adtdirect in my dd code?
or is this another product? (i.e. how do i get adtdirect library)
i see the adtdirect version 0.4.1 demo directory and files, but no source or headers.
adtdirect is a separate product. it's a plug-in to dwgdirect implementing adt objects (like arx applications in autocad)
previously only binaries were published - clients were interested only in rendering support and binaries were enough.
since 1.12 headers will be published too.
sergey slezkin