Line Style Creation Bug

I am working on creating my own Line Styles in OpenBuildings Designer but I seem to have encountered a bug. I want to select a Base Stroke Pattern but it would not let me. How can I fix this issue?

  • Hi Samuel,

    Can you tell us what version of MicroStation you exhibited this issue?   We have a bug reported for this issue.

    Regards,

    Connie Wallace


    This is a test

  • I had the same issue. I believe it may have been U12, but can't say for sure. I believe I posted something about it back then and someone else replied may have been a Bentley rep) and they could not reproduce the issue. I ended up using v8i as a workaround and have not needed to create a line style in CONNECT since then so I don't know if it is still the same with the latest version. I will need to look at that next week.

    Microstation CONNECT - 10.17.2.61

    ORD - 2021 R1 10.10.1.3

    ORD 2022 R1.1 - 10.11.3.2

    ORD 2022 R3 -  10.12.2.4

    Microstation v8i SS 10 - 08.11.09.919

    Power InRoads v8i - 08.11.09.615

    ProjectWise - 10.0.3.453

  • In U16 I am able to see the list of Base Stroke Patterns. I am not using OpemBuildings, but I had this issue in an earlier version of CONNECT. There was also an issue where I would double-click on a component of a compound sub-component (the point sub-component) and it would take me to the stroke sub-component.

    U16 does not seem to have these issues for me.

    Microstation CONNECT - 10.17.2.61

    ORD - 2021 R1 10.10.1.3

    ORD 2022 R1.1 - 10.11.3.2

    ORD 2022 R3 -  10.12.2.4

    Microstation v8i SS 10 - 08.11.09.919

    Power InRoads v8i - 08.11.09.615

    ProjectWise - 10.0.3.453

  • Hi Connie,

    I am using OpenBuildings Designer CONNECT Edition Update 8 Version 10.08.00.44. I was able to create my linestyle but the dialogue box does not look right.

    Thanks,

    Sam

  • Hi Samuel,  I came across with this issue sparsely on earlier CE Update versions, but I was not able to reproduce this consistently as I hoped for.   I have not seen the issue since MSCE Update12.  If it happens again, use the restoredefaults command .Also, please list the steps if you can remember that caused the dialog issue.  I will definitely keep my eyes open for this issue.  Needless to say this, I am still stumped by this weird behavior!  I really wish I could find a reproducible cause for this issue which isn't easy to catch.

    Regards,

    Connie Wallace


    This is a test