Querying AECC object with BrxProperties

[schoeller]

Am trying to query info from custom AECC objects as seen below

When using Brx.DbProperties to query the objects I receive

To my opinion the result reflects only partial information available. Any ideas how to alter the query in order to nail it.

import traceback
from pyrx_imp import Rx, Ge, Gi, Db, Ap, Ed, Brx

@Ap.Command()
def py_prop_sync():
    try:
        db = Db.curDb()
        ps, id, _ = Ed.Editor.entSel("\nSelect entities: ")
        vals = []
        for prop in Brx.DbProperties.listAll(id):
            isvalid, fqname = Brx.DbProperties.isValid(id,prop)
            
            if(isvalid):
                val = Brx.DbProperties.getValue(id,prop)
                vals.append((prop,val.dataType(),val.format()))
        print(vals)        

    except Exception as err:
        traceback.print_exception(err)

test_sewer.zip

[CEXT-Dan]

Hi,

In short, you can’t, I don’t see that BricsCAD has enablers for these objects. Bricsys has a conversion tool in Cv to convert civil objects, but it seems its limited in scope specific civil objects

The only option is to reverse engineer the object using a filer, which is very difficult, but not impossible. Filers are consistent, once you understand the behavior of an object, you can map out the data you need. It’s hard because you have to understand each item in in the filer. I can give you more details if you want to do a deem dive into the abyss.

Basically, you have to compute the offset to the data item you need, they can be different, but it’s deterministic

def getEntInfo(id: Db.ObjectId):
    try:
        obj = Db.DbObject(id)
        print(obj.isA().name())
        # play with the filer types
        snoop = Db.SnoopDwgFiler(Db.FilerType.kCopyFiler)
        obj.snoop(snoop)
        idx = 0
        for idx, item in enumerate(snoop.buffer()):
            if "Byte" in item[0] or "Address" in item[0] or "PointerId" in item[0]:
                continue
            print("Index = {}, Value = {}".format(idx, item))

    except Exception as err:
        print(err)


@Ap.Command()
def doit():
    try:
        ps, id, _ = Ed.Editor.entSel("\nSelect: \n")
        getEntInfo(id)
    except Exception as err:
        traceback.print_exception(err)

[schoeller]

Cheers. Very useful indeed for hacking. Limited scope is known. They seem to be keeping it slim.
Shaft name would then be index 138.

[CEXT-Dan]

It’s the tool I use to create custom objects, if you become intimate with the filers, you can create enablers (C++ only). Essentially what ODA does.
You must be careful assuming an index is always the same, for example, if you were to dump AcDbPolyline, you will get an array of vertices, any data that comes after the array will be in a different position. In this case you would have to find the entry with number of vertices, and use that to compute the offset

[CEXT-Dan]

BTW, this is the conversion code I tried first, while it does not work with these objects, it might be useful

# does not work with these objects
@Ap.Command()
def py_conv():
    try:
        db = Db.curDb()
        ps, id, _ = Ed.Editor.entSel("\nSelect: ")

        # only works with tin objects?
        infos = []
        converter = Cv.CvCivil3dConverter()
        for info in converter.getCivilEntities():
            print(info)
            if info.objectId() == id:
                infos.append(info)

        if len(infos) == 0:
            print("\nNothing")
            return

        # not a permanant conversion see getInsertedEntities
        for info, newid in converter.convert(infos):
            vals = []
            for prop in Brx.DbProperties.listAll(newid):
                isvalid, fqname = Brx.DbProperties.isValid(newid, prop)
                if isvalid:
                    val = Brx.DbProperties.getValue(newid, prop)
                    vals.append((prop, val.dataType(), val.format()))
            print(vals)

    except Exception as err: