[CE U13.1] Generated level numbers not unique?

Hi,

this question is a consequence of thinking about an issue discussed by in this post.

To refresh my knowledge, I read these two wiki articles about level numbers:

Both articles are based on two basic rules: Every level has a number (at least internally) and the number has to be unique in a context of the file.

So I did some tests using example(s) delivered with MicroStation CE U13.1 installation (_USTN_CAPABILITY < +CAPABILITY_LEVELS_USE_AUTO_GENERATED_NUMBERS configuration added to standard.cfg to see the auto-generated numbers) ... and I am confused:

In GrazURL.dgn, an initial state is:

  • Level GrazRoads, used in another model in the same file, has number  *3*
  • Level GrazPoints, used in another model in the same file, has number *6*
  • Level Interior Floors, not used, but available from MetroStation.dgnlib, has number *3*

Situation: There is no conflict in numbers, but it's visible that a threat exists, because GrazRoads and Interior Floors both have auto-generated numbers *3*.

The next step is to place an element to Interior Floors, when the level definition is copied to active design file, which requires to solve the numbering conflict. The result is:

  • Level Interior Floors, has number *3* ... it's correct, accordingly to the wiki articles, levels from dgnlibs keeps their numbers.
  • Level GrazPoints, used in another model in the same file, has number *6* ... the number did not change, fine
  • Level GrazRoads, used in another model in the same file, has number  *6* ... Why is it *6*, when *6* is used already? I have expected it would be renumbered to *7*, because it's the next free number.

I used VBA to check level internal IDs and they are fine, only numbers are in conflict.

Is it bug or I do not understand the mechanism and rules right?

I did not do any test using V8i, so I do not know whether the result is the same or different, my test was more about to understand how MicroStation CE behaves.

With regards,

  Jan