[v8i SS3 vba] Count smart solid/surface?

Unknown said:

If you say so, then that is probably my best shot.

You should not trust me too much, there is always a chance I am (completely) wrong ;-)

Regards,

  Jan

Hah! So True. Fortunately the results matter more than the road in most programming-cases ;)

Knowing that you don't know everything, but still provide a solution (indstead of arrogantly saying "no-way") is pretty much what counts - There are plenty nay-sayers around.

Using the PropertyHandler for 1000's of cells is not noticeable slowing my project. We are talking milliseconds.
(Loading the DGN's and huge DWG's are!)

Hello,

may be I'am wrong, but is this the function you are looking for?

Public Sub SolidCount()

    Dim count As Long
    Dim ee As ElementEnumerator
    Dim oscan As ElementScanCriteria
    
    Set oscan = New ElementScanCriteria
    oscan.ExcludeAllTypes
    oscan.IncludeType msdElementTypeSolid
    
    count = 0
    Set ee = ActiveModelReference.GraphicalElementCache.Scan(oscan)
    Do While ee.MoveNext
        'Debug.Print ee.Current.Type
        count = count + 1
    Loop

    MsgBox CStr(count) & "Solids"

End Sub

Best Regards

Martin

Unknown said:

Lazy Bentley programmers!

The current situation (in V8i) is mostly because of historical reasons as different approaches and modelling tools were implemented.

The completely new technology based internally on dynamic construction of parametric objects (so no more cells and nested nested nested cells with tons of attributes) is a proof Bentley programmers are not lazy ;-)

Unknown said:

as something in the scanning is actually taking ages.

VBA is not good environment for scanning huge datasets, because it requires very intensive memory allocation, which is even worse because of slow VBA API. Maybe your code can be enhanced to be faster, but in generall VBA scanning is always slow.

Regards,

  Jan

Unknown said:

Lazy Bentley programmers!

The current situation (in V8i) is mostly because of historical reasons as different approaches and modelling tools were implemented.

The completely new technology based internally on dynamic construction of parametric objects (so no more cells and nested nested nested cells with tons of attributes) is a proof Bentley programmers are not lazy ;-)

Unknown said:

as something in the scanning is actually taking ages.

VBA is not good environment for scanning huge datasets, because it requires very intensive memory allocation, which is even worse because of slow VBA API. Maybe your code can be enhanced to be faster, but in generall VBA scanning is always slow.

Regards,

  Jan

I take your word on that whole programmers not being lazy thing.. From a personal point of view, I code because I am lazy! I am probably the most lazy person I know - which has led to automations saving thousands of hours for my coworkers. ;)

Unknown said:

VBA is not good environment for scanning huge datasets, because it requires very intensive memory allocation...

True that. On a side note, and something that might pop up in another thread sometime: It seems the culprit is getting details from levels, but even that is to be honest fairly fast. About the whole "time" issue: My coworkers asked how long it would take to re-analyze all our files, and I replied "ages"... They looked scared.. .. "something like 20 minutes", and they literally laughed in relief! :D Time is indeed relative ;) The manual process would take weeks if not more and be very prone to human errors. Heh! :)