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
Hi Jon,
I have tried to reproduce this, but it seems this works correct for me.Resizing any of the 4 shapes also updates the text fields.
Just to be exact, I was resizing the single shape elements (2 green and 2 brown), not the 2 brown shapes which are components of the cells.I was using Update 11 (10.11.00.36), did you test with the same build?
Best regards,
Artur
Just to help with this
I tested this yesterday using ABD U3 and again tested just now
From Jon's dgn file the room 101 and room 102 shapes when modified updates the area (m2) perimeter (m) and area (yd2) correctly
the room 103 shape when modified updates the area (m2) but most of the time does not update the alt area and perimeter values so you get incorrect alt area and perimeter values for the modified shape. If you modify it again you sometimes get the three readings to be all corrected and sometimes not.
I then modified the room 104 shape and again the area value being reported was correct but the perimeter was incorrect. I subsequently dropped the cell Jon had created and then modified the shape on room 104 and the incorrect values did not correct themselves, but as soon as I modified the shape the value of the area and perimeter corrected themselves to the correct values for the modified shape.
Artur Goldsweer said:it seems this works correct for me
But Paul Connelly acknowledges this to be a bug!
With CONNECT Update 11 only some of the element property text fields in the cell update when their host shape (the brown shape element) is modified. You may observe one or two fields change, but not all the fields.
With V8i all fields in that same DGN model update correctly.
Ian Leighton said:the room 103 shape when modified updates the area (m2) but most of the time does not update the alt area and perimeter values so you get incorrect alt area and perimeter values for the modified shape
Well observed! That's more or less what I see.