[CONNECT C++] TextField in Cell not Updating

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.

Text Fields in Text Node are OK

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.

Text Fields in Cell don't all Update

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!

  • Am I attempting the impossible by placing text fields in a cell? 
  • Have I created the text fields in the cell correctly?
  • Should those text fields that reflect element properties all update themselves when the host shape is modified?

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.

Parents Reply
  • 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.

    Ian

    Ian

    currently using OBD 10.10.01.151

Children
No Data