Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
Hi,
Unknown said:With VBA in debug then no problem but with Addin then Value: COM Object ?
Despite of VBA and NET uses the same API, they are different in some aspects, especially if talking about Debug information. They are runtime information, so to interpret them correctly sometimes require good knowledge how API works, which in the case of COM is not always easy. And it can also easily leads to wrong picture how to use API, because object model published in API is not equal to Debug information.
Unknown said:I wan't see value level.number of element
There is no direct access from an element to level number, because the number is not the element property. It's something like:
Written in one line it would be something like
num = Element.Level.Number
With regards,
Jan
because there is no any further information or question, the code only, I am not sure how to answer. So just a few comments:
My question is why do you want to use level numbers? It's not ensured such number exist as can be easily tested in Level Manager. MicroStation uses internally system generated numbers, but they are not displayed by default. So MicroStation help file for details. But imporant thing is thay you should never (from MicroStation 8.0) work with level numbers, but always with level names or in the code with level definition objects.