[V8i 09.536] feedback of the Element Information

Hi Anthony, I can't reproduce that on 08.11.09.459 (latest commercially released version) and later test builds, I can change sub-elements attributes without problems (I tried colour, level, line weight, etc.). What attributes are you trying to change?

Is this occurring in all your DGN files? Have you got any layered application on top of MicroStation?

Can you try using the old element info dialog (key-in: analyze element)?

In addition to Marco's comments please confirm this is a cell and not shared cell ( See Element Information dialog under the heading General > Description ).

In addition also check that its not locked ( See Element Information dialog under the heading Extended > Locked.

If the suggestions dont help then may be you could post a small sample for review.

Anthony, please try again, the "Send Private Message" option should be on the green banner (just checked) on my profile page. Unfortunately we still need some user information, especially for bug tracking.

mwlong, you may want to PM Marco Salino for reporting problems too....i think.

I was just testing to see if I had the same result. I do not use the element info dialog very much. I like when others test and verify problems that I am experiencing.

Unknown said:

...I do not use the element info dialog very much...

I don't have a good answer for why I don't use the new Element Info. I do like all of the information it contains but I have found some quirks when working with cells. I can't really comment about those issues right now because I have been ignoring it. I find the old Element Info dialog easier in those situations and that's just what I am accustom to. I like to use the new element info to make a selection set of text and change the rotation of the text to a sheet in 1 shot. The one thing I do not like with the new element info is it is difficult to do such a task if there are elements within the selection set (such as text nodes) that the selected operation is not able to be applied to that type of element. The rotation value is greyed out and I can not apply the setting. Then you need to go back to the selection set and scroll through the list and deselect those elements.

I guess the best answer I can give is that I have not incorporated that dialog into my workflow & quite honestly the types of tasks that I do use it for are few and far between. I have the dialog pinned for easy access but the old adage "out of site, out of mind" applies. It is impossible to leave the dialog open because, as all drafters know, screen real estate is precious.

I basically jumped into this thread because I though I found the process in question was working a little differently for me. Upon further testing I was just confirming the issue.

I don't have a good answer for why I don't use the new Element Info. I do like all of the information it contains but I have found some quirks when working with cells. I can't really comment about those issues right now because I have been ignoring it. I find the old Element Info dialog easier in those situations and that's just what I am accustom to. I like to use the new element info to make a selection set of text and change the rotation of the text to a sheet in 1 shot. The one thing I do not like with the new element info is it is difficult to do such a task if there are elements within the selection set (such as text nodes) that the selected operation is not able to be applied to that type of element. The rotation value is greyed out and I can not apply the setting. Then you need to go back to the selection set and scroll through the list and deselect those elements.

I guess the best answer I can give is that I have not incorporated that dialog into my workflow & quite honestly the types of tasks that I do use it for are few and far between. I have the dialog pinned for easy access but the old adage "out of site, out of mind" applies. It is impossible to leave the dialog open because, as all drafters know, screen real estate is precious.

I basically jumped into this thread because I though I found the process in question was working a little differently for me. Upon further testing I was just confirming the issue.