I've discovered a bug related to corridor secondary alignments in Microstation.
The workflow:
- Create a corridor with a template
- Open the corridor objects dialog
- Select a line element as a secondary alignment
- Create a key station along the secondary alignment
- Close the corridor objects dialog
- Open the corridor objects dialog again.
On the second opening, the following dialog appears:
I created the corridor with a template that uses a horizontal feature constraint to track an element with an edge-of-pavement feature definition. The same element with this feature definition is also used as a secondary alignment in part of the corridor. I suspect that may be part of the problem, but can't confirm it. Deleting the XML file allows me access to the corridor objects file again. I suspect that adding key stationing in a region where there's a secondary alignment is the cause, as I won't see the error again unless I'm doing that.
Nevertheless, while the bug has consistently recurred, and is certainly related to the existence of the XML file, there have been occasions following this workflow where it has not occurred as well. First guess is that it's a creation-only effect - it doesn't show up unless it's the first time I create key stations that cross a secondary alignment.
XML file (Please visit the site to view this file)
Error log
(Please visit the site to view this file)