; error : Automation Error. Method [GETOBJECTIDSTRING] not available
Is Method [GETOBJECTIDSTRING] not implemented in BCAD ?
ty !
ty !
0
Comments
-
Dear Dirk,
indeed, that function is missing in our IAcadUtility interface ... I found these functions missing in that interface, actually :
SendModelessOperationStart, SendModelessOperationEnded, ObjectId32ToObjectIdString, GetObjectIdString
I will care to get them all implemented with V16 Release.
many greetings & many thanks !0 -
Ok great ! thank you very much Torsten !
Another question regarding fields in BricsCAD : Formula (w2u) in the field category Objects... is this supported yet ?0 -
Dear Dirk,
actually, formulas are only supported for Table cells ... I compared with AutoCAD's COM interface, it is the same;
not sure if I properly understand what you mean with " field category Objects" ?
Btw., you may also use the string representation of IAcadHandle instead of string from ObjectId ?
(if that handle string is suitable, i.e. for fields)
many greetings !0 -
Hello Thorsten,
see attached, this is the message a get in BCAD...field_error.jpg0 -
Dear Dirk,
I have never seen that "w2u" symbol/function in that context ... what shall that be, and where does it originate from ?
Do you have any hint about this ?
many greetings !0 -
hint : wcs 2 ucs
;-)0 -
forgot the attachment0
-
But "w2u" looks like client code, isn't it ?
If so, where is it defined ... ? It needs to be present of course ...
Does your sample mean, that field expression evaluation shall evaluate Lisp expressions ?
greetings !0 -
In the formula field you can use any function available for CAL function.
http://knowledge.autodesk.com/support/autocad-lt/learn-explore/caas/CloudHelp/cloudhelp/2016/ENU/AutoCAD-LT/files/GUID-163FB50A-B9B2-4292-A1BD-0C872CA441D5-htm.html0 -
Dear Dirk,
reviewing the topic here, it seems better you would log the problem as support request;
especially as it is related to interface / API behaviour ...
Just to mention : CAL functionality is not available with BricsCAD ...
many greetings !0
This discussion has been closed.