AreaAnnotator9.dgn
The attached DGN file has a single model. The model contains four shape elements. Each shape is annotated using text fields. Some text fields show Item Type property values; others show element properties such as area and perimeter.
The two green shapes are annotated each with a text node that contains several text fields including area, alternative area and perimeter. If you use MicroStation's modify element tool to change a green shape element you can see that all the element property text fields update themselves to show the shape's new metrics. That's the behaviour I expect.
The two brown shapes are annotated each with a cell that contains plain text elements and also several text fields including area and perimeter. If you use MicroStation's modify element tool to change a brown shape element you can see that the element property text fields do not all update themselves to show the shape's new metrics. That's not the behaviour I expect. I'm puzzled!
Note: This problem seems to be a bug in MicroStation CONNECT, as mentioned by Paul Connelly below. If I open the same DGN file with MicroStation V8i, the text fields in the cell update as expected.
Hi Jon
Had a play with this over lunch
In addition to your observations which I can replicate if you drop the complex status of your cell the values which are incorrect remain at their incorrect value until you modify the shape and then all the values are corrected.
HTH
Ian
currently using OBD 10.10.01.151
Ian Leighton said:I can replicate if you drop the complex status of your cell the values which are incorrect remain at their incorrect value until you modify the shape and then all the values are corrected
Thanks for testing, and your observation about dropping the cell!
Regards, Jon Summers LA Solutions
This looks like a bug specific to MicroStation CONNECT Edition.
Paul Connelly said:This looks like a bug specific to MicroStation CONNECT Edition
You're right! I opened that file with MicroStation V8i and modified one of the brown shapes. The text fields in the cell all updated correctly.
If it's a bug, should I file a defect? Or, is that a known problem?
Is there a workaround using the MicroStationAPI?
Hi Jon Summers,
I have asked Artur Goldsweer to review this and if/once reproducible to file a defect to be corrected in a future product release.Thank you,Bob